CN112463620A - Coverage rate testing method and device in android software integration test - Google Patents
Coverage rate testing method and device in android software integration test Download PDFInfo
- Publication number
- CN112463620A CN112463620A CN202011406234.8A CN202011406234A CN112463620A CN 112463620 A CN112463620 A CN 112463620A CN 202011406234 A CN202011406234 A CN 202011406234A CN 112463620 A CN112463620 A CN 112463620A
- Authority
- CN
- China
- Prior art keywords
- branch
- coverage rate
- version
- rate data
- diff
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 198
- 230000010354 integration Effects 0.000 title claims abstract description 37
- 238000000034 method Methods 0.000 claims abstract description 189
- 238000005259 measurement Methods 0.000 claims abstract description 138
- 238000004590 computer program Methods 0.000 claims description 25
- 238000011161 development Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000013522 software testing Methods 0.000 description 4
- 230000003068 static effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3676—Test management for coverage analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a coverage rate testing method and device in android software integration testing, computer equipment and a storage medium. The method comprises the following steps: acquiring branch measurement coverage rate data of the software to be measured in all version branches of the current version; acquiring difference logs of the release branches of the software to be tested in the current version, and merging the sub-measurement coverage rate data of all the version branches according to the difference logs to obtain merged sub-measurement coverage rate data; detecting all diff methods and all non-diff methods of the issuing branch according to the difference log, and carrying out integrated coverage rate test on codes corresponding to all diff methods in the issuing branch codes to obtain initial set test coverage rate data; and merging the initial set coverage rate data and the merged sub-set coverage rate data to obtain final set coverage rate data, and generating a coverage rate report according to the final set coverage rate data. According to the method and the device, when the coverage rate test is carried out on the issued branch codes, the coverage rate data of the codes which are independently tested can be reused, and the test efficiency of the issued branch codes is improved.
Description
Technical Field
The application relates to the technical field of software testing, in particular to a coverage rate testing method and device in android software integration testing, computer equipment and a storage medium.
Background
In software testing, statistics of code coverage for software testing procedures are often required. Code coverage indicates the extent to which a code can be covered in a test. Generally, a software tester determines whether to repeatedly execute the software test according to the code coverage rate.
One version of the application program may have multiple requirements (for example, tens of requirements), a branch is established for each requirement during development, the developed codes of each branch need to be subjected to coverage rate test one by one, if the codes of each branch are not found to be bug in the test and the code coverage rate can reach the standard, the codes of each branch need to be merged into a release branch, and then the codes of the release branch (i.e., the codes obtained by merging the codes of all branches) are subjected to coverage rate test.
However, only part of the codes in each branch may be changed after being merged into the issue branch, but the part of the codes in each branch that is not changed after being merged into the issue branch also needs to be tested after being merged, which makes the testing inefficient.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides a coverage rate testing method, a coverage rate testing device, computer equipment and a storage medium in an android software integration test.
The invention provides a coverage rate testing method in an android software integration test according to a first aspect, and in one embodiment, the method comprises the following steps:
acquiring sub-measurement coverage rate data corresponding to all version branches of the software to be measured in the current version;
acquiring a difference log corresponding to the release branch of the software to be tested in the current version, wherein the difference log is generated by diff comparison between the release branch code of the release branch and the original version branch codes of all version branches;
merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data;
detecting all diff methods and all non-diff methods corresponding to the issuing branches according to the difference logs, and performing integrated coverage rate test on codes corresponding to all diff methods in the issuing branch codes to obtain initial integrated coverage rate data of the issuing branches;
merging the initial collective coverage rate data of the issuing branches and the merged sub-collective coverage rate data to obtain final collective coverage rate data;
and generating a coverage rate report corresponding to the release branch in the integrated coverage rate test according to the final integrated coverage rate data.
In one embodiment, the step of obtaining sub-measurement coverage data corresponding to all version branches of the current version of the software to be measured includes:
acquiring a plurality of branch coverage rate files uploaded by test equipment, wherein the number of the test equipment is several, and each branch coverage rate file is generated by performing branch coverage rate test on a version branch code of one version branch by one test equipment;
and respectively generating the branch measurement coverage rate data of each version branch according to the branch coverage rate file corresponding to each version to obtain the branch measurement coverage rate data of all version branch codes.
In one embodiment, the release version code is obtained by performing a merge operation on original version branch codes of all version branches, the release version code includes a merged version branch code of each version branch, the merged version branch code of each version branch includes class codes of a plurality of classes, and the class code of each class includes method codes of a plurality of methods.
In one embodiment, the method further comprises:
performing diff comparison on the merged version branch code of each version branch included in the release branch code and the original version branch code of the version branch to determine all difference code lines of the merged version branch code of each version branch relative to the original version branch code of the version branch;
acquiring position information corresponding to all difference code lines in the merged version branch codes of each version branch, and generating key value pair information corresponding to the version branch according to the position information;
and generating a difference log corresponding to the release branch according to the generated key value pair information corresponding to each version branch.
In one embodiment, the key-value pair information corresponding to each version branch comprises key name information and key value information;
merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data, wherein the merging comprises the following steps:
and merging the sub-measurement coverage rate data corresponding to each version branch with the key value information in the key value pair information corresponding to the version branch in the difference log to obtain merged sub-measurement coverage rate data.
In one embodiment, the step of detecting all diff methods and all non-diff methods corresponding to the issue branch according to the difference log includes:
each method of traversing the issuing branches queries the difference log when traversing to one method, and if diff line information corresponding to the method is obtained by querying from the difference log, the method is determined as the diff method; and if the diff line information corresponding to the method cannot be inquired from the difference log, determining the method as a non-diff method.
In one embodiment, the step of merging the initial collective coverage data of the issuing branch with the merged partial coverage data to obtain final collective coverage data includes:
and replacing diff row information corresponding to the diff method in the combined branch measurement coverage rate data with the set measurement coverage rate data corresponding to each diff method in the initial set measurement coverage rate data of the release branch to obtain final set measurement coverage rate data.
In one embodiment, the step of generating a coverage report corresponding to the release branch in the integrated coverage test according to the final set test coverage data includes:
setting preset identifications corresponding to the version branches corresponding to the non-diff methods for the set measurement coverage data corresponding to each non-diff method in the final set measurement coverage data to obtain marked set measurement coverage data;
and generating a coverage rate report in an html format according to the marked collective measurement coverage rate data, and adding a mark for distinguishing display to the collective measurement coverage rate data provided with a preset mark when the coverage rate report is generated.
The invention provides a coverage rate testing device in android software integration test according to a second aspect, and in one embodiment, the device comprises:
the branch measurement data acquisition module is used for acquiring branch measurement coverage rate data corresponding to all version branches of the software to be measured in the current version;
the difference log obtaining module is used for obtaining a difference log corresponding to the release branch of the software to be tested in the current version, and the difference log is generated by carrying out diff comparison on the release branch code of the release branch and the original version branch codes of all version branches;
the first data merging module is used for merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data;
the integrated coverage rate testing module is used for detecting all diff methods and all non-diff methods corresponding to the issuing branch according to the difference log, and performing integrated coverage rate testing on codes corresponding to all diff methods in the issuing branch codes to obtain initial integrated coverage rate data of the issuing branch;
the second data merging module is used for merging the initial collective coverage rate data of the issuing branches and the merged sub-collective coverage rate data to obtain final collective coverage rate data;
and the coverage rate report generating module is used for generating a coverage rate report corresponding to the distribution branch in the integrated coverage rate test according to the final integrated coverage rate data.
The present invention provides according to a third aspect a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of an embodiment of any of the methods described above when executing the computer program.
The present invention provides according to a fourth aspect a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the embodiments of the method of any one of the above.
In the embodiment of the invention, the branch measurement coverage rate data corresponding to all version branches of the software to be measured in the current version and the difference log corresponding to the release branch of the software to be measured in the current version are obtained, then the branch measurement coverage rate data corresponding to all version branches are merged according to the difference log to obtain merged branch measurement coverage rate data, then all diff methods and all non-diff methods corresponding to the release branch are detected according to the difference log, the codes corresponding to all diff methods in the release branch codes are subjected to the integration coverage rate test to obtain the initial set measurement coverage rate data of the release branch, then the initial set measurement coverage rate data of the release branch and the merged branch measurement coverage rate data are merged to obtain the final set measurement coverage rate data, and finally the coverage rate report corresponding to the release branch in the integration coverage rate test is generated according to the final set measurement coverage rate data, in the embodiment, when the coverage rate test is performed on the issuing branch code of the issuing branch, the coverage rate data of the code which has been tested separately is multiplexed, so that the code which has been tested separately does not need to be tested again, and the test efficiency of performing the code coverage rate test on the issuing branch code is improved.
Drawings
FIG. 1 is a diagram of an application environment of a method for coverage testing in android software integration testing, according to an embodiment;
FIG. 2 is a flowchart illustrating a method for coverage testing in android software integration testing according to an embodiment;
FIG. 3 is a block diagram of an apparatus for coverage testing in android software integration testing, according to an embodiment;
FIG. 4 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Fig. 1 shows an application environment of the coverage testing method in the android software integration test according to an embodiment of the present invention.
Wherein the test server 10 communicates with a plurality of test devices (shown as 21/22/23 in figure 1) over a network. In an embodiment, the test server 10 may issue development packages of one or more version branches of software to be tested to each test device, so that the test device may perform software testing on the development packages received by the test device, and upload data (such as an ec file) obtained by the test to the test server 10 after the test is completed, and the test server 10 may store data returned by the test device in a database for standby, so that the test server 10 may perform subsequent integrated test based on the data returned by the test device. It should be noted that each testing device may be used to test one or more versions of the apk packet, the testing device may be, but is not limited to, various smart phones, tablet computers, and the like, and the testing server 10 may be implemented by an independent server or a server cluster composed of a plurality of servers.
The invention provides a coverage rate testing method in an android software integration test, which is explained below by taking an example that the method is applied to a testing server in fig. 1. In one embodiment, as shown in FIG. 2, the method includes the steps of:
s110: and acquiring sub-measurement coverage rate data corresponding to all version branches of the software to be measured in the current version.
In this embodiment, a version of an application may have multiple requirements (for example, tens of requirements), a branch is created for each requirement during development, and the developed codes of each branch need to be tested one by one (for convenience of distinguishing, a coverage test on the codes of the branches is referred to as a branch coverage test), if the codes of each branch pass the test, that is, no bug is found in the test and the code coverage can reach the standard, the codes of each branch need to be merged into a release branch, and then an integration test is performed on the codes of the release branch (that is, the codes obtained by merging the codes of all branches) again (for convenience of distinguishing, a coverage test on the codes of the release branch in the integration test is referred to as an integration coverage test). When the integrated coverage rate test is carried out on the release branch codes (namely the release branch codes) of the current version of the software to be tested, the branch test coverage rate data corresponding to all version branches of the software to be tested in the current version is obtained, and the branch test coverage rate data corresponding to the version branches is obtained by carrying out the branch coverage rate test on the version branch codes (namely the version branch codes).
In one embodiment, the step of obtaining sub-measurement coverage rate data corresponding to all version branches of the current version of the software to be measured includes: acquiring a plurality of branch coverage rate files uploaded by test equipment, wherein the number of the test equipment is several, and each branch coverage rate file is generated by performing branch coverage rate test on a version branch code of one version branch by one test equipment; and respectively generating the branch measurement coverage rate data of each version branch according to the branch coverage rate file corresponding to each version to obtain the branch measurement coverage rate data of all version branch codes.
In this embodiment, for an original version branch code of each version branch (the original version branch code may be a code of a version branch before merging into a release branch) that is distinguished by allocating different commit ids, a test server packs the original version branch code into an apk packet by using static instrumentation (where instrumentation inserts a flag bit for each line of code, for example, the flag bit is set to false by default to indicate that the code has not been executed), backs up a compilation process file classes file, then sends the apk packet to a test device, the test device runs the apk packet after receiving the apk packet and executes a test case, the test device modifies the flag bit corresponding to the executed code in the code of the apk packet, for example, modifies false to true (indicating that the code has been executed), and the test device saves the flag bit information of all the codes of the apk packet as a file after executing the test case and uploads the flag bit information to a test ec file The server and the testing device can test the apk packet for a plurality of times, and the generated ec file is uploaded to the testing server after each test, so that the testing server can receive a plurality of ec files related to one apk, after the test equipment completes all tests on one apk packet, the test server merges a plurality of ec files related to the apk packet to obtain a merged ec file, then uses a jacoco command line tool (an open source coverage rate test tool) to load the previously backed-up classes file and the merged ec file to generate a coverage rate report, that is, the measured coverage data of the original version branch code (referring to the coverage data of the original version branch code measured in the branch coverage test) may include data of which code lines in the original version branch code were executed during the branch test, which code lines were not executed, and the proportion of the executed code in the part of code.
S120: and acquiring a difference log corresponding to the release branch of the software to be tested in the current version.
In this embodiment, the difference log is generated by diff comparing the issue branch code of the issue branch with the original version branch codes of all version branches. The release version code is obtained by performing merging operation (merge) on original version branch codes of all version branches, the release version code comprises merged version branch codes of each version branch, the merged version branch codes of each version branch comprise class codes of a plurality of classes, and the class codes of each class comprise method codes of a plurality of methods.
As can be seen from the foregoing description, after the codes of the branches of the respective versions (i.e., the original version branch codes) are merged into the release branch, the codes of the branches of the respective versions may be changed, for example, a method in a certain class is changed, so that the codes before merging (i.e., the original version branch codes) corresponding to the branches of the respective versions are not identical to the codes after merging (i.e., the branch codes after merging). The partial codes which are not changed after being merged and contained in the merged branch codes of the branches of each version in the issued branch codes can be detected through the difference logs of the issued branches, and for the partial codes which are not changed after being merged of the branches of each version, the embodiment does not perform coverage rate test on the partial codes in the integration test, but multiplexes the coverage rate data (which code lines in the partial codes are executed during the branch test, which code lines are not executed, and the proportion of the executed codes in the partial codes, and the like) corresponding to the partial codes (namely, the partial codes) in the integration test.
The difference log corresponding to the release branch of the software to be tested in the current version can be generated in advance and stored in the database, and is acquired from the database when the integration coverage rate test needs to be performed, or can be generated again when the integration coverage rate test is performed.
In one embodiment, the process of generating the difference log by the test server may be as follows: performing diff comparison on the merged version branch code of each version branch included in the release branch code and the original version branch code of the version branch to determine all difference code lines of the merged version branch code of each version branch relative to the original version branch code of the version branch; acquiring position information corresponding to all difference code lines in the merged version branch codes of each version branch, and generating key value pair information corresponding to the version branch according to the position information; and generating a difference log corresponding to the release branch according to the generated key value pair information corresponding to each version branch.
Specifically, a diff command of the git tool may be used to compare a difference code line in which the merged branch code of each version branch is changed with respect to the original version branch code, and the position information of the difference code line in the merged branch code is used to determine which merged branch code the difference code line belongs to, which class belongs to the code, which method belongs to the class, and which line belongs to the method, and information such as a file name, an identification of the version branch, a class name and a method name, and a line number corresponding to the difference code line may be exemplarily included therein. Each version branch corresponds to one piece of key-value pair information, and the key-value pair information (i.e., key-value) corresponding to each version branch includes key name information (i.e., key) and key value information (i.e., value), and the storage form may be as follows, for example:
the key name information of the version branch may be a branch identifier of the version branch, or may be a file name (e.g., "Filename" in the above example), the key value information may be information of all classes included in the version branch, the information of each class may also be stored in the form of a key value pair, the class name (e.g., "classA" in the above example) may be used as the key name (i.e., key) of the key value pair, the information of all methods in a class may be used as the key value (i.e., value) corresponding to the key name, and the information of each method may also be stored in the form of a key value pair, the method name of a method (e.g., "methodA-1" in the above example) may be used as the key name (i.e., key), the line number (or line number) of a diff line in the method may be used as the key value (i.e., value), for example, the line number of a diff corresponding to "methodA-1" in the above example may be 1 and 2, this means that the line 1 and line 2 codes in this method "methodA-1" belong to the diff line.
S130: and merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data.
In this embodiment, when merging the branch measurement coverage data of each version branch, the test server merges the branch measurement coverage data corresponding to each version branch with the key value information in the key value pair information corresponding to the version branch in the difference log to obtain merged branch measurement coverage data.
Specifically, the test server may traverse each method in each class of each version branch in the order of file-class-method, and then determine whether the method belongs to a diff method or a non-diff method according to the diff line information corresponding to the method in the difference log, and if the traversed method belongs to the non-diff method, merge the measured coverage data corresponding to the non-diff method into the difference log. For example, the "classA" in the above example includes non-diff methods "method da-3" and "method da-4", and the measured coverage data corresponding to these two methods are full coverage and 1/2/5 th row coverage, respectively, so the combined measured coverage data of "classA" may be:
“classA”:{
“methodA-3”:[-1],“methodA-4”:[1,2,5]
}；
where a "-1" indicates full coverage.
After merging the measured coverage data of each non-diff method of each version branch into the difference log using the manner of merging coverage data described above, the merged measured coverage data is obtained.
S140: and detecting all diff methods and all non-diff methods corresponding to the issuing branches according to the difference logs, and performing integrated coverage rate test on codes corresponding to all diff methods in the issuing branch codes to obtain initial integrated coverage rate data of the issuing branches.
In this embodiment, when the test server detects all diff methods and all non-diff methods corresponding to the issue branches from the difference log, each method (method) of the distribution branch is traversed, which may be done in particular in the order of file-class-methods, in traversing a method, the difference log is queried, if the difference log is queried to obtain diff line information corresponding to the method (for example, "methodA-1": 1,2 in the above example, and the diff line information means [1,2]), the method is determined as a diff method, specifically, a method usually contains multiple lines of codes as long as one line of codes belongs to a diff line (i.e. belongs to a difference code line), and determining that the method belongs to a diff method, and if the diff line information corresponding to the method cannot be inquired from the difference log, determining the method as a non-diff method.
The test server obtains codes corresponding to all diff methods corresponding to the release branches (namely, codes corresponding to diff methods in merged branch codes of all versions of branches) through the difference logs to perform integrated coverage rate test, so that initial set test coverage rate data of the release branches are obtained.
S150: and merging the initial collective coverage rate data of the issuing branches and the merged partial coverage rate data to obtain final collective coverage rate data.
In this embodiment, the test server needs to merge the obtained initial collective coverage data and the merged partial measurement coverage data to obtain final collective coverage data. The test server may replace the integrated measurement coverage data corresponding to each diff method in the initial integrated measurement coverage data of the release branch with diff line information corresponding to the diff method in the merged integrated measurement coverage data, so as to obtain final integrated measurement coverage data.
For example, in the above example, since "methodA-1" and "methodA-2" in the category "classA" both have corresponding diff line information, and both belong to diff methods, after testing them, the set-test coverage data corresponding to the two diff methods can be obtained from the initial set-test coverage data as 2/4/6 th line coverage and full coverage, so that the merged sub-test coverage data of "classA" may be:
after the set-measuring coverage data of each diff method of each version branch and the corresponding diff line information in the merged branch-measuring coverage data are combined in the mode of using the combined set-measuring coverage data and the diff line information, the final set-measuring coverage data is obtained.
S160: and generating a coverage rate report corresponding to the release branch in the integrated coverage rate test according to the final integrated coverage rate data.
In this embodiment, the test server may continue to use the jacoco tool to load the final aggregate coverage data and generate a coverage report.
In one embodiment, the step of generating a coverage report corresponding to the release branch in the integrated coverage test according to the final set test coverage data includes:
setting preset identifications corresponding to the version branches corresponding to the non-diff methods for the set measurement coverage data corresponding to each non-diff method in the final set measurement coverage data to obtain marked set measurement coverage data;
and generating a coverage rate report in an html format according to the marked collective measurement coverage rate data, and adding a mark for distinguishing display to the collective measurement coverage rate data provided with a preset mark when the coverage rate report is generated.
Specifically, the test server marks a preset mark on the combined coverage data (referring to multiplexed sub-measurement coverage data) in the final collective coverage data, so that when a coverage report is generated, a special mark can be added in the UI for the coverage data with the preset mark in the marked collective coverage data to perform differential display (for example, a mark such as @ or # # is added in front of a code line), and a person who reads the coverage report can visually see which coverage data are multiplexed.
The embodiment of the invention obtains the branch measurement coverage rate data corresponding to all version branches of the software to be tested in the current version and obtains the difference logs corresponding to the release branches of the software to be tested in the current version through the test server, then combines the branch measurement coverage rate data corresponding to all version branches according to the difference logs to obtain the combined branch measurement coverage rate data, then detects all diff methods and all non-diff methods corresponding to the release branches according to the difference logs, carries out the integration coverage rate test on the codes corresponding to all diff methods in the release branch codes to obtain the initial set measurement coverage rate data of the release branches, then combines the initial set measurement coverage rate data of the release branches and the combined branch measurement coverage rate data to obtain the final set measurement coverage rate data, and finally generates the coverage rate report corresponding to the release branches in the integration coverage rate test according to the final set measurement coverage rate data, the test server can realize multiplexing of the coverage rate data of the individually tested codes when the coverage rate test is carried out on the release branch codes of the release branches, so that the individually tested codes do not need to be tested, and the test efficiency of the code coverage rate test on the release branch codes is improved.
It should be noted that, although the steps in the flowchart of fig. 2 are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 2 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
Based on the same inventive concept, the invention also provides a coverage rate testing device in the android software integration test. In one embodiment, as shown in fig. 3, the coverage rate testing apparatus in the android software integration test comprises the following modules:
a sub-measurement data obtaining module 110, configured to obtain sub-measurement coverage data corresponding to all version branches of the software to be measured in the current version;
a difference log obtaining module 120, configured to obtain a difference log corresponding to a release branch of the software to be tested in the current version, where the difference log is generated by performing diff comparison between a release branch code of the release branch and original version branch codes of all version branches;
the first data merging module 130 is configured to merge the sub-measurement coverage data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage data;
the integrated coverage test module 140 is configured to detect all diff methods and all non-diff methods corresponding to the release branch according to the difference log, perform an integrated coverage test on codes corresponding to all diff methods in the release branch codes, and obtain initial collective test coverage data of the release branch;
the second data merging module 150 is configured to merge the initial collective coverage data of the release branch with the merged partial coverage data to obtain final collective coverage data;
and a coverage report generating module 160, configured to generate, according to the final set coverage data, a coverage report corresponding to the release branch in the integrated coverage test.
In one embodiment, the release version code is obtained by performing a merge operation on original version branch codes of all version branches, the release version code includes a merged version branch code of each version branch, the merged version branch code of each version branch includes class codes of a plurality of classes, and the class code of each class includes method codes of a plurality of methods.
In one embodiment, the score data acquisition module includes:
the branch file acquisition submodule is used for acquiring a plurality of branch coverage rate files uploaded by the test equipment, the number of the test equipment is several, and each branch coverage rate file is generated by performing branch coverage rate test on a version branch code of one version branch by one test equipment;
and the branch measurement data generation submodule is used for generating branch measurement coverage rate data of each version according to the branch coverage rate file corresponding to each version to obtain the branch measurement coverage rate data of all versions of the branch codes.
In one embodiment, the apparatus further comprises:
the comparison module is used for carrying out diff comparison on the merged version branch code of each version branch included in the release branch code and the original version branch code of the version branch to determine all difference code lines of the merged version branch code of each version branch relative to the original version branch code of the version branch;
the key value pair information generation module is used for acquiring the position information corresponding to all the difference code lines in the merged version branch codes of each version branch, and generating the key value pair information corresponding to the version branch according to the position information;
and the difference log generation module is used for generating the difference log corresponding to the release branch according to the generated key value pair information corresponding to each version branch.
In one embodiment, the key-value pair information corresponding to each version branch includes key name information and key value information. In this embodiment, the first data merging module is further configured to merge the sub-measurement coverage data corresponding to each version branch with the key value information in the key value pair information corresponding to the version branch in the difference log, so as to obtain merged sub-measurement coverage data.
In one embodiment, the integrated coverage test module is further configured to traverse each method of the distribution branch, query the difference log when traversing to one method, and determine the method as a diff method if diff line information corresponding to the method is obtained by querying from the difference log; and if the diff line information corresponding to the method cannot be inquired from the difference log, determining the method as a non-diff method.
In an embodiment, the second data merging module is further configured to replace diff line information corresponding to each diff method in the merged partial measurement coverage data with set measurement coverage data corresponding to each diff method in the initial set measurement coverage data of the issuing branch, so as to obtain final set measurement coverage data.
In one embodiment, a coverage report generation module includes:
the preset mark setting submodule is used for setting preset marks corresponding to the version branches corresponding to the non-diff methods for the set measurement coverage rate data corresponding to each non-diff method in the final set measurement coverage rate data to obtain marked set measurement coverage rate data;
and the coverage rate report generating submodule is used for generating a coverage rate report in an html format according to the marked collective coverage rate data, and adding marks for distinguishing and displaying the collective coverage rate data provided with preset marks when the coverage rate report is generated.
For the specific definition of the coverage rate testing apparatus in the android software integration test, reference may be made to the above definition of the coverage rate testing method in the android software integration test, and details are not described herein again. Each module in the coverage rate testing device in the android software integration test can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 4. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer equipment is used for storing data such as the measured coverage rate data and the measured coverage rate file. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of coverage testing in android software integration testing.
Those skilled in the art will appreciate that the architecture shown in fig. 4 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring sub-measurement coverage rate data corresponding to all version branches of the software to be measured in the current version; acquiring a difference log corresponding to the release branch of the software to be tested in the current version, wherein the difference log is generated by diff comparison between the release branch code of the release branch and the original version branch codes of all version branches; merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data; detecting all diff methods and all non-diff methods corresponding to the issuing branches according to the difference logs, and performing integrated coverage rate test on codes corresponding to all diff methods in the issuing branch codes to obtain initial integrated coverage rate data of the issuing branches; merging the initial collective coverage rate data of the issuing branches and the merged sub-collective coverage rate data to obtain final collective coverage rate data; and generating a coverage rate report corresponding to the release branch in the integrated coverage rate test according to the final integrated coverage rate data.
In one embodiment, when the processor executes the computer program to obtain the sub-measurement coverage rate data corresponding to all the version branches of the current version of the software to be measured, the following steps are also implemented:
acquiring a plurality of branch coverage rate files uploaded by test equipment, wherein the number of the test equipment is several, and each branch coverage rate file is generated by performing branch coverage rate test on a version branch code of one version branch by one test equipment; and respectively generating the branch measurement coverage rate data of each version branch according to the branch coverage rate file corresponding to each version to obtain the branch measurement coverage rate data of all version branch codes.
In one embodiment, the release version code is obtained by performing a merge operation on original version branch codes of all version branches, the release version code includes a merged version branch code of each version branch, the merged version branch code of each version branch includes class codes of a plurality of classes, and the class code of each class includes method codes of a plurality of methods. The processor executes the computer program and further implements the steps of:
performing diff comparison on the merged version branch code of each version branch included in the release branch code and the original version branch code of the version branch to determine all difference code lines of the merged version branch code of each version branch relative to the original version branch code of the version branch; acquiring position information corresponding to all difference code lines in the merged version branch codes of each version branch, and generating key value pair information corresponding to the version branch according to the position information; and generating a difference log corresponding to the release branch according to the generated key value pair information corresponding to each version branch.
In one embodiment, the key-value pair information corresponding to each version branch comprises key name information and key value information; the processor executes the computer program to realize merging processing of the branch measurement coverage rate data corresponding to all the version branches according to the difference log, and when the merged branch measurement coverage rate data is obtained, the following steps are also realized:
and merging the sub-measurement coverage rate data corresponding to each version branch with the key value information in the key value pair information corresponding to the version branch in the difference log to obtain merged sub-measurement coverage rate data.
In one embodiment, when the processor executes the computer program to detect all diff methods and all non-diff methods corresponding to the issue branches from the difference log, the following steps are further implemented:
each method of traversing the issuing branches queries the difference log when traversing to one method, and if diff line information corresponding to the method is obtained by querying from the difference log, the method is determined as the diff method; and if the diff line information corresponding to the method cannot be inquired from the difference log, determining the method as a non-diff method.
In one embodiment, when the processor executes the computer program to merge the initial collective coverage data of the issue branch with the merged branch coverage data to obtain the final collective coverage data, the processor further performs the following steps:
and replacing diff row information corresponding to the diff method in the combined branch measurement coverage rate data with the set measurement coverage rate data corresponding to each diff method in the initial set measurement coverage rate data of the release branch to obtain final set measurement coverage rate data.
In one embodiment, when the processor executes the computer program and generates a coverage report corresponding to a release branch in the integrated coverage test according to the final set coverage data, the following steps are further implemented:
setting preset identifications corresponding to the version branches corresponding to the non-diff methods for the set measurement coverage data corresponding to each non-diff method in the final set measurement coverage data to obtain marked set measurement coverage data; and generating a coverage rate report in an html format according to the marked collective measurement coverage rate data, and adding a mark for distinguishing display to the collective measurement coverage rate data provided with a preset mark when the coverage rate report is generated.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring sub-measurement coverage rate data corresponding to all version branches of the software to be measured in the current version; acquiring a difference log corresponding to the release branch of the software to be tested in the current version, wherein the difference log is generated by diff comparison between the release branch code of the release branch and the original version branch codes of all version branches; merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data; detecting all diff methods and all non-diff methods corresponding to the issuing branches according to the difference logs, and performing integrated coverage rate test on codes corresponding to all diff methods in the issuing branch codes to obtain initial integrated coverage rate data of the issuing branches; merging the initial collective coverage rate data of the issuing branches and the merged sub-collective coverage rate data to obtain final collective coverage rate data; and generating a coverage rate report corresponding to the release branch in the integrated coverage rate test according to the final integrated coverage rate data.
In one embodiment, when the computer program is executed by the processor and the sub-measurement coverage data corresponding to all the version branches of the current version of the software to be measured is obtained, the following steps are further implemented:
acquiring a plurality of branch coverage rate files uploaded by test equipment, wherein the number of the test equipment is several, and each branch coverage rate file is generated by performing branch coverage rate test on a version branch code of one version branch by one test equipment; and respectively generating the branch measurement coverage rate data of each version branch according to the branch coverage rate file corresponding to each version to obtain the branch measurement coverage rate data of all version branch codes.
In one embodiment, the release version code is obtained by performing a merge operation on original version branch codes of all version branches, the release version code includes a merged version branch code of each version branch, the merged version branch code of each version branch includes class codes of a plurality of classes, and the class code of each class includes method codes of a plurality of methods. The computer program is executed by a processor and further implements the steps of:
performing diff comparison on the merged version branch code of each version branch included in the release branch code and the original version branch code of the version branch to determine all difference code lines of the merged version branch code of each version branch relative to the original version branch code of the version branch; acquiring position information corresponding to all difference code lines in the merged version branch codes of each version branch, and generating key value pair information corresponding to the version branch according to the position information; and generating a difference log corresponding to the release branch according to the generated key value pair information corresponding to each version branch.
In one embodiment, the key-value pair information corresponding to each version branch comprises key name information and key value information; the computer program is executed by the processor, and when the branch measurement coverage rate data corresponding to all the version branches are merged according to the difference log to obtain the merged branch measurement coverage rate data, the following steps are also realized:
and merging the sub-measurement coverage rate data corresponding to each version branch with the key value information in the key value pair information corresponding to the version branch in the difference log to obtain merged sub-measurement coverage rate data.
In one embodiment, the computer program is executed by a processor, and when all diff methods and all non-diff methods corresponding to the issue branch are detected from the difference log, the following steps are further implemented:
each method of traversing the issuing branches queries the difference log when traversing to one method, and if diff line information corresponding to the method is obtained by querying from the difference log, the method is determined as the diff method; and if the diff line information corresponding to the method cannot be inquired from the difference log, determining the method as a non-diff method.
In one embodiment, when the computer program is executed by the processor to merge the initial collective coverage data of the issue branch with the merged branch coverage data to obtain the final collective coverage data, the following steps are further implemented:
and replacing diff row information corresponding to the diff method in the combined branch measurement coverage rate data with the set measurement coverage rate data corresponding to each diff method in the initial set measurement coverage rate data of the release branch to obtain final set measurement coverage rate data.
In one embodiment, when the computer program is executed by the processor and generates a coverage report corresponding to the release branch in the integrated coverage test according to the final set test coverage data, the following steps are further implemented:
setting preset identifications corresponding to the version branches corresponding to the non-diff methods for the set measurement coverage data corresponding to each non-diff method in the final set measurement coverage data to obtain marked set measurement coverage data; and generating a coverage rate report in an html format according to the marked collective measurement coverage rate data, and adding a mark for distinguishing display to the collective measurement coverage rate data provided with a preset mark when the coverage rate report is generated.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for testing the coverage rate in an android software integration test is characterized by comprising the following steps:
acquiring sub-measurement coverage rate data corresponding to all version branches of the software to be measured in the current version;
obtaining a difference log corresponding to a release branch of the software to be tested in the current version, wherein the difference log is generated by diff comparison between a release branch code of the release branch and original version branch codes of all version branches;
merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data;
detecting all diff methods and all non-diff methods corresponding to the issuing branch according to the difference log, and performing integrated coverage rate test on codes corresponding to all diff methods in the issuing branch codes to obtain initial integrated coverage rate data of the issuing branch;
merging the initial collective coverage rate data of the issuing branches and the merged sub-collective coverage rate data to obtain final collective coverage rate data;
and generating a coverage rate report corresponding to the release branch in the integrated coverage rate test according to the final integrated coverage rate data.
2. The method for testing the coverage rate in the android software integration test of claim 1, wherein the step of obtaining sub-test coverage rate data corresponding to all version branches of the software to be tested in the current version comprises:
acquiring a plurality of branch coverage rate files uploaded by test equipment, wherein the number of the test equipment is several, and each branch coverage rate file is generated by performing branch coverage rate test on a version branch code of one version branch by one test equipment;
and respectively generating the branch measurement coverage rate data of each version branch according to the branch coverage rate file corresponding to each version to obtain the branch measurement coverage rate data of all version branch codes.
3. The method for testing the coverage rate in the android software integration test of claim 1, wherein the release version code is obtained by merging original version branch codes of all version branches, the release version code comprises a merged version branch code of each version branch, the merged version branch code of each version branch comprises class codes of a plurality of classes, and the class code of each class comprises a method code of a plurality of methods;
the method further comprises the following steps:
performing diff comparison on the merged version branch code of each version branch included in the release branch code and the original version branch code of the version branch to determine all difference code lines of the merged version branch code of each version branch relative to the original version branch code of the version branch;
acquiring position information corresponding to all difference code lines in the merged version branch code of each version branch, and generating key value pair information corresponding to the version branch according to the position information;
and generating a difference log corresponding to the release branch according to the generated key value pair information corresponding to each version branch.
4. The method for testing the coverage in the android software integration test of claim 3, wherein the key-value pair information corresponding to each of the version branches comprises key name information and key value information;
the step of merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data includes:
and merging the sub-measurement coverage rate data corresponding to each version branch with the key value information in the key value pair information corresponding to the version branch in the difference log to obtain merged sub-measurement coverage rate data.
5. The method for testing the coverage rate in the android software integration test of claim 3, wherein the step of detecting all diff methods and all non-diff methods corresponding to the release branch according to the difference log comprises:
each method of traversing the issuing branch queries the difference log when traversing to one method, and if diff line information corresponding to the method is obtained by querying from the difference log, the method is determined as the diff method; and if the diff line information corresponding to the method cannot be inquired from the difference log, determining the method as a non-diff method.
6. The method of claim 1, wherein the step of combining the initial collective coverage data of the release branch with the combined branch coverage data to obtain final collective coverage data comprises:
and replacing diff row information corresponding to the diff method in the merged sub-measurement coverage rate data with the set measurement coverage rate data corresponding to each diff method in the initial set measurement coverage rate data of the issuing branch to obtain final set measurement coverage rate data.
7. The method for testing the coverage rate in the android software integration test as claimed in claim 1, wherein the step of generating the coverage rate report corresponding to the release branch in the integration coverage rate test according to the final set-test coverage rate data includes:
setting preset identifications corresponding to the version branches corresponding to the non-diff methods for the set measurement coverage data corresponding to each non-diff method in the final set measurement coverage data to obtain marked set measurement coverage data;
and generating a coverage rate report in an html format according to the marked collective measurement coverage rate data, and adding a mark for distinguishing display for the collective measurement coverage rate data provided with a preset mark when the coverage rate report is generated.
8. A coverage rate testing device in an android software integration test is characterized by comprising:
the branch measurement data acquisition module is used for acquiring branch measurement coverage rate data corresponding to all version branches of the software to be measured in the current version;
the difference log obtaining module is used for obtaining a difference log corresponding to the release branch of the software to be tested in the current version, and the difference log is generated by diff comparison between the release branch code of the release branch and the original version branch codes of all the version branches;
the first data merging module is used for merging the sub-measurement coverage rate data corresponding to all the version branches according to the difference log to obtain merged sub-measurement coverage rate data;
the integrated coverage rate testing module is used for detecting all diff methods and all non-diff methods corresponding to the issuing branch according to the difference log, and carrying out integrated coverage rate testing on codes corresponding to all diff methods in the issuing branch codes to obtain initial integrated coverage rate data of the issuing branch;
the second data merging module is used for merging the initial collective coverage rate data of the issuing branch and the merged sub-collective coverage rate data to obtain final collective coverage rate data;
and the coverage rate report generating module is used for generating a coverage rate report corresponding to the release branch in the integrated coverage rate test according to the final integrated coverage rate data.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011406234.8A CN112463620B (en) | 2020-12-03 | 2020-12-03 | Coverage rate test method and device in android software integration test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011406234.8A CN112463620B (en) | 2020-12-03 | 2020-12-03 | Coverage rate test method and device in android software integration test |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112463620A true CN112463620A (en) | 2021-03-09 |
| CN112463620B CN112463620B (en) | 2024-09-17 |
Family
ID=74804895
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011406234.8A Active CN112463620B (en) | 2020-12-03 | 2020-12-03 | Coverage rate test method and device in android software integration test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463620B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114003501A (en) * | 2021-11-03 | 2022-02-01 | 中国银行股份有限公司 | Method and device for determining test coverage rate |
| CN115269444A (en) * | 2022-09-30 | 2022-11-01 | 平安银行股份有限公司 | Code static detection method and device and server |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105988926A (en) * | 2015-02-13 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Method and device for processing multi-version test data |
| CN106326120A (en) * | 2016-08-22 | 2017-01-11 | 北京金山安全软件有限公司 | Regression testing method and device for application software and electronic equipment |
| CN107957956A (en) * | 2017-12-26 | 2018-04-24 | 广州品唯软件有限公司 | Test method, device and the readable storage medium storing program for executing of software differences coverage rate |
| CN108519945A (en) * | 2018-03-21 | 2018-09-11 | 腾讯科技（深圳）有限公司 | Coverage rate test method, apparatus and storage device |
| CN108829593A (en) * | 2018-06-05 | 2018-11-16 | 平安壹钱包电子商务有限公司 | Code coverage calculation and analysis methods, device, equipment and storage medium |
| CN110209568A (en) * | 2018-04-24 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Coverage rate test method, apparatus and storage equipment |
| CN111078549A (en) * | 2019-12-06 | 2020-04-28 | 广州品唯软件有限公司 | Code coverage rate processing method and device and computer equipment |
| CN111124894A (en) * | 2019-12-06 | 2020-05-08 | 广州品唯软件有限公司 | Code coverage rate processing method and device and computer equipment |
| CN111444087A (en) * | 2020-03-03 | 2020-07-24 | 北京齐尔布莱特科技有限公司 | Coverage rate data processing method and device, computing equipment and readable storage medium |
-
2020
- 2020-12-03 CN CN202011406234.8A patent/CN112463620B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105988926A (en) * | 2015-02-13 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Method and device for processing multi-version test data |
| CN106326120A (en) * | 2016-08-22 | 2017-01-11 | 北京金山安全软件有限公司 | Regression testing method and device for application software and electronic equipment |
| CN107957956A (en) * | 2017-12-26 | 2018-04-24 | 广州品唯软件有限公司 | Test method, device and the readable storage medium storing program for executing of software differences coverage rate |
| CN108519945A (en) * | 2018-03-21 | 2018-09-11 | 腾讯科技（深圳）有限公司 | Coverage rate test method, apparatus and storage device |
| CN110209568A (en) * | 2018-04-24 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Coverage rate test method, apparatus and storage equipment |
| CN108829593A (en) * | 2018-06-05 | 2018-11-16 | 平安壹钱包电子商务有限公司 | Code coverage calculation and analysis methods, device, equipment and storage medium |
| CN111078549A (en) * | 2019-12-06 | 2020-04-28 | 广州品唯软件有限公司 | Code coverage rate processing method and device and computer equipment |
| CN111124894A (en) * | 2019-12-06 | 2020-05-08 | 广州品唯软件有限公司 | Code coverage rate processing method and device and computer equipment |
| CN111444087A (en) * | 2020-03-03 | 2020-07-24 | 北京齐尔布莱特科技有限公司 | Coverage rate data processing method and device, computing equipment and readable storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114003501A (en) * | 2021-11-03 | 2022-02-01 | 中国银行股份有限公司 | Method and device for determining test coverage rate |
| CN115269444A (en) * | 2022-09-30 | 2022-11-01 | 平安银行股份有限公司 | Code static detection method and device and server |
| CN115269444B (en) * | 2022-09-30 | 2023-02-03 | 平安银行股份有限公司 | Code static detection method and device and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112463620B (en) | 2024-09-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032611B (en) | Script deployment method and device, computer equipment and storage medium | |
| CN107808831B (en) | Whole-course traceable semiconductor test data recording method | |
| CN108427613B (en) | Abnormal interface positioning method and device, computer equipment and storage medium | |
| CN112363941A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN109726134B (en) | Interface test method and system | |
| CN112039900B (en) | Network security risk detection method, system, computer device and storage medium | |
| CN112463620B (en) | Coverage rate test method and device in android software integration test | |
| CN108459850B (en) | Method, device and system for generating test script | |
| CN111026647B (en) | Method and device for acquiring code coverage rate, computer equipment and storage medium | |
| CN112363937B (en) | Differential coverage rate testing method, differential coverage rate testing device, computer equipment and storage medium | |
| CN112631926B (en) | Code test coverage rate display method and device, computer equipment and storage medium | |
| CN112115005B (en) | Test data acquisition method and device, computer equipment and storage medium | |
| CN113282513B (en) | Interface test case generation method and device, computer equipment and storage medium | |
| CN111124894B (en) | Code coverage rate processing method and device and computer equipment | |
| CN112862449A (en) | Structural chemical industry bill generation method and device, computer equipment and storage medium | |
| CN113360389A (en) | Performance test method, device, equipment and storage medium | |
| CN110309057B (en) | Automatic script-based flow project testing method and related equipment | |
| CN117131545A (en) | Data processing method and device, storage medium and terminal | |
| CN112486824B (en) | Case code generation method, device, computer equipment and storage medium | |
| CN111090583B (en) | Method and device for generating code coverage rate report and computer equipment | |
| CN115203697A (en) | File detection method, device and equipment and readable storage medium | |
| CN110704218B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN114866447A (en) | Automatic test method and device for message receiving and sending of vehicle controller | |
| CN114138734A (en) | Web-based version management method facing database and file resource | |
| CN111078549B (en) | Code coverage rate processing method and device and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |