Test report enhancement method and device based on historical test data and medium

Abstract

The invention discloses a test report enhancement method and device based on historical test data and a medium, and the method comprises the steps: executing each test case corresponding to a test script to obtain an execution result, and storing the execution result in a preset execution result record; after the test task is executed every time, the number of continuous failures of the test script in the preset test period is determined; if the number of continuous failures exceeds a preset threshold value, triggering a historical failure reason identification mechanism for the test script, and generating a historical failure reason list corresponding to the test script based on the historical failure reason identification mechanism; and adding a historical failure record block in the test report configuration file, screening out a specified test script meeting a preset failure condition, and filling a historical failure reason list corresponding to the specified test script into the historical failure record block so as to jointly display the historical failure reason list and the execution result.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of automatic testing, in particular to a test report enhancement method based on historical test data, a device and a medium. BACKGROUND

[0002] With the continuous development of software technology, software automated testing is used more and more frequently in testing. After the execution of an automated script ends, generating a visual test report according to the execution result is an important link, and the traditional test report only shows the execution result of the current time, and a high-frequency fault script can be found only by manually reviewing historical reports, which has insufficient identification sensitivity for occasional faults and cannot reflect the persistence of test faults. SUMMARY

[0003] To solve the above problems, the present application provides a test report enhancement method based on historical test data, which comprises:

[0004] Each test case corresponding to a test script is executed to obtain an execution result, and the execution result is stored in a preset execution result record;

[0005] After each test task is executed, the number of consecutive failures of the test script in a preset test period is determined;

[0006] If the number of consecutive failures exceeds a preset threshold, a historical failure cause identification mechanism for the test script is triggered, and a historical failure cause list corresponding to the test script is generated based on the historical failure cause identification mechanism;

[0007] A historical failure record block is added in a test report configuration file, specified test scripts that meet a preset failure condition are screened out, and a historical failure cause list corresponding to the specified test scripts is filled into the historical failure record block, so that the historical failure cause list and the execution result are displayed together.

[0008] In an implementation manner of the present application, based on the historical failure cause identification mechanism, the historical failure cause list corresponding to the test script is generated, specifically comprising:

[0009] Based on the historical failure cause identification mechanism, the historical failure cause corresponding to the test script is obtained from the execution result record according to the case name of the test script;

[0010] A historical failure cause list is generated according to the historical failure cause.

[0011] In an implementation manner of the present application, before the historical failure cause identification mechanism for the test script is triggered, the method further comprises:

[0012] determining a cycle granularity for evaluating a success execution probability of the test script, and obtaining an execution failure rate of the test script within a preset time length matching the cycle granularity according to the cycle granularity;

[0013] determining a preset threshold corresponding to the test script within the test cycle according to the execution failure rate.

[0014] In an implementation manner of the present application, the preset threshold corresponding to the test script within the test cycle is determined according to the execution failure rate, specifically including:

[0015] calculating an execution failure rate standard deviation and an average failure rate corresponding to the execution failure rate;

[0016] determining a fluctuation coefficient according to a ratio between the execution failure rate standard deviation and the average failure rate; wherein the fluctuation coefficient reflects a fluctuation degree of an execution failure probability of the test script, and the fluctuation coefficient and the fluctuation degree are in a positive correlation relationship;

[0017] adding the fluctuation coefficient and a basic threshold to obtain the preset threshold corresponding to the test script within the test cycle.

[0018] In an implementation manner of the present application, the historical failure reason list is generated according to the historical failure reason, specifically including:

[0019] performing semantic analysis on the historical failure reason to determine an occurrence frequency corresponding to each failure keyword in the historical failure reason;

[0020] determining a priority of the failure keyword according to a descending order of the occurrence frequency, and sorting the historical failure reason containing the failure keyword according to the priority to generate the historical failure reason list.

[0021] In an implementation manner of the present application, after the historical failure reason list corresponding to the test script is generated, the method further includes:

[0022] matching the historical failure reason lists corresponding to different test scripts to determine a matching degree between the historical failure reason lists;

[0023] in a case that the matching degree is greater than a preset matching degree, generating an associated script list to fill the associated script list to the historical failure record block, and realizing associated analysis on the test script.

[0024] In an implementation manner of the present application, after the occurrence frequency corresponding to each failure keyword in the historical failure reason is determined, the method further includes:

[0025] determining the target failure keyword with the highest occurrence frequency;

[0026] taking, as a core test case, a test case in the test script that takes the target failure keyword as a failure cause;

[0027] re-executing the core test case based on a preset retry strategy, and synchronizing an execution result corresponding to the core test case to a test report.

[0028] In an implementation form of the present application, the execution result record includes a test case name, an execution time, an execution result, and a failure cause, and before storing the execution result into a preset execution result record, the method further includes:

[0029] determining whether the test script fails to execute according to the execution result;

[0030] if yes, analyzing a failure cause corresponding to the test script through log information of the test script, and storing a test case name, an execution time, an execution result, and the failure cause corresponding to the test script into a preset execution result record.

[0031] The present application provides a test report enhancement device based on historical test data, the device comprising:

[0032] at least one processor;

[0033] and a memory in communication connection with the at least one processor;

[0034] wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute a test report enhancement method based on historical test data according to any one of the above.

[0035] The present application provides a non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being configured to:

[0036] a test report enhancement method based on historical test data according to any one of the above.

[0037] The test report enhancement method based on historical test data provided by the present application can bring the following beneficial effects:

[0038] By counting the number of consecutive failures of the test script, whether the test script has a fault persistence problem is analyzed, so as to screen out high-frequency fault scripts, and when the number of consecutive failures of the test script exceeds the preset threshold, a historical failure cause identification mechanism is triggered, a historical failure cause list is generated for high-frequency fault test samples, without manually tracing back multiple historical test reports to find fault causes, the test personnel can efficiently locate the problems in the test script, and the test progress is accelerated. A historical failure record block is added in the test report configuration file, the historical failure cause list and the execution result are displayed together, so that the test report is no longer limited to the single execution result, but can fully reflect the overall operation of the test script in the preset test period, and more rich information reference is provided for the management and analysis of the test script. BRIEF DESCRIPTION OF DRAWINGS

[0039] The accompanying drawings, which are included to provide a further understanding of the application and constitute a part of this application, illustrate certain illustrative embodiments of the application and together with the description serve to explain the application. In the drawings:

[0040] Figure 1 A flowchart of a test report enhancement method based on historical test data provided by an embodiment of the application;

[0041] Figure 2 A structural diagram of a test report enhancement device based on historical test data provided by an embodiment of the application. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical scheme and advantages of the application clearer, the technical scheme of the application will be described in detail below with reference to the specific embodiments of the application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the application, not all the embodiments. Based on the embodiments in the application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the application.

[0043] The technical scheme provided by the embodiments of the application will be described in detail below with reference to the drawings.

[0044] As shown in the drawings, the test report enhancement method based on historical test data provided by an embodiment of the application comprises: Figure 1

[0045] S101: Each test case corresponding to the test script is executed to obtain an execution result, and the execution result is stored in a preset execution result record.

[0046] ​A test case is used to test whether a certain function or function point works correctly, and a test script is an automated test code written in a specific test language for a specific test case. Testers design each test case according to software requirements and design documents, including test steps, input data, and expected results. Then, a test script corresponding to each test case is written using a test tool or a script language, and the test script is run in a test environment. The test script will execute each test case in a predetermined order. During execution, the test script will automatically send input data to the system under test, simulate user operations, and obtain the actual output and state information of the system.

[0047] After the test script executes each test case, it compares the actual output with the expected result to determine whether the test script has failed, and records the test results. If one test case fails, the execution result of the execution script is a failure. For the test script that fails, the failure reason corresponding to the test script is analyzed through the log information of the test script, and the test case name, execution time, execution result, and failure reason corresponding to the test script are stored in the execution result record in the SQLite database, thereby providing a data basis for subsequent analysis of the failure reason.

[0048] S102: After each execution of the test task, determine the number of consecutive failures of the test script within a predetermined test period.

[0049] The traditional test report only shows the execution result of the current execution, and cannot reflect the continuous problem. The embodiments of the present application enhance the content of the test report by determining the number of consecutive failures of the test script, so that it can automatically identify continuous failure scripts and visualize the historical failure reasons, which helps to identify and repair problems in advance, avoids the accumulation and expansion of problems in subsequent versions, and provides more comprehensive and in-depth test information for the project team. A test script needs to be executed multiple times, and before testing, the test frequency corresponding to different test scripts needs to be specified, such as once a day, five times a week, etc. After each execution of the test task, the number of consecutive failures of the test script within a predetermined test period is determined. The test period can be one week, two weeks, one month, etc.

[0050] S103: If the number of consecutive failures exceeds a predetermined threshold, a historical failure reason identification mechanism for the test script is triggered, and a historical failure reason list corresponding to the test script is generated based on the historical failure reason identification mechanism.

[0051] A preset threshold of consecutive failure times is set in advance, a test task is executed according to a preset test plan, after each test task is completed, the consecutive failure times of each test script in a certain period are counted by querying the test result records stored in the SQLite database. If the consecutive failure times of a certain test script exceed the preset threshold, the historical failure cause identification mechanism is triggered. Based on the historical failure cause identification mechanism, the failure cause of the test script is analyzed. Specifically, according to the case name corresponding to the failed case in the test script, the test script is located from the execution result record according to the case name, and the historical failure cause corresponding to the test script is queried. The historical failure cause of the test script each time it fails may be different, therefore, the historical failure cause queried each time is summarized to generate a historical failure cause list, and the historical failure cause list can be displayed in the test report, so as to reflect the failure cause of the high-frequency fault test script. Without manual backtracking of historical test reports, the historical fault situation of the test script can be determined, which is more efficient and more convenient.

[0052] In one embodiment, the preset threshold corresponding to the consecutive failure times can be set according to actual test requirements, or can be adaptively set according to the execution failure rate of the current test script in a certain period.

[0053] Specifically, the cycle granularity for evaluating the success execution probability of the test script is determined, the cycle granularity refers to the refinement degree of the time period for evaluating the success execution probability of the test script, which can be daily, weekly, monthly, etc. The cycle granularity defines the time range in which the execution failure rate of the test script is counted. According to the cycle granularity, a preset time length matched therewith is determined, and the execution failure rate of the test script in the preset time length is obtained. For example, the cycle granularity is set to one day, then the execution failure rate of the test script is evaluated once a day, and the execution failure rate is the ratio between the failure times and the total execution times. Assuming that five tests are performed in one day, and the execution failure times are three, then the execution failure rate of the test script is 60%. It should be noted that the cycle granularity needs to be less than the test period, so as to ensure that the test script can be tested multiple times within the test period.

[0054] After the execution failure rate of the test script is calculated, it can be judged whether the test result of the test script is stable, so that the preset threshold corresponding to the continuous failure number is adaptively set according to the stability. The stability of the test result needs to be represented by the standard deviation and the average value of the execution failure rate, therefore, after the execution failure rate corresponding to each preset time length in the test period is obtained through the above calculation process, the execution failure rate standard deviation and the average failure rate corresponding to the execution failure rate are calculated. According to the ratio between the execution failure rate standard deviation and the average failure rate, the fluctuation coefficient is determined, which reflects the fluctuation degree of the execution failure probability of the test script, and has a positive correlation with the fluctuation degree. When the fluctuation coefficient is larger, it means that the test result of the test script is more unstable in a test period. In the embodiment of the present application, a basic threshold needs to be set according to the project requirements and experience, which is used to evaluate the failure number of the test script, and then the fluctuation coefficient and the basic threshold are added, so that the corresponding preset threshold of the test script in the test period is obtained.

[0055] It can be seen that the larger the fluctuation coefficient is, the larger the preset threshold is, which can effectively reduce the false alarm of occasional faults and avoid frequent triggering of alarms due to large fluctuations in the execution failure probability of the test script, so as to focus on the test scripts with real persistent problems, improve the test efficiency and avoid being disturbed by a large number of alarm of occasional faults.

[0056] In an embodiment, in order to improve the analysis efficiency of test failure reasons, the priority of the historical failure reasons is determined according to the occurrence frequency of the historical failure reasons, so that the test personnel can prioritize processing of failure reasons that have a greater impact on testing and software quality, improve work efficiency and ensure software quality.

[0057] Specifically, the natural language processing technology is used to perform semantic analysis on the obtained historical failure reasons, and representative failure keywords are extracted, such as network timeout, data error, interface exception, etc. The number of occurrences of each failure keyword in the historical failure reason record is counted, and the occurrence frequency of each keyword is calculated. The failure keywords are sorted in descending order of occurrence frequency, so as to determine the priority of the failure keywords, and the keywords with high occurrence frequency have higher priority. According to the determined priority order, the historical failure reason records containing the corresponding failure keywords are sorted to generate a historical failure reason list, which can make the failure reasons with high occurrence frequency be processed and analyzed first.

[0058] S104: A historical failure record block is added in the test report configuration file, the specified test script meeting the preset failure condition is screened out, and the historical failure reason list corresponding to the specified test script is filled into the historical failure record block, so as to jointly display the historical failure reason list and the execution result.

[0059] The traditional test report analysis method needs to manually search historical test reports to analyze persistent faults, which is not only inefficient but also cannot timely understand the running status of the test script and is difficult to find potential problems. The embodiment of the application adds a historical failure record block in the test report configuration file. When the specified test script that meets the preset failure condition is screened out, that is, the specified test script whose continuous failure times exceed the preset threshold is screened out, the specified test script is the test script with the persistent fault indication. For such a test script, the corresponding historical failure reason list needs to be filled into the historical failure record block. In this way, when generating the test report subsequently, the historical failure reason list and the execution result of the current test script are displayed to the user together, avoiding the cumbersome process of manually searching the historical test report, and the historical failure reason of the test script can be quickly obtained, thereby improving the analysis efficiency. At the same time, more comprehensive failure information can be provided, which helps to quickly locate and analyze the root cause of the problem, thereby speeding up the problem solving process.

[0060] In one embodiment, the historical failure reason list of the test script reflects the failure reason thereof. There may be some common problems between different test scripts. In order to uniformly allocate test resources and improve the utilization rate of test resources, the test scripts with similar failure reasons can be associated, so that the test personnel uniformly process the common problems and avoid repeated work, thereby improving the efficiency.

[0061] Specifically, the historical failure reason lists corresponding to different test scripts are matched to determine the matching degree between the historical failure reason lists. The matching degree can be realized by comparing the coincidence number of failure keywords, the correlation of occurrence frequencies, and the like in the historical failure reason lists. For example, the Jaccard similarity coefficient is used to calculate the similarity of the failure keyword set, or the cosine similarity is used to calculate the similarity between the failure keyword occurrence frequency vectors, so as to obtain the matching degree between the lists.

[0062] If the matching degree is greater than a preset matching degree, it means that the historical failure reasons corresponding to the two test scripts are relatively similar. At this time, the associated script list is generated. The associated script list is filled into the historical failure record block in the same way as the historical failure reason list. In this way, when the failure reason of the test script is analyzed subsequently, the associated test scripts can be processed at the same time, which is convenient for uniformly allocating test and development resources and optimizing the resource utilization rate.

[0063] In one embodiment, in order to quickly focus on the core problem in the test process, avoid blind troubleshooting in numerous test cases and failure causes, improve the efficiency and accuracy of problem positioning, and improve the efficiency of fault solving, the embodiment of the application determines a target failure keyword with the highest occurrence frequency by statistically comparing the occurrence frequencies of various failure keywords in historical failure causes. The target failure keyword is a key factor causing the test script to fail, and can quickly focus on the core point of the problem. Among all test cases included in the test script, the target failure keyword determined above is screened as a test case of the failure cause, as a core test case. The core test case is a part that needs to be focused on and solved preferentially in the entire test process, because it is directly related to the main reason for the failure of the current test script. By analyzing and repairing the core test case, the success execution probability of the test script can be effectively improved.

[0064] According to the preset retry strategy, the core test case is re-executed. The preset retry strategy is usually formulated according to experience or specific requirements of a project, for example, the retry can be set to 3 times, and the interval between each retry is 5 minutes. The purpose of re-executing the core test case is to confirm whether the problem is solved by retrying after the initial repair of the problem. After re-executing the core test case, the execution result obtained, including whether the execution is successful, the new failure cause (if it still fails) and the like, is synchronized to the test report in a timely manner, so as to ensure that the test report can truly and completely reflect the latest execution of the core test case, provide more accurate decision basis for the tester, and then take corresponding measures to solve and optimize the problem.

[0065] The above is the method embodiment provided by the application. Based on the same idea, some embodiments of the application also provide a device and a nonvolatile computer storage medium corresponding to the above method.

[0066] Figure 2 A structure schematic diagram of a test report enhancement device based on historical test data provided by the embodiment of the application is shown in FIG. 1. As shown in FIG. 1, it includes: Figure 2

[0067] at least one processor; and

[0068] a memory in communication connection with the at least one processor; wherein

[0069] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the test report enhancement method based on historical test data according to any one of the above.

[0070] ​The embodiment of the present application provides a non-volatile computer storage medium, which stores computer executable instructions, and the computer executable instructions are configured as follows:

[0071] The method for enhancing a test report based on historical test data according to any one of the above.

[0072] The embodiments in the present application are described in a progressive manner, and the same and similar parts of the embodiments can be referred to each other. Each embodiment mainly describes the difference from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, and thus the description is relatively simple, and the related parts can be referred to the part of the method embodiment.

[0073] The device and medium provided by the embodiment of the present application are one-to-one corresponding to the method, and thus the device and medium also have the similar beneficial technical effects as the method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the device and medium are not described here.

[0074] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program codes.

[0075] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices produce a device implemented in the flowcharts and / or block diagrams. Figure 1 The function of one flow or multiple flows and / or blocks Figure 1 The device for implementing the function of one block or multiple blocks.

[0076] These computer program instructions can also be stored in a computer readable storage medium, which can guide the computer or other programmable data processing devices to work in a specific manner, so that the instructions stored in the computer readable storage medium produce a product including instruction devices, which implement the flowcharts and / or block diagrams. Figure 1 The function of one flow or multiple flows and / or blocks Figure 1the function(s) specified in the block or blocks.

[0077] These computer program instructions can also be loaded into computer or other programmable data processing devices to cause a series of operational steps to be performed on the computer or other programmable devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable devices provide steps for implementing the flowchart block(s) or flowchart flow(s) and / or portions thereof. Figure 1 the flowchart block(s) or flowchart flow(s) and / or portions thereof. Figure 1 the function(s) specified in the block or blocks.

[0078] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0079] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) about which the computer stores information about an operating system, application software, and / or the like. Memory is an example of computer readable media.

[0080] Computer readable media includes permanent and non-permanent, moveable and non- moveable media that can be implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital versatile disks (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that is accessible to a computing device. According to the definition provided herein, computer readable media does not include transitory media, such as modulated data signals and carrier waves.

[0081] It should also be noted that the terms "comprising," "including," and any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by "comprises a" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or apparatus that comprises the recited element.

[0082] The above merely provides an example of the present application, and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application should be included in the scope of claims of the present application.

Claims

1. A test report enhancement method based on historical test data, characterized by, The method comprises: executing each test case corresponding to the test script to obtain an execution result, and storing the execution result into a preset execution result record; after each execution of a test task, determining a number of consecutive failures of the test script within a preset test period; if the number of consecutive failures exceeds a preset threshold, triggering a historical failure cause identification mechanism for the test script, and generating a historical failure cause list corresponding to the test script based on the historical failure cause identification mechanism; adding a historical failure record block in a test report configuration file, screening a specified test script satisfying a preset failure condition, and filling the historical failure cause list corresponding to the specified test script into the historical failure record block to jointly display the historical failure cause list and the execution result.

2. The method of claim 1, wherein, Based on the historical failure cause identification mechanism, the historical failure cause list corresponding to the test script is generated, specifically comprising: based on the historical failure cause identification mechanism, the historical failure cause corresponding to the test script is obtained from the execution result record according to the test case name corresponding to the test script; generating a historical failure cause list according to the historical failure cause.

3. The method of claim 1, wherein, Before triggering the historical failure cause identification mechanism for the test script, the method further comprises: determining a cycle granularity for evaluating the success execution probability of the test script, and obtaining an execution failure rate of the test script within a preset time period matching the cycle granularity according to the cycle granularity; determining a preset threshold corresponding to the test script within the test period according to the execution failure rate.

4. The method of claim 3, wherein, According to the execution failure rate, the preset threshold corresponding to the test script within the test period is determined, specifically comprising: calculating the execution failure rate standard deviation and the average failure rate corresponding to the execution failure rate; determining a fluctuation coefficient according to the ratio between the execution failure rate standard deviation and the average failure rate; wherein the fluctuation coefficient reflects the fluctuation degree of the execution failure probability of the test script, and the fluctuation coefficient and the fluctuation degree are in a positive correlation relationship; adding the fluctuation coefficient and the basic threshold to obtain the corresponding preset threshold of the test script within the test period.

5. The method of claim 1, wherein, According to the historical failure cause, a historical failure cause list is generated, specifically comprising: performing semantic analysis on the historical failure cause to determine the occurrence frequency of each failure keyword in the historical failure cause; determining the priority of the failure keyword in descending order of the occurrence frequency, and sorting the historical failure causes containing the failure keyword according to the priority to generate a historical failure cause list.

6. The method of claim 5, wherein, After generating the historical failure cause list corresponding to the test script, the method further comprises: matching the historical failure cause lists corresponding to different test scripts to determine the matching degree between the historical failure cause lists; in the case that the matching degree is greater than a preset matching degree, generating an associated script list to fill the associated script list into the historical failure record block to realize the association analysis of the test script.

7. The method of claim 5, wherein, After the historical failure reason list is co-displayed with the execution result, the method further includes: determining the target failure keyword with the highest frequency of occurrence; taking a test case in the test script that takes the target failure keyword as a failure reason as a core test case; re-executing the core test case based on a preset retry strategy, and synchronizing an execution result corresponding to the core test case to a test report.

8. The method of claim 1, wherein, The execution result record includes a test case name, an execution time, an execution result, and a failure reason. Before the execution result is stored in a preset execution result record, the method further includes: determining whether the test script fails to execute according to the execution result; if so, analyzing a failure reason corresponding to the test script through log information of the test script, and storing a test case name, an execution time, an execution result, and a failure reason corresponding to the test script in a preset execution result record.

9. A test report enhancement device based on historical test data, characterized by, The device includes: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute a test report enhancement method based on historical test data according to any one of claims 1-8.

10. A non-transitory computer storage medium storing computer-executable instructions that, when executed, cause a computer to perform: The computer executable instructions are configured to: execute a test report enhancement method based on historical test data according to any one of claims 1-8.

Images