CN112783800A - Test case screening method and device - Google Patents
Test case screening method and device Download PDFInfo
- Publication number
- CN112783800A CN112783800A CN202110296587.5A CN202110296587A CN112783800A CN 112783800 A CN112783800 A CN 112783800A CN 202110296587 A CN202110296587 A CN 202110296587A CN 112783800 A CN112783800 A CN 112783800A
- Authority
- CN
- China
- Prior art keywords
- case
- test
- coverage rate
- test case
- code
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3676—Test management for coverage analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/9035—Filtering based on additional data, e.g. user or group profiles
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Databases & Information Systems (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a test case screening method and a test case screening device, which can be applied to the technical field of computer application and can be used for screening test cases by acquiring change codes; obtaining a test case to be selected; determining the incremental coverage rate of the test case to be selected for the change code, wherein the incremental coverage rate represents the coverage rate of the change code when the test case to be selected is executed; and when the incremental coverage rate meets a preset condition, adding the test cases to be selected to a case library. The use case base can be reduced, and the testing efficiency is improved.
Description
Technical Field
The invention relates to the technical field of computer application, in particular to a test case screening method and device.
Background
The test cases are important bases in the iterative process of the software development project, a large number of test cases can be accumulated to a case library along with the rapid iteration and development of services, and the current test cases need to be subjected to full regression when certain services are reconstructed. For example, in the process of developing a new version, an old code corresponding to an old version is modified, and a regression test needs to be performed on the modified code, and a test is performed again by using all accumulated test cases to confirm that no new error is introduced into the modification or other codes are caused to generate errors. The large number of test cases in the case library is undoubtedly a huge workload for testing, the execution time required by testing is not inconsiderable, and how to guarantee the verification range with fewer test cases is an important content in the testing process.
Disclosure of Invention
The embodiment of the invention aims to provide a test case screening method and device, which are used for screening test cases to be added to a case library, reducing the case library and improving the test efficiency. The specific technical scheme is as follows:
in a first aspect of the present invention, a method for screening test cases is provided, including:
acquiring a change code;
obtaining a test case to be selected;
determining the incremental coverage rate of the test case to be selected for the change codes, wherein the incremental coverage rate represents the coverage rate of the change codes when the test case to be selected is executed;
and when the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library.
Optionally, when the incremental coverage meets a preset condition, adding the test case to be selected to a case library, including:
judging whether the incremental coverage rate is greater than a first preset coverage rate or not;
and when the incremental coverage rate is greater than a first preset coverage rate, adding the test case to be selected to a case library.
Optionally, when the incremental coverage meets a preset condition, adding the test case to be selected to a case library, including:
calculating the use case repeatability based on the incremental coverage rate and a second preset coverage rate;
and when the use case repetition degree is less than the preset repetition degree, adding the test use case to be selected to the use case library.
Optionally, the test cases to be selected include test cases to be selected with different priority levels, where the priority levels are determined according to service requirements;
the determining the incremental coverage rate of the to-be-selected test case for the change code includes:
determining a first coverage rate of the change codes when the highest-level to-be-selected test case is executed, wherein the highest-level to-be-selected test case is the test case with the highest priority in the to-be-selected test cases;
and when the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library, wherein the step of adding the test case to be selected to the case library comprises the following steps:
calculating the use case repeatability based on the first coverage rate and the basic coverage rate;
judging whether the use case repetition degree is less than a preset repetition degree;
when the use case repetition degree is smaller than the preset repetition degree, adding the test use case to be selected at the highest level to the use case library;
the determining the incremental coverage rate of the to-be-selected test case for the change code includes:
according to the sequence of the priority levels from high to low, aiming at each test case in other test cases to be selected, determining a second coverage rate of the change codes when the test cases are executed; the other test cases to be selected comprise test cases except the test case to be selected at the highest level in the test cases to be selected;
and when the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library, wherein the step of adding the test case to be selected to the case library comprises the following steps:
judging whether the second coverage rate is greater than the coverage rate before the test case is executed;
and when the second coverage rate is greater than the coverage rate before the test case is executed, adding the test case to the case library.
Optionally, after the determining whether the use case repetition degree is less than a preset repetition degree, the method further includes:
when the repetition degree of the use case is not less than the preset repetition degree, modifying the test use case to be selected at the highest level; and returning to the step of executing the first coverage rate of the change codes when the test case with the highest level to be selected is determined to be executed.
Optionally, the calculating a use case repetition degree based on the first coverage rate and the base coverage rate includes:
sequentially determining the current coverage rate of the change codes when the test case is executed aiming at each test case in the test cases to be selected at the highest level;
when the current coverage rate is the same as the coverage rate before the test case is executed, adding 1 to the number of case repetition until all test cases in the test cases to be selected at the highest level are executed, and obtaining the final number of case repetition;
and taking the ratio of the final number of the use cases to the total number of the use cases as the repetition degree of the use cases, wherein the total number of the use cases is the total number of the test cases to be selected at the highest level.
Optionally, the obtaining the change code includes:
acquiring a code to be detected;
searching a starting node and an ending node in the code to be detected;
obtaining a change file according to the starting node and the ending node;
analyzing to obtain a code implementation method corresponding to the changed file through a source code analysis tool, and calculating a method parameter value corresponding to the changed file;
if the method parameter value corresponding to the changed file is different from the method parameter value corresponding to the code to be tested, the method realized by the code corresponding to the changed file is used as a changing method;
the determining the incremental coverage rate of the to-be-selected test case for the change code includes:
analyzing the change method through a coverage analysis tool to generate a coverage report, wherein the coverage report comprises the incremental coverage of the test case to be selected for the change method.
In a second aspect of the present invention, there is also provided a test case screening apparatus, including:
the acquisition module is used for acquiring the change code; the change code comprises code updated relative to a reference code; obtaining a test case to be selected; the test cases to be selected are test cases to be added to a case library, and the test cases are used for testing the codes;
and the determining module is used for determining the increment coverage rate of the test case to be selected for the change codes, wherein the increment coverage rate represents the coverage rate of the change codes when the test case to be selected is executed.
The adding module is used for adding the test cases to be selected to a case library if the incremental coverage rate meets a preset condition; otherwise, the test case to be selected is not added to the case library.
Optionally, the adding module is specifically configured to determine whether the incremental coverage is greater than a first preset coverage; and when the incremental coverage rate is greater than a first preset coverage rate, adding the test case to be selected to a case library.
Optionally, the adding module is specifically configured to calculate a use case repetition degree based on the incremental coverage rate and a second preset coverage rate; and when the use case repetition degree is less than the preset repetition degree, adding the test use case to be selected to the use case library.
Optionally, the test cases to be selected include test cases to be selected with different priority levels, where the priority levels are determined according to service requirements;
the determining module is specifically configured to determine a first coverage rate of the change code when the highest-level to-be-selected test case is executed, where the highest-level to-be-selected test case is a test case with a highest priority level among the to-be-selected test cases;
the adding module is specifically used for calculating the use case repetition degree based on the first coverage rate and the basic coverage rate; judging whether the use case repetition degree is less than a preset repetition degree; when the use case repetition degree is smaller than the preset repetition degree, adding the test use case to be selected at the highest level to the use case library; when the repetition degree of the case is not less than the preset repetition degree, modifying the test case to be selected at the highest level; and returning to the step of determining the first coverage rate of the change code when the test case with the highest level to be selected is executed;
the determining module is specifically configured to determine, for each test case in other test cases to be selected, a second coverage rate of the change code when the test case is executed according to a sequence from high priority to low priority; the other test cases to be selected comprise test cases except the test case to be selected at the highest level in the test cases to be selected;
the adding module is specifically configured to determine whether the second coverage is greater than a coverage before the test case is executed; when the second coverage rate is larger than the coverage rate before the test case is executed, adding the test case to the case library; otherwise, the test case is not added to the case library.
Optionally, the adding module is specifically configured to determine, for each test case in the test cases to be selected at the highest level in sequence, a current coverage rate of the change code when the test case is executed; when the current coverage rate is the same as the coverage rate before the test case is executed, adding 1 to the number of case repetition until all test cases in the test cases to be selected at the highest level are executed, and obtaining the final number of case repetition; and taking the ratio of the final number of the use cases to the total number of the use cases as the repetition degree of the use cases, wherein the total number of the use cases is the total number of the test cases to be selected at the highest level.
Optionally, the obtaining module is specifically configured to obtain a code to be tested; searching a starting node and an ending node in the code to be detected; obtaining a change file according to the starting node and the ending node; analyzing to obtain a code implementation method corresponding to the changed file through a source code analysis tool, and calculating a method parameter value corresponding to the changed file; if the method parameter value corresponding to the changed file is different from the method parameter value corresponding to the code to be tested, the method realized by the code corresponding to the changed file is used as a changing method;
the determining module is specifically configured to analyze the change method through a coverage analysis tool to generate a coverage report, where the coverage report includes an incremental coverage of the test case to be selected for the change method.
In another aspect of the embodiment of the present invention, a test case screening device is further provided, which includes a processor, a communication interface, a memory, and a communication bus, where the processor and the communication interface complete communication between the memory and the processor through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of the first aspect when executing the program stored in the memory.
In yet another aspect of the present invention, there is also provided a computer-readable storage medium having stored therein a computer program which, when executed by a processor, implements the method steps of the first aspect.
According to the test case screening method and device provided by the embodiment of the invention, the change codes are obtained; the change code comprises code updated relative to a reference code; obtaining a test case to be selected; the test cases to be selected are test cases to be added to a case library, and the test cases are used for testing the codes; determining the incremental coverage rate of the test case to be selected for the change code, wherein the incremental coverage rate represents the coverage rate of the change code when the test case to be selected is executed; if the incremental coverage rate meets a preset condition, adding the test cases to be selected to a case library; otherwise, the test case to be selected is not added to the case library. The incremental coverage rate of the test cases to be selected for the change codes can be determined, namely the coverage rate of the change codes when the test cases to be selected are executed, and the test cases to be selected are added to the case library when the incremental coverage rate meets the preset conditions.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a flowchart of a test case screening method according to an embodiment of the present invention;
FIG. 2 is a flow chart of obtaining change codes in an embodiment of the present invention;
FIG. 3 is a flow chart of incremental coverage calculation from method dimensions in an embodiment of the present invention;
fig. 4 is another flowchart of a test case screening method according to an embodiment of the present invention;
fig. 5 is an application schematic diagram of a test case screening method provided by the embodiment of the invention;
FIG. 6 is a flowchart illustrating example of calculating a repetition rate of a use case;
fig. 7 is a schematic structural diagram of a test case screening apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of test case screening equipment according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
The inventor researches a large number of service case libraries to find that most service lines only combine the existing test cases into the case libraries after the function verification is passed, and do not perform secondary processing on the test cases, so that a large number of redundancies are generated in the case libraries, the base numbers of the case libraries are increased, and further the test efficiency is low.
In the embodiment of the invention, the historical test cases and/or newly added test cases and the like are screened by selecting the reasonable standard and are effectively put in storage, so that the minimization of the test case set can be ensured, more effective candidate cases are provided for the test, and the test efficiency is further improved. In the embodiment of the invention, the coverage rate generated by the test case is introduced, the test case added into the use case library is screened based on the coverage rate as the judgment standard for judging whether the test case is put into the warehouse or not, namely, the test case added into the use case library is screened based on the coverage rate, so that the screening of the historical test case and/or the newly added test case and the like is realized, the use case library is reduced, the test efficiency is improved, the minimum set is expected to be selected for putting into the warehouse, the minimization of the test case library is ensured, and the test efficiency is improved.
The test case screening method provided by the embodiment of the invention can be applied to business test, effectively lock the test range, ensure the effectiveness of the test cases, minimize the test case set and improve the retest efficiency. For example, a company with long service development time, multiple functions, and multiple use cases needs to improve test efficiency and simplify use cases to perform service test in a scenario.
The following describes in detail the test case screening method provided by the embodiment of the present invention.
The embodiment of the invention provides a test case screening method, which comprises the following steps:
acquiring a change code;
obtaining a test case to be selected;
determining the incremental coverage rate of the test case to be selected for the change code, wherein the incremental coverage rate represents the coverage rate of the change code when the test case to be selected is executed;
and when the incremental coverage rate meets a preset condition, adding the test cases to be selected to a case library.
In the embodiment of the invention, the incremental coverage rate of the test cases to be selected for the change codes is determined, namely the coverage rate of the change codes when the test cases to be selected are executed, and the test cases to be selected are added to the case library when the incremental coverage rate meets the preset condition, so that the test cases to be added to the case library can be screened, the case library is reduced, and the test efficiency is improved.
The execution main body of the test case screening method provided by the embodiment of the invention can be electronic equipment. In particular, the electronic device may include a terminal, a processor, a server, and the like.
Fig. 1 is a flowchart of a test case screening method according to an embodiment of the present invention. Referring to fig. 1, a test case screening method provided in an embodiment of the present invention may include:
s101, acquiring a change code.
The change code may also be understood as code that is updated relative to the reference code, and may include new code and/or modified code, new code such as code that implements new requirements, and the like.
And S102, obtaining a test case to be selected.
The test cases to be selected can comprise original historical test cases in the use case library, and can also comprise newly added test cases, such as test cases compiled according to the requirement documents when new requirements are tested; the historical test cases and the newly added test cases can be included at the same time.
S103, determining the incremental coverage rate of the test cases to be selected for the change codes.
And the increment coverage rate represents the coverage rate of the changed code when the test case to be selected is executed.
It is to be understood that the incremental coverage rate may reflect the coverage degree of the test case to be selected on the change code, such as whether the execution of the test case to be selected can cover the change code, and the covered code accounts for the proportion of the change code, and the like.
Specifically, the change code may be parsed by a coverage analysis tool to generate a coverage report.
The coverage report may include the incremental coverage of the test cases to be selected for the altered code.
In one implementation, the coverage analysis tool may be Jacoco. Jacoco is an open source coverage tool. Jacoco can get coverage counters, coverage counter row coverage, class coverage, method coverage, branch coverage, instruction coverage, round-robin complexity.
Specifically, Jacoco executes a test case for testing, generates an exec file (coverage rate information file) in the test process, analyzes the exec file, analyzes only a change code by a visitMethod of a ClassProbesAdapter class, and obtains a coverage rate report including incremental coverage rate of the test case to be selected for the change code without processing other non-specified classes and methods.
And S104, when the incremental coverage rate meets a preset condition, adding the test cases to be selected to a case library.
Whether the test case to be selected covers the change code or not can be represented through the increment coverage, or the coverage rate paths of a plurality of test cases to be selected are the same, and the like.
If the test case to be selected covers the change code, the test case to be selected can be used as an effective test case to be added to the case library, otherwise, the test case to be selected is considered to be an ineffective test case.
If the coverage rate paths of the multiple test cases to be selected are the same, the test cases to be selected with the same coverage rate paths can be summarized into one test case, and the summarized test case is added to the case library, so that the number of the test cases in the case library can be reduced, and the return speed can be improved. The coverage rate path may be understood as that the execution of the test case to be selected covers the specific code in the change code, such as the codes in lines 1 to 10.
In an alternative embodiment, S104 may include:
and judging whether the incremental coverage rate is greater than a first preset coverage rate, and adding the test cases to be selected to a case library when the incremental coverage rate is greater than the first preset coverage rate.
In one approach, the first preset coverage rate may be a preset value determined according to actual requirements or empirical values. In another way, the first preset coverage rate is a coverage rate calculated based on test cases existing in the case base.
Therefore, the method is simple, only needs to judge whether the incremental coverage rate is greater than a first preset coverage rate, and when the incremental coverage rate is greater than the first preset coverage rate, the test cases to be selected are added to the case library. If the test cases to be added to the case base can be screened in a simpler way only by judging whether the codes covered by the executed test cases to be selected are more than the codes covered by the existing test cases.
In another alternative embodiment, S104 may include:
calculating the use case repetition degree based on the incremental coverage rate and a second preset coverage rate; and when the repetition degree of the case is less than the preset repetition degree, adding the test case to be selected to the case library.
In one approach, the second preset coverage rate may be a preset value determined according to actual requirements or empirical values. In another mode, the second preset coverage rate is a coverage rate calculated based on test cases existing in the case base.
The use case repeatability can represent the degree of repetition among the newly added multiple test cases. Or, the case repetition degree may represent the repetition degree between the newly added test case and the existing test case in the case library. The degree of repetition may also be understood as the degree of repetition of multiple test case coverage paths.
The test cases to be added to the case library are screened through the repeatability, so that the repetition, namely redundancy, between the test cases in the case library can be further reduced, and the test cases can be further reduced.
In the embodiment of the invention, the incremental coverage rate of the test cases to be selected for the change codes can be determined, namely the coverage rate of the change codes when the test cases to be selected are executed, and the test cases to be selected are added to the case library when the incremental coverage rate meets the preset condition, so that the test cases to be added to the case library can be screened, the case library is reduced, and the test efficiency is improved. The incremental coverage rate is used as a judgment standard for judging whether the test cases are put into the warehouse or not, namely the test cases added into the use case base are screened based on the incremental coverage rate, so that the minimum set can be selected to be put into the warehouse to the greatest extent, the minimization of the test case base is ensured, and the test efficiency is improved.
In an alternative embodiment, as shown in fig. 2, S101: obtaining change code may include:
s1011, acquiring the code to be detected.
The code to be tested may be code submitted by a developer that requires testing.
S1012, a starting node and an ending node in the code to be tested are searched.
And S1013, obtaining a change file according to the starting node and the ending node.
In writing code, each time the code is updated, such as modifying the code or adding the code, the updated nodes, such as the start node and the end node, are generally marked.
The start and end nodes in the branch may be looked up from the developer's test code, for example, the value of SHA-1 (string computed by secure hash algorithm) in the code management tool Git.
The changed file, i.e., the changed file, is calculated from the value of SHA-1 using a Git Api (code management tool interface), and the non-java file, the test file, and the like are excluded.
And S1014, analyzing the code implementation method corresponding to the changed file through a source code analysis tool, and calculating the method parameter value corresponding to the changed file.
And S1015, if the method parameter value corresponding to the changed file is different from the method parameter value corresponding to the code to be tested, using the method realized by the code corresponding to the changed file as the changing method.
The source code analysis tool may be a Java Development Tool (JDT). The method parameter value may be an md5 (message digest algorithm) value.
Analyzing by using JDT (Java integrated development environment plug-in with complete functions added by an Eclipse platform) to obtain a code implementation method corresponding to the changed file, calculating a method parameter value corresponding to the changed file, calculating a code implementation method to be tested, and calculating a method parameter value corresponding to the code to be tested. Specifically, the JDT is used for analyzing the source codes and analyzing the md5 values of the methods for calculating the old and new (before and after change) files, whether the md5 values respectively corresponding to the files before and after the change are the same or not is compared, if the md5 values are different, the change is indicated, and the method realized by the codes corresponding to the changed files is used as the change method.
S103: determining the incremental coverage rate of the test cases to be selected for the change codes may include:
and analyzing the change method through a coverage analysis tool to generate a coverage report, wherein the coverage report comprises the incremental coverage of the test case to be selected for the change method.
The coverage analysis tool may be Jacoco. Specifically, Jacoco executes a test case for testing, generates an exec file in the test process, analyzes the exec file, analyzes only the change method by a visitMethod of ClassProbesAdapter class, and does not process other non-specified classes and methods to obtain a coverage rate report including the incremental coverage rate of the test case to be selected for the change method.
Fig. 3 is a flowchart of calculating incremental coverage from method dimensions in the embodiment of the present invention, and as shown in fig. 3, the following process may be included.
Firstly, acquiring a test code; and acquiring a starting node and an end node, namely the starting node and the end node in the test code search branch.
And then, obtaining a change file according to the starting node and the ending node.
The embodiment of the invention obtains the changed method through JDT analysis, so that the non-java file is removed before analysis, and the changed method is analyzed through JDT.
Meanwhile, deploying the tested service; jacoco service deployment; and generating exec files based on the deployed tested service and the Jacoco service execution test case.
Finally, a method of change coverage is calculated based on the method of change and the exec file.
The method and the device avoid the phenomenon of excessive simplification caused by only paying attention to line code change, can enlarge the coverage calculation range to be the coverage of the change method, namely, the incremental coverage is calculated from the dimension of the method in the embodiment of the invention.
In an optional embodiment, the test cases to be selected may include test cases to be selected with different priority levels, where the priority levels are determined according to business requirements.
The different priority levels may include P0, P1, P2, P3, P4, etc., with the priority levels from high to low for P0 → P1 → P2 → P3 → P4.
Fig. 4 is another flowchart of the test case screening method according to the embodiment of the present invention. Referring to fig. 4, S103: determining the incremental coverage rate of the test cases to be selected for the change codes may include:
and S1031, determining a first coverage rate of the change code when the test case with the highest level to be selected is executed.
And the test case with the highest level to be selected is the test case with the highest priority level in the test cases to be selected.
For example, the test case with the highest priority level to be selected may be the test case with the priority level of P0. For the existing test cases in the use case library, a Quality Assurance (QA) system screens the most core test case at the level of P0 according to the requirements of service lines. Alternatively, for new requirements testing, the QA system writes P0 priority level test cases according to the requirements document.
Specifically, the process of determining the first coverage rate of the change code when executing the test case with the highest level to be selected may refer to the process of executing S103 in the above embodiment.
S104: when the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library, which may include:
s1041, calculating the use case repetition degree based on the first coverage rate and the basic coverage rate.
The basic coverage rate can be a preset value determined according to an empirical value or an actual requirement; or the coverage rate calculated based on the test cases existing in the case base.
S1042, judging whether the repetition degree of the use case is less than the preset repetition degree.
And when the use case repetition degree is less than the preset repetition degree, executing the step S1043.
The preset repetition degree may be determined according to actual needs or experience, and may be 10% for example.
And S1043, adding the test case with the highest level to be selected to a case library.
In an implementation mode, when the repetition degree of the use case is not less than the preset repetition degree, modifying the test use case to be selected at the highest level; and returning to the step of executing the first coverage rate of the change code when the test case with the highest level to be selected is determined to be executed, namely returning to the step of executing S1031.
S103: determining the incremental coverage rate of the test cases to be selected for the change codes may include:
s1032, according to the sequence of the priority levels from high to low, aiming at each test case in other test cases to be selected, determining a second coverage rate of the change codes when the test cases are executed.
And the other test cases to be selected comprise test cases except the test case to be selected with the highest level in the test cases to be selected.
For example, according to the priority level of the test cases from high to low, the test cases of P1 → P2 → P3 → P4 are executed one by one, for example, and the second coverage rate corresponding to each test case except the test case with the highest level in the test cases to be selected is determined.
S104: when the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library, which may include:
s1044, judging whether the second coverage rate is greater than the coverage rate before the test case is executed.
S1045, when the second coverage rate is larger than the coverage rate before the test case is executed, adding the test case to the case library.
If the corresponding increment coverage rate is increased after the test case is executed, adding the test case into a case library; if the corresponding incremental coverage rate is not increased, the test case is repeated with the previous test case and is regarded as an invalid case, namely, the invalid case is not put in storage.
In a specific example, fig. 5 is an application schematic diagram of the test case screening method provided by the embodiment of the present invention, and as shown in fig. 5, the method may include the following processes.
Aiming at a test case at a P0 level, firstly, acquiring basic coverage rate data and a repetition rate; if the repetition rate is less than 10%, adding the test case into a case library; and thirdly, if the repetition rate is not less than 10%, manually adjusting the test cases at the P0 level, such as modifying the test cases at the P0 level, or reselecting the test cases at the P0 level.
Aiming at the test cases of non-P0 level, executing the test cases of non-P0 level one by one; if the coverage rate is increased, adding the test case into a case library; and sixthly, removing the use case and not warehousing the test case when the coverage rate is unchanged.
The basic coverage data may be a first coverage of the change code when the test case with the highest level to be selected is executed, which is determined in S1031.
The repetition rate may be a use case repetition degree calculated based on the first coverage rate and the base coverage rate in S1041.
The first coverage rate of the change code when the test case with the highest execution level determined in S1031 is to be selected is used as basic data, that is, when a test case with a non-P0 level is executed for the first time, the incremental coverage rate generated by executing the test case with the non-P0 level for the first time is compared with the first coverage rate, if the incremental coverage rate generated by executing the test case with the non-P0 level for the first time is greater than the first coverage rate, the test case with the non-P0 level for the first time is added into the case library, then the 2 nd test case with the non-P0 level is executed, the incremental coverage rate generated by the 2 nd test case is compared with the test case with the non-P0 level for the first time, if the incremental coverage rate generated by the 2 nd test case is greater than the test case with the non-P0 level for the first time, the 2 nd test case is added into the case library, and executing the 3 rd test case at the non-P0 level, and so on until all the test cases at the non-P0 level are executed.
In an alternative embodiment, S1041: calculating the use case repetition degree based on the first coverage rate and the base coverage rate, as shown in fig. 6, may include:
s601, sequentially aiming at each test case in the test cases to be selected at the highest level, determining the current coverage rate of the change codes when the test case is executed.
S602, when the current coverage rate is the same as the coverage rate before the test case is executed, adding 1 to the number of case repetition until all test cases in the test cases to be selected at the highest level are executed, and obtaining the final number of case repetition.
S603, the ratio of the final number of example repetitions to the total number of example is used as the degree of example repetition.
And the total number of the use cases is the total number of the test cases to be selected at the highest level.
Specifically, the total number of use cases is m, if the current incremental coverage rate after the test use cases are executed is not changed, the number of use case repetitions n is added to 1, and after all the test use cases are executed, the repetition (r) of the current use case set is calculated by the following formula:
the embodiment of the invention calculates the incremental coverage rate by a method-level incremental coverage rate calculation method, namely, calculates the incremental coverage rate from the method dimension, introduces a case repeatability concept, and takes the incremental coverage rate and the case repeatability as standards for screening a case set, namely, standards for screening test cases added into a case library. The incremental coverage rate and the case repetition rate are introduced in the case filing stage, repeated test cases can be quickly removed, the minimized test case set is ensured, and the function retest efficiency is improved.
Corresponding to the test case screening method provided in the foregoing embodiment, an embodiment of the present invention provides a test case screening apparatus, as shown in fig. 7, which may include:
an obtaining module 701, configured to obtain a change code; the change code comprises code updated relative to a reference code; obtaining a test case to be selected; the test cases to be selected are test cases to be added to a case library, and the test cases are used for testing the codes;
a determining module 702, configured to determine an incremental coverage rate of the to-be-selected test case for the change code, where the incremental coverage rate represents a coverage rate of the change code when the to-be-selected test case is executed.
An adding module 703, configured to add the test case to be selected to a case library if the incremental coverage meets a preset condition; otherwise, the test case to be selected is not added to the case library.
Optionally, the adding module 703 is specifically configured to determine whether the incremental coverage is greater than a first preset coverage; and when the incremental coverage rate is greater than a first preset coverage rate, adding the test case to be selected to a case library.
Optionally, the adding module 703 is specifically configured to calculate a use case repetition degree based on the incremental coverage rate and a second preset coverage rate; and when the use case repetition degree is less than the preset repetition degree, adding the test use case to be selected to the use case library.
Optionally, the test cases to be selected include test cases to be selected with different priority levels, where the priority levels are determined according to service requirements;
the determining module 702 is specifically configured to determine a first coverage rate of the change code when the highest-level candidate test case is executed, where the highest-level candidate test case is a test case with a highest priority level among the candidate test cases;
the adding module 703 is specifically configured to calculate a use case repetition degree based on the first coverage rate and the basic coverage rate; judging whether the use case repetition degree is less than a preset repetition degree; when the use case repetition degree is smaller than the preset repetition degree, adding the test use case to be selected at the highest level to the use case library; when the repetition degree of the case is not less than the preset repetition degree, modifying the test case to be selected at the highest level; and returning to the step of determining the first coverage rate of the change code when the test case with the highest level to be selected is executed;
the determining module 702 is specifically configured to determine, for each test case in other test cases to be selected, a second coverage rate of the change code when the test case is executed according to a sequence from high priority to low priority; the other test cases to be selected comprise test cases except the test case to be selected at the highest level in the test cases to be selected;
the adding module 703 is specifically configured to determine whether the second coverage is greater than a coverage before the test case is executed; when the second coverage rate is larger than the coverage rate before the test case is executed, adding the test case to the case library; otherwise, the test case is not added to the case library.
Optionally, the adding module 703 is specifically configured to determine, for each test case in the test cases to be selected at the highest level, a current coverage rate of the change code when the test case is executed; when the current coverage rate is the same as the coverage rate before the test case is executed, adding 1 to the number of case repetition until all test cases in the test cases to be selected at the highest level are executed, and obtaining the final number of case repetition; and taking the ratio of the final number of the use cases to the total number of the use cases as the repetition degree of the use cases, wherein the total number of the use cases is the total number of the test cases to be selected at the highest level.
Optionally, the obtaining module 701 is specifically configured to obtain a code to be detected; searching a starting node and an ending node in the code to be detected; obtaining a change file according to the starting node and the ending node; analyzing to obtain a code implementation method corresponding to the changed file through a source code analysis tool, and calculating a method parameter value corresponding to the changed file; if the method parameter value corresponding to the changed file is different from the method parameter value corresponding to the code to be tested, the method realized by the code corresponding to the changed file is used as a changing method;
the determining module 702 is specifically configured to analyze the change method through a coverage analysis tool, and generate a coverage report, where the coverage report includes an incremental coverage of the test case to be selected for the change method.
The test case screening device provided by the embodiment of the invention is a device applying the test case screening method, so that all embodiments of the test case screening method are suitable for the device and can achieve the same or similar beneficial effects.
The embodiment of the present invention further provides a test case screening device, as shown in fig. 8, which includes a processor 801, a communication interface 802, a memory 803, and a communication bus 804, where the processor 801, the communication interface 802, and the memory 803 complete mutual communication through the communication bus 804.
A memory 803 for storing a computer program;
the processor 801 is configured to implement the method steps for screening the test cases when executing the program stored in the memory 803.
The communication bus mentioned in the test case screening apparatus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the test case screening equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In another embodiment provided by the present invention, a computer-readable storage medium is further provided, in which a computer program is stored, and when being executed by a processor, the computer program implements the method steps of test case screening.
In yet another embodiment of the present invention, a computer program product containing instructions is also provided, which when run on a computer, causes the computer to perform the method steps of test case screening described above.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, the device, the computer-readable storage medium, and the computer program product embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and in relation to the description, reference may be made to some of the description of the method embodiments.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (10)
1. A test case screening method is characterized by comprising the following steps:
acquiring a change code; the change code comprises code updated relative to a reference code;
obtaining a test case to be selected; the test cases to be selected are test cases to be added to a case library, and the test cases are used for testing the codes;
determining the incremental coverage rate of the test case to be selected for the change codes, wherein the incremental coverage rate represents the coverage rate of the change codes when the test case to be selected is executed;
if the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library; otherwise, the test case to be selected is not added to the case library.
2. The method for screening test cases according to claim 1, wherein if the incremental coverage rate satisfies a preset condition, adding the test case to be selected to a case library comprises:
judging whether the incremental coverage rate is greater than a first preset coverage rate or not;
and when the incremental coverage rate is greater than a first preset coverage rate, adding the test case to be selected to a case library.
3. The method for screening test cases according to claim 1, wherein if the incremental coverage rate satisfies a preset condition, adding the test case to be selected to a case library comprises:
calculating the use case repeatability based on the incremental coverage rate and a second preset coverage rate;
and when the use case repetition degree is less than the preset repetition degree, adding the test use case to be selected to the use case library.
4. The method for screening test cases according to claim 1, wherein the test cases to be selected include test cases to be selected with different priority levels, wherein the priority levels are determined according to business requirements;
the determining the incremental coverage rate of the to-be-selected test case for the change code includes:
determining a first coverage rate of the change codes when the highest-level to-be-selected test case is executed, wherein the highest-level to-be-selected test case is the test case with the highest priority in the to-be-selected test cases;
if the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library; otherwise, not adding the test case to be selected to the case library, including:
calculating the use case repeatability based on the first coverage rate and the basic coverage rate;
judging whether the use case repetition degree is less than a preset repetition degree;
when the use case repetition degree is smaller than the preset repetition degree, adding the test use case to be selected at the highest level to the use case library;
when the repetition degree of the case is not less than the preset repetition degree, modifying the test case to be selected at the highest level; and returning to the step of determining the first coverage rate of the change code when the test case with the highest level to be selected is executed;
the determining the incremental coverage rate of the to-be-selected test case for the change code includes:
according to the sequence of the priority levels from high to low, aiming at each test case in other test cases to be selected, determining a second coverage rate of the change codes when the test cases are executed; the other test cases to be selected comprise test cases except the test case to be selected at the highest level in the test cases to be selected;
if the incremental coverage rate meets a preset condition, adding the test case to be selected to a case library, including:
judging whether the second coverage rate is greater than the coverage rate before the test case is executed;
when the second coverage rate is larger than the coverage rate before the test case is executed, adding the test case to the case library; otherwise, the test case is not added to the case library.
5. The method for screening test cases according to claim 4, wherein the calculating the case repetition degree based on the first coverage and the basic coverage comprises:
sequentially determining the current coverage rate of the change codes when the test case is executed aiming at each test case in the test cases to be selected at the highest level;
when the current coverage rate is the same as the coverage rate before the test case is executed, adding 1 to the number of case repetition until all test cases in the test cases to be selected at the highest level are executed, and obtaining the final number of case repetition;
and taking the ratio of the final number of the use cases to the total number of the use cases as the repetition degree of the use cases, wherein the total number of the use cases is the total number of the test cases to be selected at the highest level.
6. The test case screening method according to any one of claims 1 to 5, wherein the obtaining of the change code includes:
acquiring a code to be detected;
searching a starting node and an ending node in the code to be detected;
obtaining a change file according to the starting node and the ending node;
analyzing to obtain a code implementation method corresponding to the changed file through a source code analysis tool, and calculating a method parameter value corresponding to the changed file;
if the method parameter value corresponding to the changed file is different from the method parameter value corresponding to the code to be tested, the method realized by the code corresponding to the changed file is used as a changing method;
the determining the incremental coverage rate of the to-be-selected test case for the change code includes:
analyzing the change method through a coverage analysis tool to generate a coverage report, wherein the coverage report comprises the incremental coverage of the test case to be selected for the change method.
7. A test case screening apparatus, comprising:
the acquisition module is used for acquiring the change code; the change code comprises code updated relative to a reference code; obtaining a test case to be selected; the test cases to be selected are test cases to be added to a case library, and the test cases are used for testing the codes;
the determining module is used for determining the increment coverage rate of the test case to be selected for the change codes, wherein the increment coverage rate represents the coverage rate of the change codes when the test case to be selected is executed;
the adding module is used for adding the test cases to be selected to a case library if the incremental coverage rate meets a preset condition; otherwise, the test case to be selected is not added to the case library.
8. The test case screening apparatus according to claim 7, wherein the adding module is specifically configured to determine whether the incremental coverage is greater than a first preset coverage; and when the incremental coverage rate is greater than a first preset coverage rate, adding the test case to be selected to a case library.
9. The device for screening test cases according to claim 7, wherein the test cases to be selected include test cases to be selected with different priority levels, wherein the priority levels are determined according to business requirements;
the determining module is specifically configured to determine a first coverage rate of the change code when the highest-level to-be-selected test case is executed, where the highest-level to-be-selected test case is a test case with a highest priority level among the to-be-selected test cases;
the adding module is specifically used for calculating the use case repetition degree based on the first coverage rate and the basic coverage rate; judging whether the use case repetition degree is less than a preset repetition degree; when the use case repetition degree is smaller than the preset repetition degree, adding the test use case to be selected at the highest level to the use case library; when the repetition degree of the case is not less than the preset repetition degree, modifying the test case to be selected at the highest level; and returning to the step of determining the first coverage rate of the change code when the test case with the highest level to be selected is executed;
the determining module is specifically configured to determine, for each test case in other test cases to be selected, a second coverage rate of the change code when the test case is executed according to a sequence from high priority to low priority; the other test cases to be selected comprise test cases except the test case to be selected at the highest level in the test cases to be selected;
the adding module is specifically configured to determine whether the second coverage is greater than a coverage before the test case is executed; when the second coverage rate is larger than the coverage rate before the test case is executed, adding the test case to the case library; otherwise, the test case is not added to the case library.
10. The device according to any one of claims 7 to 9, wherein the obtaining module is specifically configured to obtain a code to be tested; searching a starting node and an ending node in the code to be detected; obtaining a change file according to the starting node and the ending node; analyzing to obtain a code implementation method corresponding to the changed file through a source code analysis tool, and calculating a method parameter value corresponding to the changed file; if the method parameter value corresponding to the changed file is different from the method parameter value corresponding to the code to be tested, the method realized by the code corresponding to the changed file is used as a changing method;
the determining module is specifically configured to analyze the change method through a coverage analysis tool to generate a coverage report, where the coverage report includes an incremental coverage of the test case to be selected for the change method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110296587.5A CN112783800B (en) | 2021-03-19 | 2021-03-19 | Test case screening method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110296587.5A CN112783800B (en) | 2021-03-19 | 2021-03-19 | Test case screening method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112783800A true CN112783800A (en) | 2021-05-11 |
| CN112783800B CN112783800B (en) | 2023-09-05 |
Family
ID=75762791
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110296587.5A Active CN112783800B (en) | 2021-03-19 | 2021-03-19 | Test case screening method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783800B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115905031A (en) * | 2023-03-14 | 2023-04-04 | 云筑信息科技(成都)有限公司 | Test case recommendation method based on accurate quality assurance system |
| CN117435514A (en) * | 2023-12-21 | 2024-01-23 | 杭州罗莱迪思科技股份有限公司 | Extraction method for smoke emission test case |
| CN117667750A (en) * | 2024-01-31 | 2024-03-08 | 北京纷扬科技有限责任公司 | Test case generation method, test device, computer equipment and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030093716A1 (en) * | 2001-11-13 | 2003-05-15 | International Business Machines Corporation | Method and apparatus for collecting persistent coverage data across software versions |
| DE102005020899A1 (en) * | 2005-05-04 | 2006-11-16 | Siemens Ag | Method for preparing test coverage analysis involves testing of a program with several threads of error, which results e.g. from lack of synchronization between the threads with an conflicting access on common resources |
| US20100058295A1 (en) * | 2008-09-02 | 2010-03-04 | International Business Machines Corporation | Dynamic Test Coverage |
| CN106557413A (en) * | 2015-09-25 | 2017-04-05 | 伊姆西公司 | Based on the method and apparatus that code coverage obtains test case |
| CN107391376A (en) * | 2017-07-26 | 2017-11-24 | 成都科来软件有限公司 | A kind of regression testing method |
| CN107515826A (en) * | 2017-08-28 | 2017-12-26 | 广州阿里巴巴文学信息技术有限公司 | Test case accurate recommendation method, device, system, equipment and storage medium |
| US10146668B1 (en) * | 2013-12-20 | 2018-12-04 | EMC IP Holding Company LLC | Modeling code coverage in software life cycle |
| CN110471829A (en) * | 2018-05-09 | 2019-11-19 | 阿里巴巴集团控股有限公司 | The inspection method and device of software code test coverage |
| CN110502447A (en) * | 2019-08-30 | 2019-11-26 | 西安邮电大学 | A kind of regression test case priority ordering method based on figure |
| CN110532174A (en) * | 2019-07-24 | 2019-12-03 | 平安科技（深圳）有限公司 | Calculate method, apparatus, computer equipment and the storage medium of incremental code coverage rate |
| CN111506505A (en) * | 2020-04-13 | 2020-08-07 | 北京奇艺世纪科技有限公司 | Test case obtaining method and device |
| CN111858292A (en) * | 2019-09-12 | 2020-10-30 | 北京嘀嘀无限科技发展有限公司 | Screening method, screening system, computer device and storage medium of test case |
-
2021
- 2021-03-19 CN CN202110296587.5A patent/CN112783800B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030093716A1 (en) * | 2001-11-13 | 2003-05-15 | International Business Machines Corporation | Method and apparatus for collecting persistent coverage data across software versions |
| DE102005020899A1 (en) * | 2005-05-04 | 2006-11-16 | Siemens Ag | Method for preparing test coverage analysis involves testing of a program with several threads of error, which results e.g. from lack of synchronization between the threads with an conflicting access on common resources |
| US20100058295A1 (en) * | 2008-09-02 | 2010-03-04 | International Business Machines Corporation | Dynamic Test Coverage |
| US10146668B1 (en) * | 2013-12-20 | 2018-12-04 | EMC IP Holding Company LLC | Modeling code coverage in software life cycle |
| CN106557413A (en) * | 2015-09-25 | 2017-04-05 | 伊姆西公司 | Based on the method and apparatus that code coverage obtains test case |
| CN107391376A (en) * | 2017-07-26 | 2017-11-24 | 成都科来软件有限公司 | A kind of regression testing method |
| CN107515826A (en) * | 2017-08-28 | 2017-12-26 | 广州阿里巴巴文学信息技术有限公司 | Test case accurate recommendation method, device, system, equipment and storage medium |
| CN110471829A (en) * | 2018-05-09 | 2019-11-19 | 阿里巴巴集团控股有限公司 | The inspection method and device of software code test coverage |
| CN110532174A (en) * | 2019-07-24 | 2019-12-03 | 平安科技（深圳）有限公司 | Calculate method, apparatus, computer equipment and the storage medium of incremental code coverage rate |
| CN110502447A (en) * | 2019-08-30 | 2019-11-26 | 西安邮电大学 | A kind of regression test case priority ordering method based on figure |
| CN111858292A (en) * | 2019-09-12 | 2020-10-30 | 北京嘀嘀无限科技发展有限公司 | Screening method, screening system, computer device and storage medium of test case |
| CN111506505A (en) * | 2020-04-13 | 2020-08-07 | 北京奇艺世纪科技有限公司 | Test case obtaining method and device |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115905031A (en) * | 2023-03-14 | 2023-04-04 | 云筑信息科技(成都)有限公司 | Test case recommendation method based on accurate quality assurance system |
| CN115905031B (en) * | 2023-03-14 | 2023-06-23 | 云筑信息科技(成都)有限公司 | Test case recommendation method based on accurate quality assurance system |
| CN117435514A (en) * | 2023-12-21 | 2024-01-23 | 杭州罗莱迪思科技股份有限公司 | Extraction method for smoke emission test case |
| CN117435514B (en) * | 2023-12-21 | 2024-03-01 | 杭州罗莱迪思科技股份有限公司 | Extraction method for smoke emission test case |
| CN117667750A (en) * | 2024-01-31 | 2024-03-08 | 北京纷扬科技有限责任公司 | Test case generation method, test device, computer equipment and storage medium |
| CN117667750B (en) * | 2024-01-31 | 2024-05-14 | 北京纷扬科技有限责任公司 | Test case generation method, test device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112783800B (en) | 2023-09-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112783800B (en) | Test case screening method and device | |
| US9720812B2 (en) | Risk-based test coverage and prioritization | |
| US8117598B2 (en) | Method and apparatus to automatically identify specific code changes to probabilistically exclude from regression | |
| KR101692817B1 (en) | Repairing corrupt software | |
| Bastani et al. | Specification inference using context-free language reachability | |
| CN111488578A (en) | Continuous vulnerability management for modern applications | |
| US8527965B2 (en) | Layered static program analysis framework for software testing | |
| Wu et al. | Combinatorial testing of restful apis | |
| US20160259636A1 (en) | Software patch evaluator | |
| Li et al. | CLORIFI: software vulnerability discovery using code clone verification | |
| CN114491566B (en) | Fuzzy test method and device based on code similarity and storage medium | |
| Bagheri et al. | Flair: efficient analysis of Android inter-component vulnerabilities in response to incremental changes | |
| Bagheri et al. | Efficient, evolutionary security analysis of interacting android apps | |
| Hong et al. | xVDB: A high-coverage approach for constructing a vulnerability database | |
| Munaiah et al. | Darwin: A static analysis dataset of malicious and benign android apps | |
| US20180129490A1 (en) | Object ordering preservation during lto link stage | |
| Muniz et al. | A qualitative analysis of variability weaknesses in configurable systems with# ifdefs | |
| CN116578282A (en) | Code generation method, device, electronic equipment and medium | |
| Nichols et al. | Fixpoint reuse for incremental javascript analysis | |
| US10002253B2 (en) | Execution of test inputs with applications in computer security assessment | |
| EP3692456A1 (en) | Binary image stack cookie protection | |
| Cody-Kenny et al. | Investigating the evolvability of web page load time | |
| CN113254325A (en) | Test case processing method and device | |
| Schuckert et al. | Diffcult SQLi Code Patterns for Static Code Analysis Tools | |
| US10896115B2 (en) | Investigation of performance bottlenecks occurring during execution of software applications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |