If you want your testers and your team to be GREAT you need to be ready to schedule tasks to “Waste Time” experimenting and looking at technologies and methodologies as part of their regular work. It is very easy to say that you don’t have time or that your schedule is too tight for this, but in the end these are the things that will make your team exceed in their work.
In many ways the objective of the QA Tester and of the Intelligence Officer are very similar. Each of us in his or her own contexts, are tasked with providing information that will help our superiors and the rest of the team/unit to do their work better and to make the correct decisions. Following a remark by Jerry Weinberg to one of my previous blogs, In this post I examine this topic and explain how today’s QA Engineers have some of the same challenges as Military Intelligence officers.
James Bach is one of the most influencing testers I know, he is one of the fathers of Exploratory Testing and the Context Driven Testing School. I asked James if he would be willing to answer my 5 testing questions and happily enough he agreed, so here you have Five Testing Questions with Mr. James Bach.
There are questions that I am constantly asking myself regarding testing and QA. If you’ve read some of my previous posts you will certainly be no stranger to these questions or to my point of view on them. Some time ago I thought that it would be interesting to ask other testers what they thought about these questions. And then I thought that it would be even better if I could ask Mr. Jerry Wienberg. The amazing fact is that when I asked Jerry if he would be willing to answer my questions he answered that he’d be happy to.
One of the things that differentiates between a professional and a non-professional is the way in which the first makes the things she does seem elegant and easy to do. Testing can also be made easy and elegant, but for a number of reasons some testers make a conscious effort to make their work seem complicated, harming the testing community along the way…
Following up on a comment left on a previous blog post, I wanted to explain why should testers provide their feedback regarding the priority (and not only the severity!) of bugs. The post also explains what are the ways of making sure this opinion is heard by the whole team.
- 10 reasons why You are NOT a Professional Tester! — Part 2 December 5, 2011
- Why can’t developers be good testers? May 5, 2010
- Stop being a NON-Technical Tester! December 19, 2011
- 10 reasons why You are NOT a Professional Tester! — Part 1 November 28, 2011
- Manual and automated tests together are challenging May 16, 2011
- Is friendship ruining your testing career??? June 17, 2013
- You need to schedule tasks to “waste time” as part of your regular work! June 9, 2013
- Five Testing Questions with Scott Barber April 18, 2013
- Spring cleaning your testware March 25, 2013
- Five Testing Questions with Lisa Crispin February 5, 2013
- joelmonte: Hey Kobi, You are absolutely right, I am not sur...
- Kobi Halperin: Hey Joel, Thanks for another great post, This mi...
- Guest Post: 3 Reasons Why You’re Not Advancing in Your Testing Career | Software Testing Blog: [...] a QA Blog post I published in the past calle...
- Guest Post: 3 Reasons Why You’re Not Advancing in Your Testing Career | Software Testing Blog: [...] blame them either, since these skills are in...
- Query on Test Case Designing: [...] sets. I wrote about some of my rules of thum...