当前位置:网站首页>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.
边栏推荐
猜你喜欢
abc262-D(dp)
DocuWare平台——文档管理的内容服务和工作流自动化的平台详细介绍(下)
化繁为简!阿里新产亿级流量系统设计核心原理高级笔记(终极版)
SQL Outer Join Intersection, Union, Difference Query
The host computer develops C# language: simulates the STC serial port assistant to receive the data sent by the microcontroller
RT-Thread记录(一、RT-Thread 版本、RT-Thread Studio开发环境 及 配合CubeMX开发快速上手)
HDD杭州站•ArkUI让开发更灵活
负载均衡应用场景
Android 开发用 Kotlin 编程语言 二 条件控制
张朝阳对话俞敏洪:一边是手推物理公式,一边是古诗信手拈来
随机推荐
In-depth understanding of timeout settings for Istio traffic management
The query that the user's test score is greater than the average score of a single subject
R语言ggplot2可视化:可视化密度图(Density plot)、可视化多个分组的密度图、数据点分布在箱图中间、添加主标题、副标题、题注信息
RT - Thread record (a, RT, RT Thread version - Thread Studio development environment and cooperate CubeMX quick-and-dirty)
单片机:温度控制DS18B20
Score interview (1)----related to business
Scaling-law和模型结构的关系:不是所有的结构放大后都能保持最好性能
Naive bayes
拓朴排序例题
GCC编译的时候头文件搜索规则
60行从零开始自己动手写FutureTask是什么体验?
这份阿里强推的并发编程知识点笔记,将是你拿大厂offer的突破口
机器学习——逻辑回归
gradle尚硅谷笔记
MySQL 中 auto_increment 自动插入主键值
数据可视化(二)
RT-Thread记录(一、RT-Thread 版本、RT-Thread Studio开发环境 及 配合CubeMX开发快速上手)
朴素贝叶斯
2022杭电多校 第6场 1008.Shinobu Loves Segment Tree 规律题
TiDB 6.0 Placement Rules In SQL Usage Practice