WO2021008029A1

WO2021008029A1 - Case execution method, apparatus and device, and computer readable storage medium

Info

Publication number: WO2021008029A1
Application number: PCT/CN2019/117309
Authority: WO
Inventors: 胡鹏强
Original assignee: 平安普惠企业管理有限公司
Priority date: 2019-07-15
Filing date: 2019-11-12
Publication date: 2021-01-21
Also published as: CN110502366A; CN110502366B

Abstract

The present application relates to the technical field of research and development management. Disclosed is a case execution method, comprising: obtaining the execution status of a case by querying information about the case of a device, to determine the execution state of the case; querying, according to the execution state, a corresponding failure cause; obtaining a node position where the case having an execution failure is located; generating a case execution log on the basis of the obtained information; and selecting execution control, e.g., selecting to continue the execution or restart an execution, for the case on the basis of the information recorded in the case execution log. Also disclosed are a case execution apparatus and device, and a computer readable storage medium. According to the present application, an automatic restart operation for the case is performed on the basis of the node position and context data, thereby reducing the difficult of the system in case execution control, and also implementing execution continuing control when the case execution fails; moreover, continuing the execution not only reduces the execution control time of the case, but also improves the success rate of the case execution.

Description

Case execution method, device, equipment and computer readable storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910634552.0, and the invention title is "case execution method, device, equipment and computer-readable storage medium" on July 15, 2019. The reference is incorporated in the application.

Technical field

This application relates to the field of R&D management technology, and in particular to a case execution method, device, equipment, and computer-readable storage medium.

Background technique

In the current execution control method for the case, the case often fails or is suspended during the execution process due to various reasons. For this situation, the solution in the prior art is to perform the case execution failure rerun and failure to continue. Operations such as re-running, selective suspension of re-running, etc., but most of the above-mentioned re-running operations are performed through manual inspection and manual control. For cases that cannot be continued, the case will be restarted and the case will be re-run. Execution, such a case control execution method consumes human resources and is not conducive to the current intelligent development requirements.

Summary of the invention

The main purpose of this application is to provide a case execution method, device, equipment, and computer-readable storage medium, aiming to solve the technical problem that the control of failure cases is too time-consuming due to the existing case execution control methods.

In order to achieve the above objectives, this application provides a case execution method, which includes the following steps:

Acquire information about a case that has been executed or that is being executed on the device, and check the execution of the case based on the case information to determine whether the case is in a faulty execution state;

If the case is in the fault execution state, according to the fault execution state, query the fault reason corresponding to the current fault execution state of the case from the preset relationship table between the fault execution state and the fault cause;

Obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording whether the case's failure has been processed Identification information;

Determine whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

If it is determined that the fault has been eliminated, the node position recorded in the case execution log is taken as the starting point of the case execution, and the case information is reloaded into the case execution unit of the device, and the The starting point is the execution point to continue executing the case;

If it is determined that the fault has not been eliminated, the case information is reloaded into the case execution unit of the device to restart the execution of the case.

Optionally, the generating a case execution log based on the failure reason and the node location includes:

Acquiring template information of the case execution log, where the template information is a table that records the execution status of the case and the information generated;

Acquiring the execution code corresponding to the node position and the context information of the node position;

Record the execution generation of the node location, the failure reason and the context information in the table to form a case execution log, where the context information includes at least one of a cookie, a login state, a variable, and a time stamp One kind.

Optionally, the failure execution state includes an execution interruption state and an execution failure state;

The obtaining the node location of the case in the current fault execution state, and generating a case execution log based on the fault cause and the node location includes:

Determine whether the fault execution state is an execution interruption state;

If it is determined that the execution is interrupted, the node location where the execution of the case is interrupted is acquired, and the node location is recorded in the case execution log;

If it is determined that it is not the execution interruption state, then it is determined whether the fault execution state meets the conditions of the execution failure state;

If it is determined that the conditions for the execution failure state are met, determine the cause of the failure that caused the execution of the case and the location of the node that caused the execution of the case to fail, and record the cause of the failure and the location of the node to the case Execution log.

Optionally, the determining the cause of the failure of the execution of the case includes:

Detecting whether a new case with execution priority setting is started during the execution of the case by the case execution unit;

Detecting whether the working environment corresponding to the execution of the case has changed, where the working environment includes the configuration items of the device, the server of the device, the test scenario executed by the case, and the network used by the device;

It is detected whether the case is an execution failure caused by a non-functional problem, where the non-functional problem is a failure not caused by a software configuration or a hardware configuration of the device.

Optionally, after it is detected that a new case with execution priority setting is started, the case execution method further includes:

Determine whether the execution priority of the new case is greater than the execution priority of the currently executed case;

If yes, judge whether the new case and the currently executed case are the same type of case;

If it is a case of the same type, replace the currently executed case with the new case and execute the new case;

