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

Project Portal
| See Also Enterprise-Class Source Control |
| ### Next Steps Verify a Build |
| Integrate Bug Changes ( 3 : PI : 3 : 3.1 ) Developer
Activity: Integrate Bug Changes
Developer
|  |  |  | Build |  |  |  | Stabilize |  |
|  | Participating Roles Responsible: Developer
### Overview All code changes and associated unit tests must be integrated into the main source for the product. The developer must test the code from end-to-end as part of integration. After the code is checked in, the work item associated with the code change is assigned to a tester to begin testing. After the code passes build verification tests, the code is considered successfully integrated. Code is integrated in small sets of changes, each representing a development task or bug, to maintain a level of verifiable stability. # Entry Criteria Local copy of source code is available with reviewed or refactored code. Local copy of source code is available with reviewed or refactored code. New unit tests available for any new code. New unit tests are available for any new code. # Sub-Activities
1 | Check Dependencies | Optional If the code changes are the result of implementing a development task, check to see if the task depends on any other tasks that have not been checked in. Wait until those development tasks have been integrated. If the development task is mutually dependent on another task, shelve one and retrieve it on the same machine as the other. Handle the two as a single development task but check the work in against both tasks. Synchronize with the latest versions of the code for the area in which the code changed.
2 | Test and Integrate Other Development Tasks | Test the code to be sure it works with related changes that are already integrated. Run unit tests to be sure that the set of changes is compatible with those already integrated. Debug the integration if necessary, and repeat unit tests and code analysis until there are no integration problems.
3 | Check In the Set of Changes | Set the next build number in the bug or development task. Check in the code changes and the unit tests with the bug or development task. Checking in code changes should close the development task or resolve the bug and create a new changeset.
4 | Resolve Scenario or Quality of Service Requirement Work Item | Optional If the work item associated with the changes is a scenario or quality of service requirement and you are not the owner, notify the owner the changes are complete. Set the associated work item to "Resolved" and assign it to one of the testers who created the test cases for the work item.
5 | Resolve Bug Work Item | Optional If the work item associated with the changes is a bug, set the bug work item to "Resolved," and assign it to the original person who created the bug work item.
# Exit Criteria
| New changeset is created.
| Source code is integrated into main source (promoted to build).
| New unit tests are integrated into main source (promoted to build).
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |