CN110209576A - The calculation method and relevant device of test case coverage rate - Google Patents

Abstract

The present application relates to test management in the field of test technology, and in particular to a method for calculating test case coverage and related equipment, which are applied to management equipment. The method includes: obtaining target test cases and target programs associated with target test cases; obtaining target test cases M test case identifiers of the test case and N program identifiers of the target program; keyword matching is performed between each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result ; Determine test case coverage based on matching results. The embodiment of the present application can be used to simplify the inspection method for code defects in software design.

Description

Calculation method and related equipment of test case coverage

technical field

The present application relates to the technical field of testing, in particular to a method for calculating the coverage of test cases and related equipment.

Background technique

Coverage is a measure of test completeness and a measure of test effectiveness. Currently, in the process of software development, a common method for detecting software design defects is to calculate the coverage rate of the code. The specific implementation method is as follows: inserting probe functions into the source code during the compilation stage, and quickly locating which codes are not executed by testing and running the compiled source code, thereby discovering defects in the software design. However, this code defect inspection method requires testers to have programming ability, and the steps are cumbersome and complicated.

Contents of the invention

Embodiments of the present application provide a test case coverage calculation method and related equipment, which are used to simplify the inspection method for code defects in software design.

In the first aspect, an embodiment of the present application provides a method for calculating test case coverage, which is applied to a management device, and the method includes:

Obtain the target program associated with the target test case and the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, and the target program has N subroutines, each subroutine corresponds to a program identification, the M and the N are both integers greater than or equal to 1;

Obtain M test case identifiers of the target test case and N program identifiers of the target program;

performing keyword matching on each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result;

Test case coverage is determined based on the matching results.

In the second aspect, the embodiment of the present application provides a test case coverage calculation device, which is applied to a management device, and the device includes:

The acquisition unit is used to acquire the target test case and the target program associated with the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, and the target program has N subroutines, Each subroutine corresponds to a program identification, and the M and the N are integers greater than or equal to 1; obtain M test case identifications of the target test case and N program identifications of the target program;

A matching unit, configured to perform keyword matching on each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result;

A determining unit, configured to determine test case coverage based on the matching result.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be processed by the above-mentioned The above program includes instructions for executing the steps in the method described in the first aspect of the embodiments of the present application.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the above-mentioned computer-readable storage medium is used to store a computer program, wherein the above-mentioned computer program is executed by a processor to implement the first Part or all of the steps described in the method described in one aspect.

In a fifth aspect, the embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable the computer to execute the program as implemented in the present application. For example, some or all of the steps described in the method described in the first aspect. The computer program product may be a software installation package.

It can be seen that in the embodiment of the present application, the management device first obtains the target test case and the target program associated with the target test case, and the M sub-test cases of the target test case correspond to the M test case identifiers and the N subroutines of the target program correspond to N Then each program ID is matched with each test case ID, and the test case coverage is determined based on the matching result. In the process of keyword matching each program ID with each test case ID, there is no need to insert probe functions and compile and run the target program, and the test case coverage can be obtained by directly matching the test case ID and program ID, and then The completeness of the target program can be judged by the test case coverage, thus simplifying the inspection method of code defects in software design.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a schematic flow chart of a calculation method of test case coverage provided by the embodiment of the present application;

Fig. 2 is a schematic flow chart of another calculation method of test case coverage provided by the embodiment of the present application;

FIG. 3 is a schematic structural diagram of a management device provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a test case coverage calculation device provided by an embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiment of the application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiment of the application. Obviously, the described embodiment is only It is an embodiment of a part of the application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of this application.

Each will be described in detail below.

The terms "first", "second", "third" and "fourth" in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order . Furthermore, the terms "include" and "have", as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally further includes For other steps or units inherent in these processes, methods, products or apparatuses.

Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The occurrences of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is understood explicitly and implicitly by those skilled in the art that the embodiments described herein can be combined with other embodiments.

The management device, the first electronic device and the second electronic device may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, service devices or other processing devices connected to wireless modems, and various forms of A user equipment (User Equipment, UE), a mobile station (Mobile Station, MS), a terminal device (terminal device) and so on.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a method for calculating test case coverage provided by an embodiment of the present application, which is applied to management devices. The method includes:

Step 101: Acquire the target test case and the target program associated with the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, and the target program has N sub-programs, each sub-test A program corresponds to a program identifier, and both the M and the N are integers greater than or equal to 1.

Among them, the target test case (Test Case) is a set of test inputs, execution conditions and expected results compiled for a special target, so as to test a program path or verify whether a specific requirement is met. A test case includes at least one of the following information: the name of the software or project, the version of the software or project, the name of the function module, a brief description of the test case, reference information of the test case, dependencies between this test case and other test cases, this Preconditions of the use case, number (ID) of the use case, step number, operation step description, test data description, expected and actual results, developers and testers, test execution date.

Wherein, a test case identification corresponding to each sub-test case is used to uniquely identify the sub-test case, and the test case identification can be a sub-test case ID, an application scenario of a sub-test case, or a test step of a sub-test case, or It can be the expected result of the sub-test case, and can also be other identifiers that can uniquely identify the sub-test case, which is not limited here.

Among them, the target program is a set of instructions that can be recognized and executed by a computer, and is an information tool that runs on an electronic computer and meets certain needs of people.

Wherein, a program identifier corresponding to each subroutine may be the program ID of the subroutine, the application scenario of the subroutine, or the function description of the subroutine, which is not limited here.

For example, Table 1 is a test case of the login interface. The test case of the registration interface realizes the following functions: the user enters the corresponding address in the address bar and requests to display the login interface; enters the user name and password, logs in, and the system automatically verifies and gives the corresponding Prompt information; if any information of user name or password is not entered, the system will give corresponding prompt information after login; if the verification fails for 3 consecutive times, the browser will be automatically closed.

Table 1

Step 102: Obtain M test case IDs of the target test case and N program IDs of the target program.

Further, the M test case identifiers of the target test case are test case identifiers named based on the corresponding sub-test cases during the writing stage of the target test case, and the N program identifiers are based on the corresponding sub-test case identifiers during the programming stage of the target program. The program ID of the subroutine named.

Step 103: performing keyword matching on each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result.

Wherein, the specific implementation manner of carrying out keyword matching between each program identifier in the N program identifiers and each test case identifier in the M test case identifiers may be: The keywords of the program identification i are keyword-matched with the keywords of each test case identification in the M test case identifications, until the keywords of all the program identifications in the N program identifications are all matched with the M test case identifications. The keyword of each test case identification in the test case identification carries out keyword matching; It can also be the keyword of the test case identification j in the M test case identifications and each program in the N program identifications The keywords of identification carry out keyword matching, until the keywords of all test case identifications in the M test case identifications all carry out keyword matching with the keywords of each program identification in the N program identifications, where Not limited.

Table 2

For example, Table 2 is a one-to-one correspondence table between the obtained test case identifier of the login interface test case and the program identifier of the login interface test application program. The specific matching method can be to combine the keywords "initial page display" of "initial page display" in the test case identification with the keywords "initial page display" and "User Log In_1.0" of "initial page display 1.0" in the program identification Keyword "User Log In" for "Username - Fault Tolerant Authentication 1.0" Keyword "Username - Fault Tolerant Authentication" "Username - Fault Tolerant Authentication 2.0" Keyword "Username - Fault Tolerant Authentication ", the keyword "username-fault-tolerant authentication" of "username-fault-tolerant authentication 3.0", the keyword "system login-success" of "system login-success 1.0" for keyword matching, or the program identification The keyword "initial page display" of "initial page display 1.0" in the test case identification and the keyword "initial page display" of "initial page display" and the keyword "username- Input verification", "username-fault-tolerant verification" keywords "username-fault-tolerant verification", "password-password entry" keywords "password-password entry", "system login-success" keywords" System Login-Success" for keyword matching.

Step 104: Determine test case coverage based on the matching result.

In an implementation of the present application, the matching result includes Q successful matching records, and each successful matching record includes a test case identifier and at least one program identifier that matches the one test case identifier, and the matching The results determine test case coverage, including:

Determine the Q test case identifiers recorded in the Q matching success records, the Q is an integer greater than or equal to 0 and less than or equal to M;

The test case coverage is determined based on a first formula, the first formula is: P=Q/M, and P is the test case coverage.

table 3

For example, Table 3 is a one-to-one correspondence table between the test case identifiers of another obtained login interface test cases and the program identifiers of the login interface test applications. According to step 103, three matching records can be obtained: the test case identifier "initial page display" of the test case TC1 matches successfully with the program identifier "initial page display 1.0" of the subroutine AP1, and the test case identifier "username" of the test case TC3 - Fault Tolerance Verification" and subroutine AP2's program identification "Username - Fault Tolerance Verification 1.0", AP3's program identification "User Name - Fault Tolerance Verification 2.0", AP5's program identification "Username - Fault Tolerance Verification 3.0" The matching is successful, the test case identifier "system login-success" of the test case TC5 and the program identifier "system login-success 1.0" of the subroutine AP6 match successfully. Therefore, based on the first formula, it can be determined that the test case coverage rate in Table 3 is 60%.

It can be seen that in the embodiment of the present application, the management device first obtains the target test case and the target program associated with the target test case, and the M sub-test cases of the target test case correspond to the M test case identifiers and the N subroutines of the target program correspond to N Then each program ID is matched with each test case ID, and the test case coverage is determined based on the matching result. In the process of keyword matching each program ID with each test case ID, there is no need to insert probe functions and compile and run the target program, and the test case coverage can be obtained by directly matching the test case ID and program ID, and then The completeness of the target program can be judged by the test case coverage, thus simplifying the inspection method of code defects in software design.

In an implementation manner of the present application, the management device includes an output module, and the method further includes:

Outputting the Q test case IDs, the M-Q test case IDs in the M test case IDs except the Q test case IDs and the test case coverage rate through the output module.

Further, output the Q test case identifications, the M-Q test case identifications and the test case coverage in the M test case identifications except the Q test case identifications through the output module, including :

Determining the first output parameters of the Q test case identifications, the second output parameters of the M-Q test case identifications except the Q test case identifications in the M test case identifications and the test case coverage The third output parameter of ;

Outputting the Q test case identifiers based on the first output parameter through the output module, outputting the M-Q test case identifiers based on the second output parameter, and outputting the test case based on the first output parameter coverage.

Wherein, the first output parameter, the first output parameter or the third output parameter includes at least one of the following: font color, font thickness, font size, and font background. The first output parameter, the first output parameter and the third output parameter may be the same or different, which are not limited here.

It can be seen that, in the embodiment of the present application, based on the first output parameter output matching successful Q test case identification, based on the second output parameter output matching failure M-Q test case identification, based on the third output parameter output test case coverage Different output parameters display different parts, so as to remind users and facilitate users to analyze and process test case coverage later.

In an implementation of the present application, the method further includes:

When the test case coverage rate is lower than or equal to the preset threshold, a first instruction is sent to the first electronic device of the tester associated with the management device, the first instruction carries the M-Q test case identifiers, so The first instruction is used to request the tester to select K test case identifiers from the M-Q test case identifiers, where K is an integer greater than 0 and less than or equal to M-Q;

When receiving the first response sent by the first electronic device in response to the first instruction and carrying the K test case identifiers selected by the tester, the second electronic device of the developer associated with the management device Sending a second instruction, the second instruction carrying the selected K test case identifiers, the second instruction is used to notify the R&D personnel to add K subroutines to the target program, and the K subroutines The corresponding K subroutine identifiers can be successfully matched with the selected K test case identifiers.

Wherein, the preset threshold may be 40%, 60%, 80% or other values, which are not limited herein.

For example, assuming that the preset threshold is 80%, as shown in Table 3, the test case coverage rate is 60%, and a first instruction is sent to the first electronic device of the tester associated with the management device, and the first instruction carries The two test cases are identified as "username entry-verification" and "password-password entry", and the selected K test cases are identified as "username entry-verification" and/or "password-password entry" .

It can be seen that in the embodiment of the present application, when the test case coverage rate is lower than or equal to the preset threshold, a first instruction is sent to the first electronic device of the tester associated with the management device to remind the tester of the test case Low coverage; send a second instruction to the second electronic device of the R&D personnel associated with the management device to notify the R&D personnel to add new subroutines according to the requirements of the testers, intelligently solving the problem of low test case coverage question.

In an implementation of the present application, the method further includes:

When receiving the second response sent by the second electronic device in response to the second instruction and carrying the K subroutines added by the R&D personnel, adding the K added subroutines to the target program, and compiling the target program including the added K subroutines, so that the added K subroutines can be executed.

It can be seen that, in the embodiment of the present application, when receiving the second response sent by the second electronic device for the second instruction and carrying the K subroutines added by the R&D personnel, the added K subroutines are added to the target program, And compiling the target program including the added K subroutines does not need to update the target program and compile the target program artificially, which simplifies the process of updating and compiling the target program, thereby improving work efficiency.

In an implementation manner of the present application, before the compiling the target program including the K subroutines, the method further includes:

Determining multiple program identifiers matched by Q test cases in the matching result;

determining a plurality of subroutines corresponding to the plurality of program identifiers;

Deleting subroutines in the N subroutines except for the plurality of subroutines corresponding to the plurality of program identifiers.

For example, as shown in Table 3, it is assumed that there are 10 subroutines: AP1, AP2, AP3, AP4, AP5, AP6, AP7, AP8, AP9, AP10, among the 3 successful matching records, the 3 test case identifiers are successfully matched The five subroutines corresponding to the five program identifiers are: AP1, AP2, AP3, AP5, and AP6, and the subroutines AP4, AP7, AP8, AP9, and AP10 are deleted.

It can be seen that in the embodiment of the present application, redundant subroutines are deleted to improve the simplicity and readability of the source code of the target program, thereby saving the memory of the electronic device.

In an implementation of the present application, if there are H matching successful records among the Q successful records, a test case identifier included in at least two program identifiers matches, before compiling the target program including the K subroutines, , the method also includes:

Determine at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records;

Obtain the editing time of at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records;

Delete the target subroutine in the at least two subroutines corresponding to the at least two program identifiers included in each of the H matching success records, and the editing time of the target subroutine deletion is earlier than or equal to the preset time .

For example, as shown in Table 3, among the five subroutines AP1, AP2, AP3, AP5, and AP6, the program identifiers of the three subroutines AP2, AP3, and AP5 successfully match the test case identifier "user name-fault tolerance verification" , assuming that the editing time of AP2 is January 18, 2019, the editing time of AP3 is January 20, 2019, and the editing time of AP5 is January 23, 2019, and the preset time is January 20, 2019, then Delete subroutines AP2 and AP3.

It can be seen that in the embodiment of the present application, the garbage generated by the old version of the target program during the update process is deleted based on the editing time, which improves the simplicity and readability of the source code of the target program, thereby saving the memory of the electronic device.

Consistent with the embodiment shown in FIG. 1, please refer to FIG. 2. FIG. 2 is a schematic flowchart of another calculation method for test case coverage provided by the embodiment of the present application, which is applied to management devices. The method includes:

Step 201: Acquire the target test case and the target program associated with the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, the target program has N sub-programs, each sub-test A program corresponds to a program identifier, and both the M and the N are integers greater than or equal to 1.

Step 202: Obtain M test case IDs of the target test case and N program IDs of the target program.

Step 203: perform keyword matching on each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result.

Step 204: The matching result includes Q successful matching records, and each successful matching record includes a test case ID that matches at least one program ID that matches the one test case ID, and determines the number of records recorded in the Q successful matching records Q test case identifiers, where Q is an integer greater than or equal to 0 and less than or equal to M.

Step 205: Determine the test case coverage rate based on the first formula, the first formula is: P=Q/M, and the P is the test case coverage rate.

Step 206: The management device includes an output module, through which the Q test case identifiers, the M-Q test case identifiers except the Q test case identifiers among the M test case identifiers and The test case coverage.

Step 207: When the test case coverage is lower than or equal to the preset threshold, send a first instruction to the first electronic device of the tester associated with the management device, the first instruction carrying the M-Q test cases identification, the first instruction is used to request the tester to select K test case identifications from the M-Q test case identifications, where K is an integer greater than 0 and less than or equal to M-Q.

Step 208: When receiving the first response sent by the first electronic device to the first instruction and carrying the K test case identifiers selected by the tester, report to the first response of the developer associated with the management device The second electronic device sends a second instruction, the second instruction carries the selected K test case identifiers, and the second instruction is used to notify the research and development personnel to add K subroutines to the target program, the The K subroutine identifiers corresponding to the K subroutines can successfully match the selected K test case identifiers.

Step 209: Determine multiple program identifiers matched by the Q test cases in the matching results.

Step 210: Determine a plurality of subroutines corresponding to the plurality of program identifiers.

Step 211: Delete subroutines among the N subroutines except for the plurality of subroutines corresponding to the plurality of program identifiers.

Step 212: If a test case identifier included in H successful matching records among the Q successful records matches at least two program identifiers, determine at least two test case identifiers included in each of the H successful matching records. The program identifies at least two subroutines to which it corresponds.

Step 213: Obtain the editing time of at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records.

Step 214: Delete the target subroutine among the at least two subroutines corresponding to the at least two program identifiers included in each of the H successful matching records, and the editing time of the target subroutine deletion is earlier than or equal to preset time.

Step 215: Add the added K subroutines to the target program when receiving the second response sent by the second electronic device in response to the second instruction and carrying the K subroutines added by the R&D personnel , and compiling the target program including the added K subroutines, so that the added K subroutines can be executed.

It should be noted that, for the specific implementation process of this embodiment, reference may be made to the specific implementation process described in the foregoing method embodiments, which will not be described here again.

Consistent with the embodiment shown in Figure 1 and Figure 2 above, please refer to Figure 3, Figure 3 is a schematic structural diagram of an electronic device provided by an embodiment of the present application, including a processor, a memory, a communication interface, and one or more A program, wherein the above-mentioned one or more programs are stored in the above-mentioned memory and configured to be executed by the above-mentioned processor, and the above-mentioned program includes instructions for performing the following steps:

Obtain the target program associated with the target test case and the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, and the target program has N subroutines, each subroutine corresponds to a program identification, the M and the N are both integers greater than or equal to 1;

Obtain M test case identifiers of the target test case and N program identifiers of the target program;

performing keyword matching on each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result;

Test case coverage is determined based on the matching results.

It can be seen that in the embodiment of the present application, the management device first obtains the target test case and the target program associated with the target test case, and the M sub-test cases of the target test case correspond to the M test case identifiers and the N subroutines of the target program correspond to N Then each program ID is matched with each test case ID, and the test case coverage is determined based on the matching result. In the process of keyword matching each program ID with each test case ID, there is no need to insert probe functions and compile and run the target program, and the test case coverage can be obtained by directly matching the test case ID and program ID, and then The completeness of the target program can be judged by the test case coverage, thus simplifying the inspection method of code defects in software design.

In an implementation of the present application, the matching result includes Q successful matching records, and each successful matching record includes a test case identifier and at least one program identifier that matches the one test case identifier, and based on the matching As a result of determining test case coverage, the above procedure includes instructions specifically for performing the following steps:

Determine the Q test case identifiers recorded in the Q matching success records, the Q is an integer greater than or equal to 0 and less than or equal to M;

The test case coverage is determined based on a first formula, the first formula is: P=Q/M, and P is the test case coverage.

In an implementation manner of the present application, the management device includes an output module, and the above-mentioned program includes instructions for performing the following steps:

Outputting the Q test case IDs, the M-Q test case IDs in the M test case IDs except the Q test case IDs and the test case coverage rate through the output module.

In an implementation of the present application, the above-mentioned program includes instructions for performing the following steps:

When the test case coverage rate is lower than or equal to the preset threshold, a first instruction is sent to the first electronic device of the tester associated with the management device, the first instruction carries the M-Q test case identifiers, so The first instruction is used to request the tester to determine K test case identifiers from the M-Q test case identifiers, where K is an integer greater than 0 and less than or equal to M-Q;

When receiving the first response sent by the first electronic device in response to the first instruction and carrying the K test case identifiers selected by the tester, the second electronic device of the developer associated with the management device Sending a second instruction, the second instruction carrying the selected K test case identifiers, the second instruction is used to notify the R&D personnel to add K subroutines to the target program, and the K subroutines The corresponding K subroutine identifiers can be successfully matched with the selected K test case identifiers.

In an implementation of the present application, the above-mentioned program includes instructions for performing the following steps:

When receiving the second response sent by the second electronic device in response to the second instruction and carrying the K subroutines added by the R&D personnel, adding the K added subroutines to the target program, and compiling the target program including the added K subroutines, so that the added K subroutines can be executed.

In an implementation manner of the present application, before compiling the target program including the K subroutines, the above program includes instructions for performing the following steps:

Determining multiple program identifiers matched by Q test cases in the matching result;

determining a plurality of subroutines corresponding to the plurality of program identifiers;

Deleting subroutines in the N subroutines except for the plurality of subroutines corresponding to the plurality of program identifiers.

In an implementation of the present application, if there are H matching successful records among the Q successful records, a test case identifier included in at least two program identifiers matches, before compiling the target program including the K subroutines, The above program includes instructions to also perform the following steps:

Determine at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records;

Obtain the editing time of at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records;

Delete the target subroutine in the at least two subroutines corresponding to the at least two program identifiers included in each of the H matching success records, and the editing time of the target subroutine deletion is earlier than or equal to the preset time .

It should be noted that, for the specific implementation process of this embodiment, reference may be made to the specific implementation process described in the foregoing method embodiments, which will not be described here again.

The foregoing embodiments mainly introduce the solutions of the embodiments of the present application from the perspective of executing a process on the method side. It can be understood that, in order to realize the above functions, the electronic device includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The embodiment of the present application may divide the electronic device into functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated units can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic, and is only a logical function division, and there may be another division manner in actual implementation.

The following are the device embodiments of the present application, and the device embodiments of the present application are used to implement the methods implemented by the method embodiments of the present application. Please refer to Fig. 4, a test case coverage calculation device provided by an embodiment of the present application is applied to a management device, and the test case coverage calculation device includes:

The obtaining unit 401 is used to obtain the target test case and the target program associated with the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, and the target program has N sub-programs , each subroutine corresponds to a program identification, and the M and the N are integers greater than or equal to 1; obtain the test case identification of each subroutine of the target test case and the test case identification of each subroutine of the target program Program ID;

A matching unit 402, configured to perform keyword matching between each program identifier in the N program identifiers and each test case identifier in the M test case identifiers, to obtain a matching result;

A determining unit 403, configured to determine a test case coverage rate based on the matching result.

It can be seen that in the embodiment of the present application, the management device first obtains the target test case and the target program associated with the target test case, and the M sub-test cases of the target test case correspond to the M test case identifiers and the N subroutines of the target program correspond to N Then each program ID is matched with each test case ID, and the test case coverage is determined based on the matching result. In the process of keyword matching each program ID with each test case ID, there is no need to insert probe functions and compile and run the target program, and the test case coverage can be obtained by directly matching the test case ID and program ID, and then The completeness of the target program can be judged by the test case coverage, thus simplifying the inspection method of code defects in software design.

In an implementation of the present application, the matching result includes Q successful matching records, and each successful matching record includes a test case identifier and a program identifier that matches the one test case identifier, and based on the matching result In terms of determining test case coverage, the determination unit 403 is specifically used for:

Determine the Q test case identifications recorded in the Q matching success records, the Q is an integer greater than or equal to 0 and less than or equal to M; determine the test case coverage based on the first formula, the first formula is: P=Q/M, the P is the test case coverage.

In an implementation manner of the present application, the management device includes an output module, and the device further includes an output unit 404, configured to:

Outputting the Q test case IDs, the M-Q test case IDs in the M test case IDs except the Q test case IDs and the test case coverage rate through the output module.

In an implementation of the present application, the device further includes a communication unit 405, configured to:

When the test case coverage rate is lower than or equal to the preset threshold, a first instruction is sent to the first electronic device of the tester associated with the management device, the first instruction carries the M-Q test case identifiers, so The first instruction is used to request the tester to determine K test case identifiers from the M-Q test case identifiers, where K is an integer greater than 0 and less than or equal to M-Q;

When receiving the first response sent by the first electronic device in response to the first instruction and carrying the K test case identifiers selected by the tester, the second electronic device of the developer associated with the management device Sending a second instruction, the second instruction carrying the selected K test case identifiers, the second instruction is used to notify the R&D personnel to add K subroutines to the target program, and the K subroutines The corresponding K subroutine identifiers can be successfully matched with the selected K test case identifiers.

In an implementation of the present application, the device further includes an adding compiling unit 406, configured to:

When receiving the second response sent by the second electronic device in response to the second instruction and carrying the K subroutines added by the R&D personnel, adding the K added subroutines to the target program, and compiling the target program including the added K subroutines, so that the added K subroutines can be executed.

In an implementation manner of the present application, before compiling the target program including the K subroutines, the determining unit 403 is further configured to determine a plurality of program identifiers matched by the Q test cases in the matching result; determine the A plurality of subroutines corresponding to the plurality of program identifiers;

The apparatus further includes a deleting unit 407, configured to delete subprograms among the N subprograms except the multiple subprograms corresponding to the multiple program identifiers.

In an implementation of the present application, if there are H matching successful records among the Q successful records, a test case identifier included in at least two program identifiers matches, before compiling the target program including the K subroutines, The determining unit 403 is further configured to determine at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records;

The acquiring unit 401 is further configured to acquire the editing time of at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records;

The deleting unit 407 is further configured to delete target subprograms among at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records, and the deleted target subprograms The editing time is earlier than or equal to the preset time.

It should be noted that the acquiring unit 401 , the matching unit 402 , the determining unit 403 , the output unit 404 , the adding and compiling unit 406 and the deleting unit 407 can be implemented by a processor, and the communication unit 405 can be implemented by a communication interface.

An embodiment of the present application further provides a computer storage medium, wherein the computer storage medium is used to store a computer program, and the computer program is used by a processor to execute some or all steps of any method described in the above method embodiments.

An embodiment of the present application also provides a computer program product, the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable the computer to execute any one of the methods described in the above method embodiments. Some or all steps of the method. The computer program product may be a software installation package.

It should be noted that for the foregoing method embodiments, for the sake of simple description, they are expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described action sequence. Depending on the application, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by this application.

In the foregoing embodiments, the descriptions of each embodiment have their own emphases, and for parts not described in detail in a certain embodiment, reference may be made to relevant descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the above units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components can be combined or integrated. to another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical or other forms.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the above-mentioned integrated units are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory. Several instructions are included to make a computer device (which may be a personal computer, server or network device, etc.) execute all or part of the steps of the above-mentioned methods in various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable memory, and the memory can include: a flash disk , Read-only memory (English: Read-Only Memory, abbreviated: ROM), random access device (English: Random Access Memory, abbreviated: RAM), magnetic disk or optical disk, etc.

The embodiments of the present application have been introduced in detail above, and specific examples have been used in this paper to illustrate the principles and implementation methods of the present application. The descriptions of the above embodiments are only used to help understand the methods and core ideas of the present application; meanwhile, for Those skilled in the art will have changes in specific implementation methods and application scopes based on the ideas of the present application. In summary, the contents of this specification should not be construed as limiting the present application.

Claims (10)

1. A calculation method for test case coverage, characterized in that it is applied to management equipment, and the method comprises: Obtain the target program associated with the target test case and the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, and the target program has N subroutines, each subroutine corresponds to a program identification, the M and the N are both integers greater than or equal to 1; Obtain M test case identifiers of the target test case and N program identifiers of the target program; performing keyword matching on each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result; Test case coverage is determined based on the matching result. 2. The method according to claim 1, wherein the matching result includes Q matching success records, and each matching success record includes at least one program identification that a test case identification matches with the test case identification , the determination of test case coverage based on the matching result includes: Determine the Q test case identifiers recorded in the Q matching success records, the Q is an integer greater than or equal to 0 and less than or equal to M; The test case coverage is determined based on a first formula, the first formula is: P=Q/M, and P is the test case coverage. 3. The method according to claim 2, wherein the management device comprises an output module, and the method further comprises: Outputting the Q test case IDs, the M-Q test case IDs in the M test case IDs except the Q test case IDs and the test case coverage rate through the output module. 4. The method according to claim 2 or 3, characterized in that the method further comprises: When the test case coverage rate is lower than or equal to the preset threshold, a first instruction is sent to the first electronic device of the tester associated with the management device, the first instruction carries the M-Q test case identifiers, so The first instruction is used to request the tester to select K test case identifiers from the M-Q test case identifiers, where K is an integer greater than 0 and less than or equal to M-Q; When receiving the first response sent by the first electronic device in response to the first instruction and carrying the K test case identifiers selected by the tester, the second electronic device of the developer associated with the management device Sending a second instruction, the second instruction carrying the selected K test case identifiers, the second instruction is used to notify the R&D personnel to add K subroutines to the target program, and the K subroutines The corresponding K subroutine identifiers can be successfully matched with the selected K test case identifiers. 5. method according to claim 4, is characterized in that, described method also comprises: Adding the added K subroutines to the target program when receiving the second response sent by the second electronic device in response to the second instruction and carrying the K subroutines added by the R&D personnel, and compiling the target program including the added K subroutines, so that the added K subroutines can be executed. 6. method according to claim 5, is characterized in that, before described compiling comprises the object program of described K subroutines, described method also comprises: Determining multiple program identifiers matched by Q test cases in the matching results; determining a plurality of subroutines corresponding to the plurality of program identifiers; Deleting subroutines in the N subroutines except for the plurality of subroutines corresponding to the plurality of program identifiers. 7. The method according to claim 6, wherein if a test case identification included in H matching successful records is matched with at least two program identifications in the Q successful records, the compilation includes the K Before the target program of subroutines, the method also includes: Determine at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records; Obtain the editing time of at least two subprograms corresponding to at least two program identifiers included in each of the H successful matching records; Delete the target subroutine in the at least two subroutines corresponding to the at least two program identifiers included in each of the H matching success records, and the editing time of the target subroutine deletion is earlier than or equal to the preset time . 8. A computing device for test case coverage, characterized in that it is applied to management equipment, and the device includes: The acquisition unit is used to acquire the target test case and the target program associated with the target test case, the target test case includes M sub-test cases, each sub-test case corresponds to a test case identifier, and the target program has N subroutines, Each subroutine corresponds to a program identification, and the M and the N are integers greater than or equal to 1; obtain M test case identifications of the target test case and N program identifications of the target program; A matching unit, configured to perform keyword matching on each program identifier in the N program identifiers and each test case identifier in the M test case identifiers to obtain a matching result; A determining unit, configured to determine test case coverage based on the matching result. 9. An electronic device, comprising a processor, a memory, a communication interface, and one or more programs, the one or more programs being stored in the memory and configured by the processor Execution, the program includes instructions for executing the steps in the method according to any one of claims 1-7. 10. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program, and the computer program is executed by a processor to implement the method according to any one of claims 1-7. method.