There is no standard definition of a "good tester" to my knowledge but I am sure there are ways to say if I am doing a good testing. I self certify as a "good tester" and I *think* I am respected because my standards are higher and growing!
Years back, I fell into a lot of testing traps and I fall into fewer testing traps today. The traps that I fall in decides how bad my testing is. It certainly takes time to recover from the traps and hence I lose time which otherwise could have spent adding value to the project.
Customers aren't happy to pay for the time we spend to recover from the traps we fell into. There are times where we ourselves set traps (and jump into it) and there are also times where others or situations sets a trap. Whatever is the source of the trap, we fall into it and the biggest and dangerous of all traps is this: To not realize that we have fallen into a trap or to be reluctant of having fallen in a trap.
Here is an exercise that I worked on, which I think, helps in demonstrating the art of clearing traps in testing. I would call it : 100 questions in 20 minutes - The Art of clearing traps in testing [ PDF file : 104 kilobytes ]
Wishing you a good learning experience!
Do you think I had a specification or requirement document when I took up the exercise?
-- Pradeep Soundararajan - http://testertested.blogspot.com - +91-98451-76817 - pradeep.srajan@gmail.com
"Pradeep's first language is not English--his first language appears to be testing." -- Michael Bolton
10 comments:
Readers of this article might also find this one, from Hung Quoc Nguyen, of interest.
http://www.logigear.com/resources/articles_lg/DAST.pdf
@ Dr Cem Kaner,
Thanks for dropping by again. I had a quick glance at it and I must say that readers might find it wonderful. I am sure it would help readers of this post.
On behalf of my readers, I thank you for the link.
A re-phrase:
I am sure it would help readers of this post.
I am sure it would help readers,irrespective of whether they read my post or not!
Hi Pradeep,
I am deeply involved in your Blog right from morning reading through some of your previous topics right from 2006. I got in to this blog through your community in Orkut and the current blog, the way in which you have thought about testing traffic light control system has inspired me to write my first comment in this blog. I feel its not too late for me to join this blogger, and would share my ideas , learn something new everyday with the help of Tester Tested!
- Jawahar
@Jawahar,
Last week I decided not to blog because *some* testers stole or plagiarized my articles and God made me repent for it. This week HE helped me understand why HE made me repent for it through comment like yours.
I am grateful!
You deserve it Pradeep...
Hi Pradeep
Pretty Neat articles you've got . I just wanted to start a testing blog, but didn't know how(or rather where) to start... You articles have helped my channelize my thoughts on what and how testing articles can be....
Keep up the good work
PV
ur 100 questions in 20 minutes is awesome and no wonder you have been my role model and i am proud of havin a role model like u
dipthi
Pradeep, I am sure that you did not have any specification or requirement document when you took up this exercise. You frame these questions based on whatever experiences you had with traffic lights, right? I believe that a tester can write so many test cases if he relates to his experiences and applies common sense. It will not really take a big time. Instead of peeking here and there, the tester should begin writing test cases and other cases will immediately come into his or her mind.
I believe that you wrote this post to confirm how a little common sense can help you get out of any trap.
Neeraj Jain (N. Jain)
Technical Writer
Neeraj
I believe that you wrote this post to confirm how a little common sense can help you get out of any trap.
and beyond that, questioning!
Post a Comment