Test efficiency quantification method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a test efficiency quantification method and device, equipment, a storage medium and a program product. The method comprises the following steps: receiving test information sent by a test terminal, wherein the test information comprises a tested software identifier, a test case identifier and a tester identifier; obtaining a test case corresponding to the test case identifier and tested software corresponding to the tested software identifier; performing instrumentation on the tested software to obtain instrumented software; testing the instrumented software by adopting the test case to obtain test process data; determining the test efficiency corresponding to the tester identifier according to the test process data; and outputting the test efficiency. The method is used for solving the problem that the test efficiency difference of all testers in the test process cannot be quantified.

Description

Technical Field

[0001] The present application relates to the field of software testing technology, and in particular to a test efficiency quantification method, device, equipment, storage medium and program product. Background Art

[0002] In order to ensure the normal service of the software, test cases are needed to test the unreleased software.

[0003] When testing software currently, different testers may use different testing processes for testing tasks, and the efficiency of the testing may vary.

[0004] The inventors discovered the following technical problems in the related art: currently it is impossible to quantify the differences in testing efficiency among testers during the testing process. Summary of the invention

[0005] The embodiments of the present application provide a test efficiency quantification method, apparatus, device, storage medium and program product to solve the problem that the test efficiency differences among testers during the test process cannot be quantified.

[0006] In a first aspect, an embodiment of the present application provides a method for quantifying test efficiency, comprising: receiving test information sent by a test terminal, wherein the test information includes a software under test identifier, a test case identifier, and a tester identifier; obtaining a test case corresponding to the test case identifier and a software under test corresponding to the software under test identifier; instrumenting the software under test to obtain instrumented software; testing the instrumented software using the test case to obtain test process data; determining the test efficiency corresponding to the tester identifier based on the test process data; and outputting the test efficiency.

[0007] In one possible implementation, the test process data includes the number of lines of code covered, the number of defects found, the number of test cases and the total execution time; based on the test process data, the test efficiency corresponding to the tester identification is determined, including: taking the weighted sum of the number of lines of code covered, the number of defects found and the number of test cases to obtain the test effect value; and calculating the test efficiency based on the test effect value and the total execution time.

[0008] In a possible implementation, after calculating the test efficiency based on the test effect value and the total execution time, it also includes: judging whether to perform efficiency optimization based on the test efficiency; if efficiency optimization is performed, inputting the number of test cases, the number of defects found, the duration of each test, and the test coverage into the efficiency optimization suggestion model to obtain the optimization suggestions output by the efficiency optimization suggestion model; and sending the test efficiency and the optimization suggestions to the test terminal.

[0009] In a possible implementation, after the instrumented software is tested using a test case to obtain test process data, the method further includes: determining a real-time test progress according to the test process data and each test case identifier; and outputting the real-time test progress.

[0010] In one possible implementation, the test process data includes executed test cases; determining the real-time test progress based on the test process data and each test case identifier includes: counting the number of executed test cases to obtain the number of executed cases; counting the number of test case identifiers to obtain the total number of test cases; and dividing the number of executed cases by the total number of test cases to obtain the real-time test progress.

[0011] In a possible implementation, before receiving the test information sent by the test terminal, it also includes: receiving test case query information sent by the test terminal, wherein the test case query information includes the identification of the software under test; searching for the corresponding identification of the test case to be selected according to the identification of the software under test; sending the identification of the test case to be selected to the test terminal so that the test terminal outputs each identification of the test case to be selected, and receives the selection instructions input by the tester according to each identification of the test case to be selected, and generates test information according to the identification of the test case to be selected, the identification of the software under test and the identification of the tester corresponding to the selection instructions.

[0012] In the second aspect, an embodiment of the present application provides a test efficiency quantification device, including: an information receiving module, used to receive test information sent by a test terminal, wherein the test information includes a tested software identifier, a test case identifier and a tester identifier; a data acquisition module, used to obtain a test case corresponding to the test case identifier and a tested software corresponding to the tested software identifier; a software instrumentation module, used to instrument the tested software to obtain the instrumented software; a software testing module, used to test the instrumented software using the test case to obtain test process data; an efficiency determination module, used to determine the test efficiency corresponding to the tester identifier based on the test process data; and an efficiency output module, used to output the test efficiency.

[0013] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the processor executes the first aspect above and / or various possible implementations of the first aspect.

[0014] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0015] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0016] The test efficiency quantification method, device, equipment, storage medium and program product provided in the embodiments of the present application obtain the instrumented software under test by instrumenting the software under test corresponding to the test information, and perform the test process using the instrumented software under test and the test cases corresponding to the test information to obtain the test process data. The test efficiency corresponding to the tester is determined from the test process data, thereby quantifying the test efficiency of the tester. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0018] Figure 1 A schematic diagram of a scenario for the test efficiency quantification method provided in this application;

[0019] Figure 2 A schematic diagram of a flow chart of a test efficiency quantification method provided in an embodiment of the present application;

[0020] Figure 3 A schematic diagram of a test case selection interface provided in an embodiment of the present application;

[0021] Figure 4 A schematic diagram of the structure of a test efficiency quantification device provided in an embodiment of the present application;

[0022] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0023] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0024] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0025] To ensure that the software can provide services normally, the software provider needs to use test cases to conduct rigorous testing on the unreleased software.

[0026] When conducting software testing, different testers may use different testing processes for similar testing tasks, which often leads to differences in testing efficiency. Currently, it is impossible to quantify the testing efficiency of testers.

[0027] In response to the above technical problems, the inventors proposed the following technical concept: by inserting the tested software at the beginning of the test, the test process data generated during the test is obtained, and the test efficiency of the tester is quantified by the test process data.

[0028] This application is used in the scenario of quantifying test efficiency. It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation portals for users to choose to authorize or refuse.

[0029] Figure 1 A schematic diagram of a scenario for the test efficiency quantification method provided in this application. Figure 1 , this scenario includes: a test terminal 101 and a server 102.

[0030] In a specific implementation process, the terminal device 101 may include a computer, a server, a tablet, a mobile phone, a PDA (Personal Digital Assistant), a notebook, etc., which can input data.

[0031] The server 102 can be implemented using a server or a cluster of multiple servers with more powerful processing capabilities and higher security. If possible, it can also be replaced by a computer, laptop, etc. with stronger computing power.

[0032] The connection between the server 102 and the test terminal 101 may be a wired connection or a wireless connection.

[0033] The test terminal 101 is used to receive instructions input by the tester and send corresponding information to the server 102 according to the instructions.

[0034] The server 102 is used to record the test process data obtained during the test process, determine the test efficiency corresponding to the tester according to the test process data, and output the obtained test efficiency.

[0035] It is understandable that the scenarios illustrated in the embodiments of the present application do not constitute a specific limitation on the test efficiency quantification method. In other feasible implementations of the present application, the above scenarios may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently, which can be determined according to the actual application scenario and is not limited here. Figure 1 The scenarios shown can be implemented by hardware, software, or a combination of software and hardware.

[0036] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0037] Figure 2 A flow chart of the test efficiency quantification method provided in the embodiment of the present application. The execution subject of the embodiment of the present application may be Figure 1 The server in the embodiment may also be a computer and / or a mobile phone, etc., and this embodiment does not impose any special restrictions on this. Figure 2 As shown, the method includes:

[0038] S201: receiving test information sent by a test terminal, wherein the test information includes a tested software identifier, a test case identifier, and a tester identifier.

[0039] In this step, the test information can be obtained by the staff after selecting and filling in the website page or browser plug-in of the test terminal. The test terminal can also use an automated interface to generate an HTTP (Hypertext Transfer Protocol) request, and the HTTP request contains a test case identification field. The test case identification field can be added to the HTTP request by the test terminal using a script to simulate the control of the browser plug-in. If the start test button is clicked again after changing the test case, the test case identification in the HTTP request header is updated to the new test case identification.

[0040] Figure 3 This is a schematic diagram of the test case selection interface provided in the embodiment of the present application. Figure 3As shown, the name of the software under test and the version of the software under test can be selected in the test case selection interface. It can also display a query case button, a new case button, a tester input box, and specific test cases displayed below the button. The name of the software under test and the version of the software under test together constitute the test case identification. In a possible implementation, the version of the software under test and the name of the software under test in the test case selection interface can also be replaced by a drop-down menu or text box. If the test case is selected, you can also add a "check mark" or other mark to the selected test case or change the color of the selected test case to indicate that the test case has been selected. After the staff clicks to start the test on the test terminal, the test terminal sends the test information to the server.

[0041] S202: Acquire the test case corresponding to the test case identifier and the software under test corresponding to the software under test identifier.

[0042] This step may include reading the test case corresponding to the test case identifier and the software under test corresponding to the software under test identifier from a database.

[0043] The software under test may be software in bytecode format.

[0044] S203: Insert the software under test to obtain the inserted software.

[0045] In this step, a preset plugging program may be used to plug the software under test to obtain plugged software.

[0046] Among them, the preset plug-in program is, for example, a "javaAgent" program.

[0047] S204: Testing the plugged software using test cases to obtain test process data.

[0048] This step includes inputting the test case into the instrumented software and running the instrumented software to obtain the test process data.

[0049] Among them, the test process data can include information such as the source of a single test case, code coverage, the start and end execution time of the case, and the executor. It can also include the call record of each HTTP request to ensure that the collected data is the actual test execution record.

[0050] S205: Determine the test efficiency corresponding to the tester identification according to the test process data.

[0051] In this step, it may include inputting various types of test process data into a preset test efficiency calculation formula to obtain the test efficiency; it may also include inputting various types of test process data into a preset test efficiency quantification model to obtain the test efficiency output by the test efficiency quantification model.

[0052] S206: Output the test efficiency.

[0053] This step may include displaying and outputting the test efficiency, and may also include sending the test efficiency to a test terminal.

[0054] From the description of the above embodiments, it can be seen that the embodiments of the present disclosure obtain the instrumented software under test by instrumenting the software under test corresponding to the test information, and perform the test process using the instrumented software under test and the test cases corresponding to the test information to obtain the test process data, and determine the test efficiency corresponding to the tester from the test process data, thereby quantifying the test efficiency of the tester.

[0055] In a possible implementation, the test process data includes the number of code lines covered, the number of defects found, the number of test cases, and the total execution time.

[0056] The number of lines of code covered may include the number of source code lines touched during the test case execution. The number of defects found refers to the number of defects identified and recorded during the test process. The number of test cases refers to the number of test cases used. The total execution time refers to the time used to execute all test cases.

[0057] In the above step S205, the test efficiency corresponding to the tester identification is determined according to the test process data, including: step S205A1 and step S205A2.

[0058] S205A1: Take the weighted sum of the number of lines of code covered, the number of defects found, and the number of test cases to obtain the test effect value.

[0059] In this step, the weight values ​​of the number of lines of code covered, the number of defects found, and the number of test cases can be preset by the staff.

[0060] S205A2: Calculate the test efficiency based on the test effect value and the total execution time.

[0061] In this step, the test efficiency may be obtained by dividing the test effect value by the total execution time, or the test efficiency may be obtained by dividing the test effect value by the total execution time and then by a preset value.

[0062] From the description of the above embodiments, it can be seen that the embodiments of the present disclosure obtain the test efficiency by taking the weighted sum of the number of covered code lines, the number of defects found, and the number of test cases and then dividing it by the total execution time, so that testers who have a higher number of covered code lines, a higher number of defects found, and a higher number of test cases used per unit time have higher test efficiency.

[0063] In a possible implementation, the above step S205A1 and step S205A2 can be expressed as the following formula:

[0064]

[0065] In the formula, P represents the test efficiency of the tester; S represents the number of lines of code covered; D represents the number of defects found; N represents the number of use cases, which refers to the total number of use cases executed by a single person; M represents the total execution time of a single person, and a, b, c, and d are constants that are adjusted according to actual conditions.

[0066] The number of covered code lines can be derived from the coverage of code lines by each person after deduplication. The number of defects found indicates the number of use cases that throw program exceptions.

[0067] In a possible implementation, the test process data includes the number of lines of code covered, the number of defects found, the number of test cases and the total execution time. In the above step S205, the test efficiency corresponding to the tester identification is determined according to the test process data, including: steps S205B1 to S205B3.

[0068] S205B1: weighted sum the number of covered code lines and the number of found defects to obtain a first weighted sum.

[0069] S205B2: Perform weighted summation of the number of test cases and the total execution time to obtain a second weighted sum.

[0070] S205B3: Divide the first weighted sum by the second weighted sum to obtain the test efficiency.

[0071] From the description of the above embodiments, it can be seen that the embodiments of the present disclosure obtain the test efficiency by taking the weighted sum of the number of lines of code covered and the number of defects found, divided by the weighted sum of the number of test cases and the total execution time, so as to achieve higher test efficiency for testers who obtain more lines of code covered and more defects found while using fewer test cases and less execution time. While measuring the test time, it also reflects the accuracy of the selected test cases.

[0072] In a possible implementation, after calculating the test efficiency according to the test effect value and the total execution time in step S205, the method further includes:

[0073] S220: Determine whether to perform efficiency optimization according to the test efficiency.

[0074] In this step, if the test efficiency is lower than a preset efficiency threshold, then it may be determined to optimize the efficiency, or it may be determined to rank according to the test efficiency, and if the ranking is at a preset proportion at the back, then it may be determined to optimize the efficiency.

[0075] S221: If efficiency optimization is performed, the number of test cases, the number of defects found, the duration of each test, and the test coverage are input into the efficiency optimization suggestion model to obtain optimization suggestions output by the efficiency optimization suggestion model.

[0076] In this step, the efficiency optimization suggestion model may be a neural network model pre-trained by the staff, and may be any one of a feedforward neural network model, a feedback neural network model, a recursive neural network model, and the like.

[0077] S222: Send the test efficiency and optimization suggestions to the test terminal.

[0078] In this step, the test efficiency and optimization suggestions may be sent to the test terminal in the format of messages, data packets, etc., or the test efficiency and optimization suggestions may be written into a test work analysis report, and the test work analysis report may be displayed, outputted or sent to the test terminal.

[0079] From the description of the above embodiments, it can be seen that the embodiments of the present disclosure judge whether to perform efficiency optimization based on the test efficiency difference. If efficiency optimization is needed, the number of test cases, the number of defects found, the duration of each test, and the test coverage are input into the efficiency optimization suggestion model to obtain the optimization suggestions output by the efficiency optimization suggestion model, and the test efficiency and optimization suggestions are output to achieve the goal of giving optimization suggestions when there is room for testers to improve their efficiency, so as to increase the number of lines of code covered, the number of defects found, and the number of test cases per unit time, reduce the total test time, and improve the efficiency of subsequent tests.

[0080] In a possible implementation, after the above step S204 uses the test case to test the plugged software and obtains the test process data, it also includes: step S230 and step S231.

[0081] S230: Determine the real-time test progress according to the test process data and each test case identifier.

[0082] In this step, the executed test cases are determined according to the test process data, the identification corresponding to the executed test cases is removed from the test case identification, the remaining unexecuted test cases are obtained, and the unexecuted test cases are counted as the real-time test progress. The real-time test progress can also include code coverage.

[0083] S231: Output real-time test progress.

[0084] This step may include displaying and outputting the real-time test progress, and may also include sending the real-time test progress to the test terminal.

[0085] From the description of the above embodiments, it can be seen that the embodiments of the present disclosure obtain real-time test progress by combining test process data and test case identification, and output the real-time test progress, thereby intuitively displaying the progress of the test. There is no need for testers to manually mark the test cases that have been executed, thereby reducing the workload of testers and improving the work efficiency of testers.

[0086] In a possible implementation, the test process data includes executed test cases and test coverage.

[0087] The executed test case may be an identifier of the executed test case.

[0088] In the above step S230, the real-time test progress is determined according to the test process data and each test case identifier, including: step S2301 to step S2303.

[0089] S2301: Count the number of executed test cases to obtain the number of executed test cases.

[0090] In this step, each time an executed test case is counted, the number of executed test cases is increased by 1.

[0091] S2302: Count the number of test case identifiers to obtain the total number of test cases.

[0092] In this step, this step is similar to the above step S2302 and will not be repeated here.

[0093] S2303: Divide the number of executed test cases by the total number of test cases to obtain the test case utilization rate.

[0094] In this step, for example, if the number of executed use cases is 50 and the total number of test cases is 100, the real-time test progress is 50%. For another example, if the number of executed use cases is 70 and the total number of test cases is 80, the real-time test progress is 87.5%. For another example, if the number of executed use cases is 20 and the total number of test cases is 60, the real-time test progress is 33.3%.

[0095] S2304: Use test case usage rate and test coverage as real-time test progress.

[0096] From the description of the above embodiments, it can be seen that the embodiments of the present disclosure obtain real-time test progress by dividing the executed test case reserve by the total number of test cases, thereby obtaining real-time test progress and realizing real-time detection of test progress.

[0097] In a possible implementation, before the above step S201 of receiving the test information sent by the test terminal, the method further includes: step S240 to step S242.

[0098] S240: Receive test case query information sent by the test terminal, where the test case query information includes an identifier of the software under test.

[0099] In this step, the test case query information can be generated and sent by the staff selecting the software under test identifier in the test terminal and clicking the query case button. The receiving method of the test case query information can include receiving messages or data packets.

[0100] S241: According to the identification of the software under test, searching for the corresponding identification of the test case to be selected.

[0101] In this step, it may include using the software identifier under test to find the correspondence between the software identifier and the test case identifier to obtain the test case identifier to be selected; it may also include reading the software type corresponding to the software identifier under test, using the software type to find the correspondence between the software type and the test case identifier, and obtaining the test case identifier to be selected.

[0102] Among them, the correspondence between the software identifier and the test case identifier, and the correspondence between the software type and the test case identifier can be pre-calibrated by the staff and stored in the format of a table, key-value pair, file, etc.

[0103] S242: Send the test case identifiers to be selected to the test terminal so that the test terminal outputs each test case identifier to be selected, and receives selection instructions input by the tester according to each test case identifier to be selected, and generates test information according to the test case identifier to be selected, the software identifier to be tested and the tester identifier corresponding to the selection instruction.

[0104] In this step, the identification of the test cases to be selected may be sent to the test terminal in a format such as a message, a data packet, or a table, and the test terminal displays and outputs the identification of each test case to be selected.

[0105] From the description of the above embodiments, it can be seen that the embodiments of the present disclosure receive the test case query information sent by the test terminal, and according to the identifier of the software under test, query the corresponding test case identifier to be selected, and send the test case identifier to be selected to the test terminal for the tester to view and select, thereby reducing the time for the tester to find the test case and increasing the test efficiency.

[0106] Figure 4 This is a schematic diagram of the structure of the test efficiency quantification device provided in the embodiment of the present application. Figure 4 As shown, the test efficiency quantification device 400 includes: an information receiving module 401, a data acquisition module 402, a software instrumentation module 403, a software testing module 404, an efficiency determination module 405 and an efficiency output module 406.

[0107] The information receiving module 401 is used to receive test information sent by the test terminal, wherein the test information includes the identification of the tested software, the identification of the test case and the identification of the tester.

[0108] The data acquisition module 402 is used to acquire the test case corresponding to the test case identifier and the software under test corresponding to the software under test identifier.

[0109] The software instrumentation module 403 is used to instrument the software under test to obtain instrumented software.

[0110] The software testing module 404 is used to test the plugged software using test cases to obtain test process data.

[0111] The efficiency determination module 405 is used to determine the test efficiency corresponding to the tester identification according to the test process data.

[0112] The efficiency output module 406 is used to output the test efficiency.

[0113] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0114] In one possible implementation, the test process data includes the number of lines of code covered, the number of defects found, the number of test cases and the total execution time; the efficiency determination module 405 is specifically used to weightedly sum the number of lines of code covered, the number of defects found and the number of test cases to obtain a test effect value; and the test efficiency is calculated based on the test effect value and the total execution time.

[0115] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0116] In a possible implementation, the test efficiency quantification device 400 further includes: a suggestion output module 407 .

[0117] The suggestion output module 407 is used to determine whether to perform efficiency optimization based on the test efficiency; if efficiency optimization is performed, the number of test cases, the number of defects found, the duration of each test, and the test coverage are input into the efficiency optimization suggestion model to obtain the optimization suggestions output by the efficiency optimization suggestion model; the test efficiency and optimization suggestions are sent to the test terminal.

[0118] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0119] In a possible implementation, the test efficiency quantification device 400 further includes: a progress output module 408 .

[0120] The progress output module 408 is used to determine the real-time test progress according to the test process data and each test case identifier; and output the real-time test progress.

[0121] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0122] In one possible implementation, the test process data includes executed test cases; the progress output module 408 is used to count the number of executed test cases to obtain the number of executed test cases; count the number of test case identifiers to obtain the total number of test cases; divide the number of executed test cases by the total number of test cases to obtain the test case utilization rate; and use the test case utilization rate and test coverage as real-time test progress.

[0123] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0124] In a possible implementation, the test efficiency quantification device 400 further includes: a use case selection module 409 .

[0125] The use case selection module 409 is used to receive test case query information sent by the test terminal, wherein the test case query information includes the identification of the software under test; according to the identification of the software under test, find the corresponding identification of the test case to be selected; send the identification of the test case to be selected to the test terminal so that the test terminal outputs each identification of the test case to be selected, and receives the selection instruction input by the tester according to each identification of the test case to be selected, and generates test information according to the identification of the test case to be selected, the identification of the software under test and the identification of the tester corresponding to the selection instruction.

[0126] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0127] In order to implement the above embodiment, the embodiment of the present application also provides an electronic device.

[0128] refer to Figure 5, which shows a schematic diagram of the structure of an electronic device 500 suitable for implementing the embodiment of the present application, and the electronic device 500 may be a terminal device or a server. The terminal device may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (Portable Android Devices, PADs), portable multimedia players (Portable Media Players, PMPs), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0129] like Figure 5 As shown, the electronic device 500 may include a processor (such as a central processing unit, a graphics processing unit, etc.) 501, and a memory 502 that is communicatively connected to the processor, which can perform various appropriate actions and processes according to the program stored in the memory 502, the computer execution instruction, or the program loaded from the storage device 508 to the random access memory (Random Access Memory, referred to as RAM) 503, to implement the test efficiency quantification method in any of the above embodiments, wherein the memory may be a read-only memory (Read Only Memory, referred to as ROM). In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the memory 502, and the RAM 503 are connected to each other via a bus 504. The input / output (I / O) interface 505 is also connected to the bus 504.

[0130] Typically, the following devices may be connected to the I / O interface 505: input devices 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 508 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Figure 5 The electronic device 500 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0131] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the memory 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present application are executed.

[0132] It should be noted that the computer-readable storage medium mentioned above in the present application may be a computer-readable signal medium or a computer storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable storage medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0133] The computer-readable storage medium may be included in the electronic device, or may exist independently without being installed in the electronic device.

[0134] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the method shown in the above embodiment.

[0135] The computer program code for performing the operation of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can 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 can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0136] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0137] The modules involved in the embodiments described in this application may be implemented by software or hardware. The name of a unit does not limit the module itself in some cases. For example, a receiving module may also be described as a "test information receiving module".

