I recently met so many experienced test engineers and testers, who are not with engineering background but with different streams of science & math in India. To my surprise most of them aren't aware of neither the context driven school of testing nor the heuristic aspects of testing in general.
‘Ah what does that mean?’ I can sense your interrogative look too, continue reading :)
The most “senior test engineers” or “QA professionals”, in whatsoever designation a ‘software tester (a hominid who tests software products) would like him to be identified, have just learnt how to survive in their jobs, by building test metrics, test case designing, test case execution, test automation, bug reports, traceability matrix, test reports, etc; driven fundamentally based on SDLC & STLC, for days, months & years. Though these testers pertain to be successful testers, they lack the essence of sustaining in this craft for longer period. Why is it so?
It is because, they have been practicing testing just because to uphold their jobs particularly in recession times. Although most of these experienced manual and automation testers in India, who claim they acquire 10+ and more years of experience, are into this craft of testing ONLY either by strange coincidence or by choice and NOT by Interest. So fundamentally they are reluctant to share their knowledge, ideas even to their co-tester, despite of generating teamwork cohesion. Typically, this implies a preservation of nothing.
The outcome of this attitude will conduct a tester to think & preach to his co-testers as follows:
- Testing is monotonous
- Testing has lesser scope to learn & earn.
- Testing is not challenging as programming.
- Testing is a dumb activity, if worked in the same domain for 3+ years.
- Testing is theoretical, the one who mug up the definitions can clear interviews easily to get bunch of job offers.
- Testing is a battle field with programmer. Programmer's always battles with the tester, who injects defects on his code, be prepared. *caution to tester, by senior tester.
- Testing is a dependent job, always should depend on the programmer & release engineering team.
- Testing consumes more time, not even 30% of development time is provided for testing. However, they expect 100% test coverage that too in tight deadlines.
- Testing is reiterative activity, feeling exasperated beyond endurance.
- Testing is__________________________________________
You can spend invaluable time in virtually filling you’re preserved pessimistic thoughts in your mind, If you had already been advocating the same to your co-testers, programmers & managers.
When you saw the blank straight line after the words 'Testing is" have you had a question in your mind that 'why it's left blank'? Before reading the next line of sentences?
If so, it's good continue reading... If not practice the art of questioning!
From the blog reader, mind’s- Hey, come-on Shiva Mathivanan, you have been cursing me for so long, you were just highlighting the traditional flaws, misapprehension, ambiguous definitions in testing crafts.
How can you prove that I’m wrong? I bet if you prove it will help me to understand where we mutually stand. And also tell us what is
context driven school of testing, what's
heuristics all about and how is it going to benefit me in this testing craft, how can I be more passionate towards testing?. (Yes, I can hear you)
Shiva Mathivanan - Good question: I can very well prove what you desire. However, I would like you to read what my mentors have already told about testing. Read through my mentor’s views; start contributing to the testing arenas where my mentors participate. I’m sure that your testing genes will regenerate better (like how normal hormonal genes hyper when a hot girl/boy passer-by *wit*) and you will be a self motivated tester soon, someday.
I’m honored to introduce my great testing mentors. I have chosen them as
guru in my testing religion is because I have understood their sensible talks, views, approaches and reliable service to testing community. I always have wondered, how limelight testers & mentors like
James Bach,
Cem Kaner,
Michael Bolton & ,
Jerry Weinberg have never got tired of rendering their service to this software testing community, while most of the Indian testing geeks in various parts of the globe still in obscurity?
To bring the change, I welcome you all to read my mentor’s view:
1.
Dr.Cem Kaner, Software Engineering Professor–
http://kaner.com
2.
James Bach, Principal Staisfice.Inc –
http://www.satisfice.com
3.
Jerry Weinberg, consultant -
http://www.geraldmweinberg.com
4.
Michael Bolton,
http://www.developsense.com
5.
Pradeep Soundararajan, Test consultant -
http://testertested.blogspot.com
My dear blog reader’s you too will be the
Ekalavya of above testing genius, some day if you ensure realization of their context. Get into the habit of writing blogs, Get to know
why good software testers should write blogs by Pradeep Soundararajan. Pradeep is a exceptional Indian, who never set back to consult, coach and serve as prelude to Indian testing community.
The after effects of testers who reads my mentor's blog:
- Exploratory testing is what I have been doing, but never to this extent.
- Rapid software testing is WOW.
- I'm proud to be a sapient tester, rather identified as manual tester.
- To be a tester is a blessing, I enjoy everyday test activities.
- Developer versus Tester a win-win kaizen to build quality into the product.
- I started blogging my test experience, sharing thereby learning more.
- I understood how to question a product in order to evaluate it - James Bach.
- My approach towards testing has refined a lot.
- My confidence boosted, I can be a successful independent test consultant in future.
Who knows some day, someone like me will be highlighting your views to rest of the testing world, like how I showered my tribute. All the best!
Evaluate you're testing experience,
how was testing? by www.vettanna.com
Thank you for spending valuable time!
Shiva Mathivanan
