I was always wondering how any one can mess all the automation code? Or how anyone can pass the testcase without doing any testing? And even that product get release in market too? All the time I can hear these kind of stories around me. I was from some other background and switched to testing almost 2 years back. Finally one day I got this "Brahm Gyan" when one issue hits me very badly.
"If you have done some mistake, don't try to fix it in future" this is what I learnt from my work experience as a Test Engineer. I have some genuine points for this. For example, suppose you missed some functional testing in very early days and you got that bug after few months. Mean while two-three RC/RTM cycles completed and since you missed that functional part in starting, so you thought like it is a part of this product itself(Even functional documents are also not available to verify them). And when you will be very much familiar with the product you find that issue as a bug. You raised that issue in-front of management, and that's it. All fingers will start pointing you, as you did a crime.
Yes! You are accepting that it was your fault. You are sorry about that. You want to get them fix ASAP. But the management is not looking for that, they are just wasting their time to pointing you. In-fact they got one "Bali ka bakra(scapegoat)". Even if any manager tell that this issue is existing from a long time, why you didn't logged a bug, it will be always your problem only. Not that manager's fault.
Moral : If you missed something while doing testing, never ever try to get them fix. Let it be like that if it is not affecting the product directly. After few years when you will quit the job then it will the problem for that new guy who will replace you.
This may applicable on the developer too.
Note : I know that I am ethically wrong, but that's what I learnt from this episode.
No comments:
Post a Comment