1 / 7

Why Should Closed Bugs Remain in a Bug Tracker?

http://qatestlab.com/ 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.

qatestlab
Télécharger la présentation

Why Should Closed Bugs Remain in a Bug Tracker?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Why Should Closed Software Bugs Remain in a Bug-Tracking System? Office in Ukraine Phone: +380 (472) 5-61-6-51 E-mail:contact (at) qa-testlab.com Address:154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  2. Why Should Closed Software Bugs Remain in a Bug-Tracking System? Software defects found during mobile application testing, desktop testing or website 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. Office in Ukraine Phone: +380 (472) 5-61-6-51 E-mail:contact (at) qa-testlab.com Address:154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  3. Why Should Closed Software Bugs Remain in a Bug-Tracking System? 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. Office in Ukraine Phone: +380 (472) 5-61-6-51 E-mail:contact (at) qa-testlab.com Address:154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  4. Why Should Closed Software Bugs Remain in a Bug-Tracking System? It is Not Wise to Delete any Entry From a Bug Tracker Because: 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. 1. Deleting of entries breaks the sequence of the entries numbers in the database. 2. If somebody copied the software bugs database before deleting of entries his copy will not correspond to the original bug-tracking system. 3. Office in Ukraine Phone: +380 (472) 5-61-6-51 E-mail:contact (at) qa-testlab.com Address:154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  5. Why Should Closed Software Bugs Remain in a 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. Office in Ukraine Phone: +380 (472) 5-61-6-51 E-mail:contact (at) qa-testlab.com Address:154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  6. Why Should Closed Software Bugs Remain in a Bug-Tracking System? So, any defects, discovered during web site testing, desktop testing or mobile testing should be closed, but never deleted from the bug tracker. Office in Ukraine Phone: +380 (472) 5-61-6-51 E-mail:contact (at) qa-testlab.com Address:154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  7. Thank you! Office in Ukraine Phone: +380 (472) 5-61-6-51 E-mail:contact (at) qa-testlab.com Address:154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

More Related