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

Project Portal
| ### Next Steps Close the Bug |
| Activity: Verify a Fix
Tester
|  |  |  | Close a Bug |  |
|  | Participating Roles Responsible: Tester
### Overview Verifying a fix checks that the bug has been fixed correctly and does not break any existing functionality. After a bug has been fixed by a developer, it is up to the tester to verify that the test case now runs successfully. If the test case runs successfully, the bug can be closed. Otherwise, the bug is reassigned back to the developer. # Entry Criteria The build that fixes the bug is identified. The fixed, expected behavior is known. The test cases that exercise functionality related to the bug are identified. # Sub-Activities
1 | Attempt to Reproduce the Bug | Follow the steps as originally reported in the bug description to attempt to reproduce the bug.
2 | Look for Unexpected Behavior | Exercise adjacent functionality and attempt to find unexpected behavior around the bug. This is especially important if the development task was not implemented completely.
3 | Get More Information about the Bug | Optional If the bug description is unclear or missing information, inquire with the developer or submitter for more information.
4 | Reassign the Bug | If the test case does not run successfully, the bug is reassigned back to the developer.
# Exit Criteria
| The bug is reassigned or closed with an updated description in the bug tracking system.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |