defect tracking
 |
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. |
|
 |
Don’t Let “Try It Now” Impede Your Test Initiative Sometimes environmentally based issues arise that impede your ability to access or test the software. Rather than addressing the problem methodically, as with defects, testers often attempt to solve it on their own. Here's why entering the problem into the defect-tracking database is a more efficient way to solve 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. |
|
 |
It’s 10 p.m. Do You Know Where Your Defect Fix Is? Have you ever had to ask whether your defect fix was deployed to a particular environment? You shouldn’t need to, because the answer should always be readily available. Having to request information on the status of your defect fix indicates inefficiencies and a lack of maturity within your organization’s process. |
