当前位置:网站首页>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.
边栏推荐
猜你喜欢

登录功能和退出功能(瑞吉外卖)

SQL外连接之交集、并集、差集查询

【深度学习】mmclassification mmcls 实战多标签分类任务教程,分类任务

RT - Thread record (a, RT, RT Thread version - Thread Studio development environment and cooperate CubeMX quick-and-dirty)

What are the standards for electrical engineering

双因子与多因子身份验证有什么区别?

化繁为简!阿里新产亿级流量系统设计核心原理高级笔记(终极版)

TiDB 6.0 Placement Rules In SQL Usage Practice

012年通过修补_sss_提高扩散模型效率

Create a Dapp, why choose Polkadot?
随机推荐
深入理解 Istio 流量管理的超时时间设置
拓朴排序例题
A small test of basic grammar, Go lang1.18 introductory refining tutorial, from Bai Ding to Hongru, basic grammar of go lang and the use of variables EP02
2022杭电杯超级联赛(5)
【综合类型第 35 篇】程序员的七夕浪漫时刻
5G NR 系统消息
【深度学习】mmclassification mmcls 实战多标签分类任务教程,分类任务
Three methods for extracting facial features
TiDB 6.0 Placement Rules In SQL Usage Practice
PPOCR 检测器配置文件参数详解
PCB布局必知必会:教你正确地布设运算放大器的电路板
Detailed explanation of PPOCR detector configuration file parameters
Latex如何控制表格的宽度和高度
这份阿里强推的并发编程知识点笔记,将是你拿大厂offer的突破口
2022杭电多校 第6场 1008.Shinobu Loves Segment Tree 规律题
Dynamics 365Online PDF导出及打印
PG优化篇--执行计划相关项
STM32 entry development: write XPT2046 resistive touch screen driver (analog SPI)
Header file search rules when compiling with GCC
导火索:OAuth 2.0四种授权登录方式必读