CN110543429A - Test case debugging method, device and storage medium - Google Patents

Abstract

The invention discloses a test case debugging method, a device and a storage medium. The method determines the first target step code in the current test case; adds the first target step code to the blocking queue, and the first target step code Execute the first target step code during execution; determine whether the first target step code is successfully executed and output the execution result. By determining the first target step code in the use case, the present invention enables the tester to locate any step in the current test case, thereby improving the user experience; by judging whether the first target step code is executable, the tester can set jumps in advance. By executing the executable first target step code separately, the execution time is reduced; by judging and outputting the execution result of executing a single step, the execution result of a single step can be directly obtained, which improves the debugging efficiency.

Description

Test case debugging method, device and storage medium

technical field

The present invention relates to the technical field of financial technology (Fintech), and in particular, to a test case debugging method, device and computer-readable storage medium.

Background technique

With the development of computer technology, more and more technologies (big data, distributed, blockchain, artificial intelligence, etc.) are applied in the financial field, and the traditional financial industry is gradually transforming into financial technology (Fintech). The security and real-time requirements of the industry also put forward higher requirements for technology. For the bank's software product testing system, at present, the tester usually executes the entire use case after writing the test case to check whether the steps of the use case are accurate. If there is an error step, the tester needs to repeat the execution of the entire use case after modifying the error step, and judge whether the modified step can be executed successfully until the entire use case is successfully executed. In the process of locating and analyzing the problem in the use case, the tester needs to execute the use case repeatedly. In fact, most of the steps performed are not helpful for the localization and analysis of the problem. Only a few key steps can find the problem, which leads to Debug inefficient issues during debugging of the entire use case.

SUMMARY OF THE INVENTION

The main purpose of the present invention is to propose a test case debugging method, device and computer-readable storage medium, aiming at solving the technical problem of low debugging efficiency in the debugging process of the entire use case.

In order to achieve the above object, the present invention provides a test case debugging method, the test case debugging method includes the following steps:

When receiving the use case debugging instruction, determine the first target step code in the current test case based on the relevant parameters in the use case debugging instruction, wherein the relevant parameters at least include the operation type parameter and the page element positioning path;

adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable;

If the first target step code is executable, obtain and execute the first target step code from the blocking queue;

According to the preset verification method, verify whether the first target step code is successfully executed, and output the execution result of the first target step code.

Optionally, after the step of verifying whether the first target step code is successfully executed according to a preset verification method, and outputting the execution result of the first target step code, the method further includes:

If the execution result shows that the execution of the first target step code fails, receiving the modified first target step code input by the user to update the first target step code;

Execute the modified first target step code, and return to executing the step of verifying whether the first target step code is successfully executed according to the preset verification method, and outputting the execution result of the first target step code , until the modified first target step code is successfully executed.

Optionally, after the step of verifying whether the first target step code is successfully executed according to a preset verification method, and outputting the execution result of the first target step code, the method further includes:

If the execution result shows that the first target step code is successfully executed, the step code to be judged in the current test case is obtained as the second target step code, and it is judged whether the second target step code is executable, Wherein, the to-be-determined step code is the next step code of the successfully executed first target step code.

Optionally, before the step of adding the first target step code to a preset blocking queue and judging whether the first target step code is executable, the method further includes:

Create and cyclically monitor the blocking queue to determine whether the blocking queue is empty;

If the blocking queue is empty, perform the steps of: adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable.

Optionally, after the step of creating and cyclically monitoring the blocking queue, and judging whether the blocking queue is full, the method further includes:

If the blocking queue is not empty, wait for the execution of the existing step code in the blocking queue to complete, and execute the steps: add the first target step code to the preset blocking queue, and determine the first target step Whether the code is executable.

Optionally, before the step of creating and cyclically monitoring the blocking queue and judging whether the blocking queue is empty, the method further includes:

Establish a connection with the browser, generate a time domain session, and obtain the ID value of the time domain session, so as to display the running process of the step code in the browser;

The ID value is added to the uniform resource locator of the current test case, and according to the uniform resource locator, the step code debugging page of the browser is acquired and displayed.

Optionally, after the step of adding the first target step code to a preset blocking queue and judging whether the first target step code is executable, the method further includes:

If the first target step code is not executable, generating and displaying the non-executable prompt information corresponding to the first target step code, so as to prompt the user that the first target step code is preset to be unexecutable;

Delete the first target step code from the blocking queue, and obtain the to-be-executed step code in the current test case as the third target step code, wherein the to-be-executed step code is the non-executable step code. The next step code of a target step code;

Adding the third target step code to the blocking queue, and determining whether the third target step code is executable.

According to the above test case debugging method, the test case debugging method further includes: if it is detected that all executable step codes in the current test case have been successfully executed, generating and displaying the debugging completion information of the current test case .

In addition, in order to achieve the above purpose, the present invention also provides a test case debugging device, and the test case debugging device includes:

The target code determination module is used to determine the first target step code in the current test case based on the relevant parameters in the use case debugging instruction when receiving the use case debugging instruction, wherein the relevant parameters at least include the operation type parameter and the page element positioning path;

A target code judgment module, for adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable;

a target code execution module, configured to acquire and execute the first target step code from the blocking queue if the first target step code is executable;

The target code verification module is configured to verify whether the first target step code is successfully executed according to a preset verification method, and output the execution result of the first target step code.

Optionally, the test case debugging device further includes:

a target code modification module, configured to receive the modified first target step code input by the user if the execution result shows that the first target step code fails to be executed, so as to update the first target step code;

The target code debugging module is used to execute the modified first target step code, and return to execute the according to the preset verification method, verify whether the first target step code is successfully executed, and output the first target Steps of the execution result of the step code until the modified first target step code is executed successfully.

Optionally, the test case debugging device further includes:

A code acquisition and judgment module, configured to acquire the to-be-judged step code in the current test case as the second target step code, and judge the second target step code if the execution result shows that the first target step code is successfully executed. Whether the target step code is executable, wherein the to-be-determined step code is the next step code of the successfully executed first target step code.

Optionally, the target code execution module is also used for:

Create and cyclically monitor the blocking queue to determine whether the blocking queue is empty;

If the blocking queue is empty, perform the steps of: adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable.

Optionally, the target code execution module is also used for:

If the blocking queue is not empty, wait for the execution of the existing step code in the blocking queue to complete, and execute the steps: add the first target step code to the preset blocking queue, and determine the first target step Whether the code is executable.

Optionally, the test case debugging device further includes:

a time domain session generation module, used to establish a connection with a browser, generate a time domain session, and obtain the ID value of the time domain session, so as to display the running process of the step code in the browser;

A debugging page obtaining module, configured to add the ID value to the uniform resource locator of the current test case, and obtain and display the step code debugging page of the browser according to the uniform resource locator.

In addition, in order to achieve the above object, the present invention also provides a test case debugging device, the test case debugging device includes: a memory, a processor, and a test case debugging device stored on the memory and running on the processor A program, when the test case debugging program is executed by the processor, implements the steps of the above test case debugging method.

In addition, in order to achieve the above object, the present invention also provides a computer-readable storage medium, where a test case debugging program is stored on the computer-readable storage medium, and when the test case debugging program is executed by a processor, the above-mentioned Steps of the test case debugging method.

The present invention provides a test case debugging method, device and computer-readable storage medium. The test case debugging method determines the first target step code in the current test case based on the relevant parameters in the use case debugging instruction when receiving the use case debugging instruction; adding the first target step code to the preset Block the queue, and determine whether the first target step code is executable; if the first target step code is executable, acquire and execute the first target step code from the blocking queue. Through the above method, the present invention determines the first target step code in the use case according to the relevant parameters, so that the tester can accurately locate any step in the current test case, and the user experience is improved; by putting the first target step code in the test case Block the queue, so that the first target step code is currently executed preferentially, avoiding the situation of other step codes being interrupted for execution; by judging whether the first target step code is executable, the tester can set some step codes to skip in advance, reducing the When the step code is executed, by executing the executable first target step code, the tester can debug the first target step code, which improves the debugging efficiency, thereby solving the problem of low debugging efficiency in the debugging process of the entire use case. technical problem.

Description of drawings

1 is a schematic diagram of a device structure of a hardware operating environment involved in an embodiment of the present invention;

FIG. 2 is a schematic flowchart of the first embodiment of the test case debugging method of the present invention;

FIG. 3 is a schematic diagram of a detailed flow chart of the steps of the first embodiment of the present invention in FIG. 2 .

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

Detailed ways

It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

As shown in FIG. 1 , FIG. 1 is a schematic diagram of an apparatus structure of a hardware operating environment involved in the solution of an embodiment of the present invention.

The device for debugging a test case in the embodiment of the present invention may be a PC or a server device, on which a Java virtual machine runs.

As shown in FIG. 1 , the test case debugging apparatus may include: a processor 1001 , such as a CPU, a network interface 1004 , a user interface 1003 , a memory 1005 , and a communication bus 1002 . Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (eg, a WI-FI interface). The memory 1005 may be high-speed RAM memory, or may be non-volatile memory, such as disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Those skilled in the art can understand that the structure shown in FIG. 1 does not constitute a limitation to the present solution, and may include more or less components than the one shown, or combine some components, or arrange different components.

As shown in FIG. 1 , the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a test case debugging program.

In the device shown in FIG. 1 , the network interface 1004 is mainly used to connect to the background server and perform data communication with the background server; the user interface 1003 is mainly used to connect the client (client) and perform data communication with the client; and the processor 1001 can be used to call the test case debugging program stored in the memory 1005, and perform the operations in the test case debugging method described below.

Based on the above hardware structure, an embodiment of the test case debugging method of the present invention is proposed.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of the first embodiment of the test case debugging method of the present invention. The test case debugging method includes:

Step S10, when receiving the use case debugging instruction, determine the first target step code in the current test case based on the relevant parameters in the use case debugging instruction, wherein the relevant parameters at least include the operation type parameter and the page element positioning path ;

Currently, when a tester debugs a program, usually after writing a test case, he executes the entire use case to verify that the steps of the use case are accurate. If there is an error step, the tester needs to repeat the execution of the entire use case after modifying the error step, and judge whether the modified step can be executed successfully until the entire use case is successfully executed. In the process of locating and analyzing the problem in the use case, the tester needs to execute the use case repeatedly. In fact, most of the steps executed are not helpful for the localization and analysis of the problem. Only a few key steps can reproduce the problem, which leads to It solves the problem of low debugging efficiency in the debugging process of the entire use case. For example, when a tester executes a UI automation test case that includes 10 steps of code, after the test case is executed for the first time, the result of the first execution shows that the code of the third step reports an error. The tester made the first modification to the code of the third step, and then executed the test case for the second time, and found that the code of the third step after the first modification still reported an error. After the tester made the fifth modification to the code of the third step, and executed the entire test case for the fifth time, it was found that the result of the fifth execution showed that the code of the third step was executed successfully, but the code of the seventh step began to report an error. The above specific problems show that the efficiency of the entire debugging process is very low by repeatedly executing the entire use case of multiple vehicles in order to modify the successful single-step code.

In this embodiment, in order to solve the above problems, the present invention provides a test case debugging method, that is, according to relevant parameters, the first target step code in the test case is determined, so that the tester can accurately locate any one of the current test cases. step, the user experience is improved; by putting the first target step code into the blocking queue, the first target step code is currently executed preferentially, avoiding the situation of other step codes interrupting the execution of the queue; by judging whether the first target step code is executable, The tester can set some step codes to skip in advance, which reduces the time for executing the step code. By executing the executable first target step code, the tester can debug the first target step code, which improves the debugging efficiency. , so as to solve the technical problem of low debugging efficiency in the debugging process of the entire use case. The test case debugging method is applied to the server side and the user side, and the producer-consumer mode is adopted to realize the test case debugging method through two threads of the producer and the consumer and a blocking queue. The producer-consumer pattern is a design pattern. The producer and the consumer share the same storage space in the same time period. The producer adds products to the storage space, and the consumer removes the product from the storage space. When the storage space is empty, the consumer blocks; when the storage space is full , the producer blocks. In the present invention, two threads of the producer and the consumer share a blocking queue. The producer thread adds the step code to the blocking queue, and the consumer thread takes the step code from the blocking queue and executes it. Specifically, the use case debugging command includes a debugging start command and a step selection command. The debugging start command is an command to enable the debugging mode, and the step selection command is an command for the tester to select a certain step code in the current test case. The tester clicks to start debugging on the code debugging page of the client, and sets the debugging mode to true. The client receives the debugging start command triggered by the tester and starts the debugging mode. The tester starts the user browser on the server on the client side, the client side initiates a time domain session session request to the server side, the server side receives the session request, and stores the session session, so that the user browser and the client side can communicate with each other. Maintain this Session session. The user terminal detects the test case currently ready to be debugged, and obtains the Uniform Resource Locator (URL, Uniform Resource Locator) of the current test case. According to this URL, the client opens the browser page corresponding to the current test case. The client starts the debug executor and determines the first target step code in the current test case. Wherein, the first target step code is the step code that needs to be debugged currently. If other step codes exist before the first target step code in the current test case, the first target step code is not associated with other step codes. The user terminal receives the step selection instruction, and according to the above-mentioned relevant parameters, determines the first target step code corresponding to the above-mentioned relevant parameters in the current test case. Among them, the relevant parameters include at least the operation type parameter of the first target step code, the path of the page element positioning, and can also include the input value and variable corresponding to the first target step code, and the operation type parameter can be delay, click, mouse hover Wait. The method for determining the first target step code can be that the tester manually adds the relevant parameters corresponding to the first target step code on the step code related parameter page, or the user terminal jumps from the previous step code to the first step code according to the automatic jump rule. When there is a target step, the relevant parameters corresponding to the code of the first target step are directly obtained. In a specific embodiment, if the first target step code is the fourth step code in the current test case, the tester enters the operation type parameter "mouseover" corresponding to the fourth step code in the debugging page of the browser, and the positioning path "/ /div[@class="menu-root"]/div" and the input value "3", the user terminal can determine the fourth step code in the current test case according to the three parameters input by the tester.

