WO2018000607A1

WO2018000607A1 - Method and electronic apparatus for identifying test case failure causes

Info

Publication number: WO2018000607A1
Application number: PCT/CN2016/099946
Authority: WO
Inventors: 杨彩花
Original assignee: 乐视控股（北京）有限公司; 乐视电子商务（北京）有限公司
Priority date: 2016-06-30
Filing date: 2016-09-23
Publication date: 2018-01-04
Also published as: CN105930276A

Abstract

A method and electronic apparatus for identifying test case failure causes. The method comprises: acquiring a test case that has failed a test and acquiring test results of the test case (101); selecting, from the test results, an effective test result corresponding to an expected result of the test case (102); comparing the effective test result with the expected result to determine whether service data of the effective test result is identical to service data of the expected result (103); and if the service data are different, recording the cause of failure of the test case as a change in service data (104). The method can remove a step of manual operation, automatically identify the cause of failure, and perform cause recording to facilitate subsequent recording of errors in the cause, thereby saving time of maintenance personnel and increasing the speed and efficiency of locating and fixing a problem.

Description

Method and electronic device for identifying cause of failure of test case

cross reference

This application claims priority to Chinese Patent Application No. 201610509913.5, entitled "A Method and Apparatus for Identifying Failure Causes of Test Case Failure", submitted to the Chinese Patent Office on June 30, 2016, the entire contents of which are hereby incorporated by reference. The citations are incorporated herein by reference.

Technical field

The present invention relates to the field of test monitoring technologies, and in particular, to a method and an electronic device for identifying a cause of failure of a test case.

Background technique

A test case in software engineering is a set of conditions or variables used by a tester to determine whether an application or software system is working correctly. It is a set of test inputs, execution conditions, and conditions for a particular target. Expected results to test a program path or verify that a particular requirement is met.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art:

When the test is monitored according to the test case, the system automatically sends out the test result email every day. If there is a failure in the test case, manual intervention is required to determine whether the test failure is caused by an interface exception or a business data change. In particular, during business activities, for example, business data changes frequently. Many times, after the business data has just been changed, the business personnel modify or update the business data again, resulting in a slower monitoring interface; an increase in the number of use cases. At the time, the cost of investing in people will also increase; it is more frequent and time-consuming to manually confirm changes.

The information disclosed in this Background section is only intended to increase the understanding of the general background of the invention and should not be construed as an admission The prior art is well known to those skilled in the art.

Summary of the invention

The embodiment of the present application provides a method and an electronic device for identifying a cause of failure of a test case, thereby overcoming the defect of inefficiency of the existing test monitoring.

In a first aspect, in order to achieve the above object, an embodiment of the present invention provides a method for identifying a cause of failure of a test case, including: obtaining a test case in which the test fails, and obtaining a test result of the test case; selecting and testing the test result. The effective test result corresponding to the expected result of the use case; compare the effective test result with the expected result to determine whether the valid test result is the same as the business data in the expected result; when the business data is different, mark the failure reason of the test case as Business data changes.

In a possible implementation manner, when the service data is different, the method further includes: saving the business data of the valid test result to the expected copy file; and when the business data of the valid test result is correct, using the expected copy file as the original expectation The file, the business data in which the expected result is stored in the original expected file.

In a possible implementation manner, the method further includes: comparing the effective test result with the expected result to determine whether the valid test result is the same as the service data type in the expected result; and when the service data type is different, the test case is used. The reason for the failure is marked as a change in the business data type.

In a possible implementation manner, when the service data types are different, the method further includes: sending the test result of the test failure to the vulnerability management system.

In a possible implementation manner, selecting valid test results corresponding to the expected results of the test case in the test result includes: determining an expected result identifier, identifying the expected result as an identifier of the expected result of the test case; determining the test result A valid test result that is consistent with the expected result identification.

Based on the same inventive concept, an embodiment of the present invention further provides an identification test case. The device for failure causes, comprising: an obtaining module, configured to obtain a test case in which the test fails, and obtain a test result of the test case; and a selection module, configured to select a valid test result corresponding to the expected result of the test case in the test result. a comparison module for comparing the effective test result with the expected result to determine whether the valid test result is the same as the business data in the expected result;

A tagging module is used to mark the failure reason of the test case as a business data change when the business data is different.

In a possible implementation manner, when the service data is different, the apparatus further includes: a saving module, configured to save the service data of the valid test result to the expected copy file; and a replacement module, the service data used in the valid test result When correct, the expected copy file is the original expected file, and the business data with the expected results in the original expected file.

In a possible implementation manner, the comparison module is further configured to: compare and compare the valid test result with the expected result, determine whether the valid test result is the same as the service data type in the expected result; and the marking module is further configured to: in the service data When the types are different, mark the failure reason of the test case as a business data type change.

In a possible implementation, when the service data type is different, the device further includes: a sending module, configured to send the test result of the test failure to the vulnerability management system.

In a possible implementation manner, the selecting module includes: a determining unit, configured to determine an expected result identifier, the expected result identifier is an identifier of an expected result of the test case; and the selecting unit is configured to determine that the test result is consistent with the expected result identifier Effective test results.

In order to achieve the above object, an embodiment of the present invention provides an electronic device, including: at least one processor; and a memory communicably coupled to the at least one processor; wherein the memory is stored The at least one processor executes instructions that are executed by the at least one processor to cause the at least one processor to perform the methods described in the various aspects above.

In order to achieve the above object, in another aspect, an embodiment of the present application further provides a non-transitory computer readable storage medium storing computer executable instructions, the computer executable The instructions are for performing the methods described in the various aspects above.

In order to achieve the above object, in another aspect, an embodiment of the present invention provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions When the program instructions are executed by a computer, the computer is caused to perform the methods described in the various aspects above.

The method and the electronic device for identifying the cause of the failure of the test case provided by the embodiment of the present invention can compare the effective test result with the expected result by selecting an effective test result corresponding to the expected result in the test result of the test case. Process to determine the cause of the failure of the test case. The method omits the manual operation steps, can automatically identify the cause of the failure and mark the reason, facilitates subsequent marking of the errors, saves the maintenance staff's working time, can improve the positioning problem and fix the speed and efficiency of the problem. When the business data change triggers the test failure, the latest business data is automatically obtained by replacing the original expected file in time to test the maintenance personnel to quickly locate the latest business data. The test result of the test failure is sent to the vulnerability management system, and the technician can obtain the test result in question in time, so that the subsequent technician can perform corresponding software improvement or update on the test result of the test failure.

Other features and advantages of the invention will be set forth in the description which follows, The objectives and other advantages of the invention may be realized and obtained by means of the structure particularly pointed in the appended claims.

The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments.

DRAWINGS

The one or more embodiments are exemplified by the accompanying drawings in the accompanying drawings, and FIG. The figures in the drawings do not constitute a scale limitation unless otherwise stated.

1 is a flow chart of a first method for identifying a cause of failure of a test case in an embodiment of the present invention;

2 is a flow chart of a second method for identifying a cause of failure of a test case in an embodiment of the present invention;

3 is a flowchart of a third method for identifying a cause of failure of a test case in an embodiment of the present invention;

4 is a first structural diagram of an apparatus for identifying a cause of failure of a test case in an embodiment of the present invention;

FIG. 5 is a second structural diagram of an apparatus for identifying a cause of failure of a test case in an embodiment of the present invention; FIG.

6 is a third structural diagram of an apparatus for identifying a cause of failure of a test case in an embodiment of the present invention;

Figure 7 is a structural diagram of a module selected in the embodiment of the present invention;

FIG. 8 is a structural diagram of a network device in an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention. The same reference numerals in the drawings denote the same or similar elements. Although the various aspects of the embodiments are illustrated in the drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustrative." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or preferred.

A method for identifying a cause of failure of a test case provided by an embodiment of the present invention is performed by an electronic device, as shown in FIG. 1 , including steps 101-104:

Step 101: Obtain a test case in which the test fails, and obtain a test result of the test case.

In the embodiment of the present invention, a test case (Test Case) for testing an application or system is set in advance. When the test case fails, a test failure notification is issued and the test case of the test failure is marked, and the test case in which the test fails is obtained. At the same time, each test case corresponds to one test result, and in step 101, the test result of the test case in which the test fails is simultaneously obtained. For example, test case A is a case where the test fails, and the test result is "abce", then the test case A is determined in step 101, and the test result "abce" is determined.

Step 102: Select a valid test result corresponding to the expected result of the test case in the test result.

In the embodiment of the present invention, one or more results may be included in the test result. In this case, a useful test result, that is, an effective test result, needs to be selected in the test result; the effective test result is part or all of the test result. Wherein, when setting up the test case, each test case has an expected result, that is, the result of the test case output is expected; according to the expected result, the tester's attention result can be determined, and then the test case can be selected and tested. The expected results correspond to the effective test results. For example, the expected expected results of the test case include "expected result A" and "expected result B", and the expected result does not focus on other results; and the test results output after executing the test case include "test result a", "test result b" , "test result c" and "test result d", wherein the result A corresponds to the result a, and the result B corresponds to the result b. At this time, since the expected result does not pay attention to other results, only the results corresponding to the expected result, that is, "test result a" and "test result b" are selected in step 102, so "test result a" and "test result" b" as a valid test result.

Preferably, in the embodiment of the present invention, an ID is assigned to each test result, that is, a test result identifier; at the same time, an ID is assigned to the expected result, that is, an expected result identifier; and the test result identifier and the expected result identifier adopt the same identification manner. The above step 102 "selecting valid test results corresponding to the expected results of the test cases in the test results" specifically includes steps A1-A2:

Step A1: Determine an expected result identifier, and the expected result identifier is an identifier of an expected result of the test case.

Step A2: Determine a valid test result in the test result that is consistent with the expected result identifier.

Specifically, for a test case, the tester is concerned with "01 expected result", "02 expected result" and "04 expected result", among which "01", "02", "04" are the corresponding expected results. Logo. Then, in step A2, the test results that are consistent with the expected result identifiers "01", "02", and "04", that is, "01 test result", "02 test result", and "04 test result" are determined, and the Three "01 test results", "02 test results" and "04 test results" were taken as valid test results. By selecting valid test results based on the expected result identification, it is convenient and quick to locate the test results required by the user.

Step 103: Compare the valid test result with the expected result to determine whether the valid test result is the same as the business data in the expected result.

In the embodiment of the present invention, the difference between the effective test result and the expected result can be determined by comparing the effective test result with the expected result, thereby determining the business data in the effective test result and the business data in the expected result. Is it the same? Specifically, the diff command can be used to compare the difference between the contents of the two files or directories. In the embodiment of the present invention, the diff command can be used to compare the effective test result with the expected result, and the diff result is saved, and the diff result can be used to determine the two. Whether the business data changes.

Step 104: Mark the failure reason of the test case as the service data change when the service data is different.

After the comparison process is performed in step 103, if the service data is different, the cause of the failure of the test case may be automatically determined as the service data changes. At this time, the failure reason of the test case is marked as the service data change, and then the failure reason may be targeted. Perform the appropriate processing.

In one possible implementation, comparing the valid test results with the expected results also includes comparing the business data types of the two. Specifically, referring to FIG. 2, the method further includes:

Step 105: Comparing the effective test result with the expected result, determining that there is Whether the result of the validity test is the same as the type of business data in the expected result;

Step 106: When the service data types are different, the failure reason for marking the test case is a change of the service data type.

The "comparing the effective test result and the expected result" in steps 102 and 104 can be performed simultaneously, that is, after the comparison process is performed, it can be determined whether the service data and/or the service data type has changed. In the embodiment of the present invention, the diff command can be used to compare the effective test result with the expected result, and the diff result is saved. According to the diff result, it can be determined whether the service data between the two changes, and whether the service data type changes.

The method for identifying the cause of the failure of the test case provided by the embodiment of the present invention, by selecting the effective test result corresponding to the expected result in the test result of the test case, thereby comparing the effective test result with the expected result, thereby Determine the reason for the failure of the test case. The method omits the manual operation steps, can automatically identify the cause of the failure and mark the reason, facilitates subsequent marking of the errors, saves the maintenance staff's working time, can improve the positioning problem and fix the speed and efficiency of the problem.

In a possible implementation manner, in step 104, when the service data is different, the method further includes steps B1-B2:

Step B1: Save the business data of the valid test result to the expected copy file.

Step B2: When the business data of the valid test result is correct, the expected copy file is taken as the original expected file, and the business data of the expected result is stored in the original expected file.

In the embodiment of the present invention, the business data of the expected result is stored in the original expected file, and in step 103, “determining whether the valid test result is the same as the business data in the expected result” may be the effective test result and the expected result stored in the original expected file. The results were compared. At the same time, the expected copy file is used to save the valid test result. The expected copy file is the same format as the original expected file, or the expected copy file is different from the original expected file, and the former has valid test results. The latter has the expected results.

When the business in the valid test result is confirmed to be correct, the service can be considered The data change is normal and reasonable. At this time, the expected copy file is used as the original expected file; if the original expected file is still needed during the subsequent test, the data in the original expected file is substantially the valid test result saved in step B1. Business data. When the business data change triggers the test failure, by replacing the original expected file in time, the latest business data can be automatically obtained to test the maintenance personnel to quickly locate the latest business data.

In a possible implementation manner, in step 106, when the service data types are different, the method further includes: sending the test result of the test failure to the vulnerability management system.

Specifically, the vulnerability management system is a bug management system, and the vulnerability management system supports people with different permissions or different positions to log in. After the test result of the test failure is sent to the vulnerability management system, it is convenient for the subsequent technician to perform corresponding software improvement or update on the test result of the test failure, and the technician can obtain the test result in question in time.

The flow of the method will be described in detail below through an embodiment.

In the embodiment of the present invention, the effective test result and the expected result are compared, and at the same time, whether the valid test result and the service data and the service data type in the expected result are the same. For details, refer to FIG. 3, including steps 301-309:

Step 301: Acquire a test case in which the test fails, and obtain a test result of the test case.

Step 302: Determine an expected result identifier, the expected result identifier being an identifier of an expected result of the test case.

Step 303: Determine a valid test result in the test result that is consistent with the expected result identifier.

Step 304: Compare the effective test result with the expected result, and perform step 305 and step 308, respectively.

Step 305: Determine whether the valid test result is the same as the business data in the expected result.

Step 306: When the service data is different, mark the failure reason of the test case as The business data changes and the business data of the valid test results is saved to the expected copy file.

Step 307: When the business data of the valid test result is correct, the expected copy file is used as the original expected file, and the business data of the expected result is stored in the original expected file.

Step 308: Determine whether the valid test result is the same as the service data type in the expected result.

Step 309: When the service data types are different, the failure reason for marking the test case is a change of the service data type, and the test result of the test failure is sent to the vulnerability management system.

The method for identifying the cause of failure of the test case provided by the embodiment of the present invention can select the effective test result corresponding to the expected result in the test result of the test case, and then compare and compare the effective test result with the expected result to determine The reason for the failure of the test case. The method omits the manual operation steps, can automatically identify the cause of the failure and mark, facilitates subsequent marking of the errors, saves the maintenance staff's working time, can improve the positioning problem and fix the speed and efficiency of the problem. When the business data change triggers the test failure, the latest business data is automatically obtained by replacing the original expected file in time to test the maintenance personnel to quickly locate the latest business data. The test result of the test failure is sent to the vulnerability management system, and the technician can obtain the test result in question in time, so that the subsequent technician can perform corresponding software improvement or update on the test result of the test failure.

The method flow for identifying the cause of the failure of the test case is described in detail above. The method can also be implemented by the corresponding device. The structure and function of the device are described in detail below.

An embodiment of the present invention further provides an apparatus for identifying a cause of failure of a test case. Referring to FIG. 4, the method includes: an obtaining module 41, a selecting module 42, a comparing module 43, and a marking module 44.

The obtaining module 41 is configured to obtain a test case in which the test fails, and obtain a test result of the test case;

The module 42 is configured to select a valid test result corresponding to the expected result of the test case in the test result;

The comparing module 43 is configured to compare the effective test result with the expected result, Determine whether the valid test results are the same as the business data in the expected results;

The marking module 44 is configured to mark the failure reason of the test case as a business data change when the service data is different.

In a possible implementation manner, when the service data is different, as shown in FIG. 5, the device further includes: a saving module 45 and a replacement module 46.

a saving module 45, configured to save the business data of the valid test result to the expected copy file;

The replacement module 46 is configured to use the expected copy file as the original expected file when the business data of the valid test result is correct, and the business data with the expected result in the original expected file.

In a possible implementation, the comparison module 43 is further configured to: compare the valid test result with the expected result, and determine whether the valid test result is the same as the service data type in the expected result; the marking module 44 is further configured to: When the business data types are different, the failure reason of the test case is marked as a change in the business data type.

In a possible implementation manner, when the service data types are different, as shown in FIG. 6, the apparatus further includes: a sending module 47, configured to send the test result of the test failure to the vulnerability management system.

In a possible implementation manner, referring to FIG. 7, the selection module 42 includes: a determining unit 421 and a selecting unit 422.

a determining unit 421, configured to determine an expected result identifier, where the expected result is identified as an identifier of an expected result of the test case;

The selecting unit 422 is configured to determine a valid test result in the test result that is consistent with the expected result identifier.

A method and apparatus for identifying a cause of failure of a test case provided by an embodiment of the present invention, by selecting an effective test result corresponding to an expected result in a test result of the test case, thereby comparing the effective test result with the expected result To determine the cause of the failure of the test case. This method omits the manual operation steps, and can automatically identify the cause of the failure and mark the cause. It is convenient to mark the errors in the following, which saves the maintenance staff's working time, can improve the positioning problem and fix the speed and efficiency of the problem. When the business data change triggers the test failure, the latest business data is automatically obtained by replacing the original expected file in time to test the maintenance personnel to quickly locate the latest business data. The test result of the test failure is sent to the vulnerability management system, and the technician can obtain the test result in question in time, so that the subsequent technician can perform corresponding software improvement or update on the test result of the test failure.

The embodiment of the present application further provides a non-transitory computer storage medium, where the computer storage medium stores computer executable instructions, which can execute the method in any of the foregoing method embodiments.

FIG. 8 is a block diagram showing the structure of a network device according to another embodiment of the present invention. The network device 1100 may be a host server having a computing capability, a personal computer PC, or a portable computer or terminal that can be carried. The specific embodiments of the present invention do not limit the specific implementation of the computing node.

The network device 1100 includes a processor 1110, a communications interface 1120, a memory array 1130, and a bus 1140. The processor 1110, the communication interface 1120, and the memory 1130 complete communication with each other through the bus 1140.

The communication interface 1120 is configured to communicate with a network element, where the network element includes, for example, a virtual machine management center, shared storage, and the like.

The processor 1110 is configured to execute a program. The processor 1110 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.

The memory 1130 is used to store files. The memory 1130 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory. Memory 1130 can also be a memory array. The memory 1130 may also be partitioned, and the blocks may be combined into a virtual volume according to certain rules.

In a possible implementation, the above program may be program code including computer operating instructions. This program can be used to:

In a first aspect, a method for identifying a cause of failure of a test case is provided, comprising: obtaining a test case in which the test fails, and obtaining a test result of the test case; and selecting an effective test corresponding to the expected result of the test case in the test result. Result; compare the effective test result with the expected result to determine whether the valid test result is the same as the business data in the expected result; when the business data is different, mark the failure reason of the test case as the business data change.

The above products can perform the methods provided by the embodiments of the present application, and have the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the method provided by the embodiments of the present application.

The electronic device of the embodiment of the present application exists in various forms, including but not limited to:

Mobile communication devices: These devices are characterized by mobile communication capabilities and Voice and data communication are the main goals. Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.

Ultra-mobile PC devices: These devices belong to the category of personal computers, have computing and processing functions, and generally have mobile Internet access. Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.

Portable entertainment devices: These devices can display and play multimedia content. Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, and smart toys and portable car navigation devices.

Server: A device that provides computing services. The server consists of a processor, hard disk, memory, system bus, etc. The server is similar to a general-purpose computer architecture, but because of the need to provide highly reliable services, processing power, stability, and reliability. Security, scalability, manageability and other aspects are high.

Other electronic devices with data interaction capabilities.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

The foregoing description of the specific exemplary embodiments of the present invention has The description is not intended to limit the invention to the precise forms disclosed. The embodiments were chosen and described in order to explain the particular embodiments of the invention Choose and change. The scope of the invention is intended to be defined by the claims and their equivalents.

The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Industrial applicability

The method for identifying the cause of the failure of the test case provided by the embodiment of the present application, obtains the test case of the test failure, and obtains the test result of the test case; and selects the expected result corresponding to the test case in the test result. Effective test result; comparing the effective test result with the expected result, determining the effective test result and the expected result Whether the business data in the same is the same; when the business data is different, the failure reason of the test case is marked as a change of the business data, and the beneficial effect is achieved.

Claims

A method for identifying a cause of failure of a test case, executed by an electronic device, comprising:

Obtaining a test case in which the test fails, and obtaining a test result of the test case;

Selecting valid test results corresponding to the expected results of the test cases in the test results;

Comparing the valid test result and the expected result to determine whether the valid test result is the same as the business data in the expected result;

When the business data is different, the failure reason of the test case is marked as a business data change.
The method according to claim 1, wherein when the service data is different, the method further comprises:

Saving business data of the valid test result to an expected copy file;

When the business data of the valid test result is correct, the expected copy file is taken as the original expected file, and the business data of the expected result is stored in the original expected file.
The method according to claim 1, further comprising: comparing the effective test result and the expected result to determine whether the valid test result is the same as the service data type in the expected result;

When the business data types are different, the failure reason of the test case is marked as a business data type change.
The method according to claim 3, wherein when the types of service data are different, the method further comprises:

Send test results that failed the test to the vulnerability management system.
The method according to any one of claims 1 to 4, wherein the selecting the effective test result corresponding to the expected result of the test case in the test result comprises:

Determining an expected result identification, the expected result identifying an identification of an expected result of the test case;

Determining valid test results in the test results that are consistent with the expected result identification.
A device for identifying a cause of failure of a test case, comprising:

An obtaining module, configured to obtain a test case in which the test fails, and obtain a test result of the test case;

And a selection module, configured to select, in the test result, an effective test result corresponding to an expected result of the test case;

a comparison module, configured to compare the effective test result with the expected result, and determine whether the valid test result is the same as the service data in the expected result;

The marking module is configured to mark the failure reason of the test case as a business data change when the business data is different.
The device according to claim 6, wherein when the service data is different, the device further comprises:

a saving module, configured to save the business data of the valid test result to an expected copy file;

And a replacement module, configured to: when the business data of the valid test result is correct, use the expected copy file as an original expected file, where the original expected file stores the business data of the expected result.
The device according to claim 6, wherein the comparing module is further configured to: compare the effective test result and the expected result, and determine a service in the valid test result and the expected result Whether the data types are the same;

The marking module is further configured to mark the failure reason of the test case as a service data type change when the service data types are different.
The device according to claim 8, wherein when the type of service data is different, the device further comprises:

A sending module for sending test results of the test failure to the vulnerability management system.
The apparatus according to any one of claims 6-9, wherein the selecting module comprises:

a determining unit, configured to determine an expected result identifier, the expected result identifier being an identifier of an expected result of the test case;

And a selecting unit, configured to determine a valid test result in the test result that is consistent with the expected result identifier.
An electronic device comprising:

At least one processor; and,

a memory communicatively coupled to the at least one processor; wherein

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

Obtaining a test case in which the test fails, and obtaining a test result of the test case;

Selecting valid test results corresponding to the expected results of the test cases in the test results;

Comparing the valid test result and the expected result to determine whether the valid test result is the same as the business data in the expected result;

When the business data is different, the failure reason of the test case is marked as a business data change.
The electronic device according to claim 11, wherein when the service data is different, the method further comprises:

Saving business data of the valid test result to an expected copy file;

When the business data of the valid test result is correct, the expected copy file is taken as the original expected file, and the business data of the expected result is stored in the original expected file.
The electronic device according to claim 11, further comprising: comparing the valid test result and the expected result to determine whether the valid test result is the same as the service data type in the expected result ;

When the business data types are different, the failure reason of the test case is marked as a business data type change.
The electronic device according to claim 13, wherein when the types of service data are different, the method further includes:

Send test results that failed the test to the vulnerability management system.
The electronic device according to any one of claims 11-14, wherein the selecting the effective test result corresponding to the expected result of the test case in the test result comprises:

Determining an expected result identification, the expected result identifying an identification of an expected result of the test case;

Determining valid test results in the test results that are consistent with the expected result identification.
A non-transitory computer readable storage medium, wherein the non-transitory computer readable storage medium stores computer executable instructions for:

Obtaining a test case in which the test fails, and obtaining a test result of the test case;

Selecting valid test results corresponding to the expected results of the test cases in the test results;

Comparing the valid test result and the expected result to determine whether the valid test result is the same as the business data in the expected result;

When the business data is different, the failure reason of the test case is marked as a business data change.
The non-transitory computer readable storage medium according to claim 16, wherein when the service data is different, the method further comprises:

Saving business data of the valid test result to an expected copy file;

When the business data of the valid test result is correct, the expected copy file is taken as the original expected file, and the business data of the expected result is stored in the original expected file.
The non-transitory computer readable storage medium according to claim 16, further comprising: comparing the effective test result and the expected result, determining the valid test result and the expected result Is the business data type the same?

When the business data types are different, the failure reason of the test case is marked as a business data type change.
The non-transitory computer readable storage medium according to claim 18, wherein when the types of service data are different, the method further comprises:

Send test results that failed the test to the vulnerability management system.
The non-transitory computer readable storage medium according to any one of claims 16 to 19, wherein the selecting, in the test result, the effective test result corresponding to the expected result of the test case comprises:

Determining an expected result identification, the expected result identifying an identification of an expected result of the test case;

Determining valid test results in the test results that are consistent with the expected result identification.
A computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to execute The method of any of claims 1-5.