CN113590495A

CN113590495A - Method, device, equipment and storage medium for determining test coverage rate

Info

Publication number: CN113590495A
Application number: CN202111013201.1A
Authority: CN
Inventors: 李超
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2021-08-31
Filing date: 2021-08-31
Publication date: 2021-11-02

Abstract

The invention discloses a method, a device, equipment and a storage medium for determining test coverage. The method comprises the following steps: acquiring chain proportion corresponding to each execution chain in the code to be tested; determining an execution chain in the code to be tested, which is respectively covered by each test case of the code to be tested in the execution process, so as to obtain a test case covering result; for each execution chain in the code to be tested, determining the number of test cases covering the current execution chain according to the test case covering result, and determining the case covering proportion corresponding to the current execution chain; and generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain. By the technical scheme, the coverage rate of the test case can be evaluated in a standard, scientific and quantitative manner, and the evaluation accuracy of the coverage rate is improved, so that the effect of selecting a more comprehensive test case according to an evaluation result to ensure the comprehensiveness of a test range is achieved.

Description

Method, device, equipment and storage medium for determining test coverage rate

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to a method, a device, equipment and a storage medium for determining test coverage.

Background

Under the rhythm of internet + distributed development, more and more projects are provided, the relationship among systems is complex, and when the requirements are changed, the related software systems are more and more, and the affected functions are required to be tested.

The current test methods are mainly of two kinds: one is to collect the real flow on the line as the test case according to the interface dimension, and use the collected test case to test the corresponding interface; and the other method is to manually write a test case according to the requirement and use the test case for testing.

In the process of implementing the invention, at least the following problems are found in the prior art: in order to ensure the comprehensiveness of the test range and avoid the on-line problem, the test coverage of the test case needs to be determined, but at present, there is no standard, scientific and quantifiable method for determining the test coverage.

Disclosure of Invention

The embodiment of the invention provides a method, a device, equipment and a storage medium for determining test coverage rate, so as to realize standard, scientific and quantitative evaluation of the coverage rate of a test case and improve the evaluation accuracy of the coverage rate.

In a first aspect, an embodiment of the present invention provides a method for determining a test coverage, including:

acquiring chain proportion corresponding to each execution chain in the code to be tested; the chain proportion characterization represents the proportion of the number of execution nodes contained in the corresponding execution chain to the total number of execution nodes contained in the code to be tested;

determining an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, so as to obtain a test case covering result;

for each execution chain in the code to be tested, determining the number of test cases covering the current execution chain according to the test case covering result, and determining the case covering proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of the test cases;

and generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain.

In a second aspect, an embodiment of the present invention further provides an apparatus for determining a test coverage, where the apparatus includes:

the chain proportion acquisition module is used for acquiring the chain proportion corresponding to each execution chain in the code to be tested; the chain proportion characterization represents the proportion of the number of execution nodes contained in the corresponding execution chain to the total number of execution nodes contained in the code to be tested;

the execution chain determining module is used for determining an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, so as to obtain a test case covering result;

the coverage proportion determining module is used for determining the number of the test cases covering the current execution chain according to the test case coverage result for each execution chain in the code to be tested, and determining the case coverage proportion corresponding to the current execution chain according to the number of the test cases covering the current execution chain and the total number of the test cases;

and the result determining module is used for generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain.

In a third aspect, an embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the method for determining the test coverage according to any one of the embodiments of the present invention.

In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method for determining the test coverage according to any one of the embodiments of the present invention.

The embodiment of the invention obtains the chain proportion corresponding to each execution chain in the code to be tested, determines the execution chains in the code to be tested which are respectively covered by each test case of the code to be tested in the execution process, obtains the test case coverage result, determines the number of the test cases covering the current execution chain according to the test case coverage result for each execution chain in the code to be tested, determines the case coverage proportion corresponding to the current execution chain according to the number of the test cases covering the current execution chain and the total number of the test cases, generates the determination result of the test coverage rate according to the case coverage proportion and the chain proportion corresponding to each execution chain, solves the problem that no standard, scientific and quantifiable method for determining the test coverage rate exists at present, and the test coverage rate is not evaluated completely, the coverage rate of the test cases is evaluated in a standard, scientific and quantitative mode, and the evaluation accuracy of the coverage rate is improved, so that the effect that more comprehensive test cases can be selected according to the evaluation result to ensure the comprehensiveness of the test range is achieved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

Fig. 1 is a flowchart of a method for determining test coverage according to a first embodiment of the present invention;

FIG. 2 is a flowchart of a method for determining test coverage according to a second embodiment of the present invention;

FIG. 3 is a diagram of a syntax tree in an embodiment of the present invention;

FIG. 4 is a schematic diagram of an execution chain and execution nodes in an embodiment of the present invention;

FIG. 5 is a diagram illustrating the determination of test coverage in an embodiment of the present invention;

fig. 6 is a flowchart of a method for determining test coverage according to a third embodiment of the present invention;

FIG. 7 is a block diagram of a test coverage management system according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a method for determining test coverage in an embodiment of the present invention;

fig. 9 is a schematic diagram of a device for determining coverage rate in the fourth embodiment of the present invention;

fig. 10 is a schematic structural diagram of a computer device in the fifth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

Example one

Fig. 1 is a flowchart of a method for determining test coverage according to an embodiment of the present invention, where this embodiment is applicable to a case of determining test coverage of a test case in a process of executing a code to be tested, and the method may be executed by a device for determining test coverage according to an embodiment of the present invention, where the device may be implemented in a software and/or hardware manner, as shown in fig. 1, and the method specifically includes the following steps:

s110, acquiring the chain proportion corresponding to each execution chain in the code to be tested.

The execution chain refers to a possible track of code execution analyzed in a syntax tree, and may be understood as a hierarchical chain formed by a plurality of execution nodes of a code to be tested in an execution process, and an execution node may be understood as a syntax structure in a program code, such as a packet, a type, a modifier, an operator, an interface, a return value, or a code comment, which may be used as an execution node, and generally, a line of code may be used as an execution node. One code to be tested usually contains a plurality of execution chains.

Specifically, the code to be tested is obtained and analyzed, and the chain proportion corresponding to each execution chain is determined. The chain proportion representation corresponds to the proportion of the number of the execution nodes contained in the execution chain to the total number of the execution nodes contained in the code to be tested, and reflects the proportion of the number of the execution nodes of each execution chain to the total number of the execution nodes contained in the code to be tested.

Exemplarily, acquiring the number N of execution chains in the code to be tested, determining the number runPointNum of execution nodes included in each execution chain, and recording the number runPointDeep as a chain depth runPointDeep, where the chain depth of the ith execution chain is runPointDeep _ i ═ sum (runPointNum); determining the total number of execution nodes contained in each execution chain, and recording as method depth, if the method depth of the code to be tested is

The chain weight is the proportion of the number of execution nodes contained in the corresponding execution chain to the total number of execution nodes contained in the code to be tested, that is, the chain weight runPointRatio of the ith execution chain is the weight of the chain depth runPointDeep _ i and the method depth of the ith execution chain, that is, runPointRatio _ i is runPointDeep _ i/methoddeep.

Optionally, the code to be tested includes a code that can call an interface in the software system.

S120, determining an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, and obtaining a test case covering result.

Wherein a test case may be understood as an example written or selected by a tester for testing code to be tested. Generally, in order to test each function of the code to be tested, a plurality of different test cases are adopted to sequentially execute the code to be tested, and the selection of the test cases is not limited in the embodiment of the invention.

The test case coverage result is used for representing an execution chain in the test code covered by each test case in the execution process, the test case coverage result can be represented by a data table, a mapping table or other forms, and the embodiment of the invention does not limit the representation form of the test case coverage result.

Specifically, in the process of executing the code to be tested by using each test case, an execution chain in the code to be tested covered by each test case is determined, that is, an execution chain formed by execution nodes of each test case in the execution process included in the code to be tested is determined.

And S130, for each execution chain in the code to be tested, determining the number of test cases covering the current execution chain according to the test case covering result, and determining the case covering proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of the test cases.

The case coverage ratio corresponding to the current execution chain can be understood as the number of times that the current execution chain is executed by each test case.

Illustratively, in the process of executing the code to be tested by adopting different test cases, the total number of the test cases is recorded and recorded as TestCaseNum, and the execution chains in the test code respectively covered by each test case in the execution process are obtained according to the test case covering result, so that the number of the test cases covering the current execution chain for each execution chain in the code to be tested is obtained through statistics and recorded as TestCaseNum _ i; and determining the ratio of the number of the test cases covering the current execution chain to the number of the test cases as a case covering ratio corresponding to the current execution chain, and recording the case covering ratio as coverage ratio _ i, namely coverage ratio _ i is TestCaseNum _ i/TestCaseNum.

And S140, generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain.

Illustratively, according to the use case coverage ratio coverRatio _ i and the chain weight runPointRatio _ i respectively corresponding to each execution chain, the size relationship, the difference value and the ratio of the use case coverage ratio and the chain weight respectively corresponding to each execution chain can be obtained. Therefore, the determination result of the test coverage can be generated according to the magnitude relationship, the difference value or the ratio of the case coverage ratio and the chain proportion respectively corresponding to each execution chain, or the case coverage ratio and the chain proportion respectively corresponding to each execution chain can be directly used as the determination result of the test coverage to evaluate the test coverage of the test case.

The manner of evaluating the test coverage of the test case according to the determination result of the test coverage may be: if the case coverage proportion respectively corresponding to the execution chains is smaller than the specific gravity of the chains, the case is not in place of the execution chains, and a test case capable of covering the execution chains needs to be added; if the case coverage proportion respectively corresponding to the execution chains is larger than or equal to the chain weight, the test cases are in place for the execution chains, and the test cases covering the execution chains do not need to be added.

In the technical scheme of this embodiment, by obtaining chain weights respectively corresponding to execution chains in a code to be tested, determining the execution chains in the code to be tested, which are respectively covered by the execution chains in the execution process for each test case of the code to be tested, to obtain a test case coverage result, determining the number of the test cases covering the current execution chain according to the test case coverage result for each execution chain in the code to be tested, determining a case coverage ratio corresponding to the current execution chain according to the number of the test cases covering the current execution chain and the total number of the test cases, generating a determination result of the test coverage ratio according to the case coverage ratio and the chain weights respectively corresponding to each execution chain, the coverage ratio of the test cases can be evaluated in a standard, scientific and quantitative manner, and the evaluation accuracy of the coverage ratio is improved, therefore, more comprehensive test cases can be selected according to the evaluation result to ensure the comprehensiveness of the test range.

Example two

Fig. 2 is a flowchart of a method for determining test coverage in a second embodiment of the present invention, where the embodiment is optimized based on the above embodiment, and in the embodiment, obtaining chain weights corresponding to execution chains in a code to be tested includes: analyzing the code to be tested to obtain a grammar tree corresponding to the code to be tested; analyzing execution chains contained in the code to be tested according to the syntax tree, and determining execution nodes contained in each execution chain; and for each execution chain, determining the chain specific weight corresponding to the current execution chain according to the number of execution nodes contained in the current execution chain and the total number of execution nodes contained in the code to be tested.

As shown in fig. 2, the method of this embodiment specifically includes the following steps:

s210, acquiring execution chains contained in the code to be tested and acquired by an acquisition plug-in arranged in a service system, and information of execution nodes contained in each execution chain.

Wherein the business system may be a system for executing code to be tested to implement a specific function. The acquisition plug-in is a computer application that provides predetermined acquisition functionality by interacting with a host application. Optionally, the collection plug-in may include an agent plug-in or a plugin plug-in.

In this embodiment, the collection plug-in is introduced into the business system executing the code to be tested by the project management tool maven. When the service system is started, the collection plug-in is loaded through the Spring application starter, the code to be tested is analyzed through the collection plug-in, and execution chains contained in the code to be tested and information of execution nodes contained in each execution chain are collected. The information of the execution nodes contained in the execution chain may be the number of execution nodes.

Optionally, the acquiring plugin acquires information of execution chains included in the code to be tested and execution nodes included in each execution chain, where the acquiring plugin acquires information of the execution chains included in the code to be tested and the execution nodes included in each execution chain, and the acquiring plugin includes:

analyzing the code to be tested to obtain a grammar tree corresponding to the code to be tested;

and analyzing the execution chains contained in the code to be tested and the information of the execution nodes contained in each execution chain according to the syntax tree.

Where a syntax tree is a tree representation of the abstract syntax structure of the code. In the syntax tree, the execution chain may be a path from a root node to a leaf node of the syntax tree, and the execution nodes in the execution chain may be nodes of the syntax tree.

Specifically, the JavaScript Parser can parse the code to be tested to obtain the syntax tree corresponding to the code to be tested, and the embodiment of the present invention does not limit the parsing tool. And further analyzing the grammar tree to obtain the execution chains contained in the code to be tested and the information of the execution nodes contained in each execution chain.

An example of a code to be tested is given by way of example:

analyzing the example of the code to be tested by collecting the program set in the plug-in to obtain a grammar tree corresponding to the code to be tested, as shown in fig. 3; the syntax tree is further parsed to obtain information of the execution chains included in the syntax tree and the execution nodes included in each execution chain, as shown in fig. 4. It can be seen visually from the figure that: the syntax tree comprises three execution chains in total, wherein the execution chain 1 consists of an execution node with a null type and an execution node with null return; the execution chain 2 is composed of execution nodes, wherein the type is not null, the type is not vip, and the type returns to default; the execution chain 3 is composed of execution nodes "type is not null", "type is vip", and "return to super user".

And S220, for each execution chain, determining the chain specific weight corresponding to the current execution chain according to the number of the execution nodes contained in the current execution chain and the total number of the execution nodes contained in the code to be tested.

For example, in the syntax tree corresponding to the code to be tested shown in fig. 4, the number of execution nodes included in the execution chain 1 is 2; the number of execution nodes contained in the execution chains 2 and 3 is 3; the total number of execution nodes contained in the code to be tested is the total number of execution nodes corresponding to the three execution chains, and the total number of the execution nodes is 8. Thus, according to the ratio of the chain weight corresponding to the current execution chain to the total number of the execution nodes contained in the current execution chain and the total number of the execution nodes contained in the code to be tested, the chain weight corresponding to the execution chain 1 is obtained to be 2/8 ═ 0.25; the specific gravity of the execution chain 2 and the execution chain 3 is 3/8-0.375.

S230, determining an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, and obtaining a test case covering result.

Specifically, executing a code to be tested based on a plurality of different test cases, and determining an execution chain in the code to be tested covered by each test case in the execution process, namely determining an execution path of each side case in a syntax tree of the code to be tested. For example, 10 different test cases are adopted to execute the code to be tested, and an execution chain in the code to be tested covered by each test case in the execution process is respectively determined.

For example, in the code to be tested provided in the embodiment of the present invention, if a test case one is "type ═ zhangsan", and it is known that zhangsan is VIP, an execution chain in the code to be tested covered by the test case one is execution chain 3; if the second test case is "type ═ lifour", and it is known that lifour is not a VIP user, the execution chain in the code to be tested covered by the second test case is execution chain 2. Thus, the test case coverage result is determined to be: the first test case covers an execution chain 3 in the code to be tested in the execution process, and the second test case covers an execution chain 2 in the code to be tested in the execution process.

S240, for each execution chain in the code to be tested, determining the number of test cases covering the current execution chain according to the test case covering result, and determining the case covering proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of the test cases.

For example, in the code to be tested provided in the embodiment of the present invention, if the number of test cases is 10, it is determined that the number of test cases covering the first execution chain is 0, the number of test cases covering the second execution chain is 2, and the number of test cases covering the third execution chain is 8 according to the execution chains in the code to be tested, which are respectively covered by each test case represented by the test case covering result during the execution process. Accordingly, determining that the case coverage proportion corresponding to the first execution chain is 0/10-0 according to the number of the test cases covering the current execution chain and the total number of the test cases; the use case coverage ratio corresponding to the second execution chain is 2/10-0.2; the use case coverage ratio corresponding to the second execution chain is 8/10 ═ 0.8.

And S250, generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain.

According to the technical scheme of the embodiment, the execution chains in the code to be tested, which are respectively covered by the execution chains in the code to be tested in the execution process, are determined by obtaining the chain proportion respectively corresponding to the execution chains in the code to be tested, the case coverage proportion corresponding to the current execution chain is determined according to the number of the test cases covering the current execution chain and the total number of the test cases for each execution chain in the code to be tested, the determination result of the test coverage is generated according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain, the coverage of the test cases can be evaluated in a standard, scientific and quantitative mode, the evaluation accuracy of the coverage is improved, and therefore more comprehensive test cases can be selected according to the evaluation result to ensure the comprehensiveness of the test range.

Optionally, the obtaining of the execution chains included in the code to be tested and the information of the execution nodes included in each execution chain, which are acquired by the acquisition plug-in the service system, includes:

reading execution chains contained in the code to be tested and information of execution nodes contained in each execution chain from a first data cache unit of message middleware;

the acquisition plug-in stores the acquired execution chains contained in the code to be tested and the information of the execution nodes contained in each execution chain in real time into the first data cache unit.

The message middleware can utilize an efficient and reliable message transfer mechanism to carry out platform-independent data communication, integrates a distributed system based on data communication, and can extend communication among processes in a distributed environment by providing a message transfer and message queuing model. In the embodiment of the invention, the message middleware can be used for storing the information of the execution node of each test case of the code to be tested in the execution process.

For example, the collecting plugin stores the collected execution chains included in the code to be tested and the information of the execution nodes respectively included in each execution chain in real time into the first data cache unit of the message middleware, and reads the information of the execution nodes in the execution process of each test case of the code to be tested from the first data cache unit of the message middleware when the determination result of the test coverage needs to be generated by using the information of the execution nodes.

Optionally, the method for generating the determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain includes at least one of the following:

generating a chart containing case coverage proportion and chain proportion respectively corresponding to each execution chain, and taking the chart as a determination result of the test coverage;

determining the execution chain with the case coverage proportion smaller than the specific weight of the chain as the execution chain with the case coverage not in place, and taking the execution chain with the case coverage not in place as a determination result of the test coverage rate;

and for each execution chain, determining a difference value between the case coverage ratio corresponding to the current execution chain and the chain ratio corresponding to the current execution chain, and taking the difference value as a determination result of the test coverage rate.

In a specific example, a graph including a use case coverage ratio and a chain weight corresponding to each execution chain is generated, where the form of the graph may be a two-dimensional table, a straight line graph, or a pie graph, and the form of the graph may not be limited in the embodiment of the present invention. For example, taking the code to be tested provided in this embodiment as an example, the determination result of the test coverage may be a table as shown in table 1, or a line graph as shown in the figure.

TABLE 1

Description of the invention	Chain 1	Chain 2	Chain 3
				Specific gravity of chain	0.25	0.375	0.375
Proportion of coverage of use case	0	0.2	0.8

As can be seen from both the determination results of the test coverage shown in fig. 5 and table 1, the case coverage ratio corresponding to the execution chain 1 and the execution chain 2 is smaller than the chain specific gravity, which indicates that the test case used by the current code to be tested does not cover the execution chain 1 and the execution chain 2 in place, the case coverage ratio corresponding to the execution chain 3 is larger than the chain specific gravity, which indicates that the test case used by the current code to be tested covers the execution chain 3 in place. Therefore, the test cases capable of covering the execution chains 3 can be added according to the determination result of the test coverage rate, so as to ensure that the test cases can cover each execution chain in the code to be tested in place, and further ensure the comprehensiveness of the test range.

In another specific example, if the case coverage rate corresponding to the current execution chain is greater than or equal to the chain specific weight, it indicates that the coverage of the test case on the current execution chain of the code to be tested is in place, and there is no need to add a test case that is enough to cover the current execution chain. Therefore, the execution chain with the case coverage proportion smaller than the specific weight of the chain is determined as the execution chain with the case coverage not in place, and the execution chain with the case coverage not in place is taken as the determination result of the test coverage rate.

In another specific example, for each execution chain, a difference value between the case coverage ratio corresponding to the current execution chain and the chain weight corresponding to the current execution chain is determined, and the difference value is used as a determination result of the test coverage rate, so that how large the difference between the case coverage ratio corresponding to the current execution chain and the chain weight is, and it is convenient to determine the number of test cases capable of covering the current execution chain according to the difference value.

EXAMPLE III

Fig. 6 is a flowchart of a method for determining test coverage in a third embodiment of the present invention, where the third embodiment is optimized based on the foregoing embodiments, and in the present embodiment, determining an execution chain in the code to be tested, which is respectively covered by each test case of the code to be tested in an execution process, to obtain a test case coverage result, where the method includes: acquiring information of execution nodes, which are acquired by an acquisition plug-in arranged in a business system and aim at each test case of the code to be tested in the execution process; and for each test case, determining the execution chain of the execution node of the current test case in the execution process in the code to be tested, which contains the current test case, as the execution chain of the code to be tested covered by the current test case in the execution process, so as to obtain a test case covering result.

As shown in fig. 6, the method of this embodiment specifically includes the following steps:

s310, acquiring chain proportion corresponding to each execution chain in the code to be tested.

S320, acquiring information of execution nodes in the execution process of each test case aiming at the code to be tested, which is acquired by an acquisition plug-in arranged in a business system.

Specifically, the acquisition plug-in is introduced into a business system executing the code to be tested through a project management tool maven. When the service system is started, the collection plug-in is loaded through the Spring application starter, so that the collection plug-in can collect information of execution nodes of each test case of the code to be tested in the execution process.

S330, for each test case, determining the execution chain of the execution node of the current test case in the execution process in the code to be tested as the execution chain of the code to be tested covered by the current test case in the execution process, and obtaining a test case covering result.

Specifically, for each test case, an execution node of a current test case included in the code to be tested in the execution process and an execution chain formed by the execution nodes are determined, and the execution chain is determined as the execution chain in the code to be tested covered by the current test case in the execution process.

S340, for each execution chain in the code to be tested, determining the number of test cases covering the current execution chain according to the test case covering result, and determining the case covering proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of the test cases.

And S350, generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain.

According to the technical scheme of the embodiment, the execution chains in the code to be tested, which are respectively covered by the execution chains in the code to be tested in the execution process, are determined by obtaining the chain proportion respectively corresponding to the execution chains in the code to be tested, for each execution chain in the code to be tested, the case coverage proportion corresponding to the current execution chain is determined according to the number of the test cases covering the current execution chain and the total number of the test cases, the determination result of the test coverage rate is generated according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain, the coverage rate of the test cases can be evaluated in a standard, scientific and quantitative mode, the evaluation accuracy of the coverage rate is improved, and therefore more comprehensive test cases can be selected according to the evaluation result to ensure the comprehensiveness of the test range.

Optionally, the acquiring plugin acquires information of an execution node in an execution process of each test case of the code to be tested, where the acquiring plugin acquires information of the execution node in the execution process of each test case of the code to be tested, and includes:

reading a buried point code preset in the code to be tested, and recording code execution information in the execution process of each test case aiming at the code to be tested;

and determining the information of the execution node of each test case in the execution process according to the read code execution information.

The data embedding is a common data acquisition method, namely event tracking, and is a related technology and implementation process for capturing, processing and transmitting specific user behaviors or events.

For example, the collection plug-in may perform an operation of setting the buried point code at a preset execution node in the test code after parsing out the execution chains included in the code to be tested and the execution nodes included in each execution chain according to the syntax tree. In the process of executing the codes to be tested based on the test cases, the execution information of the codes is recorded when the codes reach the embedded point, and the acquisition plug-in determines the information of the execution nodes of the test cases in the execution process by reading the recorded execution information of the codes to be tested.

Optionally, the obtaining information of an execution node in the execution process of each test case for the code to be tested, which is acquired by an acquisition plug-in arranged in the service system, includes:

reading information of an execution node of each test case of the code to be tested in the execution process from a second data cache unit of the message middleware; the acquisition plug-in stores acquired information of execution nodes of each test case of the code to be tested in the execution process into the second data cache unit in real time.

For example, the second data cache unit of the message middleware stores information of an execution node of each test case of the code to be tested in the execution process in real time, and when a determination result of the test coverage needs to be generated by using the information of the execution node, the information of the execution node of each test case of the code to be tested in the execution process is read from the second data cache unit of the message middleware, so that the system response speed and stability of the determination device of the test coverage can be improved.

For example, as shown in fig. 7, the method for determining test coverage provided by the embodiment of the present invention may be integrated in a test coverage management system, where the test coverage management system includes a management end, a test case collection end, and a test code analysis and result determination end. The management end comprises a management platform, and the management platform has the functions of business system docking, code maintenance, execution chain management, execution node management, result display and the like. The collection end includes: the device comprises a data preprocessing module, a collecting plug-in and a transmission module. The data preprocessing module can carry out preprocessing such as point burying, code dyeing and the like on a program code or an interface code corresponding to an input test case, and determines a code input parameter and a code output parameter, wherein the dyeing refers to a process of collecting information of an execution node of each test case of a code to be tested in an execution process. The collection insert may include: the plug-in or Agent plug-in is used for acquiring execution chains contained in the codes to be tested, information of execution nodes contained in each execution chain and information of the execution nodes of each test case of the codes to be tested in the execution process. The transmission module comprises a distributed message transmission platform or a message middleware and is used for storing execution chains contained in the to-be-tested codes acquired by the acquisition plug-in, information of execution nodes contained in each execution chain and information of the execution nodes of each test case of the to-be-tested codes in the execution process. The test code analysis and result determination end comprises: the analysis and calculation module is used for analyzing the codes to be tested to obtain chain proportions corresponding to execution chains in the codes to be tested; acquiring an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, wherein each execution chain determines a case coverage proportion corresponding to the current execution chain according to the number of the test cases covering the current execution chain and the total number of the test cases; and generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain. The analysis and calculation process or the off-line calculation can be completed on line in real time through the scheduling module. The storage module may include: any one of an SQL database, a Redis database or an hbase database for storing the determination result of the test coverage. And the process of generating the determination result of the test coverage is monitored in real time by the monitoring section.

Exemplarily, as shown in fig. 8, based on the test coverage management system, the method for determining test coverage provided by the embodiment of the present invention includes the specific steps of: the management terminal is used for registering or parking a business system to test the coverage rate management system, a collecting plug-in is arranged in the business system, a grammar parser in the collecting plug-in arranged in the business system is used for collecting information of an execution chain contained in a code to be tested and an execution node contained in each execution chain, and a case to be tested is dyed through the collecting plug-in, namely the information of the execution node of each test case of the code to be tested in the execution process is collected. For each execution chain, determining the chain specific weight corresponding to the current execution chain according to the number of execution nodes contained in the current execution chain and the total number of execution nodes contained in the code to be tested; determining an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process; for each execution chain in the code to be tested, determining a case coverage proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of the test cases; and generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain, and sending the determination result to a management end for displaying.

Example four

Fig. 9 is a schematic structural diagram of a device for determining test coverage according to a fourth embodiment of the present invention. The embodiment is applicable to the case of determining the test coverage of the test case in the execution process of the code to be tested, the apparatus may be implemented in a software and/or hardware manner, and the apparatus may be integrated in any device that provides the function of determining the test coverage, as shown in fig. 9, where the apparatus for determining the test coverage specifically includes: a chain specific gravity acquisition module 410, an execution chain determination module 420, a coverage ratio determination module 430, and a result determination module 440.

The chain proportion obtaining module 410 is configured to obtain chain proportions corresponding to execution chains in the code to be tested; the chain proportion characterization represents the proportion of the number of execution nodes contained in the corresponding execution chain to the total number of execution nodes contained in the code to be tested;

the execution chain determining module 420 is configured to determine an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, to obtain a test case coverage result;

a coverage proportion determining module 430, configured to determine, for each execution chain in the code to be tested, the number of test cases covering a current execution chain according to the test case coverage result, and determine a case coverage proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of test cases;

and the result determining module 440 is configured to generate a determination result of the test coverage according to the case coverage ratio and the chain proportion respectively corresponding to each execution chain.

Optionally, the chain specific gravity obtaining module 410 includes:

the first information acquisition unit is used for acquiring execution chains contained in the code to be tested and acquired by an acquisition plug-in unit arranged in a service system and information of execution nodes contained in each execution chain;

and the specific gravity determining unit is used for determining the chain specific gravity corresponding to the current execution chain according to the number of the execution nodes contained in the current execution chain and the total number of the execution nodes contained in the code to be tested.

Optionally, the acquiring plug-in acquires execution chains included in the code to be tested and information of execution nodes included in each execution chain, including:

Optionally, the first information obtaining unit is specifically configured to:

Optionally, the execution chain determining module 420 includes:

the second information acquisition unit is used for acquiring information of execution nodes, which are acquired by an acquisition plug-in arranged in a service system and aim at each test case of the code to be tested in the execution process;

and the execution chain determining unit is used for determining the execution chain of the execution node of the current test case in the execution process in the to-be-tested code as the execution chain of the to-be-tested code covered by the current test case in the execution process for each test case.

Optionally, the second information obtaining unit is specifically configured to:

reading information of an execution node of each test case of the code to be tested in the execution process from a data cache unit of the message middleware;

the acquisition plug-in stores acquired information of execution nodes of each test case of the code to be tested in the execution process into the second data cache unit in real time.

Optionally, the collection plug-in includes an agent plug-in or a plugin plug-in.

Optionally, the result determining module 440 includes at least one of the following units:

the first determining unit is used for generating a chart containing a case coverage proportion and a chain proportion which respectively correspond to each execution chain, and taking the chart as a determination result of the test coverage;

the second determining unit is used for determining the execution chain with the case coverage proportion smaller than the specific weight of the chain as the execution chain with the case coverage not in place, and taking the execution chain with the case coverage not in place as the determination result of the test coverage rate;

