Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| Activity: Close the Bug
Tester
|  |  |  | Close a Bug |  |  |  | Bug |
|  | Participating Roles Responsible: Tester
### Overview A bug is closed for many reasons. Often bugs are corrected by the developer then marked resolved and finally closed by the project manager. Bugs are closed for various reasons: deferred to another release, deemed invalid, proven not to be reproducible, or confirmed as a duplicate. # Entry Criteria The build with the bug fix is identified. The build exhibits the expected behavior. The test cases that exercise functionality related to the bug pass. Implementation constraints are identified. Duplicate bugs in the bug tracking system are identified. # Sub-Activities
1 | Update Bug to Duplicate | Optional If the bug is a duplicate of an existing bug, update the bug description to reference the existing bug.
2 | Update Bug to Not to be Fixed | Optional If the bug is not to be fixed, update the bug description detailing why. A bug might be reported for a known system constraint or for functionality that is working as designed.
3 | Update Bug to Fixed | Optional If, after performing the steps to reproduce the bug, it can no longer be reproduced, update the bug with this information and mark the bug as closed. Document the build used to verify the fix in the bug description. This assists in fixing future regressions, as well as aid in identifying bugs detected between the time of the fix and the next released build.
# Exit Criteria
| The bug is closed in the bug tracking system with a description of the fixed behavior or an explanation of why the bug was not fixed.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |