CN108170610A - The method and apparatus for determining test coverage - Google Patents
The method and apparatus for determining test coverage Download PDFInfo
- Publication number
- CN108170610A CN108170610A CN201810043871.XA CN201810043871A CN108170610A CN 108170610 A CN108170610 A CN 108170610A CN 201810043871 A CN201810043871 A CN 201810043871A CN 108170610 A CN108170610 A CN 108170610A
- Authority
- CN
- China
- Prior art keywords
- code
- application
- version
- test
- tested
- 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.)
- Pending
Links
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
Abstract
This application provides a kind of method and apparatus of determining test coverage, this method includes：The test mode information for the application currently tested that test client is sent is received, test mode information includes：The mark of code tested in the version number of application and application；Determine the incremental code in the target version of the corresponding application of version number, incremental code is in the target version of application, and there are newer codes relative to the nearest old version code issued the last before target version；According to the mark for the code tested in application, the code tested in incremental code is determined；According to the code tested in incremental code, the test coverage of incremental code is determined.The application can be the validity and quality of assessment code tester, provide more accurate and effective Appreciation gist.
Description
Technical field
This application involves technical field of data processing more particularly to a kind of method and apparatus of determining test coverage.
Background technology
After the new version of application is developed, in order to detect in the new version of application with the presence or absence of loophole, tester
The code in the new version application to exploitation is needed to test.If partial code is there are loophole in new version, and tester
Member's but test leakage partial code, then can cause using there are loopholes.
It in order to avoid there is test leakage, needs to be monitored the test process of tester, and determines test coverage, with
By test coverage come evaluation test situation.However, the test coverage got at present can not accurately reflect code
The validity and quality of test.
Invention content
In view of this, this application provides a kind of method and apparatus of determining test coverage, with to assess code tester
Validity and quality, more accurate and effective Appreciation gist is provided.
To achieve the above object, on the one hand, this application provides a kind of method of determining test coverage, including：
Receive the test mode information for the application currently tested that test client is sent, the test mode packet
It includes：The mark of code tested in the version number of the application and the application；
Determine the incremental code in the target version of the corresponding application of version number, the incremental code is the application
Target version in, relative to the nearest old version code of publication the last before the target version, there are newer generations
Code；
According to the mark for the code tested in the application, the code tested in the incremental code is determined；
According to the code tested in the incremental code, the test coverage of the incremental code is determined.
Preferably, it further includes：
Show the test result information of the incremental code in the display, the test result information includes the test
Coverage rate.
Preferably, the test result information further includes：
The code tested in the incremental code and the code do not tested.
Preferably, it further includes：
According to all codes are included in the mark for the code tested in the application and the target version, determine
Go out the corresponding total test coverage of target version of the application.
Preferably, the incremental code in the target version of the corresponding application of the determining version number, including：
It is managed in library from application version, obtains the target version of the corresponding application of the version number and the mesh
The nearest old version of the application of the last publication before marking version；
According to the target version of the application and the nearest old version of the application, the target version of the application is determined
Incremental code in this.
On the other hand, present invention also provides a kind of device of determining test coverage, including：
Information acquisition unit, for receiving the test mode information of the application currently tested of test client transmission, institute
Test mode information is stated to include：The mark of code tested in the version number of the application and the application；
Increment determination unit, it is described for determining the incremental code in the target version of the corresponding application of version number
Incremental code is in the target version of the application, relative to the nearest history version of publication the last before the target version
There are newer codes for this；
Code screening unit for the mark according to the code tested in the application, determines the incremental code
In the code tested；
Coverage rate determination unit, for according to the code tested in the incremental code, determining the incremental code
Test coverage.
Preferably, it further includes：
As a result transmitting element, for the test result information of the incremental code to be sent to the test client, with
Show the test result information in the test client, the test result information includes at least the Test coverage
Rate.
Preferably, the test result information further includes：
The code tested in the incremental code and the code do not tested.
Preferably, it further includes：
Total coverage rate computing unit, for the mark according to the code tested in the application and the target version
Comprising all codes in this, the corresponding total test coverage of target version of the application is determined.
Preferably, the increment determination unit, including：
Version querying unit for being managed in library from application version, obtains the mesh of the corresponding application of the version number
The nearest old version of the application of the last publication before marking version and the target version；
Version comparing unit, for the target version according to the application and the nearest old version of the application, really
Incremental code in the target version of the fixed application.
As known from the above, server is receiving the version number of the application currently tested of test client transmission and should answer
It is not directly using the code tested in the application, to calculate in the application after the mark for the code tested in
The test coverage of all codes, but the incremental code of target version that the version number for first obtaining the application is characterized, and really
Determine the code tested in incremental code, finally according to the code tested in incremental code, determine the survey of the incremental code
Try coverage rate, due to application target version there are the very big of loophole the reason is that due to there is leakage in the incremental code that newly increases
Therefore hole, by the test coverage of the incremental code in the target version of application, more accurate can be assessed with effective to this
The test quality of target version and the validity of test.
Description of the drawings
In order to illustrate the technical solutions in the embodiments of the present application or in the prior art more clearly, to embodiment or it will show below
There is attached drawing needed in technology description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
The embodiment of application, for those of ordinary skill in the art, without creative efforts, can also basis
The attached drawing of offer obtains other attached drawings.
Fig. 1 shows a kind of flow diagram of method one embodiment of determining test coverage of the application；
Fig. 2 shows a kind of schematic diagrames at the test result interface that server in the application exports；
Fig. 3 shows the flow diagram of another embodiment of a kind of method of determining test coverage of the application；
Fig. 4 shows a kind of composition structure diagram of device one embodiment of determining test coverage of the application.
Specific embodiment
In the case that the method that test coverage is determined in the application can be applied to there is new version in application, for
The scene that code in the new version of application is tested.
Equipment involved by the scheme of the application includes：Test client and server.
Wherein, equipment end of the test client where tester's test application.
Server is the equipment being monitored for the test case to test client test application.
With reference to more than general character, referring to Fig. 1, it illustrates a kind of method one embodiment of determining test coverage of the application
Flow diagram, the present embodiment is introduced from server side.
The method of the present embodiment can include：
S101 receives the test mode information for the application currently tested that test client is sent.
Wherein, which includes：The mark of code tested in the version number of the application and the application
Know.
The version number of application is for identifying the version of application, e.g., the version number of application can include application 0.1 version,
0.2 version of application etc., what the version number according to application can determine test is the code in which version of application.
Test client can obtain the version number for the application currently tested and tester has tested the application
The corresponding version of version number in any partial code in which file and file etc..Since each code can be tested one by one
(Codabar code is it is also assumed that line code), the code that the embodiment of the present application is previously mentioned may be considered a Codabar code.
Wherein, the code tested can be the respective mark of one or more code.
Wherein, the mode of the test mode information of application currently tested of test client acquisition can there are many realize can
Energy.Such as, in one implementation, when the code of application is to pre-process language (Hypertext using supertext
Preprocessor, PHP) when writing, which can monitor and obtain the test client using debug tools
Test mode information corresponding to test application.Wherein, debug tools are the PHP program debuggers of open source code, it can be with
For tracking, the operation conditions of PHP programs is debugged and analyzed.
Certainly, in order to enable server can determine each client, test client can also obtain test visitor
The corresponding IP address in family end or other be used for the mark of unique mark equipment, and the identification information of equipment is carried in the test
In status information.
S102 determines the incremental code in the target version of the corresponding application of version number.
For ease of description, the version by the corresponding application of the version number of the application is known as target version.Meanwhile it will apply
Target version before the version of the application of the last publication be known as nearest old version.For example, it is assumed that it is sent out according to the time
The sequencing of cloth has issued 0.2 version of application and 0.3 version of application, it is assumed that 0.3 version of application is mesh successively
Version is marked, then 0.2 version of the application is relative to the nearest old version in the target version.
Wherein, incremental code is in the target version of application, relative to publication the last before the target version most
There are newer codes for nearly old version code.It is described herein there are newer code can be in target version increase newly generation
Code or the opposite code with finding transformation in the nearest old version etc..
It is understood that the incremental code in target version can have it is one or more of, according to the version of different application
This update status is different, and the quantity of the incremental code in target version can also have different situations.
Wherein, server determine incremental code in the target version mode can there are many：
Such as, it in the case of a kind of possibility, is managed in library from application version, obtains the mesh of the corresponding application of the version number
Mark version and the nearest old version of the corresponding application of the target version；According to the application target version and should should
Nearest old version determines the incremental code in the target version of the application.For example, it is nearest with this to compare the target version
Each line code in old version, so as to find out the incremental code included in the target version.
Wherein, the code using each version is stored in application version management library, e.g., application version management library can
Think Git code library management systems.
For another example, in the case of another is possible, if stored in application version management library the application is nearest from this
Old version is upgraded to the difference packet needed for the target version, which includes a line or multirow incremental code, then services
Device can directly acquire the incremental code included in the difference packet.
S103 according to the mark for the code tested in the application, determines the code tested in the incremental code.
Since the code tested that test client is sent is all codes having been tested in target version, because
This, has part and is not belonging to incremental code in the code tested, therefore, it is necessary to the mark according to the code tested,
The code tested is found out from all incremental codes.
S104 according to the code tested in the incremental code, determines the test coverage of the incremental code.
Test coverage is the ratio that the code tested occupies the code do not tested.
In the embodiment of the present application, for incremental code, the corresponding test coverage of incremental code is determined.Such as, will
The code tested in incremental code is determined as test coverage with the ratio of all incremental codes.
Inventor it has been investigated that, for the version of an application, before the version of the application is relative to the version
There are newer code it is exactly incremental code in the version of the last time publication, and the part except incremental code does not occur then
Variation.Moreover, the version of application there are the very big of loophole the reason is that due in the incremental code that newly increases there are loophole, because
This, if tested code quantity is not more in incremental code, the risk that application starts a leak is larger.However, at present very
In the mode of more test coverages, obtained test coverage is all only that the code tested in the version of application occupies this
The ratio of all codes in the version of application.Since incremental code is usually sub-fraction code in the version applied, such as
Incremental code is by the more of test leakage in the version of fruit application, and the code in the version of the application except incremental code is by side leakage
Code is less, then the corresponding test coverage of all codes may also can be higher in the version of the application.It follows that only increase
The coverage rate that amount code is tested is higher, can just illustrate that the quality of the test to the version of the application is higher, just can be accurate
Assess the validity of test.
Based on above the study found that the application is for the incremental code in the target version of application, to determine incremental code
Test coverage, with the test coverage according to the incremental code, to evaluate and test the test that tester tests the target version
Quality.
As it can be seen that in the embodiment of the present application, server is receiving the application currently tested of test client transmission
After the mark of code tested in version number and the application, it is not directly using the code tested in the application, comes
The test coverage of all codes in the application is calculated, but the increasing of target version that the version number for first obtaining the application is characterized
Code is measured, and determines the code tested in incremental code, finally according to the code tested in incremental code, determines the increasing
The test coverage of code is measured, there are the very big the reason is that due to the increment generation newly increased of loophole due to the target version of application
There are loophole in code, therefore, by the test coverage of the incremental code in the target version of application, can it is more accurate with have
Effect assessment is to the test quality of the target version and the validity of test.
It is understood that in order to which the personnel of server side are convenient for checking, this can be shown in the display of server
The test coverage of incremental code in the target version of the application of test client test.
Such as, referring to Fig. 2, it illustrates a kind of interface schematic diagrams that server shows test result, can be seen by the Fig. 2
Go out, shown in the server involved in the different branches (it is considered that sub-project of a project) for disparity items
And the version number of the application version arrived, the test client for testing the application version (represent test client in the test machine of Fig. 2
End) mark, starting testing time of the application version and terminate the testing time, the item number of the incremental code in the application increases
The item number of code and the test coverage of incremental code etc. have been tested in amount code.
Further, in order to enable user can intuitively see which incremental code has been tested, which
Not tested, server can also be shown in incremental code in addition to this test result information of test coverage is shown
The code and the information of not tested code being tested.Such as, the mark of each Codabar code tested in incremental code, with
And the specific code content for each Codabar code tested；The particular content of the mark for the code do not tested and the code do not tested
Deng.For example, server can show the mark and specific code of all incremental codes, and pass through red-label and go out to have tested
Incremental code, and the incremental code do not tested then labeled as red.
Such as, in the interface shown of Fig. 2, each corresponding each test result information of application version finally wraps
One " details " row are included, " checking " option is provided in " details " row, if user clicks the option for being somebody's turn to do " checking ", server
The information of the code being tested in incremental code and not tested code can be obtained, and passes through another displaying interface
Go out incremental code, and pass through special identifier and indicate the code tested in incremental code.
Certainly, the test coverage of the incremental code can also be sent to the test client by server, in the survey
The test coverage is shown in examination client.
Further, in order to enable user can intuitively see which incremental code has been tested, which
Not tested, server can also will increase other than test coverage this test result information is sent to client
The code and the information of not tested code being tested in amount code are to the test client.
For the ease of the clearer scheme for understanding the application, referring to Fig. 3, determine that test is covered it illustrates the application one kind
The flow diagram of another embodiment of the method for lid rate, the method for the present embodiment can include：
S301 when test client detects the test request that tester initiates, determines test request institute request for test
Application target version, record test initial time and monitors the testing progress of the target version of the application.
Such as, when tester is initiated to application test request, what test client can determine currently to test is which should
Which version, and pass through the debug tools and collect the information of each Codabar code tested in test process, test client
Characterized mark of test machine in end etc..
S302, when test client detects EOT end of test instruction, the record test end time, and adopted to server transmission
The test mode information collected.
When tester completes the test of the target version of the application or terminates test, test client determines to detect
It is instructed to the EOT end of test, and determines the test end time, while the test mode information that will be collected into can be triggered and be sent to clothes
Business device.
Wherein, which includes：The mark of code tested in the version number of the application and the application
Know, test the time started, test the end time, test client mark.
S303, server is according to the version number of the application, and from application management server, obtaining that the version number is corresponding should
The nearest old version of the application of the last publication before the target version of application and the target version.
S304, server determine the application according to the target version of the application and the nearest old version of the application
Incremental code in target version.
S305 according to the mark for the code tested in the application, determines the code tested in the incremental code.
Above step S303 may refer to the related introduction of preceding embodiment to step S305, and details are not described herein.
S306 according to the code and the total number of incremental code tested in the incremental code, calculates the increasing tested
Amount code occupies the ratio of all incremental codes, by the test coverage that the ratio-dependent is the incremental code.
For example, it is assumed that one shares 100 incremental codes, wherein the code tested has 80, then the test of incremental code
Coverage rate is 80 percent.
S307, server go out the test result information of the target version of the application by displaying interface in the display.
The concrete mode that server shows the test result information may refer to the related introduction of front, no longer superfluous herein
It states.
It is understood that in the embodiment above, the test coverage using all codes is checked for the ease of user,
Server can also be determined according to all codes are included in the mark for the code tested in application and the target version
The corresponding total test coverage of target version of the application.Such as, include 1000 Codabar codes altogether in the target version of application,
In, the code tested has 700 (including incremental code and the code for being not belonging to incremental code), then total test coverage is hundred
/ seven ten.
Further, server while the test coverage of output increment code, can also export the target of application
The corresponding total test coverage of version.
A kind of method of determining test coverage of corresponding the application, present invention also provides a kind of determining test coverages
Device.
Such as, referring to Fig. 4, it illustrates a kind of composition structures of device one embodiment of determining test coverage of the application
Schematic diagram, the device can be applied to the server for being monitored to test client.The device includes：
Information acquisition unit 401, for receiving the test mode information of the application currently tested of test client transmission,
The test mode information includes：The mark of code tested in the version number of the application and the application；
Increment determination unit 402, for determining the incremental code in the target version of the corresponding application of version number, institute
It states in the target version that incremental code is the application, relative to the nearest history of publication the last before the target version
There are newer codes for version；
Code screening unit 403 for the mark according to the code tested in the application, determines the increment generation
The code tested in code；
Coverage rate determination unit 404, for according to the code tested in the incremental code, determining the incremental code
Test coverage.
As it can be seen that server receive test client transmission the application currently tested version number and the application in
It is not directly using the code tested in the application, to calculate all generations in the application after the mark of the code of test
The test coverage of code, but the incremental code of target version that the version number for first obtaining the application is characterized, and determine increment
The code tested in code finally according to the code tested in incremental code, determines the Test coverage of the incremental code
Rate, due to application target version there are the very big of loophole the reason is that due in the incremental code that newly increases there are loophole, because
This, by the test coverage of the incremental code in the target version of application, more accurate can assess with effective to the target
The test quality of version and the validity of test.
In one implementation, which can also include：
As a result transmitting element, for the test result information of the incremental code to be sent to the test client, with
Show the test result information in the test client, the test result information includes at least the Test coverage
Rate.
Further, the test result information further includes：
The code tested in the incremental code and the code do not tested.
In a kind of possible realization method, which can also include：
Total coverage rate computing unit, for the mark according to the code tested in the application and the target version
Comprising all codes in this, the corresponding total test coverage of target version of the application is determined.
In one implementation, the increment determination unit, including：
Version querying unit for being managed in library from application version, obtains the mesh of the corresponding application of the version number
The nearest old version of the application of the last publication before marking version and the target version；
Version comparing unit, for the target version according to the application and the nearest old version of the application, really
Incremental code in the target version of the fixed application.
It should be noted that each embodiment in this specification is described by the way of progressive, each embodiment weight
Point explanation is all difference from other examples, and just to refer each other for identical similar part between each embodiment.
For device class embodiment, since it is basicly similar to embodiment of the method, so description is fairly simple, related part is joined
See the part explanation of embodiment of the method.
Finally, it is to be noted that, herein, relational terms such as first and second and the like be used merely to by
One entity or operation are distinguished with another entity or operation, without necessarily requiring or implying these entities or operation
Between there are any actual relationship or orders.Moreover, term " comprising ", "comprising" or its any other variant meaning
Covering non-exclusive inclusion, so that process, method, article or equipment including a series of elements not only include that
A little elements, but also including other elements that are not explicitly listed or further include for this process, method, article or
The intrinsic element of equipment.In the absence of more restrictions, the element limited by sentence "including a ...", is not arranged
Except also there are other identical elements in the process including element, method, article or equipment.
The foregoing description of the disclosed embodiments enables those skilled in the art to realize or use the present invention.To this
A variety of modifications of a little embodiments will be apparent for a person skilled in the art, and the general principles defined herein can
Without departing from the spirit or scope of the present invention, to realize in other embodiments.Therefore, the present invention will not be limited
The embodiments shown herein is formed on, and is to fit to consistent with the principles and novel features disclosed herein most wide
Range.
It the above is only the preferred embodiment of the present invention, it is noted that those skilled in the art are come
It says, various improvements and modifications may be made without departing from the principle of the present invention, these improvements and modifications also should be regarded as
Protection scope of the present invention.
Claims (10)
- A kind of 1. method of determining test coverage, which is characterized in that including：The test mode information for the application currently tested that test client is sent is received, the test mode information includes：Institute State application version number and the application in the mark of code tested；Determine the incremental code in the target version of the corresponding application of version number, the incremental code is the mesh of the application It marks in version, relative to the nearest old version code issued the last before the target version, there are newer codes；According to the mark for the code tested in the application, the code tested in the incremental code is determined；According to the code tested in the incremental code, the test coverage of the incremental code is determined.
- 2. the method for determining test coverage according to claim 1, which is characterized in that further include：Show the test result information of the incremental code in the display, the test result information includes the Test coverage Rate.
- 3. the method for determining test coverage according to claim 1 or 2, which is characterized in that the test result information It further includes：The code tested in the incremental code and the code do not tested.
- 4. the method for determining test coverage according to claim 1 or 2, which is characterized in that further include：According to all codes are included in the mark for the code tested in the application and the target version, institute is determined State the corresponding total test coverage of target version of application.
- 5. the method for determining test coverage according to claim 1, which is characterized in that the determining version number is corresponding Incremental code in the target version of the application, including：It is managed in library from application version, obtains the target version of the corresponding application of the version number and the target version The nearest old version of the application of the last publication before this；According to the target version of the application and the nearest old version of the application, in the target version for determining the application Incremental code.
- 6. a kind of device of determining test coverage, which is characterized in that including：Information acquisition unit, for receiving the test mode information of the application currently tested of test client transmission, the survey Examination status information includes：The mark of code tested in the version number of the application and the application；Increment determination unit, for determining the incremental code in the target version of the corresponding application of version number, the increment Code is in the target version of the application, deposits relative to the nearest old version of publication the last before the target version In newer code；Code screening unit for the mark according to the code tested in the application, is determined in the incremental code The code of test；Coverage rate determination unit, for according to the code tested in the incremental code, determining the test of the incremental code Coverage rate.
- 7. the device of determining test coverage according to claim 6, which is characterized in that further include：As a result transmitting element, for the test result information of the incremental code to be sent to the test client, in institute It states and shows the test result information in test client, the test result information includes at least the test coverage.
- 8. the device of the determining test coverage described according to claim 6 or 7, which is characterized in that the test result information It further includes：The code tested in the incremental code and the code do not tested.
- 9. the device of the determining test coverage described according to claim 6 or 7, which is characterized in that further include：Total coverage rate computing unit, in the mark according to the code tested in the application and the target version Comprising all codes, the corresponding total test coverage of target version of the application is determined.
- 10. the device of determining test coverage according to claim 9, which is characterized in that the increment determination unit, packet It includes：Version querying unit for being managed in library from application version, obtains the target version of the corresponding application of the version number The nearest old version of this and the target version application of the last publication before；Version comparing unit for the target version according to the application and the nearest old version of the application, determines institute State the incremental code in the target version of application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810043871.XA CN108170610A (en) | 2018-01-17 | 2018-01-17 | The method and apparatus for determining test coverage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810043871.XA CN108170610A (en) | 2018-01-17 | 2018-01-17 | The method and apparatus for determining test coverage |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108170610A true CN108170610A (en) | 2018-06-15 |
Family
ID=62515073
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810043871.XA Pending CN108170610A (en) | 2018-01-17 | 2018-01-17 | The method and apparatus for determining test coverage |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108170610A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109857631A (en) * | 2018-11-02 | 2019-06-07 | 平安科技（深圳）有限公司 | Code coverage statistical method, device, equipment and storage medium based on artificial intelligence |
| CN110532174A (en) * | 2019-07-24 | 2019-12-03 | 平安科技（深圳）有限公司 | Calculate method, apparatus, computer equipment and the storage medium of incremental code coverage rate |
| CN110727602A (en) * | 2019-10-23 | 2020-01-24 | 网易（杭州）网络有限公司 | Coverage rate data processing method and device and storage medium |
| CN111026665A (en) * | 2019-12-09 | 2020-04-17 | 中国建设银行股份有限公司 | Test range analysis method, device and equipment |
| CN111124910A (en) * | 2019-12-20 | 2020-05-08 | 北京达佳互联信息技术有限公司 | Method, device, equipment and storage medium for determining test code execution data |
| CN113537780A (en) * | 2021-07-19 | 2021-10-22 | 山东浪潮通软信息科技有限公司 | Method, device and medium for testing coverage assessment through API (application program interface) |
| CN113535533A (en) * | 2020-04-15 | 2021-10-22 | 百度在线网络技术（北京）有限公司 | Method, apparatus, device and storage medium for testing code |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8522215B1 (en) * | 2008-07-14 | 2013-08-27 | The Mathworks, Inc. | Coverage analysis for variable size signals |
| CN104298587A (en) * | 2013-07-15 | 2015-01-21 | 腾讯科技（深圳）有限公司 | Code coverage test method, device and system |
| CN105608011A (en) * | 2016-03-01 | 2016-05-25 | 网易（杭州）网络有限公司 | Determination method and device for code testing coverage rate statistical results |
| CN106201863A (en) * | 2016-06-22 | 2016-12-07 | 广州唯品会信息科技有限公司 | A kind of method and apparatus obtaining code coverage |
| CN107480066A (en) * | 2017-08-18 | 2017-12-15 | 网易（杭州）网络有限公司 | Code coverage statistical method, device, storage medium, processor and terminal |
-
2018
- 2018-01-17 CN CN201810043871.XA patent/CN108170610A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8522215B1 (en) * | 2008-07-14 | 2013-08-27 | The Mathworks, Inc. | Coverage analysis for variable size signals |
| CN104298587A (en) * | 2013-07-15 | 2015-01-21 | 腾讯科技（深圳）有限公司 | Code coverage test method, device and system |
| CN105608011A (en) * | 2016-03-01 | 2016-05-25 | 网易（杭州）网络有限公司 | Determination method and device for code testing coverage rate statistical results |
| CN106201863A (en) * | 2016-06-22 | 2016-12-07 | 广州唯品会信息科技有限公司 | A kind of method and apparatus obtaining code coverage |
| CN107480066A (en) * | 2017-08-18 | 2017-12-15 | 网易（杭州）网络有限公司 | Code coverage statistical method, device, storage medium, processor and terminal |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109857631A (en) * | 2018-11-02 | 2019-06-07 | 平安科技（深圳）有限公司 | Code coverage statistical method, device, equipment and storage medium based on artificial intelligence |
| CN110532174A (en) * | 2019-07-24 | 2019-12-03 | 平安科技（深圳）有限公司 | Calculate method, apparatus, computer equipment and the storage medium of incremental code coverage rate |
| CN110727602A (en) * | 2019-10-23 | 2020-01-24 | 网易（杭州）网络有限公司 | Coverage rate data processing method and device and storage medium |
| CN110727602B (en) * | 2019-10-23 | 2024-02-06 | 网易（杭州）网络有限公司 | Coverage rate data processing method, coverage rate data processing device and storage medium |
| CN111026665A (en) * | 2019-12-09 | 2020-04-17 | 中国建设银行股份有限公司 | Test range analysis method, device and equipment |
| CN111026665B (en) * | 2019-12-09 | 2023-02-28 | 建信金融科技有限责任公司 | Test range analysis method, device and equipment |
| CN111124910A (en) * | 2019-12-20 | 2020-05-08 | 北京达佳互联信息技术有限公司 | Method, device, equipment and storage medium for determining test code execution data |
| CN113535533A (en) * | 2020-04-15 | 2021-10-22 | 百度在线网络技术（北京）有限公司 | Method, apparatus, device and storage medium for testing code |
| CN113535533B (en) * | 2020-04-15 | 2024-04-05 | 百度在线网络技术（北京）有限公司 | Method, apparatus, device and storage medium for testing code |
| CN113537780A (en) * | 2021-07-19 | 2021-10-22 | 山东浪潮通软信息科技有限公司 | Method, device and medium for testing coverage assessment through API (application program interface) |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108170610A (en) | The method and apparatus for determining test coverage | |
| Antunes et al. | Benchmarking vulnerability detection tools for web services | |
| CN106201863A (en) | A kind of method and apparatus obtaining code coverage | |
| Briand et al. | A comprehensive empirical validation of design measures for object-oriented systems | |
| Wert et al. | Supporting swift reaction: Automatically uncovering performance problems by systematic experiments | |
| US7469362B2 (en) | Using a call stack hash to record the state of a process | |
| Orso et al. | Leveraging field data for impact analysis and regression testing | |
| Chen et al. | An automated approach to estimating code coverage measures via execution logs | |
| Schröter et al. | If your bug database could talk | |
| US9052980B2 (en) | Exception based quality assessment | |
| US20100058295A1 (en) | Dynamic Test Coverage | |
| US10360140B2 (en) | Production sampling for determining code coverage | |
| US20080249647A1 (en) | System and Method of Data Harvesting | |
| US20110093954A1 (en) | Apparatus and method for remotely diagnosing security vulnerabilities | |
| Bangash et al. | A methodology for relating software structure with energy consumption | |
| CN110287056A (en) | Webpage error message acquisition methods and device | |
| CN105681124B (en) | A kind of wire-speed detection method and device | |
| CN108009085B (en) | Channel package testing method | |
| CN110781073A (en) | Security testing method and system | |
| US7299453B2 (en) | Testing measurements | |
| Marchetto et al. | Crawlability metrics for automated web testing | |
| CN106022728A (en) | User evaluation method and device | |
| Okun et al. | Effect of static analysis tools on software security: preliminary investigation | |
| Brodie et al. | Automated problem determination using call-stack matching | |
| CN109670316A (en) | A kind of leak detection method and device based on Java exception |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180615 |
|
| RJ01 | Rejection of invention patent application after publication |