Step S20, adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable;

In this embodiment, the client obtains the first target step code from the current test case, and adds the first target step code to the preset blocking queue. Among them, the blocking queue is a queue that supports two additional operations on the basis of the queue. When the queue is full, the queue blocks the producer thread until the queue is full; when the queue is empty, the consumer thread waits for the queue to become non-empty. The blocking queue is just suitable for the stored queue, and the step code for executing the debugging is stored in the queue. The user terminal determines whether the first target step code is executable code. Specifically, the user terminal presets a skip field in the local database, and judges whether the first target step code is an executable step code according to whether there is a skip field in the first target step. In the above process, the producer thread is used to add the acquired first target step code to the blocking queue.

Step S30, if the first target step code is executable, obtain and execute the first target step code from the blocking queue;

In this embodiment, if the client determines that the first target step code is executable code, the client obtains the first target step code from the blocking queue, and drives the server to execute the first target through the debug executor in the current debugging mode. step code. Among them, the debug executor is a module that executes the use case step code in debug mode. The specific judgment situation may be: if there is no skip field in the first target step code, the user terminal determines that the first target step code is executable code. During the execution process, the browser synchronously displays the relevant operations of the code of the first target step, such as clicking a button, entering a user name, and the like. The server side records the log and execution result of executing the code of the first target step, and intercepts and saves a screenshot of the page of the execution process of the code of the first target step. In the above process, the consumer thread is used to obtain and execute the first target step code from the blocking queue.

Step S40 , according to a preset verification method, verify whether the first target step code is successfully executed, and output the execution result of the first target step code.

In this embodiment, the tester selects one or more verification methods from the preset verification methods before the code of the first target step is executed, and the user terminal receives the verification method selection instruction triggered by the tester, according to the The selected verification method verifies whether the first target step code is successfully executed, and outputs the execution result of the first target step code on the page. Wherein, the preset verification method may be: using an image recognition algorithm, judging whether the screenshot of the execution page of the first target step matches the preset picture; judging whether the page element value corresponding to the code of the first target step matches the preset value ; Check the markup attribute of the page element corresponding to the first target step code through the interface provided by the driver software Selenium WebDriver in the selenium element framework web page, and determine whether the page element is editable; determine whether the page element value corresponding to the first target step code contains a preset characters, etc. Specifically, the user side checks whether the editable attribute value of the page element corresponding to the first target step code is true through the interface provided by the Selenium WebDriver framework. In the above process, the consumer thread is used to judge whether the first target step code is successfully executed.

The present invention provides a test case debugging method, device and computer-readable storage medium. The test case debugging method determines the first target step code in the current test case based on the relevant parameters in the use case debugging instruction when receiving the use case debugging instruction, wherein the relevant parameters at least include an operation type parameter and an operation type parameter. page element positioning path; add the first target step code to the preset blocking queue, and determine whether the first target step code is executable; if the first target step code is executable, from the blocking queue Acquire and execute the first target step code in the system; verify whether the first target step code is successfully executed according to a preset verification method, and output the execution result of the first target step code. Through the above method, the present invention determines the first target step code in the use case according to the relevant parameters, so that the tester can accurately locate any step in the current test case, and the user experience is improved; by putting the first target step code in the test case Block the queue, so that the first target step code is currently executed preferentially, avoiding the situation of other step codes being interrupted for execution; by judging whether the first target step code is executable, the tester can set some step codes to skip in advance, reducing the When the step code is executed, by executing the executable first target step code, the tester can debug the first target step code, which improves the debugging efficiency; by judging the execution of the first target step code, and outputting The corresponding execution result enables the tester to directly obtain the execution result of the code of the first target step without spending time executing other steps in the current embodiment, which improves the debugging efficiency of the tester and thus solves the problem of the entire use case. Debugging technical problems with low efficiency during debugging.

Referring to FIG. 3 , FIG. 3 is a schematic diagram of a refinement process according to the first embodiment of the present invention.

Based on the first embodiment shown in FIG. 2 above, a second embodiment of the test case debugging method of the present invention is proposed. In this embodiment, after the step S40, it further includes:

Step S50, if the execution result shows that the execution of the first target step code fails, receive the modified first target step code input by the user to update the first target step code;

In this embodiment, the client maintains the connection with the server through the time domain session identification code SessionID, and the server displays the execution result corresponding to the first target step code on the browser page. After judging that the execution of the first target step code fails according to the preset verification method, the user terminal modifies the first target step code on the page of the browser. The client saves the relevant modified data to the local database. The modified first target step code may be the first target step code that the tester re-edited on the browser page in real time; or after adding a new step code before the first target step code, the new step The combination of the code and the first target step code.

Step S60, execute the modified first target step code, and return to execute the pre-set verification method to verify whether the first target step code is successfully executed, and output the execution of the first target step code The resulting steps until the modified first target step code is executed successfully.

In this embodiment, the debugging module drives the server to execute the modified first target step code through the connection between the server and the client maintained by the SessionID. The server side displays the execution process and result of the modified first target step code on the page of the browser. If the execution result of the code of the first target step after the first modification still shows that the execution fails, the tester will modify the code of the first target step again and execute it until the code of the first target step that has been modified several times can be successfully executed and output Execute successful result. Wherein, the modified first target code may be the first target step code after modification once, or may be the first target step code after modification multiple times. The target step code must be the modified first target step code to run successfully.

Further, after step S40, it also includes:

Step S01, if the execution result shows that the first target step code is successfully executed, obtain the to-be-determined step code in the current test case as the second target step code, and determine whether the second target step code is not. Executable, wherein the to-be-determined step code is the next step code of the successfully executed first target step code.

In this embodiment, the client maintains the connection with the server through the SessionID, and the server displays the execution result corresponding to the code of the first target step on the browser page. If the client determines that the code of the first target step is successfully executed according to the preset verification method, and the debugging page of the server side synchronously displays the result of the successful execution of the code of the first target step, the debugging of the first target step is completed. The client obtains the to-be-determined step code in the current test case as the second target step code. The second target step code is the next step code of the successfully executed first target step code in the current test case. In this embodiment, the consumer thread is used to drive the server to display the execution result of the first target step code and execute the modified first target step code.

The present invention provides a test case debugging method, device and computer-readable storage medium. The test case debugging method further enables the tester to complete the debugging of the first target step code independently by passing the first target step code that fails to be executed until the debugging is successful, thereby improving the debugging efficiency and improving the user experience; After the first target step code is successfully executed, it automatically jumps to the next step, which simplifies the tester's operation and improves the user experience.

Not shown in the figure, based on the first embodiment shown in FIG. 2 above, a third embodiment of the test case debugging method of the present invention is proposed.

In this embodiment, before step S20, it further includes:

Step a, creating and cyclically monitoring the blocking queue, and judging whether the blocking queue is empty;

In this embodiment, the client creates a blocking queue, and cyclically monitors the blocking queue. The client determines whether the step code in this blocking queue is empty. Among them, the step code storage space of the blocking queue is preset so that only one step code can be added at a time. In a specific embodiment, in order to determine whether the blocking queue is empty, the user terminal will generate a corresponding return value whenever step codes in the blocking queue are added or deleted. The user terminal determines whether the current return value matches the preset return value according to the obtained current return value.

Step b, if the blocking queue is empty, perform the steps of: adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable.

In this embodiment, if the user terminal obtains the information that the step code in the above-mentioned blocking queue is empty after judgment, the user terminal adds the first target step code to the above-mentioned blocking queue, and judges the first target step Whether the code is executable. In a specific embodiment, if the current return value matches the preset return value, the user terminal determines that the step code in the blocking queue is empty.

Step c, if the blocking queue is not empty, wait for the execution of the existing step code in the blocking queue to be completed, and execute the step: add the first target step code to the preset blocking queue, and determine the first target step code. Whether a target step code is executable.

In this embodiment, if the user terminal obtains the information that the step code in the blocking queue is not empty after judgment, the user terminal waits for the original step code in the blocking queue to be fetched and executed. After the debugging of the original step code is completed, the user terminal determines whether the current blocking queue is empty. Since the blocking queue is preset so that only one step code can be cached, and the original step code has been obtained and executed, the client obtains the information that the current blocking queue is empty. The client adds the first target step code to the currently empty blocking queue, and determines whether the first step code is executable.

Further, in this embodiment, before step a, it also includes:

Step d, establish a connection with the browser, generate a time domain session, and obtain the ID value of the time domain session, so as to display the running process of the step code in the browser;

In this embodiment, the tester starts the user browser on the server, the client initiates a time-domain session session request to the server, and the server receives the session request, obtains and stores the SessionID corresponding to the session request, so as to pass the session request. This SessionID maintains the connection between the user's browser on the client side and the server side, drives the browser in the server to execute the step code and displays the running process of the step code.

Step e, adding the ID value to the uniform resource locator of the current test case, and acquiring and displaying the step code debugging page of the browser according to the uniform resource locator.

In this embodiment, the user terminal detects the test case currently to be debugged, and obtains the Uniform Resource Locator (URL, Uniform Resource Locator) of the current test case. The client adds this ID value to the URL of the current test case, and according to this URL, obtains the step code debugging page corresponding to the current test case. In this embodiment, the consumer thread is used to cyclically monitor the blocking queue.

The present invention provides a test case debugging method, device and computer-readable storage medium. The test case debugging method further monitors whether the blocking queue is empty, and only waits for the blocking queue to be empty again when the blocking queue is full, and then puts the first target step code, so that the current test case can only be executed independently The first target step code avoids the interference of the step code outside the blocking queue; maintains the connection with the server through the ID value in the time domain session, so that the single step code will not be disconnected immediately after the execution fails, but can be continuously modified And execute the code of this step until the debugging is successful, which improves the debugging efficiency.

Not shown in the figure, based on the first embodiment shown in FIG. 2 above, a fourth embodiment of the test case debugging method of the present invention is proposed.

In this embodiment, after step S20, it further includes:

Step f, if the first target step code is not executable, generate and display the non-executable prompt information corresponding to the first target step code, so as to prompt the user that the first target step code is preset to be unexecutable;

In this embodiment, if the user terminal determines that the first target step code is an unexecutable code, it generates unexecutable prompt information corresponding to the first target step code. In a specific embodiment, if the first target step code is considered by the tester as a skippable step, and before debugging the current test case, the first target step code is added to the non-executable field, then the client obtains the code from the blocking queue. When the first target step is reached, this non-executable field is detected, and corresponding non-executable prompt information is generated and displayed to the tester. From this prompt message, the tester can know that the first target step code is a skippable step code.

Step g, delete the first target step code from the blocking queue, and obtain the to-be-executed step code in the current test case as the third target step code, wherein the to-be-executed step code is unavailable. the next step code of the executed first target step code;

In this embodiment, the user terminal deletes the first target step code from the blocking queue, and obtains the third target step code in the current test case. Wherein, the third target step code is the next step code of the unexecutable first target step code in the current test case. The above process is to automatically execute the next step code in sequence after skipping the first target step code.

Step h, adding the third target step code to the blocking queue, and determining whether the third target step code is executable.

In this embodiment, before adding the third target step code to the blocking queue, the client first determines whether the blocking queue is full, if not, the client adds the third step code to the blocking queue; if it is full, then When the user terminal waits for the blocking queue to be less than full, it adds the third step code to the blocking queue, and judges whether the third target step code is executable.

Further, the test case debugging method of the present invention also includes:

In step i, if it is detected that all executable step codes in the current test case have been successfully executed, the debugging completion information of the current test case is generated and displayed.

In this embodiment, when the user terminal detects that all the preset settings in the current test case are executable, the corresponding debugging completion information is generated and displayed to the tester. The specific detection method can be: adding an identification field to the last step code of the current test case in advance, if the user side detects the identification field in the blocking queue and receives the execution success information or unexecutable information of the last step code to generate and display the debugging completion information corresponding to the current test case. After step S1, the tester sees the debugging completion information and knows that the current test case has been successfully executed, clicks to end debugging, sets the debugging mode to false, and closes the browser. The client exits the current debug mode and closes the above session.

The present invention provides a test case debugging method, device and computer-readable storage medium. The test case debugging method further improves the user experience by displaying the unexecutable prompt information to the user, so that the user knows that the code of this step is set to be skipped before, and the user experience is improved; by automatically jumping to the next step when the code of the first target step is not executable. Step code that simplifies the operation of the tester.

The present invention also provides a test case debugging device, and the test case debugging device includes:

The target code determination module is used to determine the first target step code in the current test case based on the relevant parameters in the use case debugging instruction when receiving the use case debugging instruction, wherein the relevant parameters at least include the operation type parameter and the page element positioning path;

A target code judgment module, for adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable;

a target code execution module, configured to acquire and execute the first target step code from the blocking queue if the first target step code is executable;

The target code verification module is configured to verify whether the first target step code is successfully executed according to a preset verification method, and output the execution result of the first target step code.

The test case debugging device further includes:

a target code modification module, configured to receive the modified first target step code input by the user if the execution result shows that the first target step code fails to be executed, so as to update the first target step code;

The target code debugging module is used to execute the modified first target step code, and return to execute the according to the preset verification method, verify whether the first target step code is successfully executed, and output the first target Steps of the execution result of the step code until the modified first target step code is executed successfully.

The test case debugging device further includes:

A code acquisition and judgment module, configured to acquire the to-be-judged step code in the current test case as the second target step code if the execution result shows that the first target step code is successfully executed, and judge the Whether the second target step code is executable, wherein the to-be-determined step code is the next step code of the successfully executed first target step code.

The target code execution module is also used for:

Create and cyclically monitor the blocking queue to determine whether the blocking queue is empty;

If the blocking queue is empty, perform the steps of: adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable.

The target code execution module is also used for:

If the blocking queue is not empty, wait for the execution of the existing step code in the blocking queue to complete, and execute the steps: add the first target step code to the preset blocking queue, and determine the first target step Whether the code is executable.

The test case debugging device further includes:

a time domain session generation module, used to establish a connection with a browser, generate a time domain session, and obtain the ID value of the time domain session, so as to display the running process of the step code in the browser;

A debugging page obtaining module, configured to add the ID value to the uniform resource locator of the current test case, and obtain and display the step code debugging page of the browser according to the uniform resource locator.

The test case debugging device further includes an information prompt module, and the information prompt module is used for:

If the first target step code is not executable, generating and displaying the non-executable prompt information corresponding to the first target step code, so as to prompt the user that the first target step code is preset to be unexecutable;

Delete the first target step code from the blocking queue, and obtain the to-be-executed step code in the current test case as the third target step code, wherein the to-be-executed step code is the non-executable step code. The next step code of a target step code;

Adding the third target step code to the blocking queue, and determining whether the third target step code is executable.

The test case debugging device further includes:

The detection unit is configured to generate and display debugging completion information of the current test case if it is detected that all executable step codes in the current test case have been successfully executed.

For the methods executed by the above program modules, reference may be made to the various embodiments of the service exception handling method of the present invention, which will not be repeated here.

The present invention also provides a computer-readable storage medium.

A test case debugging program is stored on the computer-readable storage medium of the present invention, and when the test case debugging program is executed by the processor, the steps of the above-mentioned test case debugging method are implemented.

Wherein, for the method implemented when the test case debugging program is executed, reference may be made to the various embodiments of the test case debugging method of the present invention, which will not be repeated here.

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or system comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or system. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article or system that includes the element.

The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages or disadvantages of the embodiments.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on such understanding, the technical solutions of the present invention can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products are stored in a storage medium (such as ROM/RAM) as described above. , magnetic disk, optical disk), including several instructions to make a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present invention.

The above are only preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present invention, or directly or indirectly applied in other related technical fields , are similarly included in the scope of patent protection of the present invention.

Claims (16)

1. a test case debugging method, is characterized in that, described test case debugging method comprises: When receiving the use case debugging instruction, determine the first target step code in the current test case based on the relevant parameters in the use case debugging instruction, wherein the relevant parameters at least include the operation type parameter and the page element positioning path; adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable; If the first target step code is executable, obtain and execute the first target step code from the blocking queue; According to the preset verification method, verify whether the first target step code is successfully executed, and output the execution result of the first target step code. 2. The test case debugging method according to claim 1, wherein, according to a preset verification method, verifying whether the first target step code is executed successfully, and outputting the execution of the first target step code After the resulting steps, also include: If the execution result shows that the execution of the first target step code fails, receiving the modified first target step code input by the user to update the first target step code; Execute the modified first target step code, and return to executing the step of verifying whether the first target step code is successfully executed according to the preset verification method, and outputting the execution result of the first target step code , until the modified first target step code is successfully executed. 3. The test case debugging method according to claim 1, wherein, according to a preset verification method, verifying whether the first target step code is successfully executed, and outputting the execution of the first target step code After the resulting steps, also include: If the execution result shows that the first target step code is successfully executed, the step code to be judged in the current test case is obtained as the second target step code, and it is judged whether the second target step code is executable, Wherein, the to-be-determined step code is the next step code of the successfully executed first target step code. 4. The test case debugging method according to claim 1, wherein before the step of adding the first target step code to a preset blocking queue and judging whether the first target step code is executable ,Also includes: Create and cyclically monitor the blocking queue to determine whether the blocking queue is empty; If the blocking queue is empty, perform the steps of: adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable. 5. The test case debugging method according to claim 4, wherein after the step of creating and cyclically monitoring the blocking queue, and judging whether the blocking queue is full, the method further comprises: If the blocking queue is not empty, wait for the execution of the existing step code in the blocking queue to complete, and execute the steps: add the first target step code to the preset blocking queue, and determine the first target step Whether the code is executable. 6. The test case debugging method according to claim 4, wherein before the step of creating and cyclically monitoring the blocking queue and judging whether the blocking queue is empty, the method further comprises: Establish a connection with the browser, generate a time domain session, and obtain the ID value of the time domain session, so as to display the running process of the step code in the browser; The ID value is added to the uniform resource locator of the current test case, and according to the uniform resource locator, the step code debugging page of the browser is acquired and displayed. 7. The test case debugging method according to claim 1, wherein after the step of adding the first target step code to a preset blocking queue and judging whether the first target step code is executable ,Also includes: If the first target step code is not executable, generating and displaying the non-executable prompt information corresponding to the first target step code, so as to prompt the user that the first target step code is preset to be unexecutable; Delete the first target step code from the blocking queue, and obtain the to-be-executed step code in the current test case as the third target step code, wherein the to-be-executed step code is the non-executable step code. The next step code of a target step code; Adding the third target step code to the blocking queue, and determining whether the third target step code is executable. 8. The test case debugging method according to any one of claims 1-7, wherein the test case debugging method further comprises: If it is detected that all executable step codes in the current test case have been successfully executed, the debugging completion information of the current test case is generated and displayed. 9. A test case debugging device, wherein the test case debugging device comprises: The target code determination module is used to determine the first target step code in the current test case based on the relevant parameters in the use case debugging instruction when receiving the use case debugging instruction, wherein the relevant parameters at least include the operation type parameter and the page element positioning path; A target code judgment module, for adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable; a target code execution module, configured to acquire and execute the first target step code from the blocking queue if the first target step code is executable; The target code verification module is configured to verify whether the first target step code is successfully executed according to a preset verification method, and output the execution result of the first target step code. 10. The test case debugging device according to claim 9, wherein the test case debugging device further comprises: a target code modification module, configured to receive the modified first target step code input by the user if the execution result shows that the first target step code fails to be executed, so as to update the first target step code; The target code debugging module is used to execute the modified first target step code, and return to execute the according to the preset verification method, verify whether the first target step code is successfully executed, and output the first target Steps of the execution result of the step code until the modified first target step code is executed successfully. 11. The test case debugging device according to claim 9, wherein the test case debugging device further comprises: A code acquisition and judgment module, configured to acquire the to-be-judged step code in the current test case as the second target step code, and judge the second target step code if the execution result shows that the first target step code is successfully executed. Whether the target step code is executable, wherein the to-be-determined step code is the next step code of the successfully executed first target step code. 12. The test case debugging device according to claim 9, wherein the target code execution module is further used for: Create and cyclically monitor the blocking queue to determine whether the blocking queue is empty; If the blocking queue is empty, perform the steps of: adding the first target step code to a preset blocking queue, and judging whether the first target step code is executable. 13. The test case debugging device according to claim 12, wherein the target code execution module is further used for: If the blocking queue is not empty, wait for the execution of the existing step code in the blocking queue to complete, and execute the steps: add the first target step code to the preset blocking queue, and determine the first target step Whether the code is executable. 14. The test case debugging device according to claim 12, wherein the test case debugging device further comprises: a time domain session generation module, used to establish a connection with a browser, generate a time domain session, and obtain the ID value of the time domain session, so as to display the running process of the step code in the browser; A debugging page obtaining module, configured to add the ID value to the uniform resource locator of the current test case, and obtain and display the step code debugging page of the browser according to the uniform resource locator. 15. A test case debugging device, characterized in that the test case debugging device comprises: a memory, a processor, and a test case debugging program stored on the memory and running on the processor, the test case debugging program The test case debugging method according to any one of claims 1 to 8 is implemented when the use case debugging program is executed by the processor. 16. A computer-readable storage medium, characterized in that, a test case debugging program is stored on the computer-readable storage medium, and when the test case debugging program is executed by the processor, any one of claims 1 to 8 is implemented. The steps of the test case debugging method described in item.