What are your thoughts after reading the title of this post? How can we incorporate emotions into software testing? What types of emotions will be discussed? How do everyday emotions impact software testing? Keep reading to find out…
Software Testing is an inevitable aspect of the Software Development Lifecycle. Many times I have come across the argument that Software Testing is not that challenging and anyone can work as a Software Tester.
Recommended IPTV Service Providers
- IPTVGREAT – Rating 4.8/5 ( 600+ Reviews )
- IPTVRESALE – Rating 5/5 ( 200+ Reviews )
- IPTVGANG – Rating 4.7/5 ( 1200+ Reviews )
- IPTVUNLOCK – Rating 5/5 ( 65 Reviews )
- IPTVFOLLOW -Rating 5/5 ( 48 Reviews )
- IPTVTOPS – Rating 5/5 ( 43 Reviews )
Yes and No.
Yes, for those who believe that software testing solely involves executing predefined test cases, it is indeed easy.
No, because Software Testing is not and will never be restricted to predefined test cases. No matter how many test cases you create and thoroughly test for a specific application, bugs will always exist.
Why do Software Testers face embarrassment in the conference room when everyone looks at us as if we are responsible for every bug reported by a customer? Indirectly, it is true because the bug reached the customer as we failed to find/report it.
While testing software, it is expected that you act as an end-user. You make mistakes like an end-user, you interact with the product as an end-user, and you follow the documentation as an end-user. However, once we become comfortable with limited thinking and vision, we often forget about the end-user. Then the real end-user encounters an issue, reports a bug, and transforms our lives into a BUG.
Is Software Testing a Sentimental Task?
Today, I will draw connections between daily life situations/problems and Software Testing, discussing how they can be prevented, and the contribution that a tester can make.
Please review the table below row by row:
| Daily situation | Feeling | Relevance | Prevention or input as a tester |
|---|---|---|---|
| How would you feel if the grocery bag burst while carrying it? | Oh My God!!! Can’t it handle this load? | This is how customers feel when the website you tested (although it functions properly) crashes when the 100th user logs in simultaneously. | Customers often have uncertain requirements or the requirements keep changing. However, as a tester, if we pay attention to the requirements and their implications, we can test accordingly. |
| How would you react to a knife that fails to cut the fruit when your toddler desperately wants it? | Want to get rid of it | This is how customers curse the FTP site you tested when it fails to transfer data while their customers are waiting for it | Negative testing and thinking out-of-the-box can help identify scenarios that end-users may encounter. |
| How would you react if you discovered that you were late for work because the clock wasn’t working properly? | Frustrated. They said this clock was automatic and needed minimal maintenance, so what is this? | This is how customers get frustrated when they have to contact your customer care repeatedly within a week. Either the product was not adequately tested or the customer was not properly educated. | Software testing entails various responsibilities. It’s not just about testing the product; it involves providing a comprehensive review, understanding the customers, and anticipating how they will feel using or observing specific behaviors in the product. |
| How would an administrator react when the downloaded report from the badge system turns out to be blank at the end of the month due to minor system changes? | Lost and unsure what to do | This is how customers respond when the antivirus confidently provided fails to start on time due to a time zone issue, allowing a critical virus to infect the system. | Thinking globally and understanding the customer’s stake in the product, as well as considering this perspective during testing. |
| How would you control your anger when you’re getting ready for an important event and discover that the tailor forgot to attach the buttons to your dress? | Angry and tempted to slap the tailor | This is how customers are expected to react when they realize that the outsourced testing project, marked as “successfully completed” on your end, failed to consider the GUI during testing (simply because it was not mentioned in the document) | Certain essential aspects must be checked in each iteration, which every tester should be familiar with. Incremental knowledge updates are necessary to handle missing elements not mentioned in artifacts but are important for testing. |
| How disappointed would you be if you visited an amusement park you had been longing to go to and discovered that it was closed on Mondays? | Why don’t they provide this information? | This is how excited customers feel when they attempt to install software on an unsupported Windows version because the user guide failed to mention specific support for Windows versions. | As a tester, it is your responsibility to review documents, especially the user guide, irrespective of whether it was included in your task list. Providing feedback and highlighting incorrect information in the user guide is always appreciated. |
| How would you handle a situation as a product owner when you discover that the color of the product is incorrect just before delivery? | Why did we find this out so late? Why wasn’t it identified earlier? | This is how the project manager, company management, customers (who are eagerly awaiting the product), and others react when a bug is discovered late in the process. | Testers should report issues as soon as they are identified. If something seems questionable, seek clarification, always have the latest documents, think pragmatically, and provide input accordingly. |
Conclusion
So, this is Software Testing – uncovering hidden scenarios (which often surface when end-users utilize the software) and striving for continuous improvement. These are the elements that strengthen this community.
Shall we begin today? Will you join?
We eagerly await your suggestions and ideas for improvement.