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.
Learning from a 5 year old who’s Testing the World
This weekend I caught myself in the car with my oldest son, having one of those incredible conversations one can only have with a kid his age who’s discovering the World and its workings. What I hadn’t realized until now is that he is actually testing HIS world, and using some simple tools we can all re-learn as testers in our daily work…
If there only was a TV series about Software Testers…
Has any of your kids (or nephews) every turned to you and said that “when they grow up they want to be testers?” I guess not…
Would a TV Series about a team of testers solving mysteries help to make our jobs look more interesting to the “non-testers” among us? I’m not sure, but it may be interesting to play with the idea…
Don’t waste time on a Team/Company Quality Agenda!
What is a Quality Agenda, how to create a good one, and maybe most importantly: “should you be wasting time creating and pushing one in your company???” We try to answer these and some additional questions on this QA Intelligence post
Stop being a NON-Technical Tester!
There is an on-going discussion in the World of Testing around whether a tester should be more or less technical in his work… (and this is without even asking if we should call someone technical or not!)
The truth is that I believe testers SHOULD be technical, and that there is a marked added value for a tester that is technical over one that is not.
This doesn’t mean we should be only technical and stop concentrating on understanding our users, or that we should strive to be more technical than our programming peers. But there are many ways in which we should start getting rid Non-Technical tester each of us carries inside of us.
10 reasons why You are NOT a Professional Tester! — Part 2
This is part 2 of the article I published last week with the 10 Reasons why You are NOT a Professional Testers. As I started on the first part of this series, I think the bulk of the blame is on us, the testers, for not looking at our jobs as a profession.
Without going into the specific reasons, for that you can read inside, I think we need to improve the way we look at our tasks, how we communicate with our teammates, and how we look at the future of our profession.
I am looking for your feedback, so please feel free to let me know what you think!
- 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
- Please, stop calling us QA ninjas! May 11, 2012
- Learning from a 5 year old who’s Testing the World May 1, 2012
- If there only was a TV series about Software Testers… April 23, 2012
- Don’t waste time on a Team/Company Quality Agenda! February 23, 2012
- Stop being a NON-Technical Tester! December 19, 2011
- Eri: Excellent comment!! This is a very nice QA blog,...
- joelmonte: I remember in the Silicon Valley back in 1999 or 2...
- Fahad Suleman: Applying for a QA job should be based on a challen...
- joelmonte: As a BSG fan I am fully in-favor of making anythin...
- joelmonte: My point exactly, what if it's not "just a name...