To Fix or Not to Fix? That Is the Question

by Nataliia Vasylyna | August 4, 2016 5:56 am

For a novice software tester, the most important thing is to present his/her professionalism and knowledge by finding a lot of bugs during functional testing, regression testing, load testing[1], unit testing, security testing[2], etc.

With time, a tester starts to notice that far from every found bug ever gets fixed. In a software testing company, it is impossible to fix all defects before the product release. If a tester doubts that a found bug will be fixed, he/she should explain the necessity of its fixing right in a bug report.

What Else Should Be in a Bug Report to Help a Bug Get Fixed?

It is also a great idea to explain possible negative consequences of not fixing a bug. The problem here is that a software testing[3] specialist is often not competent enough to grasp all the consequences. This is where a business analyst should come into play. Another option is to show a bug directly to a client and get to know his/her opinion. After all, the client’s wishes always come first.

If a tester is still not certain whether a bug will be fixed, he/she can describe a practical scenario in which the importance of fixing this bug will be distinctly demonstrated.

Learn more from QATestLab

Related Posts:

Endnotes:
  1. load testing: https://qatestlab.com/services/Withstand-the-Load/Load-Testing/
  2. security testing: https://qatestlab.com/services/Is-Your-Software-Secure/security-testing/
  3. software testing: https://qatestlab.com/services/We-Are-Professionals-in/software-product-testing/
  4. Assessing Bug Priority and Severity: https://blog.qatestlab.com/2011/07/03/assessing-bug-priority-and-severity/
  5. How One Bug Can Wreck Your Reputation — And How QA Prevents It: https://blog.qatestlab.com/2025/04/01/how-one-bug-can-wreck-your-reputation-and-how-qa-prevents-it/
  6. The Secret of NFT Games Popularity: Features and Benefits: https://blog.qatestlab.com/2022/07/13/nft-games-features-benefits/

Source URL: https://blog.qatestlab.com/2016/08/04/fix-bug-question/