defects
 |
Stop Releasing Untested Defect Fixes into Production Releasing untested defect fixes into production is a real possibility. Being aware of how this can occur may help reduce the possibility of it happening. Let’s explore the common reasons defect fixes go untested—insufficient testing or resources, and undocumented fixes—as well as the steps we can take to prevent them. |
|
 |
Defect Reporting: The Next Steps When a software defect is identified, best practices usually only pertain to the initial writing of the defect, not the tasks required to close it. Many factors can influence the tester's work. The solution is to add a “Next Steps” section that identifies the work remaining and the person responsible for completing it. |
|
 |
Get Your Defect-Tracking Database Back on Track When defects are ignored or mismanaged, it can compromise the integrity of the defect-tracking database. When this happens, defects could go unfixed, or code fixes may not be verified by the production release. Before you can resolve a compromised defect-tracking database, you need to know how to recognize one. |
