This is one of the conversation which i heard.
"why do you opt testing domain?, People wont get recognized in this testing field. He/She gave me an instance as follows: suppose a module has to be designed for a particular client, then if the module is designed well, then that person who designed the module will be getting credits not the tester. So recognition is more in Development than in Testing".
My view is, Module will be designed well only when testers test all the paths of the module and helps developers in correcting broken paths. once all the incidents are fixed and module is say 80% to 90 % stable, then it is known as well designed module. clients recognizing testers or not, is totally a clients perception, some clients may and some may not.
We have to do the work in such a way that people recognize it.
Don't run behind credits, do the work intelligently, then credit will come to you automatically. Don't do things for credit sake, just do the work efficiently with interest. Exhibit your best.
Subscribe to:
Post Comments (Atom)
1 comment:
@Deepthi,
Would that developer take the credits when someone breaks the application and billions of dollars go waste? Do they take those credits / blame? No, they point their finger towards tester. So you see the credibility here of a tester in making the product break-proof :)
I hope you would answer that person who said this to you talking about credits. How many times have we not listened to customers saying,
"This product has been tested better".
"There are no major bugs in this product".
"The product is so user-friendly".
"Cool product which has cool features that work in a robust way".
So here you are receiving the credits but it's just that you are not aware of it.
Thanks,
Santhosh Shivanand Tuppad
Post a Comment