First, the main content of integration testing
It refers to the test that all functions are assembled according to the requirements of the outline design on the basis of unit testing, which is called the test of the system or subsystem.
Integration testing is also called assembly testing, joint testing, subsystem testing, component testing
Second, the level of integration testing
1. In-module integration
2. Inter-module integration
3. Inter-subsystem integration
3. Criteria for judging module quality
High cohesion, low coupling: It is the standard for judging the quality of software design. is a concept in software engineering
Cohesion: refers to the degree to which elements within a module are combined with each other
Coupling: refers to the degree of interconnection between different modules within a software structure
Fourth, the focus of integration testing
1. Interface between units
2. Integrated functions
Interaction between functions
Accuracy Accumulation Problem
Five, integration testing strategy
1. Big Bang Integration
One-time integration of all code
Advantages: simple and fast, one-step completion, only one driver is required
Disadvantage: The one-time integration failure rate of complex systems is extremely high
Difficulty locating defects
Scope of application: maintenance projects
2. Top-down integration
Integrate the top-level first, and then go down one by one
Advantages: Only one driver is required to support fault isolation
Disadvantage: need to write a pile
Scope of application: the top layer is completed first or the top layer is relatively stable
3. Bottom-up integration
First integrate the bottom layer, and then go up one by one
Pros: Reduced development of piles
Disadvantage: need to write driver
Scope of application: the bottom layer is completed first or the bottom layer is relatively stable
4. Sandwich Integration
The system is divided into three layers: the top layer, the middle layer, and the bottom layer. The target layer is the middle layer
The top-down strategy is adopted for above the target layer, the bottom-up strategy is adopted for below the target layer, and finally converges at the target layer
Pros: Works with most software
Disadvantage: The target layer is not fully tested before being integrated
Scope of application: applicable to most software
other strategies
5. Based on backbone integration: backbone, peripheral
6. Based on layered integration:
7. Based on function integration:
8. Based on progress integration:
9. Based on message integration:
10. Risk based integration: