CN114116480A - Method, device, medium and equipment for determining application program test coverage rate - Google Patents

Method, device, medium and equipment for determining application program test coverage rate Download PDF

Info

Publication number
CN114116480A
CN114116480A CN202111422287.3A CN202111422287A CN114116480A CN 114116480 A CN114116480 A CN 114116480A CN 202111422287 A CN202111422287 A CN 202111422287A CN 114116480 A CN114116480 A CN 114116480A
Authority
CN
China
Prior art keywords
test
work order
determining
development work
information
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
Application number
CN202111422287.3A
Other languages
Chinese (zh)
Inventor
杨琪
向兆威
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing ByteDance Network Technology Co Ltd
Original Assignee
Beijing ByteDance Network Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing ByteDance Network Technology Co Ltd filed Critical Beijing ByteDance Network Technology Co Ltd
Priority to CN202111422287.3A priority Critical patent/CN114116480A/en
Publication of CN114116480A publication Critical patent/CN114116480A/en
Pending legal-status Critical Current

Links

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
    • 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/3688—Test management for test execution, e.g. scheduling of test suites
    • 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/3692—Test management for test results analysis

Abstract

The disclosure relates to a method, a device, a medium and equipment for determining application program test coverage rate, wherein the method comprises the following steps: responding to the received test instruction, obtaining test data of the target application program, wherein the test data comprises code information executed in a test operation process corresponding to at least one development work order, and each development work order corresponds to one function of the target application program; acquiring work order information of a tested and developed work order of a target application program, wherein the work order information comprises change file information; determining a test record corresponding to the tested development work order from the test data according to the changed file information; and determining the test coverage rate corresponding to the tested development work order according to the changed file information and the test record. Therefore, a test case of the back-end simulation data does not need to be written aiming at the changed file, and the test coverage of the changed file is determined based on the data in the actual environment of the test operation of the application program, so that the test data is more matched with the actual application scene.

Description

Method, device, medium and equipment for determining application program test coverage rate
Technical Field
The present disclosure relates to the field of testing, and in particular, to a method, an apparatus, a medium, and a device for determining application test coverage.
Background
The development of computer technology gradually raises the requirements of users on the accuracy of various application programs. In order to improve the adaptation of the application program to the use of the user, the application program generally needs to be updated, and after the update, corresponding tests need to be performed on the application program to determine that the new version is available, and then the new version can be put into use.
Currently, statistics is usually performed in a mode of executing unit test cases when determining the test coverage in the update test of an application program, for example, the test cases may be written to call an execution change method, where an executed parameter is backend simulation data for testing, so as to implement the statistics of the test coverage. In the related technology, the logic of part of the application programs is complex, the relevance of the test data to the running environment and the user operation is large, the actual data is difficult to simulate through the back-end simulation data, and the test coverage rate of the application programs is difficult to count through the technical scheme.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In a first aspect, the present disclosure provides a method for determining application test coverage, where the method includes:
responding to a received test instruction, and acquiring test data of a target application program, wherein the test data comprises code information executed in a test running process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program;
acquiring work order information of a tested and developed work order which is tested and completed by the target application program, wherein the work order information comprises change file information;
determining a test record corresponding to the tested development work order from the test data according to the change file information;
and determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record.
In a second aspect, the present disclosure provides an apparatus for determining application test coverage, the apparatus comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for responding to a received test instruction and acquiring test data of a target application program, the test data comprises code information executed in a test operation process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program;
the second acquisition module is used for acquiring the work order information of the tested and developed work order which is tested and completed by the target application program, wherein the work order information comprises change file information;
the first determining module is used for determining a test record corresponding to the tested development work order from the test data according to the change file information;
and the second determining module is used for determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record.
In a third aspect, the present disclosure provides a computer readable medium having stored thereon a computer program which, when executed by a processing apparatus, performs the steps of the method of the first aspect.
In a fourth aspect, the present disclosure provides an electronic device comprising:
a storage device having a computer program stored thereon;
processing means for executing the computer program in the storage means to carry out the steps of the method of the first aspect.
According to the technical scheme, the execution condition of the test process on the change file in the tested development work order is determined through the code information executed in the test operation process of the target application program, so that the test coverage is obtained, on one hand, a test case of rear-end simulation data does not need to be written aiming at the change file, the accuracy of the test data is ensured, on the other hand, the test coverage on the change file can be determined based on the data in the actual environment of the test operation of the target application program, so that the test data is more matched with the actual application scene, and the accuracy of the test process and the test result is ensured. In addition, the method can be applied to the test process of the application program with high relevance of test data, the operating environment and user operation, the application range of the method is further widened, meanwhile, accurate prompt can be provided for whether the test process of a tester is comprehensive or not, accurate data support is provided for the tester to carry out more comprehensive test, and the safety and the stability of target application program updating are further guaranteed.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale. In the drawings:
FIG. 1 is a flow chart of a method for determining application test coverage provided in accordance with one embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a project management tool provided in accordance with one embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a test results interface in a test platform provided in accordance with one embodiment of the present disclosure;
FIG. 4 is a schematic illustration of a test results interface in a test platform provided in accordance with another embodiment of the present disclosure;
FIG. 5 is a schematic illustration of a test results interface in a test platform provided in accordance with another embodiment of the present disclosure;
FIG. 6 is a block diagram of an apparatus for determining application test coverage provided in accordance with one embodiment of the present disclosure;
FIG. 7 illustrates a schematic diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Fig. 1 is a flowchart illustrating a method for determining application test coverage according to an embodiment of the present disclosure, where as shown in fig. 1, the method includes:
in step 11, in response to receiving a test instruction, obtaining test data of a target application program, where the test data includes code information executed in a test running process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program.
Illustratively, among other things, code updates are typically required during the update process of a target application to optimize functionality or add new functionality. In the process, the updating process can be recorded by submitting a development work order for each function to be processed, and the updating process is tested after the development is completed so as to determine the availability of the updated or newly added function. The method provided by the disclosure can be applied to a test platform, when a test is required, a user can trigger a test instruction in the test platform by clicking a button, so that the test platform receives the test instruction, can monitor the test process of the target application program, and automatically determines the test coverage of the target application program in the test process according to the monitoring data. By way of example, the target application program may automatically record test data, such as code information executed by its running process, in the test running process, and upload the test data to the test platform or store the test data in a preset storage location. Therefore, the test platform can automatically acquire the test data after receiving the test instruction, and the test process is analyzed based on the test data.
In step 12, work order information of the tested and developed work order of the target application program is obtained, wherein the work order information includes information of the changed file.
Illustratively, development work order management may be performed by Redmine project management tools. For example, a development work order may be created for a function that needs to be updated in the target application, and then a developer may develop the development work order to perform a corresponding development process, where the state of the development work order is converted into the production state and then into the production completion state, that is, the development process is completed. Then, the test can be performed based on the function corresponding to the development work order, and the state of the development work order is further converted into the state during the test and the state closed until the state closed indicates that the function development test is completed, as shown in fig. 2, the state is a schematic diagram of a project management tool, which can include the development work orders in each state, such as the state during the manufacture, the state during the test, the state closed, and the like, so that the corresponding work order information can be directly obtained through the work order management tool, and the unified management is facilitated.
Therefore, in this embodiment, the development work order may be obtained by calling the relevant work order management system, the development work order in the closed state, that is, the development work order after the test is determined as the tested development work order, such as the development work orders corresponding to "# 81" and "# 82" in fig. 2, and the work order information of the tested development work order is obtained, so as to obtain the corresponding file change condition in the development process.
In step 13, a test record corresponding to the tested development work order is determined from the test data based on the changed file information.
In this step, in order to determine whether the file changed in the test process is tested and executed, the test record corresponding to the changed file information in the test data may be used as the test record corresponding to the tested development work order, and the test record corresponding to the changed file information is filtered, so as to reduce the amount of data that needs to be analyzed.
In step 14, the test coverage corresponding to the tested development work order is determined according to the changed file information and the test record. The test coverage rate can be represented by the degree of new changed data executed in the test process, so that accurate data reference can be provided for the test comprehensiveness.
Therefore, according to the technical scheme, the execution condition of the test process on the change file in the tested development work order is determined through the code information executed in the test operation process of the target application program, so that the test coverage is obtained, on one hand, a test case of rear-end simulation data does not need to be written aiming at the change file, the accuracy of the test data is ensured, on the other hand, the test coverage on the change file can be determined based on the data in the actual environment of the test operation of the target application program, so that the test data is more matched with the actual application scene, and the accuracy of the test process and the test result is ensured. In addition, the method can be applied to the test process of the application program with high relevance of test data, the operating environment and user operation, the application range of the method is further widened, meanwhile, accurate prompt can be provided for whether the test process of a tester is comprehensive or not, accurate data support is provided for the tester to carry out more comprehensive test, and the safety and the stability of target application program updating are further guaranteed.
In one possible embodiment, an exemplary implementation of obtaining test data of a target application in response to receiving a test instruction is as follows, which may include:
and receiving test execution data sent after the target application program is started in response to the received test instruction.
As an example, in response to receiving the test instruction, the test platform may send a notification message to the target application, and after receiving the notification message, the target application may start recording the code execution data at the time of test start of the target application. For example, the target application may be a game application, and code execution data during game operation may be recorded at the beginning of game testing. As an example, in the process, when the code is executed to each line, it may be triggered to record attribute information of the code line by a debug.
And in response to receiving the notification message of the end of the target application program test, merging the received test execution data, and determining the file, line number information and execution times of each executed code line in the merged data to obtain the code information.
As an example, the target application may periodically send the recorded execution data to the testing platform, and send a notification message to the testing platform when the game is ended, so as to determine that the game testing is ended when the testing platform receives the notification message, and integrate the data received from the start to the end of the game testing, so as to obtain the test data of the running process of the target application.
For example, after the test platform receives the notification message and determines that the game test is finished, the received test execution data may be integrated, for example, for each executed code line, a file to which the code line belongs, a line number of the code line, the number of execution times of the code line, a version number of the file executed by the code line, a test user identifier corresponding to the test execution data, and the like are determined, so that the integrated data may be stored to facilitate a subsequent analysis process.
Therefore, according to the technical scheme, a user does not need to write back-end simulation data in a test case aiming at the test process of the target application program, the data recording can be carried out on the target application program in the test process, and therefore the actual data in the running process of the target application program can be used as test data to be analyzed, the test coverage in the test process is determined, the skill requirement on the test user is reduced, and the convenience and the applicability of the test of the target application program are improved.
In a possible embodiment, the test data further includes a user identifier corresponding to the test data, a test time corresponding to the test data, and an identifier of a test version corresponding to the test data; the work order information also comprises the completion time of the tested development work order, a test user identifier and a target version when the tested development work order is submitted;
an exemplary implementation manner of determining the test record corresponding to the tested development work order from the test data according to the change file information is as follows, and the step may include:
determining test records in the test data that satisfy the following conditions as test records corresponding to the tested development work order:
and in the condition 1, the file information of the file to which the code information corresponding to the test data belongs is the changed file information. In the present disclosure, determining the test coverage is to determine the degree of test execution on the changed file in the current test process, so in this embodiment, only the test record corresponding to the changed file needs to be obtained, and the test process for other unchanged files does not need to be analyzed.
And 2, the identifier of the test version corresponding to the test data is greater than or equal to the identifier of the target version.
The target version is a file version when the tested development work order is submitted, that is, a final version of a change file corresponding to the tested development work order, and if data before the target version is not test data of the change file of the tested development work order, a test record corresponding to the version before the target version does not need to be analyzed.
And 3, the test time corresponding to the test data is earlier than the completion time.
The completion time is the completion time of the tested development work order, that is, the test completion time of the tested development work order, and the test record after the completion time does not belong to the test process, so that the test record does not need to be analyzed.
And 4, the user identification corresponding to the test data is the same as the test user identification.
In general, a tested development work order is tested by the same tester in the testing process, so that test data related to the tester corresponding to the tested development work order can be directly selected for the tested development work order, and the test data corresponding to other users does not need to be analyzed.
Therefore, the test records corresponding to the change files of the corresponding test development work orders can be accurately and comprehensively determined through the judgment of the conditions, the comprehensiveness of the test records is guaranteed, the data volume needing to be analyzed can be effectively reduced, the accuracy of the test coverage calculation is guaranteed, the efficiency of the test coverage calculation is improved, and accurate data support is provided for the subsequent test process analysis and test result verification.
In a possible embodiment, the exemplary implementation of determining the test coverage corresponding to the tested development work order according to the change file information and the test record in step 14 includes:
and determining a change code line corresponding to the tested development work order according to the change file information.
The change file information may be identification information of a change file corresponding to the tested development work order, and then files before and after the current change may be obtained according to the identification information, a change code line corresponding to the change file is determined by comparing the files before and after the change, and a change code line corresponding to each change file is determined as the change code line corresponding to the tested development work order. The method for determining the changed code line by comparing the files before and after the change can be performed by using common tools in the field, and is not described herein again.
And determining the execution times of each change code line according to the test record.
The test record records the line number of each code line executed in the test process, so that query can be performed from the test record based on the determined line number of the changed code line, the test record which is queried from the test record and corresponds to the line number of the changed code line is used as one test execution of the changed code line, and the number of the queried test records is used as the execution times of the changed code line.
As another embodiment, as described above, after the test data of the target application program is obtained, the test data may be subjected to merging processing, and the merging processing may be performed by counting test records corresponding to each code line in the test data, so that the test record corresponding to each code line may be obtained, so as to obtain the number of execution times corresponding to each code line, and store the corresponding relationship between the code line and the execution test. In this embodiment, the query may be directly performed from the above correspondence based on the line number of the changed code line, so that the number of times of execution obtained by the query is used as the number of times of execution of the changed code line, thereby further improving the calculation efficiency and simplifying the calculation flow.
And then, determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
As an example, the preset threshold may be set to zero. For example, if the number of times of executing the changed code line is zero, it indicates that the changed code line is not executed in the test process, i.e. the changed code line is not covered in the test process; if the execution times of the changed code line is larger than zero, the changed code line is executed in the test process, namely the changed code line is covered in the test process.
As another example, in order to ensure the reliability of the test procedure, the preset threshold may be set to an integer N greater than zero, that is, in the case that a code line is executed N times, the execution requirement of the code line in the test procedure is considered to be met, in which case the code line may be used as the code line that has been executed by the test; when the execution number of a code line is less than N, the number is considered to be less not in accordance with the execution requirement of the test process, and the code line is not taken as the code line after test execution.
Therefore, in this embodiment, the ratio of the number of changed code lines whose execution times is greater than the preset threshold to the total number of changed code lines may be determined as the test coverage, that is, the ratio of the number of changed code lines that have been tested and executed in the test process to the total number of changed code lines.
Therefore, according to the technical scheme, whether each change code line corresponding to the tested development work order is tested and executed in the test process is determined, so that the test coverage rate corresponding to the test process is determined, in the process, the execution condition of the change code line can be directly analyzed and determined based on the test data, the calculation flow of the test coverage rate is simplified, meanwhile, effective data support can be provided for the follow-up verification test result, data support is provided for the comprehensiveness of the test process, and the accuracy and the effectiveness of the test result are ensured.
In a practical application scenario, shared changes may be made to one code file by multiple users after the current user submits the code file. For example, after the development user a1 of the tested development work order modifies the 200 th line code of the F1 file, another development user a2 may also modify the F1 file after the submission of the modification, such as adding 10 lines of code in the F1 file, thereby possibly causing the line number of the change code line corresponding to the tested development work order to change. Based on this, the present disclosure also provides the following embodiments.
In a possible embodiment, another exemplary implementation manner of determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record in step 14 is as follows, and the step may include:
and determining a change code line corresponding to the tested development work order according to the change file information. The implementation of this step is described in detail above, and is not described herein again.
And if the versions of the change files corresponding to the test records are multiple, determining the mapping code line corresponding to the change code line in the change file of the associated version according to the identification information of each change code line, wherein the associated version of the change file is a version, later than the target version when the tested development worksheet is submitted, of the multiple versions.
As is well known to those skilled in the art, in the iterative process of the application program, the version number of the updated version is usually gradually increased, so that the associated version of the change file is a version of the multiple versions, which is later than the target version when the tested development work order is submitted, that is, the version number of the associated version is greater than the version number of the target version, that is, the version is modified by other users after the change file of the tested development work order is submitted.
The testing process is carried out after the file corresponding to the tested development work order is developed and submitted, so that the version when the tested development work order is submitted can be used as a target version to determine the line number of the changed code line of the current change, the line number of the determined changed code line cannot be influenced by the modification of the code line in the version submitted by other users before the line number, and the line number of the changed code line can be deviated only by the modification carried out by other users after the tested development work order is submitted. Therefore, in the embodiments of the present disclosure, the mapping code line of each change code line in the respective associated versions may be determined based on the content of the change code line.
And aiming at each associated version, determining the execution times of each mapping code line corresponding to the associated version according to the test record corresponding to the associated version.
The number of the queried test records is determined as the execution times of the mapping code line. Similarly, after the test records are merged, the query may be performed according to the line number of each mapping code line, so as to query the execution times of each mapping code line.
And determining the test coverage rate according to the test record corresponding to the target version and the execution times of each mapping code line corresponding to the associated version.
Therefore, according to the technical scheme, when the test records correspond to the multiple versions, the mapping code lines of each change code line under the multiple versions can be determined according to the code content of the change code line, so that the test coverage can be determined based on the execution times of the change code line and the corresponding mapping code line, the combination of the test records under the multiple versions is realized, the accuracy of the test coverage calculation is further ensured, and the accuracy of the test result is ensured.
In a possible embodiment, the exemplary implementation manner of determining the test coverage according to the test record corresponding to the target version and the execution times of each mapping code line corresponding to the associated version may include:
and determining the execution times of each change code line in the target version according to the test record corresponding to the target version.
The manner of determining the execution times of each change code line in the target version is similar to the above-mentioned manner of determining the execution times, and is not described herein again.
And determining the sum of the execution times of each changed code line in the target version and the execution times of the mapping code line corresponding to the changed code line as the execution times of the changed code line.
As described above, the changed code line and the mapping code line corresponding to the changed code line substantially correspond to the same line code, which is a line number offset due to modification by other users after the test development work order is submitted, and therefore, the actual execution number of each changed code line, that is, the sum of the execution number of the changed code line in the target version and the execution number of the mapping code line corresponding to the changed code line, may be determined as the execution number of the changed code line, that is, the number of times the changed code line is actually executed in the test process, based on the correspondence between the changed code line and the mapping code line.
And determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
Therefore, by the technical scheme, the execution times of the changed code line and the execution times of the mapping code line corresponding to the changed code line can be further merged, so that the actual execution times of the changed code line is obtained, the accuracy and comprehensiveness of the determined execution times are ensured while the data merging compatibility of multiple versions is improved, the accuracy of a test result is further ensured, accurate data support is provided for the subsequent target application program evaluation, and the availability of the target application program is ensured.
In a possible embodiment, the method further comprises:
and responding to a received display instruction of the test coverage, and sending display information to the terminal so as to enable the terminal to display the test coverage and the display information on a coverage display interface, wherein the display information comprises files to which the change code lines belong, the change code lines and the execution times corresponding to each change code line.
Fig. 3 is a schematic diagram of a test result interface in the test platform, and the test coverage corresponding to each development work order after the test is completed may be displayed in the interface. Then, the user may trigger a display instruction of the test coverage by clicking a display button of the corresponding development work order, and if the display instruction may be triggered by clicking an icon of the left "+" in fig. 3 or clicking the corresponding test coverage, the display instruction may be sent to the server, so that the server determines the display information corresponding to the tested development work order based on the display instruction.
Then, the test platform terminal receives the display information, and may further display the display information in the test result interface, as shown in fig. 4, after receiving the display information sent by the server, the display information corresponding to the test development work order may be expanded and displayed below the display record of the tested development work order, for example, a file to which a change code line belongs is displayed in an a1 area, the change code line is displayed in an a2 area, and the execution times corresponding to each change code line is displayed in an A3 area, so that a user can conveniently view detailed information of a test process.
In this embodiment, in response to the operation requirement of the user, the change file corresponding to the test process and the execution times of each change code line corresponding to the change code line may be further displayed, so that the user may make the execution condition of each change code line in the test process more clear, the user may conveniently grasp the whole test process, provide data reference for retesting or ending the test, provide data support for performing a supplemental test on the change code line, and conveniently find a test gap in the test process, thereby further ensuring the accuracy and comprehensiveness of the test process.
Similarly, the user may also check the relevant file by clicking the corresponding "check" button on the test result interface, for example, by clicking the "check" button under the change file, the change file may be checked, and by clicking the "check" button under the test record, the test record may be checked, as shown in fig. 5, a new window may be displayed on the layer of the test result display interface to display the test record, so as to meet the checking requirement of the user.
In one possible embodiment, the method may further comprise:
and responding to a received checking instruction aiming at a target user, and determining a test development work order corresponding to the user identification of the target user and a test coverage rate corresponding to the test development work order.
For example, the test condition of a certain test user can be checked based on the test platform, then the user can select a test record of a target user in the display interface for checking, in response to receiving a check instruction, the terminal can send the check instruction to the test platform, then the test platform receives the check instruction, and can query with the user identifier contained in the check instruction, so as to obtain a test development work order with the test user identifier as the user identifier, and a test coverage rate corresponding to the test development work order.
And sending the test development work order and the test coverage rate corresponding to the test development work order to a terminal so as to display the test development work order corresponding to the target user and the test coverage rate corresponding to the test development work order by the terminal.
The queried information may then be sent to the terminal for display at the terminal. As an example, the test development work order corresponding to the target user and the test coverage corresponding to the test development work order may be directly displayed. As another example, the average test coverage of the target user for testing the development work order may be determined according to the number of the test development work orders corresponding to the target user and the test coverage corresponding to each test development work order, so that the test capability of the target user may be characterized, the target user may conveniently make a related test mode in time, the convenience of the method may be further improved, and the user experience may be improved.
The present disclosure also provides an apparatus for determining application test coverage, as shown in fig. 6, where the apparatus 10 includes:
a first obtaining module 100, configured to obtain, in response to receiving a test instruction, test data of a target application program, where the test data includes code information executed in a test running process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program;
a second obtaining module 200, configured to obtain work order information of a tested and developed work order in which the target application program is tested, where the work order information includes change file information;
a first determining module 300, configured to determine, according to the change file information, a test record corresponding to the tested development work order from the test data;
and a second determining module 400, configured to determine, according to the change file information and the test record, a test coverage corresponding to the tested development work order.
Optionally, the second determining module includes:
the first determining submodule is used for determining a change code line corresponding to the tested development work order according to the change file information;
the second determining submodule is used for determining the execution times of each change code line according to the test record;
and the third determining submodule is used for determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
Optionally, the second determining module includes:
the first determining submodule is used for determining a change code line corresponding to the tested development work order according to the change file information;
a fourth determining submodule, configured to determine, if there are multiple versions of the change file corresponding to the test record, a mapping code line corresponding to the change code line in a change file of an associated version according to identification information of each change code line, where the associated version of the change file is a version, later than a target version when the tested development work order is submitted, of the multiple versions;
a fifth determining submodule, configured to determine, for each associated version, the number of times of executing each mapping code line corresponding to the associated version according to the test record corresponding to the associated version;
and a sixth determining submodule, configured to determine the test coverage according to the test record corresponding to the target version and the execution times of each mapping code line corresponding to the associated version.
Optionally, the sixth determining sub-module includes:
a seventh determining submodule, configured to determine, according to the test record corresponding to the target version, the number of times of execution of each change code line in the target version;
an eighth determining submodule, configured to determine, as the number of execution times of the changed code line, a sum of the number of execution times of each changed code line in the target version and the number of execution times of the mapped code line corresponding to the changed code line;
and the third determining submodule is used for determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
Optionally, the apparatus further comprises:
the first sending module is used for responding to a received display instruction of the test coverage rate and sending display information to the terminal so that the terminal can display the test coverage rate and the display information on a coverage rate display interface, wherein the display information comprises files to which the change code lines belong, the change code lines and the execution times corresponding to each change code line.
Optionally, the test data further includes a user identifier corresponding to the test data, test time corresponding to the test data, and an identifier of a test version corresponding to the test data; the work order information also comprises the completion time of the tested development work order, a test user identifier and a target version when the tested development work order is submitted;
the first determining module includes:
a ninth determining sub-module, configured to determine a test record satisfying the following conditions in the test data as a test record corresponding to the tested development work order:
the file information of the file to which the code information corresponding to the test data belongs is the changed file information;
the mark of the test version corresponding to the test data is greater than or equal to the mark of the target version;
the test time corresponding to the test data is earlier than the completion time;
and the user identification corresponding to the test data is the same as the test user identification.
Optionally, the apparatus further comprises:
the third determining module is used for responding to a received checking instruction aiming at a target user, and determining a test development work order corresponding to the user identification of the target user and a test coverage rate corresponding to the test development work order;
and the second sending module is used for sending the test development work order and the test coverage rate corresponding to the test development work order to the terminal so as to display the test development work order corresponding to the target user and the test coverage rate corresponding to the test development work order.
Optionally, the first obtaining module includes:
the receiving submodule is used for responding to the received test instruction and receiving test execution data sent after the target application program is started in a test mode;
and the merging submodule is used for merging the received test execution data in response to the received notification message of the end of the target application program test, and determining the file, the line number information and the execution times of each executed code line in the merged data so as to obtain the code information.
Referring now to FIG. 7, a block diagram of an electronic device 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 7, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 7 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: responding to a received test instruction, and acquiring test data of a target application program, wherein the test data comprises code information executed in a test running process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program; acquiring work order information of a tested and developed work order which is tested and completed by the target application program, wherein the work order information comprises change file information; determining a test record corresponding to the tested development work order from the test data according to the change file information; and determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present disclosure may be implemented by software or hardware. The name of the module does not in some cases constitute a limitation of the module itself, and for example, the first obtaining module may also be described as a "module that obtains test data of a target application in response to receiving a test instruction".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Example 1 provides a method of determining application test coverage, in accordance with one or more embodiments of the present disclosure, wherein the method comprises:
responding to a received test instruction, and acquiring test data of a target application program, wherein the test data comprises code information executed in a test running process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program;
acquiring work order information of a tested and developed work order which is tested and completed by the target application program, wherein the work order information comprises change file information;
determining a test record corresponding to the tested development work order from the test data according to the change file information;
and determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record.
Example 2 provides the method of example 1, wherein the determining, according to the change file information and the test record, the test coverage corresponding to the tested development work order includes:
determining a change code line corresponding to the tested development work order according to the change file information;
determining the execution times of each change code line according to the test record;
and determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
Example 3 provides the method of example 1, wherein the determining, according to the change file information and the test record, the test coverage corresponding to the tested development work order includes:
determining a change code line corresponding to the tested development work order according to the change file information;
if the versions of the change files corresponding to the test records are multiple, determining a mapping code line corresponding to the change code line in the change file of the associated version according to the identification information of each change code line, wherein the associated version of the change file is a version, later than a target version when the tested development worksheet is submitted, of the multiple versions;
aiming at each associated version, determining the execution times of each mapping code line corresponding to the associated version according to the test record corresponding to the associated version;
and determining the test coverage rate according to the test record corresponding to the target version and the execution times of each mapping code line corresponding to the associated version.
Example 4 provides the method of example 3, wherein the determining the test coverage according to the test record corresponding to the target version and the execution times of each mapping code line corresponding to the associated version includes:
determining the execution times of each change code line in the target version according to the test record corresponding to the target version;
determining the sum of the execution times of each changed code line in the target version and the execution times of the mapping code line corresponding to the changed code line as the execution times of the changed code line;
and determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
Example 5 provides the method of any of examples 2-4, wherein the method further comprises, in accordance with one or more embodiments of the present disclosure:
and responding to a received display instruction of the test coverage, and sending display information to the terminal so as to enable the terminal to display the test coverage and the display information on a coverage display interface, wherein the display information comprises files to which the change code lines belong, the change code lines and the execution times corresponding to each change code line.
Example 6 provides the method of example 1, wherein the test data further includes a user identification corresponding to the test data, a test time corresponding to the test data, and an identification of a test version corresponding to the test data; the work order information also comprises the completion time of the tested development work order, a test user identifier and a target version when the tested development work order is submitted;
determining a test record corresponding to the tested development work order from the test data according to the change file information, wherein the test record comprises:
determining test records in the test data that satisfy the following conditions as test records corresponding to the tested development work order:
the file information of the file to which the code information corresponding to the test data belongs is the changed file information;
the mark of the test version corresponding to the test data is greater than or equal to the mark of the target version;
the test time corresponding to the test data is earlier than the completion time;
and the user identification corresponding to the test data is the same as the test user identification.
Example 7 provides the method of example 6, wherein the method further comprises, in accordance with one or more embodiments of the present disclosure:
in response to receiving a viewing instruction for a target user, determining a test development work order corresponding to a user identifier of the target user and a test coverage rate corresponding to the test development work order;
and sending the test development work order and the test coverage rate corresponding to the test development work order to a terminal so as to display the test development work order corresponding to the target user and the test coverage rate corresponding to the test development work order by the terminal.
Example 8 provides the method of example 1, wherein the obtaining test data of the target application in response to receiving the test instruction, includes:
receiving test execution data sent after the target application program is started in response to the received test instruction;
and in response to receiving the notification message of the end of the target application program test, merging the received test execution data, and determining the file, line number information and execution times of each executed code line in the merged data to obtain the code information.
Example 9 provides an apparatus for determining application test coverage, according to one or more embodiments of the present disclosure, wherein the apparatus includes:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for responding to a received test instruction and acquiring test data of a target application program, the test data comprises code information executed in a test operation process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program;
the second acquisition module is used for acquiring the work order information of the tested and developed work order which is tested and completed by the target application program, wherein the work order information comprises change file information;
the first determining module is used for determining a test record corresponding to the tested development work order from the test data according to the change file information;
and the second determining module is used for determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record.
Example 10 provides a computer readable medium having a computer program stored thereon, wherein the program, when executed by a processing device, implements the steps of the method of any of examples 1-8, in accordance with one or more embodiments of the present disclosure.
Example 11 provides, in accordance with one or more embodiments of the present disclosure, an electronic device, comprising:
a storage device having a computer program stored thereon;
processing means for executing said computer program in said storage means to carry out the steps of the method of any of examples 1-8.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Claims (11)

