The integration test cycle includes the following:
The software is likely to have problems during the integration test cycle, and might not build successfully. The goal is to find problems right away, not to get a high-quality installation area. Stability is not the goal right now because of the unstable nature of the software in the development cycle.
The kinds of problems you might see during integration-level builds include:
Remember that the integration build area is not a stable environment because it contains the most recently completed tasks. Another reason is that the candidates change frequently as developers complete their tasks. (This instability is normal.)
The integration test cycle is short and frequent, which helps you to find problems as early in the development cycle as possible. Additionally, developers with insulated development projects do not bring in each outside changes until the tasks have passed integration testing.
The integration cycle works best if you can build and test every day. Make the newly tested tasks available to developers immediately after they pass testing.
Typically, the integration-level build cycle includes the following:
Now that you understand the tasks to complete during the integration test cycle and why you must complete these operations, you are ready to perform the operations.