|
|
 |
 |
 |
 |
Activity:
Validate a Release
 |
|
Participating Roles
Responsible:
Release Manager
Consult:
Tester |
A build is ready to be validated for release when functionality, time, and quality objectives defined in the vision statement and test approach are met. Alpha and beta releases also constitute releases. The build must pass a final set of regression tests and subsequent triage to become a release. When regression tests are complete, a decision is made whether to fix bugs or designate the build as the release candidate.
Entry Criteria
Dependencies:
- The release candidate build meets time or functionality objectives established in the vision statement.
- The release candidate build meets quality objectives from the test approach.
Sub-Activities
|
|
1 |
Create a Release Branch |
- Create a new branch for the release candidate. This isolates the code so that only selected fixes may be applied.
|
|
2 |
Run Regression Test |
- Run a full regression test on the release candidate.
|
|
3 |
Open a Bug |
- A test failure results in a new bug report. Assess the impact and reproduce each bug.
- Check for duplicate bugs. Attach bugs identified to the test task that generated the bugs.
- Attach the test case, test results, test configuration, and scenario or quality of service requirement to the bug report.
|
Exit Criteria
 |
No regression test is blocked. | |
 |
 |
 |
 |
© 2005, 2006 Microsoft Corporation. All rights reserved.
Version 4.0.1 |
 |
Overview 