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.
I saw a job posting that was looking for a QA-Ninja and it made me think about how sometimes development managers don’t understand how we testers see our jobs, and maybe most importantly what we really contribute to the development team and process. This post is about these points and about how we can start modifying this erroneous understanding even before we choose to take such a job.
- 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
- 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
- Of Testers & Soldiers… January 21, 2013
- Five Testing Questions with James Bach December 17, 2012
- Dan: Nice post! Did you realize your Practitest graphi...
- ICU Staff For Hospital In Pune: Thanks For sharing this with Us. Good Questions an...
- Thanh: Thanks Joel. Your example is excellent to help me ...
- joelmonte: Hi Thanh, I think that the answer to this questio...
- Thanh: Thanks Joel for this article. Another different vi...