Why Should Closed Software Bugs Remain in a Bug-Tracking System?

Why Should Closed Software Bugs Remain in a Bug-Tracking System?

Software defects found during mobile application testing, desktop testing or web site testing and reported by means of a defect-tracking instrument should be fixed. An error must remain in the bug tracker even when it is corrected and does not appear during regression testing.

A software testing company does not recommend deleting any entries from a bug-tracking system. It is more preferable to close an error than to delete it from the database.

software testing company

It is Not Wise to Delete any Entry From a Bug Tracker Because:

  1. If all the entries remain in the database one may track any software bug or the history of the testing and the development process in the future, when this information may be very useful.
  2. Deleting of entries breaks the sequence of the entries numbers in the database.
  3. If somebody copied the software bugs database before deleting of entries his copy will not correspond to the original bug-tracking system.

However, not all reported software buds are closed because they have been corrected. There may be other reasons for closure of an error.

A Defect May Be Closed in a Bug Tracker by Reason Of:

  • the defect appeared to be not a software bug;
  • the defect has already been reported;
  • the defect appeared to be a feature of the tested application.

So, any defects, discovered during web site testing, desktop testing or mobile testing should be closed, but never deleted from the bug tracker.

Knowledge Center
Knowledge Center
Subscribe

*- required fields