This week, we dig in to the topic of how to be a better tester. First, it’s about improving relationships and knowing the value that you bring to the organization. Then, it’s understanding the type of tester you are and where your strengths are. Third, where can you add the most value? Should you focus on the most likely scenarios or elsewhere? Finally, the ever-present question about how much programming should you be able to do? All this and more in this week’s Neotys Testing Roundup, so read on!
A Dilbert comic is always a great way to start a tech blog, right? We’d say it’s worth checking out the post just for that. But then why not keep reading, because the author does some great dispelling of myths such as, “anyone can do testing,” “testing is boring,” and many more. Read the article to find out how to prove your worth and have a better relationship with the business and with development.
According to author James Bach, there isn’t just one type of tester…in fact, it’s not even just five types. Rather, there are seven distinct types of testers out in the world each with an interesting pattern of skills and temperament. Therefore, it’s impossible to grade testers against one simple template. What type are you? Read on to find out!
To begin this article, Eric Jacobson posits something that some may find obvious: if you make two lists for a software feature, the list of plausible user scenarios and the list of implausible user scenarios, the second one will probably be much longer. Why does this matter? Well, he goes on to say that as time gets more valuable and limited, we should spend our time testing the plausible scenarios. If a bug is a problem that effects someone who matters, then we should probably focus on the most likely user scenarios. Read on for more details and a great chart Jacobson uses to illustrate the point.
To develop or not to develop, that is the question. Or at least it’s the question for blogger Jeff Nyman. He goes on to say that if we expect developers to learn from testers, then we need some more focus on returning that favor as well. As he learned more about programming and developing, he found that it helped his own testing. Now, what do you think? Read the rest of the article for a very well thought out argument in favor of learning more programming, then respond in the comments on our blog.