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

Project Portal
| See Also Walkthrough: Viewing Team Build Report Results |
| ### Next Steps Fix a Build Accept a Build |
| Verify a Build ( 3 : PI : 3 : 3.3 ) Build Engineer
Activity: Verify a Build
Build Engineer
|  |  |  | Stabilize |  |
|  | Participating Roles Responsible: Build Engineer
### Overview 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 ensure functionality changed as a result of bug fixing, or new features, work as expected. # Entry Criteria Build Report Build report containing details on build; for example, time stamps and errors. When: Upon build completion or failure. # 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 as expected.
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 as bug work items.
# Exit Criteria
| Bugs are created for any problems discovered in the build.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |