CN-113342676-B - Evaluation method and device for software test, computing equipment and storage medium

CN113342676BCN 113342676 BCN113342676 BCN 113342676BCN-113342676-B

Abstract

The embodiment of the application provides a method, a device, a computing device and a storage medium for evaluating software test, wherein the method comprises the steps of determining the target proportion of test software according to the historical proportions of a plurality of historical version software corresponding to the test software; determining the target defect number of the target sub-period of the test software in the test according to the target proportion, the test defect accumulated number of the test software in the inflection sub-period and the sequence of the inflection sub-period of the test software in the test, comparing the test defect number of the test software in the target sub-period with the corresponding target defect number, and determining whether the test software is sufficiently tested according to the comparison result. Because the relevance of the test software and the historical version software is larger, the influence of factors such as a test environment, testers and the like is small, and the target proportion of the test software is accurately determined based on the historical proportion of the historical version software, so that whether the test software is sufficiently tested is accurately evaluated.

Inventors

YAN XIAOBIN
LU DAOHE
ZHOU JIE
LIU JIAN
WENG YUPING
CHEN WENLONG
WANG HONG

Assignees

深圳前海微众银行股份有限公司

Dates

Publication Date: 20260512
Application Date: 20210629

Claims (8)

1. A method of evaluating a software test, the method comprising: Determining a target proportion of the test software according to the history proportion of a plurality of history version software corresponding to the test software, wherein the history proportion of any history version software is the proportion of the accumulated number of test defects in a corresponding history inflection point subcycle relative to the total number of test defects in a corresponding history test; Determining the target defect number of the target sub-period of the test software in the test according to the target proportion, the test defect accumulated number of the test software in the inflection sub-period and the order of the inflection sub-period of the test software in the test; comparing the number of the test defects of the test software in the target sub-period with the corresponding number of the target defects, and determining whether the test software is tested sufficiently or not according to a comparison result; Determining the target defect number of the target sub-period in the test of the test software according to the target proportion, the test defect accumulated number of the test software in the inflection sub-period and the order of the inflection sub-period of the test software in the test, wherein the method comprises the following steps: Determining the ratio of the test defect accumulation number of the test software in the inflection point subcycle to the target proportion as the target defect total number; Determining the target defect number of the inflection sub-period according to the total number of the target defects and the sequence of the inflection sub-period of the test software in the test, and/or determining the target defect number of other target sub-periods except the inflection sub-period according to the total number of the target defects, the sequence of the inflection sub-period of the test software in the test and the sequence of the other target sub-periods of the test software in the test; if the order of the inflection sub-periods of the test software is not the target order, the target sub-periods comprise the inflection sub-periods of the test software and the sub-periods of the target order, and if the order of the inflection sub-periods is the target order, the target sub-periods comprise the inflection sub-periods of the test software; The target sequence is determined according to the total number of subcycles of the test software in the test and a first preset proportion.
2. The method of claim 1, wherein determining the target proportion of the test software based on the historical proportions of the plurality of historical versions of the software corresponding to the test software comprises: filtering the historical proportions of the anomalies from the plurality of historical proportions; and determining the average value of the filtered historical proportion as the target proportion.
3. The method of claim 2, wherein the historical proportion of anomalies is determined by: determining standard deviations corresponding to the plurality of history proportions; for any one of the history proportions, if a deviation of the history proportion from an average of the plurality of history proportions is greater than the standard deviation, the history proportion is determined to be an abnormal history proportion.
4. A method according to any one of claims 1 to 3, wherein determining whether the test software is tested sufficiently based on the comparison results comprises: and if the variation amplitude of the test defect quantity of the test software in the target sub-period relative to the corresponding target defect quantity does not exceed the preset amplitude, determining that the test software is sufficiently tested.
5. The method of claim 4, further comprising, prior to determining that the test software is sufficiently tested: And determining the number of the test defects of the test software in the last subcycle in the test, wherein the proportion of the number of the test defects relative to the total number of the test defects in the test does not exceed a second preset proportion.
6. An evaluation device for software testing, comprising: The system comprises a proportion determining module, a proportion determining module and a proportion judging module, wherein the proportion determining module is used for determining the target proportion of the test software according to the historical proportion of a plurality of historical version software corresponding to the test software, wherein the historical proportion of any historical version software is the proportion of the accumulated number of test defects in a corresponding historical inflection point subcycle relative to the total number of test defects in a corresponding historical test; the quantity determining module is used for determining the target defect quantity of the target sub-period in the test of the test software according to the target proportion, the test defect accumulated quantity of the test software in the inflection sub-period and the sequence of the inflection sub-period of the test software in the test; the evaluation module is used for comparing the number of the test defects of the test software in the target sub-period with the corresponding number of the target defects, and determining whether the test software is sufficiently tested according to the comparison result; The quantity determining module is specifically configured to: Determining the ratio of the test defect accumulation number of the test software in the inflection point subcycle to the target proportion as the target defect total number; Determining the target defect number of the inflection sub-period according to the total number of the target defects and the sequence of the inflection sub-period of the test software in the test, and/or determining the target defect number of other target sub-periods except the inflection sub-period according to the total number of the target defects, the sequence of the inflection sub-period of the test software in the test and the sequence of the other target sub-periods of the test software in the test; if the order of the inflection sub-periods of the test software is not the target order, the target sub-periods comprise the inflection sub-periods of the test software and the sub-periods of the target order, and if the order of the inflection sub-periods is the target order, the target sub-periods comprise the inflection sub-periods of the test software; The target sequence is determined according to the total number of subcycles of the test software in the test and a first preset proportion.
7. A computing device comprising at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the method of any of claims 1 to 5.
8. A computer readable storage medium, characterized in that it stores a computer program executable by a computing device, which when run on the computing device, causes the computing device to perform the method of any of claims 1 to 5.

Description

Evaluation method and device for software test, computing equipment and storage medium Technical Field The embodiment of the application relates to the field of financial science and technology (Fintech), in particular to a software test evaluation method, a software test evaluation device, a computing device and a storage medium. Background With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changed into financial technology, but due to the requirements of safety and instantaneity of the financial industry, the technology is also required to be higher. In the financial field, in order to ensure that software operates normally and efficiently, it is necessary to test the software to repair software defects. If the software is not sufficiently tested, the software defects cannot be repaired well. In the related art, whether the software test is sufficient is evaluated through the code coverage rate, however, the code written by a developer is influenced by technology and experience, the written code may not completely cover the requirement, and a tester cannot accurately evaluate whether the software test is sufficient according to the existing overlooked code. In summary, there is a need for a method for evaluating software testing to accurately evaluate whether the software is tested sufficiently. Disclosure of Invention The embodiment of the application provides an evaluation method, an evaluation device, a computing device and a storage medium for software testing, which are used for accurately evaluating whether software is tested sufficiently or not. In a first aspect, an embodiment of the present application provides a method for evaluating a software test, where the method includes: Determining a target proportion of the test software according to the history proportion of a plurality of history version software corresponding to the test software, wherein the history proportion of any history version software is the proportion of the accumulated number of test defects in a corresponding history inflection point subcycle relative to the total number of test defects in a corresponding history test; Determining the target defect number of the target sub-period of the test software in the test according to the target proportion, the test defect accumulated number of the test software in the inflection sub-period and the order of the inflection sub-period of the test software in the test; comparing the number of the test defects of the test software in the target sub-period with the corresponding number of the target defects, and determining whether the test software is tested sufficiently or not according to the comparison result. According to the technical scheme, as the relevance of each software and the historical version software is larger, namely the defect distribution of the software of the same project is similar in the test process, and the defect distribution difference of the software of different projects is larger in the test process under the influence of factors such as test environments, testers and the like, according to the historical proportion of the historical version software corresponding to the test software, the target proportion of the accumulated number of defects at the inflection point subcycle relative to the total number of defects can be determined when the test software is tested sufficiently, and further, the target defect number of the target subcycle can be accurately determined according to the target proportion when the test software is tested sufficiently, and whether the test software is tested sufficiently can be accurately determined according to the comparison result of the test defect number in the actual test of the target subcycle and the corresponding target defect number when the test is sufficiently. Optionally, determining the target proportion of the test software according to the historical proportions of the plurality of historical version software corresponding to the test software includes: filtering the historical proportions of the anomalies from the plurality of historical proportions; and determining the average value of the filtered historical proportion as the target proportion. In the above technical solution, since some historical version software in the plurality of historical version software may test for anomalies, the defect distribution of the historical version software in the test is greatly different from the defect distribution of other historical version software in the test, and the historical version software corresponds to the historical proportion of the anomalies, the influence of the anomalies in the test is reduced by filtering the historical proportion of the anomalies from the historical proportion of the plurality of historical version software, and further determining the average value of the filtered historical pro