- The Bug has been found and logged into the Bug Tracking System. It will be treated as New Bug in the System.
- The Bug will be assigned to the concerned Developer for a Resolution.
- The developer looks in to the possibilities of the resoultion & takes a call on Resolution by fixing it or differing over the information provided.
- Tester validates the resolved issue in the build & checks for the regression scenarios over the fix.
- If the issue found fixed, then he choose to Close the issue else he / she will Re-open the same.
- The Cycle follows again for the re-opened issue till it get’s closed.
It worth doing the following activities
- Capturing the required and re-usable info to the Bug Report at it’s each stage.
- Check for all the closed bugs of Severity 1 & 2 against final build for the release.
In the next post, I will share my thoughts on the useful metrics over the Bug Tracking Repository.
Happy Testing..