What are the benefits of retesting closed defects that are found during functional testing in the regression test phase?
Requires Free Membership to View
When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.
Hannah Smalltree, Editorial Director
Areas of code that need multiple fixes tend to be fragile. The value in retesting closed defects is that you are watching the code and application carefully to make sure an issue doesn't resurface, which is what regression testing is all about. There are instances where retesting all closed bugs becomes impractical.
What I've been doing on recent project work is not retesting the specific defect that was closed but opting to execute an exploratory test charter on and around that feature or functionality that had recent bug fixes. The point is twofold: first, to ensure that issues resolved haven't reopened, and the second is to provide a sanity check that the core functionality is working as expected.
I've been gaining more confidence in that approach, and when I think about why this may be more effective, it ties back to my first statement which is that areas of code that have needed multiple fixes are more fragile. With that potential in mind, a good test session in the area gives me more confidence than a one-off retest of a particular bug. I also think at some point, you have to consider the case closed -- meaning you have to begin looking elsewhere for bugs because by over-focusing in one area of an application, you could be missing defects in other areas of the application. I often remind myself to "keep hunting."
|
 |
I've been gaining more confidence in that approach, and when I think about why this may be more effective, it ties back to my first statement which is that areas of code that have needed multiple fixes are more fragile. With that potential in mind, a good test session in the area gives me more confidence than a one-off retest of a particular bug. I also think at some point, you have to consider the case closed -- meaning you have to begin looking elsewhere for bugs because by over-focusing in one area of an application, you could be missing defects in other areas of the application. I often remind myself to "keep hunting."
This was first published in November 2008