If it is not the same type of case, set the currently executed case to the execution interrupted state or the execution failed state, and jump to the execution of the new case. After the execution of the new case is completed, return to the set execution interrupted state or The execution of the failed case continues.

Optionally, the node position recorded in the case execution log is used as the starting point of the case execution, and the case information is reloaded into the case execution unit of the device, taking the starting point as the execution point Continuing the execution of the cases includes:

If the failure execution state is an execution failure state, the class name and method name of the case in the execution failure state are acquired through reflection;

Read the context information from the case execution log according to the class name and method name, and call a case execution failure processing strategy to restart the case in the execution failure state.

Optionally, before the step of reloading the case information into the case execution unit of the device to restart the execution of the case, the method further includes: classifying the case according to the cause of the failure ；

The reloading the case information into the case execution unit of the device to perform restart execution processing on the case includes:

Selecting a corresponding case buffer area from the device according to the type of the case;

Load the case information to be reloaded into the case buffer area and wait for the call execution of the case execution unit.

In addition, in order to achieve the above objective, this application also provides a case execution device, the case execution device includes:

The monitoring module is used to obtain information about a case that has been executed or that is being executed on the device, and check the execution of the case according to the case information to determine whether the case is in a faulty execution state;

The query module is used to, when the case is in the fault execution state, according to the fault execution state, from a preset table of the corresponding relationship between the fault execution state and the failure cause, query the case corresponding to the current fault execution state cause of issue;

The recording module is used to obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording the case Identification information of whether the fault has been processed;

The judgment module is used to judge whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

The processing module is configured to, when judging that the fault has been eliminated, use the node position recorded in the case execution log as the starting point of the case execution, and reload the case information to the case execution unit of the device , Continue to execute the case with the starting point as the execution point; and when it is determined that the fault has not been eliminated, reload the case information into the case execution unit of the device to restart the execution of the case .

In addition, in order to achieve the above objective, the present application also provides a case execution device, the case execution device includes: a memory, a processor, and a case execution program stored on the memory and running on the processor, so When the case execution program is executed by the processor, the steps of the case execution method described in any one of the above are implemented.

In addition, in order to achieve the above object, the present application also provides a computer-readable storage medium with a case execution program stored on the computer-readable storage medium. When the case execution program is executed by a processor, the implementation is as described in any of the above The steps of the case execution method described.

Through the detection of the reasons for the execution failure of the case, and classify the detected reasons, at the same time record the location of the node where the execution failed and the context data corresponding to the node. After the cause of the execution failure is solved, according to the node location and context data Arrange the automatic restart operation of the case, and realize the rerun control of the case based on this recording and automatic restart method, thus reducing the difficulty of the system to control the case execution, and also realize the continued execution control when the case execution fails. Compared with the existing method of re-executing the case, the continued execution can save the execution time of the case and increase the success rate of case execution.

Description of the drawings

FIG. 1 is a schematic flowchart of the first embodiment of the case execution method provided by this application;

2 is a schematic flowchart of a second embodiment of the case execution method provided by this application;

FIG. 3 is a schematic structural diagram of a server operating environment involved in a solution of an embodiment of the application;

FIG. 4 is a schematic diagram of functional modules of an embodiment of a case execution apparatus provided by this application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Detailed ways

It should be understood that the specific embodiments described herein are only used to explain the application, and not used to limit the application.

Referring to Fig. 1, Fig. 1 is a flowchart of a case execution method provided by an embodiment of the application. In this embodiment, the case execution method specifically includes the following steps:

Step S110: Obtain information about a case that has been executed or is being executed on the device, and check the execution of the case according to the case information to determine whether the case is in a faulty execution state;

In this step, the case can be understood as a test case, it can also be understood as the execution process or test process of a certain functional code on the system or device, or even an application and data processing case, etc. In practical applications, the case may be a collection including multiple cases.

For the acquisition action here, the specific implementation can be collected from the code execution pool on the system or device, or read from the started application management background.

In this step, it is specifically the real-time execution status of the case in the collection device. The real-time execution status includes two states of normal execution and failure execution. The failure execution state can be understood as the case is interrupted, stopped, and temporarily suspended. Execution, even re-run execution.

Of course, in actual applications, for real-time case execution status acquisition, it means monitoring the case being executed on the device to obtain the information generated during the execution of the case; while for the case information that has been executed, it can be obtained from Obtained in the case execution log record, general equipment will record the case in a certain period of time during the execution of the case.

In this embodiment, the monitoring of the failure is specifically through the records in the work log file generated during the execution of the monitoring case, the monitoring and comparison of each work log in the work log file is correct, and the calculation of the incorrect work log , Until the calculated number of work logs is greater than the preset value, it is considered that the execution of the case has failed, or it is stopped, suspended, etc.

Step S120: If the case is in the fault execution state, according to the fault execution state, query the fault cause corresponding to the current fault execution state of the case from the preset relationship table between the fault execution state and the fault cause ；

Step S130: Obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording the case's failure Whether the identification information has been processed;

In this embodiment, for the above-mentioned failure causes including non-functional problems on the system, working environment and other factors, the non-functional problems should be understood as problems caused by non-system defects, such as environmental problems, that is, some configurations of the system. Item configuration error, some systems' servers are restarting, some systems are being tested abnormally, some network failures, etc.

In practical applications, the inspection of the execution of the case can be implemented in the following ways:

First of all, when developing the case, a test statement is set for each execution statement in each case, and all the test statements are combined to obtain a test program for a case, and the program will start automatically when the case is executed , Through these test statements to monitor and record the execution of the case.

In practical applications, the execution of each statement basically reflects the value of "true" or "false", and the execution status of each case statement of the case is realized by judging the "true" and "false" values of these statements Perform testing to determine whether there is a fault in the case.

If a statement failure is detected, the statement corresponding to the failure in the case is obtained, and the execution function of the statement in the case is analyzed to determine which failure execution state of the failure data is, and based on the failure experience or troubleshooting of the statement History is used to comprehensively judge the main reason for the failure. For example, the main function of the statement is to realize the path mapping of data retrieval. Generally speaking, the reason that the statement cannot be executed is that the mapped path information does not exist or the path information is incorrect. It can be seen that the cause of the failure is incorrect path information, and the incorrect path information is marked.

After analyzing the cause, extract the location of the fault point from the monitored work log file and use this location as the location of the faulty node;

Based on the node position, determine the node code position in the case execution code;

Record the code at the code position and the code data before and after the code position (that is, the context data) to generate an execution log.

In practical applications, generally a case corresponds to a work log file, and when the work log file records the case execution, it is recorded in the order in which the statements of the case are executed. During the recording process, all states of the statement during the execution process are recorded. The information and the information that needs to be applied, as well as the fault label are recorded. The processor analyzes the work log file and traverses the data generated during the execution of each sentence to check and compare to determine whether there is a fault label. If it exists, then Obtain the label and the position in the case sentence of the sentence corresponding to the label to determine the node position of the fault. Further, extract the fault label, case information, case sentence position where the label is located, and context information at that position. Take it down to form an inspection execution log, which can be used to process the case in subsequent case maintenance. Preferably, the position of the sentence in the case can be specifically determined by the pointing frame of the sentence when the case is executed.

In this embodiment, the context information can also be variables and parameters in the case execution process, etc., and also include the class name and method name of the case that records the execution failure, and when recording node information, the class name and method can be created The correspondence between names and context information is stored in the generated case execution log.

Step S140, judging whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

The troubleshooting in this step is mainly to eliminate the fault through artificial interference. When the system analyzes that there is a fault that causes the case to fail, it will detect the fault regularly, and detect whether the fault is Excluded, of course, the response to the troubleshooting of the fault can be through the response of the identification information after the fault is eliminated, or through the response of some other parameters. If it is eliminated, then transfer to step S160 to restart the case .

In practical applications, the identification information can be specifically identified by a binary identification bit, "0" means not excluded, and "1" means excluded. In this step, it is determined by obtaining 0 or 1 in the identification bit. Whether the fault has been eliminated; in addition, it can be identified by adding a symbol bit in the execution log. The specific identification includes "N" and "Y". "N" means not eliminated, and "Y" means eliminated, and judge The method is consistent with the binary identification bit, so I won’t repeat it here.

Step S150, if it is determined that the fault has been eliminated, the node position recorded in the case execution log is used as the starting point of the case execution, and the case information is reloaded into the case execution unit of the device, Continue to execute the case with the starting point as the execution point;

Step S160: If it is determined that the fault has not been eliminated, reload the case information into the case execution unit of the device to perform restart execution processing on the case.

In this embodiment, the restart operation refers to re-running the case; when the system detects a response that the fault is eliminated, it returns to the execution process of the case, and obtains the node corresponding to the case from the execution log Record and retrieve the response processing method to rerun the case.

In actual applications, in order to facilitate restart processing, it also includes setting a restart case loading data buffer. After determining the case that needs to be restarted and executed, upload the corresponding case information to the buffer, and the buffer will upload The information of the case is saved in the restart table in the buffer. When the timer expires, you can directly read the case information in the table and execute the restart program to realize the restart operation of the case.

In this embodiment, in order to facilitate the subsequent operation of restarting the case, it also includes: classifying the case according to the reason that caused the execution of the case to fail. The cases implemented are divided into one category and so on.

In this embodiment, the reasons for the execution failure of the case can be specifically understood as being divided into the following categories: the startup of the new case is interrupted, the mapping of the statement is incorrect, the system hardware failure and the operating system failure, for the case according to the reason for the execution failure Specifically, according to the above-mentioned concentration reasons, the cases are preliminarily classified, and for the classified cases, whether to perform a continue operation or a restart operation, jump to step S140 for the next processing.

