Bloggo back to the blog
Blog Spy Vol 24: A Weekly Round-up From The Software Testing Blogosphere-->
A round up of some of the latest blog posts from the Software Testing Industry in the past week. If you would like to have your blog featured in our regular round-up, please email details and a link to the post to [email protected] or tweet us @esconfs.
Conference at a Glance, part II – My glance on the Tuesday AM tutorials – Pekka Marjamaki
“This is the second part of my series of posts about EuroSTAR 2013 conference. I apply the same method of evaluating as I did previously, so read the “My glance on the Monday tutorials” before this post, if you haven’t done that already.” Pekka discusses his thoughts on some of the Tuesday Morning tutorials at this year’s EuroSTAR Conference including Ian Rowland’s “Thinking Outside The Locks”, Prof Harry Collins and James Bach’s “Using Sociology To Examine Testing Expertise”, Peter Zimmerer’s “Questioning Testability”, Anne-Marie Charrett’s “Coaching Software Testers”, James Christie’s “Questioning Auditors Questioning Testing”, and Pradeep Soundararajan & Dhanasekar Subramaniam’s “Context Driven Mind Mapping”. Read more here.
Software Life-Cycle Model for Customer-Driven Quality – John Ruberto
“The software life-cycle model for Customer-Driven Quality is somewhat simplified, intended to be replaced by the actual life-cycle model used by your company. The purpose of this definition is not to define a life-cycle, but to describe the customer-driven practices during each phase of your particular life-cycle. These practices work with both Agile and waterfall life-cycles.” Read more here.
How Easy is Good Management? – Johanna Rothman
“Bad management is easy. Well, let me rephrase that. It’s easy to perform management badly. But, it’s not so easy to perform management well. From the outside, it can seem as if management is effortless. But that doesn’t mean that good management is easy.” Read more here.
Cumulative Flow Diagram – Pawel Brodzinski
“One of charts that give you a quick overview of what’s happening in a project or product work is Cumulative Flow Diagram (CFD). On one hand in CFD you can find typical information about status of work: how much work is done, ongoing and in backlog, what is the pace of progress, etc. This is the basic stuff. On the other hand, once you understand the chart, it will help you to spot all sorts of issues that a team may be facing. This is where Cumulative Flow Diagram shows its real value.” Read more here.
Five Presentation Traps To Avoid in Technical Talks – Christian Heilmann
“Speaking on stage and in meetings is all about doing it and repeating it until you are more confident and good at it. Yes, you can rehearse the one talk to rule them all and repeatedly deliver it but I promise it will be much more rewarding to you and your audiences to mix it up and do different things for different audiences.” Read more here.
Manual Testing and Automated Testing – the myths, the misconceptions and the reality… – Dan Ashby
“There are many misconceptions in the software industry regarding both Manual Testing and Automated Testing. Some people believe that Automated Testing is the bee’s knees and exists as a replacement for Manual Testing (which is simply not true). And others believe that Manual Testing is a simple set of step-by-step tasks that anyone can run through to check an expected output, and that it’s dying out (which is also not true).” Read more here.
Successful Software Projects: LeanWings GR Testers Style – Pete Walen
“It is funny. I was asked once “How do you come up with ideas for meeting topics?” One of the ways we find topics is in the course of discussion of another topic. That is where this month’s topic came from. A couple of months ago, in the course of discussing bugs or some such, one of the participants asked a question: What Makes A Software Project Successful? Awesome question. That became the topic for July.” Read more here.
Why Test Engineers Should Learn Ruby – Jeff Nyman
“Test engineers most definitely should have Ruby as part of their tool set. This post is not so much to showcase my clear bias for Ruby when writing test solutions. This post is rather to showcase with some evidence why I have chosen Ruby as my tool of choice. My reason is mainly because you can do so many cool things with Ruby that other languages struggle with, particularly if your emphasis is on creating a DSL.” Read more here.