5.4 Procedure for Integration Testing

Entry criteria: Any unit about to undergo Integration Testing must have passed all its unit tests. This ensures that Integration Testing focuses on interfaces between classes or modules and not internal structure.
Exit criteria: The thread being integrated passes its Integration Tests.

The procedure for Integration Testing is as follows:

1. Once all the classes corresponding to a particular thread have been coded and unit tested, the authors of the classes will work together to come up with a set of integration test cases.
2. These test cases may be made up the unit tests for the classes at the ends of the thread. For example, if a thread is made up of modA - modB - modC, then the integration test could use the unit test input for modA and expected output of modC.
3. A tester for the thread will be allocated (via email or at a Team Meeting), and this tester is responsible for running the test cases (using the testing script as described in 1.7) and creating a report for the thread (see section 5.6).
4. Once the testing is complete, the tester must notify the authors of the thread of the outcome of the test.
5. If the test was unsuccessful, the tester must either fix the problem or request for another person to fix it.

Once this step has been performed for the first time for a particular thread, it will become necessary to run integration tests along with unit tests before committing any changes to code.