and a third determining unit, configured to determine, for each execution chain, a difference between a case coverage ratio corresponding to the current execution chain and a chain ratio corresponding to the current execution chain, and use the difference as a determination result of the test coverage.

The product can execute the method for determining the test coverage rate provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

EXAMPLE five

Fig. 10 is a schematic structural diagram of a computer device in the fourth embodiment of the present invention. FIG. 10 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention. The computer device 12 shown in FIG. 10 is only an example and should not bring any limitations to the functionality or scope of use of embodiments of the present invention.

As shown in FIG. 10, computer device 12 is embodied in the form of a general purpose computing device. The components of computer device 12 may include, but are not limited to: one or more processors or processors 16, a system memory 28, and a bus 18 that connects the various system components (including the system memory 28 and the processors 16).

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Computer device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. Computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 10, and commonly referred to as a "hard drive"). Although not shown in FIG. 10, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.

Computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with computer device 12, and/or with any devices (e.g., network card, modem, etc.) that enable computer device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. In the computer device 12 of the present embodiment, the display 24 is not provided as a separate body but is embedded in the mirror surface, and when the display surface of the display 24 is not displayed, the display surface of the display 24 and the mirror surface are visually integrated. Also, computer device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via network adapter 20. As shown, network adapter 20 communicates with the other modules of computer device 12 via bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with computer device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processor 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement the method for determining test coverage provided by the embodiment of the present invention: acquiring chain proportion corresponding to each execution chain in the code to be tested; determining an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, so as to obtain a test case covering result; for each execution chain in the code to be tested, determining the number of test cases covering the current execution chain according to the test case covering result, and determining the case covering proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of the test cases; and generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain.

EXAMPLE six

A sixth embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for determining a test coverage according to all embodiments of the present invention: acquiring chain proportion corresponding to each execution chain in the code to be tested; determining an execution chain in the code to be tested, which is covered by each test case of the code to be tested in the execution process, so as to obtain a test case covering result; for each execution chain in the code to be tested, determining the number of test cases covering the current execution chain according to the test case covering result, and determining the case covering proportion corresponding to the current execution chain according to the number of test cases covering the current execution chain and the total number of the test cases; and generating a determination result of the test coverage rate according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain.

Any combination of one or more computer-readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for determining test coverage, the method comprising:

2. The method of claim 1, wherein obtaining the chain weight corresponding to each execution chain in the code to be tested comprises:

acquiring execution chains contained in the code to be tested and acquired by an acquisition plug-in arranged in a service system and information of execution nodes contained in each execution chain;

and for each execution chain, determining the chain specific weight corresponding to the current execution chain according to the number of execution nodes contained in the current execution chain and the total number of execution nodes contained in the code to be tested.

3. The method of claim 2, wherein the collecting plug-in collects information of execution chains included in the code to be tested and execution nodes included in each execution chain, and comprises:

4. The method of claim 2, wherein obtaining information of execution chains included in the code to be tested and execution nodes included in each execution chain, which are acquired by an acquisition plug-in provided in a service system, comprises:

5. The method of claim 1, wherein determining an execution chain in the code to be tested, which is respectively covered by each test case of the code to be tested during execution, to obtain a test case coverage result, comprises:

acquiring information of execution nodes, which are acquired by an acquisition plug-in arranged in a business system and aim at each test case of the code to be tested in the execution process;

and for each test case, determining the execution chain of the execution node of the current test case in the execution process in the code to be tested, which contains the current test case, as the execution chain of the code to be tested covered by the current test case in the execution process, so as to obtain a test case covering result.

6. The method of claim 5, wherein the collecting plug-in collects information of an execution node in the execution process of each test case of the code to be tested, and comprises:

7. The method of claim 5, wherein obtaining information of an execution node in an execution process of each test case for the code to be tested, the information being collected by a collection plug-in disposed in a business system, comprises:

8. The method of any one of claims 2-7, wherein the collection plug-in comprises an agent plug-in or a plugin plug-in.

9. The method according to any one of claims 1 to 7, wherein the determination result of the test coverage rate is generated according to the case coverage proportion and the chain proportion respectively corresponding to each execution chain, and comprises at least one of the following items:

10. An apparatus for determining test coverage, the apparatus comprising:

11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of determining test coverage as claimed in any one of claims 1 to 9 when executing the program.

12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of determining test coverage according to any one of claims 1 to 9.