Many times we as testers feel that we are harming our friends whenever we report to management that the project is delayed or that a group of programmers are reporting large quantities of bugs. These feelings don’t only harm our professionalism as testers, they also harm the overall performance of the whole team. This post analyses this issue and provides some ideas on how to approach the issue in a better and more productive way for the whole team.
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.
If you would need to choose a motto for the testing profession and all the testers worldwide, regardless of the company or applications they work with, what would it be? For me this motto would be “To Protect and Serve”!
Following up on my last blog about “Stop making testing complicated” I wanted to share 5 simple tips that will help you make your testing simpler and more efficient. These ideas are easy to apply, straightforward and can be used on most testing or development projects.
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...