Is Software Testing an Emotional Task?

What do you think after reading the title of the post? How can we include emotions while testing software? What kind of emotions am I going to talk about? How does daily life emotions effect/impact software testing? Please read on…

Software Testing is an unavoidable part of the software development life cycle. Many times I have heard the argument that software testing is not that difficult and anyone can be a software tester. Right and wrong.

Right for them =>  for those who see software testing as just executing documented test cases, it is really easy.

Wrong because => Software testing is not and will never be limited to documented test cases. No matter how many test cases you write for particular application and test them thoroughly for a number of rounds, products never come out bug free. Why are we, software testers, facing humiliation in the conference room when every face looks at us like we are responsible for each and every bug reported by customer? Indirectly, it is true because the bug reached the customer as we did not find/report it.

While testing software, it is expected that you work as an end user. You make mistakes as an end user, you play with product as an end user, and you follow the documentation as an end user. Although initially followed, once we settle down in that comfort zone of testing with limited thinking and vision, most of us forget about the end user. Then the real end user comes into the picture, reports a bug and makes our life like a BUG.


Is Software Testing an Emotional Task?

Software testing task

Today, I am going to correlate some daily life situations/problems with software testing, how they can be prevented, and what kind of contribution a tester can provide. 

Please read and understand the below table row-wise:

Daily situationFeelingCo-relevancePrevention or input as tester
How would you feel when the carry bag carrying groceries will burst out on the way?Oh My God!!! Can't this adjust this much load?This is how the customer feels when the website you tested (although works fine functionality wise) crashes when 100th number of user logged in simultaneously.Most of the time, customers are not sure about requirement OR the requirements keep changing is the truth. But at the same time, as a tester, if we keep an eye on requirement and their reciprocals, and test likewise.
How would you curse that knife which did not cut the fruit when your toddler was crying for it?Want to throw it outThis is how the customer curses the FTP site, you tested, does not transfer data when his customers are waiting for the sameNegative testing and out of box thinking can help in identifying scenarios end user is going to face.
How would you respond when you find that you were late for office because the clock was not working properly?Frustrated. They told this clock is automatic and needs almost nil maintenance, what is this?This is how the customer gets frustrated when he has to call your customer care department for more than 3 times within a week. Either the product was really not tested properly or the customer was not educated properly.Software testing is a package of responsibilities. You just don’t need to test the product, you need to provide review of product, you need to understand customers, you need to figure out in advance - how customer will feel while using this product or while seeing specific behavior?
How would that administrator react when at the end of month the downloaded report from badge system comes out blank due to minor changes he did in system?Lost and does not know what to doThis is how the customer responds when the confidently delivered antivirus did not start working on scheduled time due to time zone issue, and a critical virus was introduced during that duration.Thinking globally and understanding customer stake of product and reflection of same while testing.
How would you control the anger when you get ready for an important function and you find that the tailor forgot to put those show buttons on the dress?Angry and want to slap that tailorThis is how the customer is expected to react when the outsourced testing project marked as "completed successfully" at your end and the customer observes that GUI was not taken into consideration while testing (because it was not mentioned in the document)There are some basic things which are supposed to be checked in each iteration, about which every tester needs to be aware, about which incremental knowledge update is required. Sometimes, artifacts do not mention everything but those missing things are the things to be taken care while testing.
How low your excitement would sit when you reach to the amusement park, you wanted to visit since long and find that it remains close on Monday?Why can't they publish this information?This is how the excited customer feels when he tried to install the software on unsupported windows version, as the user guide did not mention about specific support for windows versions.As a tester, it’s your duty to test documents, especially user guide (no matter, whether it has been included in your task list or not). Suggestions and responses about wrong information in user guide will always welcomed.
How would you approach to a problem as a product owner when you find that the color of product is not right, while the product is ready to deliver?Why so late? Why did not we find out this early?This is how the project manager, management of company, customer (who is waiting for the product) and others react when the bug is identified lately.The tester should report the problem as and when found. If something is questionable then speak, get clarification, and always get latest documents. Always think practically and finally provide your inputs.

Conclusion:

So, this is software testing, discovering hidden scenarios (which most of the time get revealed when end user use the software) and working towards continuous improvement. These are the only factors that can make this community strong.

Shall we start today?

Are you joining?

We are waiting for your suggestions and improvement ideas.

About the Author: Awesome post by Bhumika Mehta. She is a project lead, carrying 7 years of software testing experience. She is totally into testing and loves to test everything that exists.




Recommended reading

36 comments ↓

#1 Hariprasad

the examples are superb. customer’s reaction put in very well words.

#2 sumit khubnani

i m very confused,testing or cdac…..i dnt knw wat to chose….plz help me out..i m 2013 be passed

#3 Tejaswini

Thanks Bhumika for this perfect article and a perfect topic

#4 Gaurav K

One of the best post available on this site, Really nice examples and the relation with Testing. Great work Bhumika :)

regards
gaurav

#5 Ahesanali Vijapura

Really an innovative idea to present software testing with real life situations. Author explained testing Co-relevance and Prevention technique in such a good way with
example of real life situation and feelings which covers almost majority area where QA person needs to take care while doing testing.

I also like Right and Wrong section mentioned above.

Happy writing.

#6 Satish

Definately… Software testing is an emotional task.

#7 Bhumika Mehta

@Hariprasad, @Tejaswini, @Gaurav, @Satish, @Ahesanali,

Thank you for your kind words and encouragement.
Tune in for more posts like this :-)

#8 Baby Nimisha

Good Document…Can you provide information onWhat is meant by “heart beat testing in web applications and how it can be performed using a tool(out of question)..But I couldnt find it anywhere???Please Provide infoon it, I realy need it….

#9 Vijay Kumar Chauhan

@sumit khubnani

Please move to testing , rather than joining CDAC.
Testing is more creative and the work done in CDAC is not really R and D.

Vijay Kumar Chauhan
Project Engineer
CDAC-Noida

#10 Vijay Kumar Chauhan

Nice examples

#11 Ashwini

Nice Article

#12 Hari

@Bhumika Mehta – Nice article.
I have question to ask , i work has a Sw test engineer with 1+ Exp…..My Tl And manager Are giving more preference for Sw Developers but not for test engineers,it makes me to think that i have chosen a wrong career….is this a status in all IT companies ???

#13 Moorthy

Correlating testing with real time scenarios was excellent.

#14 vidya

Vey good comparision….Great work..Keep postingg like this

#15 sree

My question is same to @hari’s question..Am working as a manual tester since 6 months.

#16 Bhumika Mehta

@Hari, @Sree,
No, its not the same situation across the industry. As per me, its more of a personal perspective.
As I have mentioned in this article, software testing is an unavoidable part of SDLC and no one can deny it. To get recognized, you have to be excellent in what you are doing – software testing :-).

#17 Bhumika Mehta

@Murthy, @Vidya,

Thanks for those kind words. I really appreciate your readership.

#18 Vijay Naicker

— Bhumika,

All your articles are really excellent. I have read all of them.
Every time you come up something out of the box and just enlightens the subject in a very sensible way.
Your hard work is really appreciated.
Pls. continue to share your views.

— Vijay

#19 Bhumika Mehta

@Vijay
Thanks for your readership and those kind words.

#20 Nitin D.

Bhumika,

Woderful post as always …thx.

#21 Muzammil

That is superb article ..
Nice work…

#22 Bhumika Mehta

@Nitin, @Muzammil,

Glad to know that you liked the article.
Thanks !!!

#23 Arun

fine.
Good, u just made out what exactly i have faced /facing for the last year. probably u are in same case/expireienced. Nice & interesting Bhumika..

#24 Mriganka Mukherjee

Real time problems put in a very practical way

#25 Baby Nimisha

Some one please explain what is mean by “HEART BEAT TESTING” in web applications and can we test it?

#26 Ajay Sanodaria

Thanks Bhumika for sharing such a useful knowledge. I liked the most “daily life scenarios co-relation between testing” in article.

#27 Ashok Akula

Bhumika …your article was awesome !!!! I am happy that i am on right track ….

#28 Manoranjan Dubey

Quite Good Example…!
The Real life Examples (Corellation with real life itesms and Testing) is Very Important to understand the values of Software Testing.

Thank you So much Bhumika to share this nice articles.

Thanks
Manoranjan Dubey

#29 Kiran Raj

Very good article, awesome examples
Very much informative…

Thanks Bhumika… :)

#30 Bhumika Mehta

@Mriganka , @Ajay, @Ashok, @Manoranjan , @Kiran,

THanks a lot for your readership and please tune in for more of this kind of articles.

#31 Kalyan

@Bhumika Mehta

haha..i got it very easily becuase of the examples…thank you so much..

#32 Inder

Testing is a challenging and intellectual process. It is indispensable for any project. It should be given more importance than ever and more planning must go into it. Testers are respected for the risks they uncover , which ultimately saves money and time.

Great post….thanks!

#33 Bhumika Mehta

@Kalyan, @inder,

Thanks a lot for your readership, we really appreciate.

#34 Amruta

Thanks a lot!!!
Bhumika …your articles are of great help :)

Thanks again:)

#35 ankit

i am a big fan of her..:)

#36 Karthickrajan

Nice article. Facts mentioned is absolutely true. Great and keep posted your thoughts.

All the best :)

Leave a Comment