Well, I did want to mean "Disastrous Testing" when I wrote "Testing like Osama", sorry if you could not grasp it. Its perhaps been the longest time interval between two posts ( just 10 days though ) because of me doing some interesting testing stuff @ work.
In this post, I would want to share one of the shocking experience I have had while observing a Tester at work
_ Testing like Osama _
It was hard to digest lot of work, sometime back in one of the companies I have worked for. I thought of easing myself sitting with my colleagues to observe the way they work. Seriously, I did want to learn something from them and I did, but ...
Mr A was a Test Tool Developer/Tester and I sat beside him for a while to observe his way/style of work. ( of course, after seeking his permission )
He kept on executing the cases as a focused tester . It was time I had seen enough of his style and was about to leave..... something caught my attention and I still cant digest the shock I had that day.
He was testing a mobile phone's multimedia feature and one such feature is to download an mp3 song from the server and play it on the phone.
What he did ?
He did not know the settings to be made on the mobile phone in order to connect to the server and hence downloaded a song from his PC via USB and was playing the mp3 file in order to execute that case.
My surprise did not stop there ...
He played the entire song and by all manual mistakes he marked the next case in the list as Pass.
Wow ! He read a case, executed someother case and declared a "Pass" for some other case.
This is a classic example of destroying the quality of the product and I am sure I can never come across such a worst scenario of Testing and probably missing out 3 bugs at a time for every test case executed.
When I tried to make him realize his mistake by letting him know what he had done ... he said .. "Dude, relax, go back to your place" ... "This test case execution has come to me because you and the other guy were unable to complete the test cases in the given time".
What I learnt seeing that ?
- If you do not know how to test a case, do not find a work around for that.
- If you do not have the energy to test something, at least at that point of time, take a break and ensure you come back only when you can deliver better quality of work.
- If you are unable to execute all the cases in the given time, do not manipulate test reports/data.
- It could be possible that your manager is disappointed that you did not execute some cases because you ran out of time but ensure every test case you have tested does ensure the product's quality.
- Managers do not look at people who have taken strain to execute each test case with care and keep appreciating the ones who completed the test cases on time, without knowing they have done some wonders like Mr A.
- Test cases executed by one should and must be verified by someone else too before making a major release to a client/customer.
- Putting pressure on Testers, without motivating them will result in missing 3 bugs for every test case executed.
- Mistakes can happen, it is better to select cases randomly and re-execute it before we give our individual test reports.
- Managers, do not estimate the time that needs to be go in to test and produce a quality
I recently heard a shocking news from the same person when he called me up and told "Hey dude, I have been promoted"...
"Shit, for what ?" ... I was so disappointed by that news that I cried. There were other testers in my team who were worth a promotion. What's going wrong in this industry ? Why is all this happening ? Will things change or should we too change the way the industry likes us to be ?
I am clear that the day I am in a position to command, I shall spend time with Testers ... motivating them , making them realize the importance of a test case and would hire 2 extra testers at the cost of my salary to ensure Testers get time to meet quality standards.
Sorry if I have got emotional, as a passionate Tester, I am unable to bear the pain after seeing people not passionate about testing and yet continuing with testing.
__End of _ Testing like Osama __
Trust me, I feel Osama bin Laden has some good testing skills. When he did architect the attack on WTC .. he took into account the fuel on the plane and the heat needed to bring down the building by melting the TOR steel. He is a Civil Engineer.. hope you know that ?
"Firing such testers is a golden contribution to Testing community"Regards,
Disclaimer : This post is to let out my personal fury against the incident I witnessed, since I feel I am passionate about testing and I respect Testing.There is no confidential info I have let out here and I am not holding any company/organization responsible for anything that has happened. I should also thank that incident, since after that I am taking utmost care to ensure I have executed the right case and I am marking the result against the same. To learn testing books are not the only source, roam around the world.. when you return home you would be a better tester. I wish someday I write "Mr A has realized his mistake and today is a competent passionate tester".