To say that uTester Ajay Balamurugadas has an impressive software testing resume would be an obvious understatement. Coached by Pradeep Soundararajan, he has been awarded a scholarship from the Software Testing Club; is a proud student of the Miagi-Do School run by Matt Heusser, and co-founded “Weekend Testing.” Oh yeah, and he’s also the latest contributor to our guest blogger series. For more of his work, be sure to check out his blog or follow him on Twitter.
In this post, Ajay takes a stroll down memory lane…
This is an article on my experiences with software testing, the traps I fell into, and the lessons I learned in the process. Before I share my story, let me make one thing clear: I’m no software testing expert. I make mistakes, learn, practice and apply my learning to improve my skills as a tester. To illustrate, I’ve split the journey into five simple stages.
Stage 1: Testing = Find Bugs
I am hired as an Associate QA Engineer at my first job. I was called upon to help remove all bugs in the product before it reached the customer – simple enough. As an obedient student, I did what was expected of me. The execution percentage never reached 100%. I could not complete a cycle of execution in the stipulated time. I did not know that I was checking and not testing. Whenever I tested, I could not achieve 100% execution. Some of the bugs I logged were termed as ‘Deferred – Will not be fixed’. I was bombarded with questions like: “Which user would do that? Good bug, but why did you find it now? Why did you miss it? ”
I did not have an answer for the questions. I myself had more questions than answers.