[0138] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0139] The present application also provides a computer-readable storage medium, which stores computer execution instructions. When the processor executes the computer execution instructions, the technical solution of the test efficiency quantification method in any of the above-mentioned embodiments is implemented. The implementation principle and beneficial effects are similar to the implementation principle and beneficial effects of the test efficiency quantification method. Please refer to the implementation principle and beneficial effects of the test efficiency quantification method, which will not be repeated here.

[0140] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A 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, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0141] The present application also provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the technical solution of the test efficiency quantification method in any of the above-mentioned embodiments. Its implementation principle and beneficial effects are similar to the implementation principle and beneficial effects of the test efficiency quantification method. Please refer to the implementation principle and beneficial effects of the test efficiency quantification method, and no further details will be given here.

[0142] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in this application (but not limited to) by each other to form a technical solution.

[0143] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0144] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A test efficiency quantification method, characterized in that: include: Receiving test information sent by the test terminal, wherein the test information includes a tested software identifier, a test case identifier, and a tester identifier; Obtaining the test case corresponding to the test case identifier and the software under test corresponding to the software under test identifier; Inserting the software under test to obtain the inserted software; Using the test case to test the plugged software to obtain test process data; Determining the test efficiency corresponding to the tester identification according to the test process data; The test efficiency is output.

2. The method according to claim 1, characterized in that: The test process data includes the number of lines of code covered, the number of defects found, the number of test cases and the total execution time; Determining the test efficiency corresponding to the tester identification according to the test process data includes: The number of covered code lines, the number of found defects and the number of test cases are weighted and summed to obtain a test effect value; The test efficiency is calculated according to the test effect value and the total execution time.

3. The method according to claim 2, characterized in that After calculating the test efficiency according to the test effect value and the total execution time, the method further includes: According to the test efficiency, determining whether to perform efficiency optimization; If efficiency optimization is performed, the number of test cases, the number of defects found, the duration of each test, and the test coverage are input into the efficiency optimization suggestion model to obtain optimization suggestions output by the efficiency optimization suggestion model; The test efficiency and the optimization suggestion are sent to the test terminal.

4. The method according to any one of claims 1 to 3, characterized in that: After the test case is used to test the plugged software and the test process data is obtained, the method further includes: Determine the real-time test progress according to the test process data and each test case identifier; The real-time test progress is output.

5. The method according to claim 4, characterized in that The test process data includes executed test cases; Determining the real-time test progress according to the test process data and each test case identifier includes: Counting the number of executed test cases to obtain the number of executed test cases; Counting the number of test case identifiers to obtain the total number of test cases; The number of executed test cases is divided by the total number of test cases to obtain a test case utilization rate; The test case utilization rate and the test coverage rate are used as the real-time test progress.

6. The method according to any one of claims 1 to 3, characterized in that: Before the receiving of the test information sent by the test terminal, the method further includes: Receiving test case query information sent by the test terminal, wherein the test case query information includes the tested software identifier; According to the tested software identifier, searching for the corresponding test case identifier to be selected; The test case identifier to be selected is sent to the test terminal so that the test terminal outputs each test case identifier to be selected, and receives a selection instruction input by the tester according to each test case identifier to be selected, and generates the test information according to the test case identifier to be selected, the software identifier to be tested and the tester identifier corresponding to the selection instruction.

7. A test efficiency quantification device, characterized in that: include: An information receiving module, used to receive test information sent by the test terminal, wherein the test information includes a tested software identifier, a test case identifier, and a tester identifier; A data acquisition module, used to acquire the test case corresponding to the test case identifier and the software under test corresponding to the software under test identifier; A software plugging module, used for plugging the software under test in response to the start of the test process to obtain the plugged software; A software testing module, used to test the plugged software using the test case to obtain test process data; An efficiency determination module, used to determine the test efficiency corresponding to the tester identification according to the test process data; The efficiency output module is used to output the test efficiency.

8. An electronic device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when being executed by a processor.

Images