The integration test method is divided into top-down and bottom-up two kinds.
Top-down integration (Top-down integration):
Starting from the main control module, move down the program level and gradually combine the modules.
You can use a combination of depth-first or breadth-first strategies.
Top-down integration steps:
1, the main control module to test, using the pile module to replace the module called by the main control modules
2, according to the selected strategy (depth/breadth), each time with an actual module substitution of a pile module
3, the integration test
4, in order to ensure that the added module did not introduce new errors, according to the need for regression testing. 2-4 Cycles.
Example:
Implement the top-down depth first test of the module.
Test method:
Self-low-up integration (bottom-up integration)
The bottom-up test starts with the module at the bottom of the software structure and tests the assembly.
Since the module is combined from the bottom up, it is always possible to get the required lower module processing function, so the pile module is not required.
Self-low-up integration steps
1. Combine the underlying module into a family that implements a specific sub-function
2, write test driver, coordinate the input and output of test data
3. Test the sub-functional family
4, remove the test driver, from the bottom up to move, the function of the combination of functions into a larger sub-functional family. 2-4 Cycles
The above modules are tested with bottom-up integration.
The method is:
There is also a sandwich test that sets up both of the above tests, which we do not cover in detail here.
Examples of integration test methods