To Fix or Not to Fix – That Is the Question

To Fix or Not to Fix – That Is the Question

Executing mobile testing, software product testing or desktop application testing, a specialist discovers bugs and system inadequacy.  

The high product quality speaks for the specialist professionalism and his competence. The newcomers in the testing sphere try to detect as many bugs as possible and follow that they all be have been debugged. Regression testing for some is one of the preferable types of checking.

But software testing company knows well that it is impossible to remove absolutely all bugs before the product release. If having conducted functional testing or load checking, a tester doubts whether the detected by him bug will be fixed, then it is better to explain in the bug report the need to remove exactly this error.

What Information Should Be Represented in the Bug Report?

  • The error name and its brief but clear description
  • Bug priority and severity
  • Used tests
  • The system area and build version in which the mistake was discovered
  • Steps to reproduce
  • Additional related information

It will be also appropriate to explain the possible negative consequences in the case if the bug is not fixed. But the problem occurs here – the point is that the software testing specialists do not always possess enough information in order to foresee the consequences.

In this case, the business analytic already gets into a game. Also, one may ask the client’s opinion towards the problem bug. As the client’s desires are always at the first place.

But one should not hound all because of some small and unserious bugs, compose the presentations, and write long speeches about why it is very important to fix a certain error. It is necessary not to waste the time of colleagues and other project members too.

Knowledge Center
Knowledge Center

*- required fields