A code coverage analysis method, device, equipment and storage medium

Abstract

The invention discloses a code coverage analysis method, device, equipment and storage medium. The method includes: during code testing, merging code coverage result files of each testing stage, and generating a summary based on the merged files. code coverage result report; determine the first code under test and the second code under test to be analyzed, and obtain the code coverage results of the first code under test and the second code under test in the aggregated code coverage result report report; establish a mapping relationship between the code coverage results of the first tested code and the second tested code, and perform a difference analysis on the two code coverage results according to the mapping relationship. The solution of the present invention realizes the statistical analysis of the test coverage rate as a whole, and based on the analysis result of the analysis, the test can be more targeted and repeated coverage can be reduced.

Description

technical field [0001] The invention relates to the field of software testing, in particular to a code coverage analysis method, device, equipment and storage medium. Background technique [0002] Software testing refers to the process of testing software in an automated or manual way to find program errors and ensure software quality. It usually includes different levels such as unit testing, interface testing, integration testing, performance testing, etc., and from the perspective of implementation, it is divided into manual testing, automated testing, ad-hoc testing (random testing) and so on. [0003] It can be seen that software testing is divided into different stages and different implementation types. However, the coverage of each stage of software testing is counted separately. For example, unit testing is usually carried out by developers, and integration testing is usually carried out by testers. It is difficult for developers and testers to understand the detai...

AI Technical Summary

Problems solved by technology

However, the coverage rate of each stage of software testing is counted separately. For example, unit testing is usually performed by developers, and integration testing is usually performed by testers. It is difficult for developers and testers to understand the details of each other's test coverage. Add test cases for coverage as a whole

For different implementation types, such as manual testing and automated testing, it is also difficult to synchronize the coverage rate with each other, and it is difficult to grasp the missing test situation as a whole

In addition, in the iterative process of software functions, in the process of conducting a series of tests for new functions, it is difficult to count the impact of the coverage of new functions on the overall coverage.

[0004] That is to say, the existing test coverage statistical tools can only run on a single machine, and there is a problem that it is impossible to conduct statistical analysis on the test coverage as a whole

Images