Strategies for Integration testing

Here are a few strategies for integration testing:

1) Big Bang integration
advantages: integration testing can be completed quickly And as long as a very small number of drive and pile modules; Use cases are minimal; Resource utilization is high

fit for a maintenance project or a test system smaller




adapt to the product control structure is relatively clear and stable; high-level interface changes are small, the underlying interface is undefined or often may be modified; The production control component has a large technical risk and needs to be verified as soon as possible. , and want to see the system function behavior of the product as early as possible.



is suitable for the bottom interface is relatively stable, high-level interface changes more frequently, the underlying component is completed earlier.

4) sandwich integration

cons: Middle-tier testing is not sufficient
adapt to most software development projects


cons: the structure and interdependence of the system must be carefully analyzed, the driving and pile development is large, the strategy of the Big Bang is adopted locally, and some interfaces may not be adequately tested.
embedded systems commonly used

6) tiered integration
adapt to systems with distinct hierarchical relationships

7) feature-based integration
Pros: Prioritize the correctness of key functions, reduce driver development, and make progress faster.

8) Message-based integration
Pros: Prioritize the correctness of critical messages, reduce driver development, and make progress faster.
Disadvantage: The interface test is not sufficient, there is a large redundancy test.

9) Risk-based integration
Advantages: The most risky components are first validated to help the system to be fast and stable.
Cons: A clear analysis of the risks of each component is required.

10) Progress-based integration
Advantages: high degree of parallelism, can effectively shorten the project development progress.
Cons: Pile and drive workloads are large; some interfaces are not adequately tested; some tests are repetitive and wasteful.

The above strategy should be based on the actual situation to adopt, can also be combined use!

Strategies for Integration testing