To Fix or Not to Fix? That Is the Question

To Fix or Not to Fix? That Is the Question
August 04 05:56 2016 Print This Article

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, unit testing, security testing, 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?

  • Bug name, summary and description (brief but exhaustive)
  • Priority and severity
  • Affected test(s)
  • Environment(s) and build(s) where a bug was found
  • Steps to reproduce
  • Due date

It is also a great idea to explain possible negative consequences of not fixing a bug. The problem here is that a software testing 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.

Related Posts:

  Article "tagged" as:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles


write a comment

No Comments Yet!

You can be the one to start a conversation.

Add a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person.
All fields are required.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.