CN115203004A - Code coverage test method, device, storage medium and electronic device - Google Patents

Abstract

The present disclosure relates to a code coverage test method, device, storage medium and electronic device, so as to reduce the time delay and memory consumption in the code coverage test process. The method includes: in response to receiving the coverage data file, parsing the coverage data file to obtain function coverage information corresponding to the coverage data file, the function coverage information including the function name and coverage times corresponding to the function; mapping according to the function coverage information and the first function file relationship, determine the file coverage information corresponding to the function coverage information; obtain the modified file information of the source code file compared to the historical source code file from the code project repository, and determine the target file coverage information in the file coverage information according to the modified file information; determine the target file coverage The function entity information corresponding to the information, and the line coverage rate of the coverage data file is determined according to the coverage times and the function entity information.

Description

Code coverage test method, device, storage medium and electronic device

technical field

The present disclosure relates to the field of testing technologies, and in particular, to a code coverage testing method, apparatus, storage medium, and electronic device.

Background technique

The code coverage rate is an important reflection of the degree of code coverage by the test, and it can count the execution of the code after the mobile device runs. In related technologies, the test of code coverage mainly relies on open source tools. First, multiple coverage data files are aggregated, then the aggregated files are parsed, the complete source code files are loaded, and the full coverage is generated by combining the parsed aggregate files and complete source code files. , and finally parse and map to get incremental coverage. However, generating coverage reports in this way strongly depends on the native tool environment and the acquisition of complete source code files. Moreover, due to the limitation of native tools, after uploading the overlay data file, it is necessary to perform the step of aggregating data first, and then parse the aggregated file, which is very weak in real-time. When the concurrency is high, the calculation needs to load all the source files and data files, which consumes a lot of memory.

SUMMARY OF THE INVENTION

This Summary is provided to introduce concepts in a simplified form that are described in detail in the Detailed Description section that follows. This summary section is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to be used to limit the scope of the claimed technical solution.

In a first aspect, the present disclosure provides a code coverage testing method, the method comprising:

In response to receiving the coverage data file, parsing the coverage data file to obtain function coverage information corresponding to the coverage data file, where the function coverage information includes a function name and coverage times corresponding to the function;

Determine the file coverage information corresponding to the function coverage information according to the function coverage information and the first function file mapping relationship, where the first function file mapping relationship is used to represent the function and the function file in the instrumentation product corresponding to the source code file. the corresponding relationship;

Obtain the modified file information of the source code file compared to the historical source code file from the code project warehouse, and determine the target file coverage information in the file coverage information according to the modified file information;

Determine the function entity information corresponding to the target file coverage information, and determine the line coverage rate of the coverage data file according to the coverage times and the function entity information.

In a second aspect, the present disclosure provides a code coverage testing device, the device comprising:

A parsing module, configured to parse the coverage data file in response to receiving the coverage data file, and obtain function coverage information corresponding to the coverage data file, where the function coverage information includes the function name and coverage times corresponding to the function;

A first determining module, configured to determine the file coverage information corresponding to the function coverage information according to the function coverage information and the first function file mapping relationship, where the first function file mapping relationship is used to represent the instrumentation corresponding to the source code file Correspondence between functions and function files in the product;

A second determining module, configured to compare the modified file information of the source code file obtained from the code project repository with the historical source code file, and determine target file coverage information in the file coverage information according to the modified file information;

The third determining module is configured to determine the function entity information corresponding to the target file coverage information, and determine the line coverage rate of the coverage data file according to the coverage times and the function entity information.

In a third aspect, the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processing apparatus, implements the steps of the method described in the first aspect.

In a fourth aspect, the present disclosure provides an electronic device, comprising:

a storage device on which a computer program is stored;

A processing device is configured to execute the computer program in the storage device to implement the steps of the method in the first aspect.

Through the above technical solution, the overlay data file can be parsed without relying on native tools, so the overlay data file can be parsed in response to receiving the overlay data file, and the uploaded file can be parsed. Compared with relying on native tools, it is possible to save the The steps of file aggregation, thereby reducing the delay in the code coverage testing process. In addition, the incremental file coverage information can be filtered out according to the file coverage information and the modified file information obtained from the code project repository, so as to determine the line coverage rate according to the incremental file coverage information, eliminating the need to generate the full coverage rate. Loading complete source files can not only further reduce latency, but also reduce memory consumption.

Other features and advantages of the present disclosure will be described in detail in the detailed description that follows.

Description of drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent when taken in conjunction with the accompanying drawings and with reference to the following detailed description. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale. In the attached image:

Fig. 1 is the process schematic diagram of the code coverage test method in the related art;

2 is a flowchart of a code coverage testing method according to an exemplary embodiment of the present disclosure;

3 is a schematic diagram of a process of parsing an instrumentation product to obtain a function file mapping relationship in a code coverage testing method according to an exemplary embodiment of the present disclosure;

4 is a schematic diagram of a function file mapping relationship obtained in a code coverage test method according to an exemplary embodiment of the present disclosure;

5 is a schematic diagram of a process of determining the line coverage of a coverage data file according to a function file mapping relationship in a code coverage test method according to an exemplary embodiment of the present disclosure;

6 is a schematic process diagram of a code coverage testing method according to another exemplary embodiment of the present disclosure;

7 is a block diagram of a code coverage testing apparatus according to an exemplary embodiment of the present disclosure;

Fig. 8 is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure.

Detailed ways

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for the purpose of A more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes, and are not intended to limit the protection scope of the present disclosure.

It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and/or in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this regard.

As used herein, the term "including" and variations thereof are open-ended inclusions, ie, "including but not limited to". The term "based on" is "based at least in part on." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below.

It should be noted that concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or interdependence. In addition, it should be noted that the modifications of "a" and "a plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless the context clearly indicates otherwise, they should be understood as "a" or more".

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are only for illustrative purposes, and are not intended to limit the scope of these messages or information.

The code coverage rate is an important reflection of the degree of code coverage by the test, and it can count the execution of the code after the mobile device runs. Referring to Figure 1, the test of code coverage in related technologies mainly relies on open source tools. First, multiple coverage data files uploaded from the client are aggregated, then the aggregated files are parsed, the complete source code files are loaded, and the parsed aggregated files are combined. Generate full coverage with the complete source code file, and finally parse and map to obtain incremental coverage. However, generating coverage reports in this way strongly depends on the native tool environment and the acquisition of complete source code files. Moreover, due to the limitation of native tools, after uploading the overlay data file, it is necessary to perform the step of aggregating data first, and then parse the aggregated file, which is very weak in real-time. When the concurrency is high, the calculation needs to load all the source files and data files, which consumes a lot of memory.

In view of this, the present disclosure provides a code coverage testing method, apparatus, storage medium and electronic device to reduce time delay and memory consumption during code coverage testing.

FIG. 2 is a flowchart of a code coverage testing method proposed according to an embodiment of the present disclosure. Referring to Figure 2, the code coverage testing method includes:

Step 201, in response to receiving the coverage data file, parse the coverage data file to obtain function coverage information corresponding to the coverage data file. The function coverage information includes the function name and coverage times corresponding to the function.

For example, the coverage data file is generated by the client in response to the user operation, and can represent the code situation covered by the user operation. The client can upload the coverage data file generated by each user operation to the code coverage testing device. Wherein, the client may be an electronic device installed with an IOS mobile operating system. The code coverage testing device may be a server device, which is not limited in this embodiment of the present disclosure. The code coverage testing device may, in response to receiving the coverage data file, parse the coverage data file to obtain function coverage information corresponding to the coverage data file. The function coverage information includes the function name and coverage times corresponding to the function in the coverage data file. Among them, the number of coverage is used to represent the number of executions of each line of code in the function. It should be understood that the function coverage information obtained by parsing the coverage data file roughly represents the code coverage situation. In order to obtain more detailed code coverage data, subsequent steps need to be performed.

Step 202: Determine the file coverage information corresponding to the function coverage information according to the mapping relationship between the function coverage information and the first function file. The first function file mapping relationship is used to represent the corresponding relationship between the function and the function file in the instrumentation product corresponding to the source code file.

For example, multiple functions may form a function file. In practical applications, the number of functions is large, and the number of function files is relatively small. Therefore, in the embodiment of the present disclosure, the file coverage information corresponding to the function coverage information is determined according to the mapping relationship between the function coverage information and the first function file, and the processing dimension is converted from the function dimension to the file dimension, so as to improve the processing efficiency of the subsequent process.

In step 203, the modified file information of the source code file compared with the historical source code file is obtained from the code project repository, and the target file coverage information is determined in the file coverage information according to the modified file information.

For example, the code project repository may be, for example, gitlab, which is not limited in this embodiment of the present disclosure. The code project repository can record the code version submitted by developers each time. Therefore, the modified file information of the latest source code file compared to the historical source code file can be obtained from the code project repository, that is, the source code file information modified in this version can be obtained, so that according to the modified file information, the file coverage information can be filtered from the file coverage information. The target file coverage information related to the function information modified this time is obtained, and then the function entity information corresponding to the incremental code is loaded to realize coverage detection.

Step 204: Determine the function entity information corresponding to the target file coverage information, and determine the line coverage rate of the coverage data file according to the coverage times and the function entity information.

For example, the coverage times can represent the execution times of each line of code in the function, which can be represented by an array of coverage times. For example, if the coverage count array of the first function is [2, 5, 3], it means that the first line of code in the first function is executed 2 times, the second line of code is executed 5 times, and the third line of code is executed 3 times . The function entity information is used to represent the function name corresponding to each function file in the target file coverage information, the starting position information of the function code block, and the like. The LLVM (LowLevel Virtual Machine, low-level virtual machine) tool can determine the line coverage rate of the coverage data file according to the coverage times and the corresponding function entity information.

Through the above method, the overlay data file can be parsed without relying on native tools. Therefore, the overlay data file can be parsed in response to receiving the overlay data file, so that the uploaded file can be parsed. Compared with the method of relying on native tools, the file can be omitted. Aggregate steps to reduce latency during code coverage testing. In addition, the incremental file coverage information can be filtered out according to the file coverage information and the modified file information obtained from the code project repository, so as to determine the line coverage rate according to the incremental file coverage information, eliminating the need to generate the full coverage rate. Loading complete source files can not only further reduce latency, but also reduce memory consumption.

In order to make those skilled in the art better understand the code coverage testing method provided by the present disclosure, the above steps are illustrated in detail below.

In a possible way, the function file mapping relationship can be obtained by: parsing the instrumentation product corresponding to the source code file, and obtaining the function name and function attribute information of all functions in the source code file, the function attribute information includes function code block information, parsing Function code block information, obtain the function file information of each function in the source code file and the location information of the code block corresponding to each function in the function file to which it belongs. The function file information and the location information of the code block corresponding to each function in the function file to which it belongs are used to establish the function file mapping relationship.

It should be understood that program instrumentation is to insert some probes (also known as "probes") into the program on the basis of ensuring the original logic integrity of the program under test, which is essentially a code segment for information collection, which can be Assignment statement or function call to collect coverage information), through the execution of the probe and throw out the characteristic data of the program running, through the analysis of these data, the control flow and data flow information of the program can be obtained, and then dynamic information such as logic coverage can be obtained. . In the embodiment of the present disclosure, the instrumentation product may be a result obtained by compiling the source code file after performing the instrumentation process on the source code file. When the source code file is modified, the instrumentation product changes accordingly.

For example, after the packaging platform has packaged the binary instrumentation product, when the coverage data file is uploaded for the first time, the instrumentation product can be parsed to obtain the function file mapping relationship. Therefore, when the source code file is not modified, the function file mapping relationship can be used at any time in the subsequent process to perform code coverage test after one analysis, which reduces the dependence of the code coverage test on the source code file.

For example, referring to FIG. 3 , by analyzing the instrumentation product corresponding to the source code file, function names and function attribute information of all functions in the source code file can be obtained. The hash value of the function can be calculated and stored through the function name, which is convenient for subsequent possible calculation processing. The function code block information, the function associated file information, and the file index of the function file to which the function belongs can be obtained by parsing the function attribute information. Then, the function code block information can be parsed to obtain the function file information to which the function belongs and the starting position information of the code block corresponding to the function in the function file to which the function belongs. Thereby, function file information corresponding to each function can be obtained, and the function file information includes the function name of the function, the function file information to which each function belongs, and the location information of the code block corresponding to each function in the function file to which it belongs. Then, the function file mapping relationship can be established according to the function file information of each function.

For example, referring to FIG. 4 , according to the function file information, a first function file mapping relationship and a second function file mapping relationship can be established. The first function file mapping relationship is used to represent the corresponding relationship between the function and the function file, and the second function file mapping relationship is used to represent the corresponding relationship between the function file and the function entity information. In practical applications, the first function file mapping relationship can be stored in the cloud for subsequent analysis, and the second function file mapping relationship can be stored in the database, so that the function entity information corresponding to the file coverage information can be quickly obtained in the subsequent process.

It should be understood that parsing the instrumentation product corresponding to the source code file may be parsing the instrumentation product corresponding to the latest source code file in the current version. The function file mapping relationship thus obtained can be used to generate full coverage and incremental coverage to meet the needs of different application scenarios. Alternatively, you can first obtain the file information modified in this version from the code project repository, and then parse the instrumentation product corresponding to the file information related to the modification in this version. Thereby, the storage amount of the function file mapping relationship can be reduced.

In a possible manner, parsing the coverage data file to obtain the function coverage information corresponding to the coverage data file may be: parsing the coverage data file, obtaining the function information of all functions in the coverage data file, and filtering the function information not included in the first Function information in the function file mapping relationship to obtain function coverage information corresponding to the coverage data file.

To parse the aggregated overlay data files in the related art, it is necessary to first read the header information corresponding to each overlay data file, then obtain the file version according to the header information, and then perform different parsing logics for different file versions. In the embodiment of the present disclosure, the header information of the overlay data file may also be read first, and the version of the overlay data file may be acquired according to the header information, and then the overlay data files of different versions may be processed. Specifically, for coverage data files of different versions, function information of all functions in the coverage data file may be parsed first, and then function information not included in the mapping relationship of the first function file is filtered from all function information. Then, for the filtered function information, the corresponding function coverage times array can be read according to the function name corresponding to the function information, so as to obtain the function coverage information including the function name and the function coverage times array.

It should be understood that, in the testing process, the code covered by user operations may include functions that do not exist in the source code instrumentation products. These invalid functions can be filtered through the above method, the parsing efficiency can be improved, and the coverage detection efficiency can be improved. . After that, the code covered by the user operation may also include code that is not related to the revision of this version. Therefore, in order to implement the coverage test of the incremental code, you can also filter from the file dimension according to the first function file mapping relationship. Further improve processing efficiency and reduce latency and memory consumption during code coverage testing.

For example, the file coverage information corresponding to the function coverage information may be determined according to the mapping relationship between the function coverage information and the first function file. Then, the target file coverage information is determined in the file coverage information according to the modified file information of the latest source code file obtained from the code project repository compared with the historical source code file. In this way, the file coverage information irrelevant to this modification can be filtered. After that, the function entity information corresponding to the target file coverage information can be determined, so as to implement the incremental code coverage test according to the function entity information.

In a possible manner, determining the function entity information corresponding to the target file coverage information may be: reading the function entity information corresponding to the target file coverage information from the database according to the second function file mapping relationship, the second function file mapping relationship using It is used to characterize the correspondence between the function file and the function entity information in the instrumentation product corresponding to the source code file.

For example, the mapping relationship of the second function file is generated by parsing the instrumentation product and saved in the database when the coverage data is uploaded for the first time. Therefore, after the coverage data is uploaded for the first time, the function entity information corresponding to the target file coverage information can be read from the database according to the second function file mapping relationship. After that, the function entity information corresponding to the target file coverage information read from the database can be saved in the local cache, so as to speed up the parsing speed of the subsequently uploaded data files.

In another possible manner, determining the function entity information corresponding to the target file coverage information may also be: first read the function entity information corresponding to the target file coverage information from the local cache, if the target file coverage information is read from the local cache If the corresponding function entity information fails, the function entity information corresponding to the target file coverage information is read from the database according to the second function file mapping relationship, and the second function file mapping relationship is used to represent the function in the instrumentation product corresponding to the source code file. The corresponding relationship between the file and the function entity information, the database stores the function entity information corresponding to each function file in the second function file mapping relationship.

Each subsequent upload of coverage data, you can first read the function entity information corresponding to the target file coverage information from the local cache. If the function entity information corresponding to the target file coverage information fails to be read from the local cache, the second function File mapping relationship, read the function entity information corresponding to the target file coverage information from the database. Therefore, the function entity information is preferentially read from the local cache, which can improve processing efficiency. And through the second function file mapping relationship, the function entity information is searched in units of files, which can improve the efficiency and reduce the access pressure of the database compared with the search method in units of functions.

For example, referring to FIG. 5 , multiple coverage data files are received, and the function coverage information includes a function name and an array of coverage times, for example, the coverage times array of function functionName1 is [1, 1, 0]). The file coverage information can be obtained according to the function coverage information corresponding to each coverage data file and the first function file mapping relationship. Then, the target file coverage information is determined according to the file coverage information and the modified file information obtained from the code project repository. Afterwards, if the function entity information corresponding to the target file coverage information fails to be read from the local cache, the function entity information corresponding to the target file coverage information is read from the database according to the second function file mapping relationship. Finally, the line coverage of each coverage data file can be obtained by combining the function entity information and the function coverage information.

In a possible manner, the function coverage information includes multiple coverage times arrays, each coverage times array has function identification information, and each element in each coverage times array is used to represent the execution times of each line of code in the corresponding function, Then, for each function in the function coverage information, perform the following processing: determine the function entity information corresponding to the function, and determine the corresponding coverage times array from the multiple coverage times arrays according to the function identification information of the function; Array of function entity information and coverage times to determine line coverage information. Then, the line coverage information of each function is aggregated to obtain the line coverage of the coverage data file.

For example, the coverage times may be represented by a coverage times array. Since user operations may cover multiple functions, after parsing the coverage data file, multiple coverage times arrays may be obtained, and each coverage times array may have a corresponding function identifier. The function can be associated with the corresponding coverage times array through the function identifier, so that in the subsequent process, the coverage times array corresponding to the function can be determined according to the function identifier. The function entity information can be used to characterize the starting position and ending position of the function code block, that is, to determine the code block position of the function covered by the user operation, and then combine the function entity information corresponding to the function and the coverage times array to determine the code in the function. line coverage.

After that, the line coverage of each function can be aggregated through the LLVM tool to obtain the line coverage of the coverage data file. In this way, the line coverage information of each function can be determined synchronously. Compared with the method of sequentially determining the code coverage rate of each line in the coverage data file, processing efficiency can be improved, thereby reducing the time delay in the code line coverage test process.

In a possible way, after the line coverage of the coverage data file is obtained, the historical line coverage of the source code file can also be obtained from the database, and then the historical line coverage and the line coverage of the coverage data file are accumulated to obtain the source code. The target line coverage for the file.

It should be understood that the above method can determine the incremental line coverage of a single coverage data file. In this case, in order to obtain the full line coverage of the source code file, the historical line coverage corresponding to the source code file can be obtained from the database, and then the historical line coverage and the line coverage of the coverage data file can be accumulated. After that, the line coverage of the source code file obtained after accumulation can also be saved, for example, it can be saved in the redis database, so as to facilitate the subsequent determination of the full line coverage. In addition, in a possible way, it is also possible to obtain the line coverage of the saved source code file, such as obtaining the line coverage of the source code file from the redis database, and then performing incremental mapping on the line coverage of the obtained source code file. Displayed on the front end for QA (Quality Assurance, quality assurance) analysis. The manner of incremental mapping may be similar to that in the related art, and details are not described here.

The code coverage testing method provided by the present disclosure will be described below through another exemplary embodiment.

Referring to FIG. 6 , the packaging platform first packs a binary instrumentation product, and when an overlay data file is uploaded for the first time, the instrumentation product is parsed to obtain a first function file mapping relationship and a second function file mapping relationship. In addition, the first function file mapping relationship and the second function file mapping relationship can be stored in the database for subsequent analysis.

After the terminal device uploads the overlay data file, in response to receiving the overlay data file, it can parse the overlay data file to obtain function overlay information corresponding to the overlay data file. Afterwards, the file coverage information corresponding to the function coverage information may be determined according to the mapping relationship between the function coverage information and the first function file. Next, the modified file information of the source code file compared to the historical source code file can be obtained from gitlab (code project repository), and the target file coverage information can be determined in the file coverage information according to the modified file information. Then, the function entity information corresponding to the target file coverage information can be read from the local cache. If the function entity information corresponding to the target file coverage information is read from the local cache fails, the second function file mapping relationship is read from the database. The function entity information corresponding to the target file coverage information is obtained, so that the line coverage rate of the coverage data file can be determined according to the function entity information, that is, the incremental line coverage rate of a single coverage data file can be obtained.

Continuing to refer to Figure 6, after obtaining the incremental line coverage of a single coverage data file, the historical line coverage of the source code file can be obtained from the database, and then the historical line coverage and the incremental line coverage can be accumulated. Obtain the target line coverage of the source code file, that is, obtain the full line coverage of the source code file. After that, in a possible way, the full line coverage can be incrementally mapped for front-end display. Through the above method, the dependence on the source code file during the code coverage test can be reduced. When the source code file is not modified, the function file mapping relationship can be obtained through one analysis of the instrumentation product, so that the subsequent process can directly pass this function. File mapping relationship for code coverage testing. In addition, the overlay data file can be parsed in response to the upload of the overlay data file, and the upload file can be parsed. Compared with the method in the related art, the step of file aggregation can be omitted, thereby reducing the code coverage test. delay in the process.

In addition, after parsing the coverage data file, the incremental code coverage test can be performed through the function file mapping relationship, without the need to load the instrumentation product corresponding to the complete source code file into the memory for each test. After testing, compared with the method of loading the instrumentation product corresponding to the complete source code file into the memory, the method provided by the present disclosure can reduce the memory consumption by two-thirds.

Based on the same inventive concept, an embodiment of the present disclosure also provides a code coverage testing apparatus. 7, the code coverage testing device 700 includes:

A parsing module 701, configured to parse the coverage data file in response to receiving the coverage data file, and obtain function coverage information corresponding to the coverage data file, where the function coverage information includes the function name and coverage times corresponding to the function;

The first determination module 702 is configured to determine the file coverage information corresponding to the function coverage information according to the function coverage information and the first function file mapping relationship, where the first function file mapping relationship is used to represent the insert code corresponding to the source code file. Correspondence between functions and function files in the pile product;

A second determination module 703, configured to compare the latest source code file obtained from the code project repository with the modification file information of the historical source code file, and determine target file coverage information in the file coverage information according to the modification file information;

The third determining module 704 is configured to determine the function entity information corresponding to the target file coverage information, and determine the line coverage rate of the coverage data file according to the coverage times and the function entity information.

Optionally, the parsing module 701 is used for:

Parse the coverage data file, obtain function information of all functions in the coverage data file, and filter the function information not included in the mapping relationship of the first function file from the function information to obtain the coverage data The function coverage information corresponding to the file.

Optionally, the second determining module 703 is used for:

Read the function entity information corresponding to the target file coverage information from the local cache;

When reading the function entity information corresponding to the target file coverage information from the local cache fails, read the function entity information corresponding to the target file coverage information from the database according to the second function file mapping relationship, and the second function entity information corresponding to the target file coverage information is read from the database. The function file mapping relationship is used to represent the corresponding relationship between the function file and the function entity information in the instrumentation product corresponding to the source code file, and the database stores the function entity corresponding to each function file in the second function file mapping relationship. information.

Optionally, the function coverage information includes a plurality of coverage times arrays, each of the coverage times arrays has function identification information, and each element in each of the coverage times arrays is used to represent each line of code in the corresponding function. The number of times of execution, the third determining module 704 is used for:

For each function in the function coverage information, the following processing is performed:

Determine the function entity information corresponding to the function, and determine the corresponding coverage times array in the multiple coverage times arrays according to the function identification information of the function;

Determine row coverage information according to the corresponding function entity information and the coverage times array;

Aggregate the line coverage information of each of the functions to obtain the line coverage of the coverage data file.

Optionally, the apparatus 700 also includes the following modules for obtaining the function file mapping relationship:

a first processing module, configured to parse the instrumentation product corresponding to the source code file, and obtain function names and function attribute information of all functions in the source code file, where the function attribute information includes function code block information;

The second processing module is used to parse the function code block information, and obtain the function file information to which each function in the source code file belongs and the position information of the code block corresponding to each function in the function file to which it belongs;

The establishment module is configured to establish a function file mapping relationship according to the function name of each function in the source code file, the function file information to which each function belongs, and the position information of the code block corresponding to each function in the function file to which it belongs.

Optionally, the apparatus 700 further includes:

The acquisition module is used to obtain the historical line coverage corresponding to the source code file from the database;

The accumulation module is configured to accumulate the historical line coverage and the line coverage of the coverage data file to obtain the target line coverage of the source code file.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Based on the same inventive concept, an embodiment of the present disclosure further provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processing device, implements the steps of any of the foregoing code coverage testing methods.

Based on the same inventive concept, an embodiment of the present disclosure also provides an electronic device, including:

a storage device on which a computer program is stored;

A processing device is configured to execute the computer program in the storage device, so as to implement the steps of any of the above code coverage testing methods.

Referring next to FIG. 8 , it shows a schematic structural diagram of an electronic device 800 suitable for implementing an embodiment of the present disclosure. Terminal devices in the embodiments of the present disclosure may include, but are not limited to, such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablets), PMPs (portable multimedia players), vehicle-mounted terminals (eg, mobile terminals such as in-vehicle navigation terminals), etc., and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in FIG. 8 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 8 , an electronic device 800 may include a processing device (eg, a central processing unit, a graphics processor, etc.) 801 that may be loaded into random access according to a program stored in a read only memory (ROM) 802 or from a storage device 808 Various appropriate actions and processes are executed by the programs in the memory (RAM) 803 . In the RAM 803, various programs and data necessary for the operation of the electronic device 800 are also stored. The processing device 801 , the ROM 802 , and the RAM 803 are connected to each other through a bus 804 . An input/output (I/O) interface 805 is also connected to bus 804 .

Typically, the following devices may be connected to the I/O interface 805: input devices 806 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speakers, vibration An output device 807 of a computer, etc.; a storage device 808 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 809. Communication means 809 may allow electronic device 800 to communicate wirelessly or by wire with other devices to exchange data. While FIG. 8 shows an electronic device 800 having various means, it should be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication device 809 , or from the storage device 808 , or from the ROM 802 . When the computer program is executed by the processing device 801, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are executed.

It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with computer-readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, electrical wire, optical fiber cable, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol), can be used for communication, and can communicate with digital data in any form or medium (eg, communication network) interconnection. Examples of communication networks include local area networks ("LAN"), wide area networks ("WAN"), the Internet (eg, the Internet), and peer-to-peer networks (eg, ad hoc peer-to-peer networks), as well as any currently known or future development network of.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device; or may exist alone without being assembled into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device: in response to receiving the overlay data file, parse the overlay data file, and obtain the The function coverage information corresponding to the coverage data file, the function coverage information includes the function name and coverage times corresponding to the function; according to the function coverage information and the first function file mapping relationship, determine the file coverage information corresponding to the function coverage information, so The first function file mapping relationship is used to represent the corresponding relationship between the function and the function file in the instrumentation product corresponding to the source code file; the source code file obtained from the code project warehouse is compared with the modification file information of the historical source code file, and Determine target file coverage information in the file coverage information according to the modified file information; determine function entity information corresponding to the target file coverage information, and determine the coverage data according to the coverage times and the function entity information The line coverage of the file.

Computer program code for performing operations of the present disclosure may be written in one or more programming languages, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and This includes conventional procedural programming languages - such as the "C" 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 kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (eg, using an Internet service provider to via Internet connection).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.

The modules involved in the embodiments of the present disclosure may be implemented in software or hardware. Among them, the name of the module does not constitute a limitation of the module itself under certain circumstances.

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), Systems on Chips (SOCs), Complex Programmable Logical Devices (CPLDs) and more.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with the instruction execution system, apparatus or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

According to one or more embodiments of the present disclosure, Example 1 provides a code coverage testing method, including:

In response to receiving the coverage data file, parsing the coverage data file to obtain function coverage information corresponding to the coverage data file, where the function coverage information includes a function name and coverage times corresponding to the function;

Determine the file coverage information corresponding to the function coverage information according to the function coverage information and the first function file mapping relationship, where the first function file mapping relationship is used to represent the function and the function file in the instrumentation product corresponding to the source code file. the corresponding relationship;

The source code file obtained from the code project warehouse is compared with the modification file information of the historical source code file, and the target file coverage information is determined in the file coverage information according to the modification file information;

Determine the function entity information corresponding to the target file coverage information, and determine the line coverage rate of the coverage data file according to the coverage times and the function entity information.

According to one or more embodiments of the present disclosure, Example 2 provides the method of Example 1. The method of parsing the coverage data file to obtain function coverage information corresponding to the coverage data file includes:

Parse the coverage data file, obtain function information of all functions in the coverage data file, and filter the function information not included in the mapping relationship of the first function file from the function information to obtain the coverage data The function coverage information corresponding to the file.

According to one or more embodiments of the present disclosure, Example 3 provides the method of Example 1, and the determining the function entity information corresponding to the target file coverage information includes:

Read the function entity information corresponding to the target file coverage information from the local cache;

If it fails to read the function entity information corresponding to the target file coverage information from the local cache, read the function entity information corresponding to the target file coverage information from the database according to the second function file mapping relationship. The function file mapping relationship is used to represent the corresponding relationship between the function file and the function entity information in the instrumentation product corresponding to the source code file, and the database stores the function entity corresponding to each function file in the second function file mapping relationship. information.

According to one or more embodiments of the present disclosure, Example 4 provides the method of any one of Examples 1-3, the function coverage information includes a plurality of coverage times arrays, each of the coverage times arrays having function identification information, and Each element in each of the coverage times array is used to represent the execution times of each line of code in the corresponding function, and the line coverage rate of the coverage data file is determined according to the coverage times and the function entity information, include:

For each function in the function coverage information, the following processing is performed:

Determine the function entity information corresponding to the function, and determine the corresponding coverage times array in the multiple coverage times arrays according to the function identification information of the function;

Determine row coverage information according to the corresponding function entity information and the coverage times array;

Aggregate the line coverage information of each of the functions to obtain the line coverage of the coverage data file.

According to one or more embodiments of the present disclosure, Example 5 provides the method of any one of Examples 1-3, and the function file mapping relationship is obtained in the following manner:

Parse the instrumentation product corresponding to the source code file, and obtain the function names and function attribute information of all functions in the source code file, where the function attribute information includes function code block information;

Parse the function code block information to obtain the function file information to which each function in the source code file belongs and the location information of the code block corresponding to each function in the function file to which it belongs;

The function file mapping relationship is established according to the function name of each function in the source code file, the function file information to which each function belongs, and the location information of the code block corresponding to each function in the function file to which it belongs.

According to one or more embodiments of the present disclosure, Example 6 provides the method of any one of Examples 1-3, the method further comprising:

Obtain the historical line coverage corresponding to the source code file from the database;

The historical line coverage rate and the line coverage rate of the coverage data file are accumulated to obtain the target line coverage rate of the source code file.

According to one or more embodiments of the present disclosure, Example 7 provides a code coverage testing apparatus, the apparatus comprising:

A parsing module, configured to parse the coverage data file in response to receiving the coverage data file, and obtain function coverage information corresponding to the coverage data file, where the function coverage information includes the function name and coverage times corresponding to the function;

A first determining module, configured to determine the file coverage information corresponding to the function coverage information according to the function coverage information and the first function file mapping relationship, where the first function file mapping relationship is used to represent the instrumentation corresponding to the source code file Correspondence between functions and function files in the product;

A second determination module, configured to compare the modified file information of the latest source code file obtained from the code project warehouse with the historical source code file, and determine target file coverage information in the file coverage information according to the modified file information;

The third determining module is configured to determine the function entity information corresponding to the target file coverage information, and determine the line coverage rate of the coverage data file according to the coverage times and the function entity information.

According to one or more embodiments of the present disclosure, Example 8 provides the apparatus of Example 7, the parsing module for:

Parse the coverage data file, obtain function information of all functions in the coverage data file, and filter the function information not included in the mapping relationship of the first function file from the function information to obtain the coverage data The function coverage information corresponding to the file.

According to one or more embodiments of the present disclosure, Example 9 provides the apparatus of Example 7, the second determining module is configured to:

Read the function entity information corresponding to the target file coverage information from the local cache;

When reading the function entity information corresponding to the target file coverage information from the local cache fails, read the function entity information corresponding to the target file coverage information from the database according to the second function file mapping relationship, and the second function entity information corresponding to the target file coverage information is read from the database. The function file mapping relationship is used to represent the corresponding relationship between the function file and the function entity information in the instrumentation product corresponding to the source code file, and the database stores the function entity corresponding to each function file in the second function file mapping relationship. information.

According to one or more embodiments of the present disclosure, Example 10 provides the apparatus of any one of Examples 7-9, the function coverage information includes a plurality of coverage times arrays, each of the coverage times arrays having function identification information, and Each element in each of the coverage times array is used to represent the execution times of each line of code in the corresponding function, and the third determination module is used for:

For each function in the function coverage information, the following processing is performed:

Determine the function entity information corresponding to the function, and determine the corresponding coverage times array in the multiple coverage times arrays according to the function identification information of the function;

Determine row coverage information according to the corresponding function entity information and the coverage times array;

Aggregate the line coverage information of each of the functions to obtain the line coverage of the coverage data file.

According to one or more embodiments of the present disclosure, Example 11 provides the apparatus of any one of Examples 7-9, and the apparatus further includes the following modules for obtaining the function file mapping relationship:

a first processing module, configured to parse the instrumentation product corresponding to the source code file, and obtain function names and function attribute information of all functions in the source code file, where the function attribute information includes function code block information;

The second processing module is used to parse the function code block information, and obtain the function file information to which each function in the source code file belongs and the position information of the code block corresponding to each function in the function file to which it belongs;

The establishment module is configured to establish a function file mapping relationship according to the function name of each function in the source code file, the function file information to which each function belongs, and the position information of the code block corresponding to each function in the function file to which it belongs.

According to one or more embodiments of the present disclosure, Example 12 provides the apparatus of any of Examples 7-9, the apparatus further comprising:

an acquisition module for acquiring the historical line coverage corresponding to the source code file from the database;

An accumulation module, configured to accumulate the historical line coverage and the line coverage of the coverage data file to obtain the target line coverage of the source code file.

According to one or more embodiments of the present disclosure, Example 13 provides a computer-readable medium having stored thereon a computer program that, when executed by a processing apparatus, implements the steps of the method in any one of Examples 1-6 .

According to one or more embodiments of the present disclosure, Example 14 provides an electronic device comprising:

a storage device on which a computer program is stored;

A processing device for executing the computer program in the storage device to implement the steps of the method in any one of Examples 1-6.

The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of the disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, and should also cover, without departing from the above-mentioned disclosed concept, the technical solutions formed by the above-mentioned technical features or Other technical solutions formed by any combination of its equivalent features. For example, a technical solution is formed by replacing the above-mentioned features with the technical features disclosed in the present disclosure (but not limited to) with similar functions.

Additionally, although operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although the above discussion contains several implementation-specific details, these should not be construed as limitations on the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or logical acts of method, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims. Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Claims (10)

1. A method for code coverage testing, the method comprising:

responding to a received coverage data file, analyzing the coverage data file to obtain function coverage information corresponding to the coverage data file, wherein the function coverage information comprises a function name and coverage times corresponding to a function;

determining file coverage information corresponding to the function coverage information according to the function coverage information and a first function file mapping relation, wherein the first function file mapping relation is used for representing the corresponding relation between a function and a function file in an insertion product corresponding to a source code file;

acquiring modified file information of the source code file compared with a historical source code file from a code project warehouse, and determining target file coverage information in the file coverage information according to the modified file information;

and determining function entity information corresponding to the coverage information of the target file, and determining the row coverage rate of the coverage data file according to the coverage times and the function entity information.

2. The method according to claim 1, wherein the analyzing the overlay data file to obtain function overlay information corresponding to the overlay data file comprises:

analyzing the coverage data file to obtain function information of all functions in the coverage data file, and filtering function information which is not included in the mapping relation of the first function file from the function information to obtain function coverage information corresponding to the coverage data file.

3. The method according to claim 1, wherein the determining function entity information corresponding to the target file coverage information includes:

reading function entity information corresponding to the target file coverage information from a local cache;

if the function entity information corresponding to the target file coverage information is failed to be read from the local cache, reading the function entity information corresponding to the target file coverage information from a database according to a second function file mapping relation, wherein the second function file mapping relation is used for representing the corresponding relation between the function files and the function entity information in the instrumentation product corresponding to the source code file, and the database stores the function entity information corresponding to each function file in the second function file mapping relation.

4. The method according to any one of claims 1 to 3, wherein the function coverage information includes a plurality of coverage times arrays, each of the coverage times arrays has function identification information, and each element in each of the coverage times arrays is used for characterizing the execution times of each line of code in a corresponding function, and the determining the line coverage of the coverage data file according to the coverage times and the function entity information includes:

for each function in the function coverage information, performing the following processing:

determining function entity information corresponding to the function, and determining a corresponding coverage time array in the multiple coverage time arrays according to the function identification information of the function;

determining row coverage information according to the corresponding function entity information and the coverage time array;

and aggregating the row coverage information of each function to obtain the row coverage rate of the coverage data file.

5. The method according to any one of claims 1 to 3, wherein the function file mapping relationship is obtained by:

analyzing the instrumentation product corresponding to the source code file to obtain function names and function attribute information of all functions in the source code file, wherein the function attribute information comprises function code block information;

analyzing the function code block information to obtain function file information to which each function belongs in the source code file and position information of a code block corresponding to each function in the function file to which the function belongs;

and establishing a function file mapping relation according to the function name of each function in the source code file, the function file information of each function and the position information of the code block corresponding to each function in the function file.

6. The method according to any one of claims 1-3, further comprising:

acquiring the historical row coverage rate of the source code file from a database;

and accumulating the historical row coverage rate and the row coverage rate of the coverage data file to obtain the target row coverage rate of the source code file.

7. An apparatus for code coverage testing, the apparatus comprising:

the analysis module is used for responding to the received coverage data file, analyzing the coverage data file and obtaining function coverage information corresponding to the coverage data file, wherein the function coverage information comprises a function name and coverage times corresponding to a function;

the first determining module is used for determining file coverage information corresponding to the function coverage information according to the function coverage information and a first function file mapping relation, wherein the first function file mapping relation is used for representing the corresponding relation between a function and a function file in an instrumentation product corresponding to a source code file;

the second determining module is used for comparing the source code file acquired from the code project warehouse with the modified file information of the historical source code file and determining target file coverage information in the file coverage information according to the modified file information;

and the third determining module is used for determining function entity information corresponding to the coverage information of the target file and determining the row coverage rate of the coverage data file according to the coverage times and the function entity information.

8. The apparatus of claim 7, wherein the parsing module is configured to:

analyzing the coverage data file to obtain function information of all functions in the coverage data file, and filtering the function information which is not included in the mapping relation of the first function file from the function information to obtain function coverage information corresponding to the coverage data file.

9. A computer-readable medium, on which a computer program is stored which, when being executed by a processing means, carries out the steps of the method according to any one of claims 1 to 6.

10. An electronic device, comprising:

a storage device having a computer program stored thereon;

processing means for executing the computer program in the storage means to carry out the steps of the method according to any one of claims 1 to 6.

Images