1. Basic concepts:
Test the software after integrating it. Integration testing is also called subsystem testing, assembly testing, component testing, etc. Integration testing mainly tests high-level software designs, generally testing modules and subsystems.
2. Levels included in integration testing:
1. Integration within the module is mainly to test the interactive integration relationship between various interfaces in the module;
2. Integration within subsystems and testing the interactive relationships between modules within subsystems;
3. System integration, testing the integration relationship between subsystems and modules within the system;
The essence of integration testing is to test the relationship between interfaces.
Supplement: Integration testing has elements of both white box testing and black box testing. It combines the characteristics of white box testing and black box testing, and is generally classified as gray box testing.
3. The relationship between integration testing and software outline (high-level) design:
Software outline (high-level) design is also called architecture design. An extremely important part of architecture design is the interface diagram. Integration testing generally relies on interface diagrams and module interfaces for testing. In a well-designed system, the software interface diagram should be an acyclic directed graph (hierarchical graph).
4. Is integration testing necessary?
Generally speaking, integration testing is necessary, but in actual situations, there is often not enough time to do integration testing due to time schedule issues, and there are many reasons why people are unwilling to do integration testing. However, integration testing must be done in the following situations:
1. Software systems with high software quality requirements, such as aerospace software, telecommunications software, system underlying software, etc.
2. Software with a wide range of uses and a large user base.
3. The usage class is software developed in a language with pointers such as C/C++.
4. Class libraries, middleware and other products.
Note: Integration testing is a test with a wide range of tests. When the integration test is further refined, it becomes a unit test.
现在我也找了很多测试的朋友，做了一个分享技术的交流群，共享了很多我们收集的技术文档和视频教程。
如果你不想再体验自学时找不到资源，没人解答问题，坚持几天便放弃的感受
可以加入我们一起交流。而且还有很多在自动化，性能，安全，测试开发等等方面有一定建树的技术大牛
分享他们的经验，还会分享很多直播讲座和技术沙龙
可以免费学习！划重点！开源的！！！
qq群号：110685036
5. The difference between integration testing and unit testing:
1. The units tested are different
Unit testing is testing of basic units of software (such as functions), while integration testing is testing of modules and subsystems as units, mainly testing the relationship between interfaces.
2. The basis for testing is different
Unit testing is a test based on the detailed design of the software, and the main basis of the test cases is also the detailed design. Integration testing is a test based on the general design of the software, and the main basis of the test cases is the general design.
3. Different test spaces
Integration testing mainly tests the test space of the interface layer, while unit testing mainly tests the test space of the internal implementation layer.
4. Integration testing uses different methods than unit testing
Integration testing focuses on the integration of interfaces, while unit testing only focuses on a single unit, so the specific testing methods are also different.
6. Integration methods for integration testing:
Integration methods mainly include big bang integration, bottom-up integration, top-down integration and sandwich integration. They are all integration methods based on the interface call graph.
Finally, I would like to thank everyone who read my article carefully. Looking at the increase in fans and attention, there is always some courtesy. Although it is not a very valuable thing, if you can use it, you can take it directly!
Software Testing Interview Document
We must study to find a high-paying job. The following interview questions are from the latest interview materials from first-tier Internet companies such as Alibaba, Tencent, Byte, etc., and some Byte bosses have given authoritative answers. After finishing this set I believe everyone can find a satisfactory job based on the interview information.