1. A method for determining application test coverage, the method comprising:
responding to a received test instruction, and acquiring test data of a target application program, wherein the test data comprises code information executed in a test running process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program;
acquiring work order information of a tested and developed work order which is tested and completed by the target application program, wherein the work order information comprises change file information;
determining a test record corresponding to the tested development work order from the test data according to the change file information;
and determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record.
2. The method of claim 1, wherein the determining the test coverage corresponding to the tested development work order according to the change file information and the test record comprises:
determining a change code line corresponding to the tested development work order according to the change file information;
determining the execution times of each change code line according to the test record;
and determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
3. The method of claim 1, wherein the determining the test coverage corresponding to the tested development work order according to the change file information and the test record comprises:
determining a change code line corresponding to the tested development work order according to the change file information;
if the versions of the change files corresponding to the test records are multiple, determining a mapping code line corresponding to the change code line in the change file of the associated version according to the identification information of each change code line, wherein the associated version of the change file is a version, later than a target version when the tested development worksheet is submitted, of the multiple versions;
aiming at each associated version, determining the execution times of each mapping code line corresponding to the associated version according to the test record corresponding to the associated version;
and determining the test coverage rate according to the test record corresponding to the target version and the execution times of each mapping code line corresponding to the associated version.
4. The method according to claim 3, wherein the determining the test coverage according to the test record corresponding to the target version and the execution times of each mapping code line corresponding to the associated version comprises:
determining the execution times of each change code line in the target version according to the test record corresponding to the target version;
determining the sum of the execution times of each changed code line in the target version and the execution times of the mapping code line corresponding to the changed code line as the execution times of the changed code line;
and determining the ratio of the number of the changed code lines of which the execution times is greater than a preset threshold value to the total number of the changed code lines as the test coverage rate.
5. The method according to any one of claims 2-4, further comprising:
and responding to a received display instruction of the test coverage, and sending display information to the terminal so as to enable the terminal to display the test coverage and the display information on a coverage display interface, wherein the display information comprises files to which the change code lines belong, the change code lines and the execution times corresponding to each change code line.
6. The method of claim 1, wherein the test data further comprises a user identifier corresponding to the test data, a test time corresponding to the test data, and an identifier of a test version corresponding to the test data; the work order information also comprises the completion time of the tested development work order, a test user identifier and a target version when the tested development work order is submitted;
determining a test record corresponding to the tested development work order from the test data according to the change file information, wherein the test record comprises:
determining test records in the test data that satisfy the following conditions as test records corresponding to the tested development work order:
the file information of the file to which the code information corresponding to the test data belongs is the changed file information;
the mark of the test version corresponding to the test data is greater than or equal to the mark of the target version;
the test time corresponding to the test data is earlier than the completion time;
and the user identification corresponding to the test data is the same as the test user identification.
7. The method of claim 6, further comprising:
in response to receiving a viewing instruction for a target user, determining a test development work order corresponding to a user identifier of the target user and a test coverage rate corresponding to the test development work order;
and sending the test development work order and the test coverage rate corresponding to the test development work order to a terminal so as to display the test development work order corresponding to the target user and the test coverage rate corresponding to the test development work order by the terminal.
8. The method of claim 1, wherein obtaining test data for the target application in response to receiving the test instruction comprises:
receiving test execution data sent after the target application program is started in response to the received test instruction;
and in response to receiving the notification message of the end of the target application program test, merging the received test execution data, and determining the file, line number information and execution times of each executed code line in the merged data to obtain the code information.
9. An apparatus for determining application test coverage, the apparatus comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for responding to a received test instruction and acquiring test data of a target application program, the test data comprises code information executed in a test operation process corresponding to at least one development work order, and each development work order corresponds to a function of the target application program;
the second acquisition module is used for acquiring the work order information of the tested and developed work order which is tested and completed by the target application program, wherein the work order information comprises change file information;
the first determining module is used for determining a test record corresponding to the tested development work order from the test data according to the change file information;
and the second determining module is used for determining the test coverage rate corresponding to the tested development work order according to the change file information and the test record.
10. A computer-readable medium, on which a computer program is stored, characterized in that the program, when being executed by processing means, carries out the steps of the method of any one of claims 1 to 8.
11. An electronic device, comprising:
a storage device having a computer program stored thereon;
processing means for executing the computer program in the storage means to carry out the steps of the method according to any one of claims 1 to 8.
CN202111422287.3A 2021-11-26 2021-11-26 Method, device, medium and equipment for determining application program test coverage rate Pending CN114116480A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111422287.3A CN114116480A (en) 2021-11-26 2021-11-26 Method, device, medium and equipment for determining application program test coverage rate

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111422287.3A CN114116480A (en) 2021-11-26 2021-11-26 Method, device, medium and equipment for determining application program test coverage rate

Publications (1)

Publication Number Publication Date
CN114116480A true CN114116480A (en) 2022-03-01

Family

ID=80370167

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111422287.3A Pending CN114116480A (en) 2021-11-26 2021-11-26 Method, device, medium and equipment for determining application program test coverage rate

Country Status (1)

Country Link
CN (1) CN114116480A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114690988A (en) * 2022-03-08 2022-07-01 北京字跳网络技术有限公司 Test method and device and electronic equipment

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114690988A (en) * 2022-03-08 2022-07-01 北京字跳网络技术有限公司 Test method and device and electronic equipment
CN114690988B (en) * 2022-03-08 2024-01-23 北京字跳网络技术有限公司 Test method and device and electronic equipment

Similar Documents

Publication Publication Date Title
CN111625473A (en) Interface test case generation method and device, storage medium and electronic equipment
CN112597047A (en) Test method, test device, electronic equipment and computer readable medium
CN111209202A (en) Terminal application testing method and device
CN111679990B (en) Test data generation method and device, readable medium and electronic equipment
CN111400625B (en) Page processing method and device, electronic equipment and computer readable storage medium
CN111950857A (en) Index system management method and device based on service indexes and electronic equipment
CN116225886A (en) Test case generation method, device, equipment, storage medium and program product
CN114116480A (en) Method, device, medium and equipment for determining application program test coverage rate
CN113392018A (en) Traffic distribution method, traffic distribution device, storage medium, and electronic device
CN115203004A (en) Code coverage rate testing method and device, storage medium and electronic equipment
CN112596738A (en) Method and device for determining front-end page to be tested, storage medium and electronic equipment
CN109408387B (en) Page testing method and device
CN114328700B (en) Data checking method and device in medical data ETL task
CN112379967B (en) Simulator detection method, device, equipment and medium
CN114860559A (en) User operation recording method, user operation reproduction device, readable medium and equipment
CN114328215A (en) Test data deployment method, device, equipment, readable storage medium and product
CN111143355B (en) Data processing method and device
CN113849416A (en) Test method, test device, storage medium and electronic equipment
CN112905090A (en) Spreadsheet processing method, device, terminal and storage medium
CN112084086A (en) Information collection method, device, medium and electronic equipment
CN112286808A (en) Application program testing method and device, electronic equipment and medium
CN114510305B (en) Model training method and device, storage medium and electronic equipment
CN116820989A (en) Test coverage rate determining method and device, readable medium and electronic equipment
CN110489341B (en) Test method and device, storage medium and electronic equipment
CN114296986A (en) Memory leak positioning method, device, medium and electronic 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