当前位置:网站首页>Integration testing of software testing
Integration testing of software testing
2022-08-05 10:57:00 【51CTO】
1. Concept of integration testing
1. Integration testing is also called assembly testing, joint testing, subsystem testing or component testing.
2. Integration testing is to assemble all modules into subsystems or systems according to the outline design requirements (such as according to the structure diagram) on the basis of unit testing for integration testing.
2. Purpose of integration testing
1. Find out the module interface and the overall architecture problems;
2. Ensure that the components can work together as intended when combined, and ensure that the incremental behavior is correct;
3. The integration test is a gray box test;
1) Verify that the interface conforms to the design;
2) Discover errors in design and requirements.
3. The focus of integration testing
Although some modules can work normally alone, they cannot be guaranteed to work normally when connected. Problems that cannot be reflected in some parts of the program may be exposed globally., which affects the realization of the function.
Therefore, integration tests should consider two questions:
1. Interface between modules (two points to consider)
1) When connecting each module, whether the data passing through the module interface will be lost;
2) Is there any problem with the global data structure and will it be modified abnormally.
2. Integrated functions (three points need to be considered)
1) Can the sub-functions be combined to meet the expected parent function;
2)Whether the function of one module will adversely affect the function of another module;
3) Will the accumulated errors of a single module be amplified to an unacceptable level?
4. Level of integration testing
The development process of a product includes a hierarchical design and gradual refinement process, from the initial product to the smallest unit can be divided into: product -> subsystems --> hardware subsystem, software subsystem -> software module - software program -> unit.
The general unit test is aimed at the smallest unit structure, the system test corresponds to the product level, and all the tests of each layer need to be completed through the integration test.Divide integration tests into 3 levels:
1. Integration test within the module (after the unit test is completed)
2. Intra-subsystem integration test, namely inter-module integration test
3. Inter-subsystem integration test
For more information on testing technology, please pay attention to: Shenzhen Multi-Tester Software and Technical Service Co., Ltd.
边栏推荐
猜你喜欢
随机推荐
Detailed explanation of PPOCR detector configuration file parameters
MySQL 中 auto_increment 自动插入主键值
19.3 restart the Oracle environment
TiDB 6.0 Placement Rules In SQL 使用实践
Use KUSTO query statement (KQL) to query LOG on Azure Data Explorer Database
STM32 entry development: write XPT2046 resistive touch screen driver (analog SPI)
Custom filters and interceptors implement ThreadLocal thread closure
ECCV 2022 | 视听分割:全新任务,助力视听场景像素级精细化理解
【C语言指针】用指针提升数组的运算效率
60行从零开始自己动手写FutureTask是什么体验?
FPGA: Basic Getting Started Button Controlling LED Lights
【加密解密】明文加密解密-已实现【已应用】
数分面试(一)----与业务相关
Image segmentation model - a combination of segmentation_models_pytorch and albumations to achieve multi-category segmentation
问题征集丨ECCV 2022中国预讲会 · Panel专题研讨会
UDP通信
Score interview (1)----related to business
flutter 服务器返回数据判断是否为空
如何测试一下现场的备机失败,转发主机的场景?
自定义过滤器和拦截器实现ThreadLocal线程封闭