Task Descriptor: Integrate and Create Build |  |
This task describes how to integrate all changes made by developers into the code base and perform the minimal testing to validate the build.
Based on Method Task: Integrate and Create Build
Relationships
Roles | Main: Developer | Additional: | Assisting:
Inputs | Mandatory: Developer Test Implementation Test Script | Optional: None | External: None
Outputs | Build
Steps
Integrate implemented elements
In the relevant Workspace, combine all completed Change Sets that are not in the latest baseline. Resolve any conflicting versions of the artifacts by either removing one of the change sets that created the conflict or by creating a new change set that includes merged versions of the conflicting artifacts.
Create build
Create the build. The details of this step depend upon the implementation language and development environment and may involve compiling and linking (in the case of compiled languages) and/or other processes that result in an executable increment of the system. Examples of these steps include: Compiling and linking the source artifacts to create an executable Loading binary objects on a test bench or simulator Running a script to load/update database schemas Packaging and deploying web applications
Test integrated elements
Run Developer Tests against the integrated elements to verify that they behave the same as they did in isolation. Ensure that the scope of these tests is as broad as possible, which ensures that the latest change sets did not cause failing developer tests in other areas of the system.
Run "Smoke Tests"
Several builds will be created in each iteration. For each build, this step is performed only when change sets have been delivered to satisfy the requirements of that build. Execute a sub-set of the system tests to ensure that the build is suitable prior to committing resources to the full scope of system testing. While the level of testing will vary, focus on gaining confidence that the increment is of sufficient quality to establish a baseline for system testing.
Create a baseline
Several builds will be created in each iteration. For each build, this step is performed only when change sets have been delivered to satisfy the requirements of that build. The procedure for this step depends on the configuration management tools in use. Create a baseline that unambiguously identifies the configuration for the build that is ready for system testing. Identify the version of each implementation element and supporting artifacts that were used to create this build.
Properties
Multiple Occurrences |
Event-Driven |
Ongoing |
Optional |
Planned |
Repeatable |
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.