 |
Activity:
Verify Fix (CMMI Level 3 : VER 3.1 )
 |
|
Participating Roles
Responsible:
Tester |
When verifying a bug resolution, you may find that the bug was not completely fixed or you may disagree with the resolution. In this case, you discuss the bug with the person who resolved it, come to an agreement, and possibly reactivate the bug. If you do reactivate a bug, make sure you include the reasons for reactivating the bug in the bug description so that information is preserved.
Entry Criteria
When:
Dependencies:
- Bug: A bug has been resolved.
- Build: The bug fix is available in a product build.
Sub-Activities
|
|
1 |
Attempt to Reproduce Bug |
- If the bug work item includes steps for reproducing the bug, follow them. Verify if the bug still exists.
- If the bug results from running a test, run the test. Verify through test results if the bug still exists.
- If the bug resolution indicates the bug will not be fixed, or that the functionality is by design, review the reasons behind this decision.
|
|
2 |
Look for Unexpected Behavior |
- Test product functionality in the same area as the bug fix and try to find unexpected behavior that might show the bug fix was incomplete or affected other components.
|
|
3 |
Reactivate Bug |
- Optional
- If the bug is still reproducible, reactivate the bug work item. Assign it to the appropriate person and set the state to Active.
- If the bug is fixed, but the fix is different than the agreed upon fix in triage, reactivate the bug work item. Assign it to the appropriate person and set the state to Active.
- If the bug was resolved as By design, decide if the reason is acceptable based on the quality of service requirements for the product. If you do not feel the reasons are acceptable, discuss the bug with the person who resolved it and come to an agreement whether to close the bug or reactivate it.
|
Exit Criteria
 |
Bug fix has been verified. |
|
Bug still exists and is reactivated. | |
 |
Program Management