In this embodiment, the re-running can be the continued execution of the case or the re-execution of the case. Of course, it is preferable to choose whether to continue or re-execute the case according to the cause of the failure execution of the case.

Based on the above steps, the execution control of the case is realized, and different rerun operations are realized according to the classification of the case execution failure, thereby avoiding the problem of excessive execution time and resource consumption due to the re-execution of existing case failures. It realizes the control method that supports cases such as automatic re-run after failure, continued re-run after failure, and selective suspension and re-run, which greatly improves the user's use and operation experience.

Further, in this embodiment, generating a case execution log based on the failure cause and the node location includes:

Record the execution generation of the node location, the cause of the failure, and the context information in the table to form a case execution log, where the context information includes at least one of a cookie, a login state, a variable, and a time stamp One kind.

Specifically, the record of the node position is specifically expressed as the execution code in the program of the case corresponding to the node position, that is, the execution code corresponding to the node position is recorded, and the context information of the node position is also recorded in the In the execution log, the context information includes at least one of a cookie, a login state, a variable, and a time stamp.

In this embodiment, the failure execution state includes an execution interruption state and an execution failure state;

Determine whether the fault execution state is an execution interruption state;

In practical applications, for the judgment of the execution interruption state, it is optional to determine whether the execution of the case is considered to be an interrupt operation by detecting the case execution interrupt button in the system. If the case interrupt button is pressed, or the If the button has a response signal output, it is considered that the case is in an interrupted state.

Based on the interruption state, and the user actively pauses. There is a pause button on the platform. If the user clicks pause during the execution of a case, the platform background will suspend the case process and save all variables and information executed somewhere so that the subsequent process can continue to execute normally.

For the judgment of the execution failure status, the optional is to determine whether the execution method of the case is ended. If so, further analyze the reason for the termination to determine the reason for the termination. Under normal circumstances, the case There are several situations in which the execution method is terminated, which are environmental reasons, cases are manually terminated, system functional defects, etc.

In this embodiment, the determining the cause of the failure of the execution of the case includes:

In practical applications, the working environment refers to some configuration items of the system, the server of the system, the system being tested, the network, etc., while the change of the working environment refers to the configuration of some configuration items of the system incorrectly, and the server of the system is Restart, the system is being tested, the scene is abnormal, the network fails, etc.

When the case execution fails due to environmental reasons, the execution process of the case will stay at the failed node, and the context of the failure will be recorded. When the environmental problem is solved, you can click the Continue Execution button to make the case fail. Continue execution at the node, or realize the automatic start of the automatic case through the preset case restart program.

The specific implementation plan for re-running cases for environmental reasons can be as follows:

Record the context of the execution code, that is, cookies, login status, variables, timestamps and other information, stored in the database

When the environmental problem is solved, the class name and method name of the current execution failure case are obtained through reflection

When the continue execution button is clicked, the context data is read and the method at the failure point of the current failed case is called to continue the case.

In this embodiment, if it is analyzed that the execution of the case fails due to the start of a new case, the case execution method further includes:

In practical applications, the execution failure of a case may be due to the start of a case with a high priority level, but under the premise that the processing resources of the system are not enough, it will selectively stop some cases currently being executed to idle out. Part of the resources are used in new cases. For the case execution failure in this case, the case can be rerun by continuing the execution.

Further, when a case fails to execute due to a non-functional problem, the case is started by automatically re-executing the case, and the case is stopped until the case is completely executed successfully or the execution fails due to functional problems multiple times.

The specific implementation scheme can be to add monitoring of the test execution result in the @AfterMethod annotation method, and use the ITestResult interface to determine whether the test execution is successful. If it fails, get the class name and method name of the current execution failure case through reflection, and then call The method realizes one or more reruns, and the number of reruns can be set by yourself.

In this embodiment, if the failure execution state is the execution failure state, the node position recorded in the case execution log is used as the starting point of the case execution, and the case information is reloaded into the In the case execution unit of the device, the step of continuing to execute the case with the starting point as the execution point specifically includes:

Obtain the class name and method name of the case in the execution failure state through reflection;

In practical applications, the above reflection is a technique in java programming, through which the specified class object can be obtained. In this embodiment, reflection is used to obtain the class object, and the function is to save the class object when the execution fails, and save it, so that the object can be subsequently called to execute the subsequent step method of the corresponding case.

For class names and method names, it refers to the terms of some codes in the java programming code. In the code, objects are created through classes and methods are manipulated through objects. One method is to implement some data processing, that is, to complete the steps of some cases.

Reading context data means that when you click to continue executing the case, the background will read all the variable values stored in the database related to this case according to the previously saved class name and method name, and then redefine the variables and assign values , To reproduce the data environment of the case. As a result, the suspended case can continue to be executed.

In other words, when the case is detected as an execution failure state, the class name of the case and the method name of the execution of the case will be recorded at the same time. After the problem that caused the execution failure is solved, the class name and method of the failure case of the division are queried through reflection Name, and rerun the case based on the recorded node position and context data.

In this embodiment, if the reason for the execution failure of the case is that the user ends the case, the case cleaning program will be started, and all related to the terminated case will be cleaned up, so as to realize the closing operation of the case.

In this embodiment, before the step of reloading the case information into the case execution unit of the device to restart the execution of the case, the method further includes: performing the case according to the failure cause Type division;

To sum up, the case execution method provided in the embodiments of the present application determines the execution status of the case by querying the case information of the device to obtain the execution status of the case, and then queries the corresponding failure cause according to the execution status, and then obtains the execution failure The location of the node where the case is located, based on the information obtained above to generate a case execution log, based on the information recorded in the case execution log to select the execution control of the case, choose whether to continue or restart the execution, that is, by executing the case Detect the cause of the failure, and classify the detected cause, and record the location of the node where the execution failed and the context data corresponding to the node. After the cause of the execution failure is solved, the automatic case is arranged according to the node location and context data The restart operation reduces the difficulty of the system's control over the case execution, and at the same time realizes the continued execution control when the case execution fails. Compared with the existing secret re-execution method, the continued execution can save the execution time of the case. It also improves the success rate of case execution.

The following takes specific failure causes as an example to describe in detail the case execution method provided in this application. As shown in Figure 2, it is a specific implementation flowchart when the case execution fails. The method specifically includes the following steps:

Step S210, acquiring information about cases where execution failed on the device;

In this step, it can specifically be a case that has been executed, but the end should be understood as the case information that has been stored in the case record table, that is, because it is recorded as the teacher table by the equipment system and has not been Cases to be re-executed; further, it can also be a case that is being executed, which has just been marked as a failed execution.

Step S220: Analyze and extract the location of the node that caused the execution of the case to fail during execution;

In this step, there may be multiple node positions of this kind. For this, it is also necessary to determine whether the case can be continued according to the node position and the reason for the failure of the node position. If not, directly start the restart operation step .

Further, it is also possible to determine the location of the first failed node by tracing the execution history of the case, determine the executability of the location of the first failed node, and restart the operation directly if it is impossible to proceed, and continue to determine the next node if possible Executability of the location, until all nodes in the case have a non-continuable execution, restart, otherwise continue execution.

Step S230: Determine the operability of the cause of the failure at the node location;

In practical applications, the executability here includes useable to continue executing case operations and non-continuous case operations.

Step S240, select the control scheme of the case according to the judgment result;

In this step, its control scheme refers to continuing to perform operations and re-running operations.

Step S250, generating a case execution log file according to the node location and the control scheme;

Step S260: Perform a control operation on the case according to the record information in the case execution log file.

In this embodiment, when the node location is recorded, it also includes the execution code of the node location and the context data of the location corresponding to the node location. The context data includes information such as cookies, login status, variables, and time stamps, which are stored in the case execution Log file.

In this embodiment, it is further detected that the execution failure is due to environmental problems. After the environmental problem is solved, you can choose to continue the execution control plan for processing. Specifically, when the environmental problem is solved, the class of the current execution failure use case is obtained through reflection. Name and method name. When you click the Continue Execution button, the context data is read, and the method at the failure of the current failed use case is called to continue the case.

Further, if the execution fails due to a non-functional problem, the method of automatically re-executing the case is selected until the case is completely executed successfully or the execution fails due to a functional problem.

Implementation scheme: In the @AfterMethod annotation method, add monitoring of test execution results, use the ITestResult (best test result) interface to judge whether the test execution is successful, if it fails, get the class name and method name of the current execution failure case through reflection , And then call the method to rerun once (or multiple times, the number of times can be set by yourself).

In order to solve the above-mentioned problems, this application also provides a case execution device, which can be used to implement the case execution method provided in the embodiments of this application. Its physical implementation exists in the form of a server. The specific hardware implementation of the server is as follows: As shown in Figure 1.

Referring to FIG. 3, the server includes: a processor 301, such as a CPU, a communication bus 302, a user interface 303, a network interface 304, and a memory 305. Among them, the communication bus 302 is used to implement connection and communication between these components. The user interface 303 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the network interface 304 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 305 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as a magnetic disk memory. Optionally, the memory 305 may also be a storage device independent of the aforementioned processor 301.

As shown in FIG. 3, the memory 305 as a non-volatile computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a case-based execution program. Among them, the operating system is a program that manages and executes the device and software resources, and supports the operation of the execution program and other software and/or programs.

In the hardware structure of the server shown in FIG. 3, the network interface 104 is mainly used to access the network; the user interface 103 is used to execute case information on the device and data generated during the execution of the case, and the processor 301 can be used to call The case execution program is stored in the memory 305 and executes the operations of each embodiment of the following case execution method.

In this embodiment of the Ming Dynasty, the implementation of FIG. 3 can also be a mobile terminal capable of touch operation such as a mobile phone. The processor of the mobile terminal can implement the case execution method by reading the data stored in the buffer or storage unit. The program code is used to analyze the case and generate a case execution log to control which method is selected to perform operations on the case.

In order to solve the above-mentioned problems, an embodiment of the present application also provides a case execution device. Referring to FIG. 4, FIG. 4 is a schematic diagram of functional modules of the case execution device provided in an embodiment of the application. In this embodiment, the device includes:

The monitoring module 41 is configured to obtain information about cases that have been executed or being executed on the device, and check the execution of the case according to the case information to determine whether the case is in a faulty execution state;

The query module 42 is configured to, when the case is in the failure execution state, according to the failure execution state, from a preset table of the corresponding relationship between the failure execution state and the failure cause, query the case corresponding to the current failure execution state Cause of failure;

The recording module 43 is configured to obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording the Identification information of whether the failure of the case has been processed;

The judgment module 44 is configured to judge whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

The processing module 45 is configured to, when judging that the fault has been eliminated, use the node position recorded in the case execution log as the starting point of the case execution, and reload the case information to the case execution of the device In the unit, continue to execute the case with the starting point as the execution point; and when it is determined that the fault has not been eliminated, reload the case information into the case execution unit of the device to restart execution of the case deal with.

Based on the description of the embodiment that is the same as the case execution method of the above embodiment of the present application, the content of the embodiment of the case execution device in this embodiment will not be repeated.

This embodiment detects the reasons for the execution failure of the case and classifies the detected reasons. At the same time, it records the location of the node where the execution failed and the context data corresponding to the node. After the cause of the execution failure is resolved, the location of the node The case execution log is generated with context data to arrange the automatic restart operation of the case. Based on this recording and automatic restart method, the rerun control of the case is realized, thereby reducing the difficulty of the system to control the execution of the case, and also realizes the case Continue execution control when execution fails. This control method can save the execution time of the case, improve the control efficiency of the case, and increase the success rate of case execution.

The present application also provides a computer-readable storage medium, where the computer-readable storage medium may be volatile or non-volatile, which is not specifically limited by the present application.

In this embodiment, a case execution program is stored on the computer-readable storage medium, and the case execution program of the H5 webpage is executed by a processor to implement the steps of the case execution method described in any of the above embodiments. Among them, the method implemented when the case execution program is executed by the processor can refer to the various embodiments of the case execution method of the present invention, so it will not be repeated.

The embodiments of the present invention have been described based on the above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific embodiments. The above-mentioned specific embodiments are only illustrative and not restrictive. Those of ordinary skill in the art Under the enlightenment of the present invention, without departing from the purpose of the present invention and the scope of protection of the claims, many forms can be made, and any equivalent structure or equivalent process transformation made by using the content of the description and drawings of the present invention, Or directly or indirectly used in other related technical fields, all of which belong to the protection of the present invention.

Claims

A case execution method, the case execution method includes the following steps:

Acquire information about a case that has been executed or that is being executed on the device, and check the execution of the case based on the case information to determine whether the case is in a faulty execution state;

If the case is in the fault execution state, according to the fault execution state, query the fault reason corresponding to the current fault execution state of the case from the preset relationship table between the fault execution state and the fault cause;

Obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording whether the case's failure has been processed Identification information;

Determine whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

If it is determined that the fault has been eliminated, the node position recorded in the case execution log is taken as the starting point of the case execution, and the case information is reloaded into the case execution unit of the device, and the The starting point is the execution point to continue executing the case;

If it is determined that the fault has not been eliminated, the case information is reloaded into the case execution unit of the device to restart the execution of the case.
The case execution method according to claim 1, wherein said generating a case execution log based on said failure cause and said node location comprises:

Acquiring template information of the case execution log, where the template information is a table that records the execution status of the case and the information generated;

Acquiring the execution code corresponding to the node position and the context information of the node position;

Record the execution generation of the node location, the failure reason and the context information in the table to form a case execution log, where the context information includes at least one of a cookie, a login state, a variable, and a time stamp One kind.
The case execution method according to claim 1, wherein the failure execution state includes an execution interruption state and an execution failure state;

The obtaining the node location of the case in the current fault execution state, and generating a case execution log based on the fault cause and the node location includes:

Determine whether the fault execution state is an execution interruption state;

If it is determined that the execution is interrupted, the node location where the execution of the case is interrupted is acquired, and the node location is recorded in the case execution log;

If it is determined that it is not the execution interruption state, then it is determined whether the fault execution state meets the conditions of the execution failure state;

If it is determined that the conditions for the execution failure state are met, determine the cause of the failure that caused the execution of the case and the location of the node that caused the execution of the case to fail, and record the cause of the failure and the location of the node to the case Execution log.
The case execution method according to claim 3, wherein the determining the cause of the failure of the case execution failure comprises:

Detecting whether a new case with execution priority setting is started during the execution of the case by the case execution unit;

Detecting whether the working environment corresponding to the execution of the case has changed, where the working environment includes the configuration items of the device, the server of the device, the test scenario executed by the case, and the network used by the device;

It is detected whether the case is an execution failure caused by a non-functional problem, where the non-functional problem is a failure not caused by a software configuration or a hardware configuration of the device.
5. The case execution method according to claim 4, after detecting that a new case with execution priority setting is started, the case execution method further comprises:

Determine whether the execution priority of the new case is greater than the execution priority of the currently executed case;

If yes, judge whether the new case and the currently executed case are the same type of case;

If it is a case of the same type, replace the currently executed case with the new case and execute the new case;

If it is not the same type of case, set the currently executed case to the execution interrupted state or the execution failed state, and jump to the execution of the new case. After the execution of the new case is completed, return to the set execution interrupted state or The execution of the failed case continues.
The case execution method according to claim 5, wherein the node position recorded in the case execution log is used as the starting point of the case execution, and the case information is reloaded into the case execution unit of the device, Using the starting point as the execution point to continue executing the case includes:

If the failure execution state is an execution failure state, the class name and method name of the case in the execution failure state are acquired through reflection;

Read the context information from the case execution log according to the class name and method name, and call a case execution failure processing strategy to restart the case in the execution failure state.
The case execution method according to claim 6, before the step of reloading the case information into the case execution unit of the device to restart the execution of the case, further comprising: according to the cause of the failure Classify the case;

The reloading the case information into the case execution unit of the device to perform restart execution processing on the case includes:

Selecting a corresponding case buffer area from the device according to the type of the case;

Load the case information to be reloaded into the case buffer area and wait for the call execution of the case execution unit.
A case execution device, the case execution device includes:

The monitoring module is used to obtain information about a case that has been executed or that is being executed on the device, and check the execution of the case according to the case information to determine whether the case is in a faulty execution state;

The query module is used to, when the case is in the fault execution state, according to the fault execution state, from a preset table of the corresponding relationship between the fault execution state and the failure cause, query the case corresponding to the current fault execution state cause of issue;

The recording module is used to obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording the case Identification information of whether the fault has been processed;

The judgment module is used to judge whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

The processing module is configured to, when judging that the fault has been eliminated, use the node position recorded in the case execution log as the starting point of the case execution, and reload the case information to the case execution unit of the device , Continue to execute the case with the starting point as the execution point; and when it is determined that the fault has not been eliminated, reload the case information into the case execution unit of the device to restart the execution of the case .
The case execution device according to claim 8, wherein the failure execution state includes an execution interruption state and an execution failure state; the recording module includes a detection subunit and a recording subunit

The detection subunit is used to determine whether the fault execution state is an execution interruption state;

The recording subunit is configured to, when it is determined that the execution is interrupted, obtain the node position where the case execution is interrupted, and record the node position in the case execution log;

The detection subunit is configured to determine whether the faulty execution state meets the condition of the execution failure state when it is judged that it is not the execution interruption state;

The recording subunit is used to determine the cause of the failure of the execution of the case and the location of the node that caused the failure of the execution of the case when the conditions of the execution failure state are satisfied The node location is recorded in the case execution log.
9. The case execution device according to claim 9, wherein the recording sub-unit is used to detect whether a new case with execution priority setting is activated during the execution of the case by the case execution unit; detecting execution of the case Whether the corresponding working environment has changed, where the working environment includes the configuration items of the device, the server of the device, the test scenario executed by the case, and the network used by the device; check whether the case The execution failure is caused by a non-functional problem, where the non-functional problem is a failure not caused by the software configuration or hardware configuration of the device.
The case execution device according to claim 10, wherein the judgment module is further configured to judge whether the execution priority of the new case is greater than the execution priority of the currently executed case; if so, judge whether the new case is different from the currently executed case Whether the cases are of the same type;

When it is judged that the cases are of the same type, replace the currently executed case with the new case, and execute the new case;

The processing module is used to set the currently executed case to the execution interrupted state or the execution failed state when it is judged that the case is not the same type, and jump to the execution of the new case, and after the execution of the new case is completed, Return to the case set to the execution interruption state or execution failure state to continue execution.
The case execution device of claim 11, if the failure execution state is an execution failure state, the processing module is configured to obtain the class name and method name of the case in the execution failure state through reflection; according to the The class name and method name read the context information from the case execution log, and call the case execution failure processing strategy to restart the case in the execution failure state.
The case execution device according to claim 12, wherein the case execution device further comprises a classification module for classifying the case according to the cause of the failure;

The processing module is configured to select a corresponding case buffer area from the device according to the type of the case; load the case information to be reloaded into the case buffer area and wait for the case execution unit to call carried out.
A case execution device, the case execution device comprising: a memory, a processor, and a case execution program stored in the memory and capable of running on the processor, and when the case execution program is executed by the processor Steps to implement the case execution method described below:

Acquire information about a case that has been executed or that is being executed on the device, and check the execution of the case based on the case information to determine whether the case is in a faulty execution state;

If the case is in the fault execution state, according to the fault execution state, query the fault reason corresponding to the current fault execution state of the case from the preset relationship table between the fault execution state and the fault cause;

Obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording whether the case's failure has been processed Identification information;

Determine whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

If it is determined that the fault has been eliminated, the node position recorded in the case execution log is taken as the starting point of the case execution, and the case information is reloaded into the case execution unit of the device, and the The starting point is the execution point to continue executing the case;

If it is determined that the fault has not been eliminated, the case information is reloaded into the case execution unit of the device to restart execution of the case.
The case execution device according to claim 14, wherein the failure execution state includes an execution interruption state and an execution failure state;

When the case execution program is executed by the processor to realize the step of obtaining the node position of the case in the current fault execution state, and generating a case execution log based on the failure cause and the node position, the following steps are included :

Determine whether the fault execution state is an execution interruption state;

If it is determined that the execution is interrupted, the node location where the execution of the case is interrupted is acquired, and the node location is recorded in the case execution log;

If it is determined that it is not the execution interruption state, then it is determined whether the fault execution state meets the conditions of the execution failure state;

If it is determined that the conditions for the execution failure state are met, determine the cause of the failure that caused the execution of the case and the location of the node that caused the execution of the case to fail, and record the cause of the failure and the location of the node to the case Execution log.
15. The case execution device according to claim 15, when the case execution program is executed by the processor to implement the step of determining the cause of the failure causing the case execution failure, the step includes the following steps:

Detecting whether a new case with execution priority setting is started during the execution of the case by the case execution unit;

Detecting whether the working environment corresponding to the execution of the case has changed, where the working environment includes the configuration items of the device, the server of the device, the test scenario executed by the case, and the network used by the device;

It is detected whether the case is an execution failure caused by a non-functional problem, where the non-functional problem is a failure not caused by a software configuration or a hardware configuration of the device.
The case execution device according to claim 16, when the case execution program is executed by the processor, the following steps of the case execution method are further implemented:

Determine whether the execution priority of the new case is greater than the execution priority of the currently executed case;

If yes, judge whether the new case and the currently executed case are the same type of case;

If it is a case of the same type, replace the currently executed case with the new case and execute the new case;

If it is not the same type of case, set the currently executed case to the execution interrupted state or the execution failed state, and jump to the execution of the new case. After the execution of the new case is completed, return to the set execution interrupted state or The execution of the failed case continues.
The case execution device according to claim 17, wherein the case execution program is executed by the processor to realize the use of the node position recorded in the case execution log as the starting point of the case execution, and the case information When reloading into the case execution unit of the device, and continuing to execute the steps of the case with the starting point as the execution point, the following steps are included:

If the failure execution state is an execution failure state, the class name and method name of the case in the execution failure state are acquired through reflection;

Read the context information from the case execution log according to the class name and method name, and call a case execution failure processing strategy to restart the case in the execution failure state.
The case execution device according to claim 18, when the case execution program is executed by the processor, the following steps of the case execution method are further implemented:

Classify the case according to the cause of the failure;

The reloading the case information into the case execution unit of the device to perform restart execution processing on the case includes:

Selecting a corresponding case buffer area from the device according to the type of the case;

Load the case information to be reloaded into the case buffer area and wait for the call execution of the case execution unit.
A computer-readable storage medium on which a case execution program is stored, and when the case execution program is executed by a processor, the steps of the case execution method described below are implemented:

Acquire information about a case that has been executed or that is being executed on the device, and check the execution of the case based on the case information to determine whether the case is in a faulty execution state;

If the case is in the fault execution state, according to the fault execution state, query the fault reason corresponding to the current fault execution state of the case from the preset relationship table between the fault execution state and the fault cause;

Obtain the node position of the case in the current failure execution state, and generate a case execution log based on the failure cause and the node position, wherein the case execution log also includes recording whether the case's failure has been processed Identification information;

Determine whether the fault corresponding to the cause of the fault is eliminated according to the identification information in the case execution log;

If it is determined that the fault has been eliminated, the node position recorded in the case execution log is taken as the starting point of the case execution, and the case information is reloaded into the case execution unit of the device, and the The starting point is the execution point to continue executing the case;

If it is determined that the fault has not been eliminated, the case information is reloaded into the case execution unit of the device to restart the execution of the case.