|
|
 |
 |
 |
 |
Activity:
Verify a Build
 |
|
Participating Roles
Responsible:
Developer |
It is important to maintain the quality of the application as each build is created and accepted. Run verification tests to make sure the basic build functionality is intact. Verification tests are also run to make sure functionality changed as part of bug fixing or that new feature implementation works correctly.
Entry Criteria
Dependencies:
- The build process has completed.
Sub-Activities
|
|
1 |
Verify Basic Functionality |
- Run a minimal subset of validation tests, such as build verification tests, also known as smoke tests, to determine if the basic functionality of the build is stable.
|
|
2 |
Verify Changed Functionality |
- Run additional validation tests to make sure all changesets expected in the build were added and work properly.
|
|
3 |
Notify Team of Build Acceptance |
- If the build passes all required validation tests, inform the users and release organization that the build is accepted.
- If the build does not pass, inform the development team of the problem(s) and log them in the bug tracking system.
|
Exit Criteria
 |
If the build passes all required validation tests, the team is informed of build acceptance. |
|
If tests fail and the build is not accepted, the development team is informed of the problem and all problems are logged as bugs. | |
 |
 |
 |
 |
© 2006 Microsoft Corporation. All rights reserved.
Version 4.1.0 |
 |
Overview 