CN117453561A - Test script calling method, device, computer equipment and storage medium - Google Patents

Abstract

The present application relates to a test method, device, computer equipment and storage medium for test cases. When a test request exists, in response to the test request of the test case, if it is determined that the verification rule of the test case has changed according to the test request, select a target event that matches the new verification rule after the change from the candidate event script script; and determine the target test script based on the general test script and target event script of the test case; and run the target test script to test the test case. By encoding the verification rules for verifying test cases into corresponding event scripts, and when the verification rules for test cases change, by determining the event script corresponding to the new verification rules, and determining the target test with the general test script Compared with the hard-coding method in the existing technology, the script does not need to repeatedly modify the program code when the verification rules are changed, thereby improving the testing efficiency of the test cases.

Description

Test script calls methods, devices, computer equipment and storage media

Technical field

The present application relates to the field of computer technology, and in particular to a test script calling method, device, computer equipment and storage medium.

Background technique

A test case is a detailed normative document used to test the functionality of a software application or system. It consists of a set of steps, input data, expected results, and possible pre- and post-conditions to verify that a specific functionality works as required. Normally, after a test case is designed, the tester performs the test step by step according to the process described in the test case, obtains the actual results, and compares the actual results with the expected results. In order to improve testing efficiency, automatic testing of different test cases can be implemented through hard coding.

However, the verification rule requirements for different devices and different test cases are inconsistent, hard-coded development is complex, and the workload is large. When the test case verification rules change, the program code needs to be modified repeatedly, making the test case testing inefficient.

Contents of the invention

Based on this, it is necessary to provide a test case testing method, device, computer equipment and storage medium to address the above technical problems, which can improve the testing efficiency of test cases.

In the first aspect, this application provides a test case testing method, which method includes:

In response to the test request of the test case, if it is determined that the verification rule of the test case has been changed according to the test request, selecting a target event script that matches the changed new verification rule from the candidate event scripts;

Determine a target test script according to the general test script of the test case and the target event script;

Run the target test script to test the test case.

In one embodiment, determining that the verification rules of the test case have changed based on the test request includes:

Extract target test requirements from the test request;

If the target test requirement is inconsistent with the original test requirement of the test case, it is determined that the verification rule for the test case has been changed.

In one embodiment, selecting a target event script that matches the changed new verification rule from the candidate event scripts includes:

Construct a target event according to the target test requirements; wherein the target event includes a target event identifier and a changed new verification rule;

Based on the correspondence between the candidate event identifier and the candidate event script, a target event script in the candidate event script that matches the changed new verification rule is determined according to the target event identifier.

In one embodiment, selecting a target event script that matches the changed new verification rule from the candidate event scripts includes:

If there is no target event script matching the changed new verification rules among the candidate event scripts, the script generation interface will be displayed to the test demand side;

Generate a target event script matching the new verification rule according to the input operation performed by the test demand side on the script generation interface.

In one embodiment, selecting a target event script that matches the changed new verification rule from the candidate event scripts includes:

If there is no target event script in the candidate event script that matches the new verification rule after the change, the general event script is updated according to the target test requirements in the test request to obtain the event script that matches the new verification rule. Target event script.

In one embodiment, when the number of new verification rules is at least two, the method further includes:

According to the execution sequence between the target event scripts corresponding to each new verification rule, the test results of the test cases are summarized, and the summarized test results are displayed to the test demand side.

In a second aspect, this application also provides a test device for test cases, and the device includes:

a selection module, configured to respond to a test request of the test case, and select a new verification rule from the candidate event script that matches the changed new verification rule when it is determined according to the test request that the verification rule of the test case has changed. target event script;

A determination module, configured to determine a target test script based on the general test script of the test case and the target event script;

A running module is used to run the target test script to test the test case.

In a third aspect, this application also provides a computer device. The computer device includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, it implements the following steps:

In response to the test request of the test case, if it is determined that the verification rule of the test case has been changed according to the test request, selecting a target event script that matches the changed new verification rule from the candidate event scripts;

Determine a target test script according to the general test script of the test case and the target event script;

Run the target test script to test the test case.

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer-readable storage medium has a computer program stored thereon. When the computer program is executed by a processor, the following steps are implemented:

In response to the test request of the test case, if it is determined that the verification rule of the test case has been changed according to the test request, selecting a target event script that matches the changed new verification rule from the candidate event scripts;

Determine a target test script according to the general test script of the test case and the target event script;

Run the target test script to test the test case.

In a fifth aspect, this application also provides a computer program product. The computer program product includes a computer program. When the computer program is executed by a processor, the following steps are implemented:

In response to the test request of the test case, if it is determined that the verification rule of the test case has been changed according to the test request, selecting a target event script that matches the changed new verification rule from the candidate event scripts;

Determine a target test script according to the general test script of the test case and the target event script;

Run the target test script to test the test case.

The test method, device, computer equipment and storage medium of the above-mentioned test case, when there is a test request, respond to the test request of the test case, and when it is determined that the verification rules of the test case are changed according to the test request, from the candidate event Select the target event script in the script that matches the changed new verification rule; determine the target test script based on the general test script and target event script of the test case; and then run the target test script to test the test case. By encoding the verification rules for verifying test cases into corresponding event scripts, and when the verification rules for test cases change, by determining the event script corresponding to the new verification rules, and determining the target test with the general test script Compared with the hard-coding method in the existing technology, the script does not need to repeatedly modify the program code when the verification rules are changed, thereby improving the testing efficiency of the test cases.

Description of the drawings

Figure 1 is an application environment diagram of the test method of the test case in an embodiment;

Figure 2 is a schematic flow chart of a test method for test cases in an embodiment;

Figure 3 is a schematic flowchart of a method for determining a target event script that matches a new verification rule in one embodiment;

Figure 4 is a schematic flowchart of a method for generating a target event script in one embodiment;

Figure 5 is a schematic flow chart of a test method for test cases in another embodiment;

Figure 6 is a structural block diagram of a test device for a test case in an embodiment;

Figure 7 is a structural block diagram of a test device for a test case in another embodiment;

Figure 8 is an internal structure diagram of a computer device in one embodiment.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

The test case testing method provided by the embodiment of this application can be applied to the scenario of testing the test case. For example, FIG. 1 is an application environment diagram of a test method for test cases provided in the embodiment of the present application. Among them, the terminal 102 communicates with the server 104 through the network. For example, the terminal 102 sends a test request of a test case to the server 104. The server 104 responds to the test request of the test case, generates a target test script, tests the test case, and returns the test results to the terminal 102. The data storage system may store data that server 104 needs to process. The data storage system can be integrated on the server 104, or placed on the cloud or other network servers.

Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart vehicle-mounted devices, etc. . Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 104 can be implemented as an independent server or a server cluster composed of multiple servers. The server 104 may include a test system function module and a script test function module. The test system function module is used to manage a general test platform, for example, for test case addition control (change of test case data), user management (tester login verification) , test case management (adding test cases or modifying test cases, etc.), test case editing, transmitting test results to the terminal 102, etc.; the script test function module is used to call the corresponding test script, test the test cases, and send the test results Sent to test system.

In one embodiment, as shown in Figure 2, a test case testing method is provided. This method is explained by taking the method applied to the server 104 in Figure 1 as an example, and includes the following steps:

S201. In response to the test request of the test case, if it is determined that the verification rule of the test case has changed according to the test request, select a target event script that matches the new verification rule after the change from the candidate event scripts.

Optionally, a test case can be a detailed normative document used to test a software application or system function, which contains a set of steps, input data, expected results, and possible preconditions and postconditions to verify whether a specific function Operate normally as required. When there is a test requirement on the test demand side, a test case test request will be initiated. Verification rules can be understood as verification rules for the data involved in the test case to determine when the data involved in the test case meets the requirements. For example, the test case is to test the data collection accuracy of data collection channel 1, and the verification rule can be to verify whether the difference between the data collected by data collection channel 1 and the expected data is within the preset range. The target event script can be understood as the script file corresponding to the new validation rule.

The server 104 receives the test request, and in response to the test request of the test case, may first determine whether the verification rules for the test case have changed according to the test request. When it is determined that the verification rules of the test case are changed according to the test request, a target event script that matches the new verification rule after the change is selected from the candidate event scripts. It should be understood that the event script corresponding to each verification rule can be edited in advance, a one-to-one correspondence between each event script and each verification rule can be established, and a candidate event script can be generated. In this way, when the verification rules of the test case are changed, the target event script that matches the changed new verification rules can be selected from the candidate event scripts based on the correspondence between the test rules and the event scripts.

Optionally, according to the test request, determine whether the verification rules of the test case have changed. This can be achieved in the following ways:

First, target test requirements are extracted from the test request; among them, the target test requirements can include information such as test data for testing test cases, methods of obtaining test data, and rules for verifying test data. Then determine whether the target test requirements are consistent with the original test requirements of the test case. If the target test requirements are inconsistent with the original test requirements of the test case, it is determined that the verification rules of the test case have been changed.

S202: Determine the target test script according to the general test script and the target event script of the test case.

Optionally, a universal test script can be understood as a universal script file for testing test cases, that is, a test script that is needed to test each test case. The target event script is the script file corresponding to the new validation rule. The target test script can be understood as a script file used to test test cases. The test case's general test script and target event script can be called to determine the target test script.

S203: Run the target test script to test the test case.

After determining the target test script for testing the test script, run the target test script to complete the test of the test case, such as outputting the final test results.

The test method of the above test case, when there is a test request, responds to the test request of the test case, and when it is determined that the verification rules of the test case have been changed according to the test request, select a new one after the change from the candidate event script. Verify the target event script that matches the rule; determine the target test script based on the general test script and the target event script of the test case; and then run the target test script to test the test case. By encoding the verification rules for verifying test cases into corresponding event scripts, and when the verification rules for test cases change, by determining the event script corresponding to the new verification rules, and determining the target test with the general test script Compared with the hard-coding method in the existing technology, the script does not need to repeatedly modify the program code when the verification rules are changed, thereby improving the testing efficiency of the test cases.

In one embodiment, see Figure 3, which provides a schematic flowchart of a method for determining a target event script that matches a new verification rule, which specifically includes the following steps:

S301: Construct a target event according to the target test requirements.

Optionally, when there is a target test requirement, a target event can be constructed according to the target test requirement, where the target event includes the target event identifier and the changed new verification rule. For example, the target event is to test the accuracy of the collected data of data collection channel 1. The target event identifier can create an event for the event name and event; the new verification rule after the change can be used to verify whether the relative difference between the collected data of data collection channel 1 and the expected data is within 10%.

S302: Based on the correspondence between the candidate event identifier and the candidate event script, determine the target event script in the candidate event script that matches the changed new verification rule according to the target event identifier.

Optionally, a corresponding target event script can be generated in advance according to the target event, and a corresponding relationship is established with the target event according to the target event identifier, and then placed into the candidate event script together with other event scripts. In this way, based on the corresponding relationship between the candidate event identifier and the candidate event script, the target event script in the candidate event script that matches the changed new verification rule can be determined according to the target event identifier.

In the embodiment of the present application, through the target event identifier, the target event script in the candidate event script that matches the changed new verification rule can be quickly determined, so as to improve the testing efficiency of the test case.

Optionally, the target event script that matches the changed new verification rule may not exist in the candidate event scripts. In this case, the target event script can be generated to test the test case. In one embodiment, see Figure 4, which provides a schematic flowchart of a method for generating a target event script. Specifically, it includes the following steps:

S401. If there is no target event script matching the changed new verification rule in the candidate event script, display the script generation interface to the test demand side.

Optionally, if there is no target event script matching the new verification rule after the change among the candidate event scripts, the script generation interface is displayed to the test demand side. The script generation interface may include an event script similar to the target event script, so that the user can modify the event script through the test demand side to generate the target event script.

S402: Generate a target event script that matches the new verification rule according to the input operation on the script generation interface performed by the test demand side.

The user can operate the script generation interface through the test demand side, for example, modify a similar script file in the script generation interface. The server 104 can generate a new script based on the input operation on the script generation interface by the test demand side. Validation rules match the target event script.

In the embodiment of this application, when there is no target event script matching the changed new verification rule in the candidate event script, the script generation interface is displayed to the test demand side so that the corresponding user of the test demand side can generate the script. interface to generate target event scripts. There is no need to modify a large number of script files, which improves the efficiency of generating target event scripts.

Furthermore, in the case that the target event script that matches the changed new verification rule may not exist in the candidate event script, the target event script can also be automatically generated to test the test case. Optionally, if there is no target event script in the candidate event script that matches the new verification rule after the change, the general event script can be updated according to the target test requirements in the test request to obtain a script that matches the new verification rule. target event script. Among them, the universal event script is essentially an event script template.

For example, you can extract key fields in the target test requirements and fill in the key fields into the corresponding positions of the universal event script to obtain a target event script that matches the new validation rules.

In the embodiment of this application, by updating the general event script according to the target test requirements in the test request, the target event script that matches the new verification rule can be automatically generated, thereby improving the efficiency of generating the target event script.

Optionally, when the test demand side initiates different test requests for test cases, different target test requirements can be extracted from the different test requests, and different target events can be generated according to the target test requirements. When there are multiple target events, the target events can be placed in the event queue. According to the order of the events in the event queue, and based on the target event identification, the target in the candidate event script that matches the verification rule included in the target event is determined. event script, and run the general test script and the target event script until there are no unprocessed target events in the event queue, and run the script of the stop command to complete the test of the test case.

In one embodiment, when the number of new verification rules is at least two, corresponding test results can also be generated and displayed according to the sequence of target events corresponding to each new verification rule. The specific implementation process is as follows:

Optionally, summarize the test results of the test cases according to the execution order between the target event scripts corresponding to each new verification rule, and display the summarized test results to the test demand side. Among them, the test results can include test data, verification rules, test results, etc.

In the embodiment of this application, the test results of the test cases are summarized and the summarized test results are displayed to the test demand side to facilitate viewing by users of the test demand side.

In one embodiment, referring to Figure 5, Figure 5 provides a schematic method flow diagram of another test case testing method, which specifically includes the following steps:

S501: In response to the test request of the test case, extract the target test requirements from the test request.

Optionally, the server 104 receives the test request, and in response to the test request of the test case, can extract the target test requirements from the test request. Among them, the target test requirements may include information such as test data for testing test cases, methods of obtaining test data, and rules for verifying test data.

S502: Determine whether the target test requirements are consistent with the original test requirements of the test case. If they are inconsistent, it is determined that the verification rules for the test case have been changed, and step S503 is executed at this time; if they are consistent, it is determined that the verification rules for the test case have not been changed, and step S506 is executed at this time.

S503: Construct the target event according to the target test requirements.

Optionally, when there is a target test requirement, a target event can be constructed according to the target test requirement, where the target event includes the target event identifier and the changed new verification rule. For example, the target event is to test the accuracy of the collected data of data collection channel 1. The target event identifier can create an event for the event name and event; the new verification rule after the change can be used to verify whether the relative difference between the collected data of data collection channel 1 and the expected data is within 10%.

S504: Based on the correspondence between the candidate event identifier and the candidate event script, determine the target event script in the candidate event script that matches the changed new verification rule according to the target event identifier.

Optionally, a corresponding target event script can be generated in advance according to the target event, and a corresponding relationship is established with the target event according to the target event identifier, and then placed into the candidate event script together with other event scripts. In this way, based on the corresponding relationship between the candidate event identifier and the candidate event script, the target event script in the candidate event script that matches the changed new verification rule can be determined according to the target event identifier.

If the candidate event script may not contain a target event script that matches the new verification rule after the change, the target event script can be generated to test the test case.

Specifically, if there is no target event script matching the new verification rule after the change among the candidate event scripts, the script generation interface is displayed to the test demand side. The script generation interface may include an event script similar to the target event script, so that the user can modify the event script through the test demand side to generate the target event script.

The user can operate the script generation interface through the test demand side, for example, modify a similar script file in the script generation interface. The server 104 can generate a new script based on the input operation on the script generation interface by the test demand side. Validation rules match the target event script.

Furthermore, if there is no target event script matching the changed new verification rules in the candidate event scripts, the general event script can also be updated according to the target test requirements in the test request to obtain a target event script that matches the new verification rules. Target event script. For example, you can extract key fields in the target test requirements and fill in the key fields into the corresponding positions of the universal event script to obtain a target event script that matches the new validation rules.

S505: Determine the target test script according to the general test script and the target event script of the test case.

Optionally, a universal test script can be understood as a universal script file for testing test cases, that is, a test script that is needed to test each test case. The target event script is the script file corresponding to the new validation rule. The target test script can be understood as a script file used to test test cases. The test case's general test script and target event script can be called to determine the target test script.

S506: Use the test script corresponding to the original test requirement as the target test script.

Among them, the test scripts corresponding to the original test requirements include general test scripts for test cases and event scripts determined based on the original test requirements.

S507: Run the target test script to test the test case.

After determining the target test script for testing the test script, run the target test script to complete the test of the test case, such as outputting the final test results.

S508: Summarize the test results of the test cases and display the summarized test results to the test demand side.

Optionally, summarize the test results of the test cases according to the execution order between the target event scripts corresponding to each new verification rule, and display the summarized test results to the test demand side. Among them, the test results can include test data, verification rules, test results, etc.

For the specific processes from S501 to S508, please refer to the description of the above method embodiment. The implementation principles and technical effects are similar and will not be described again here.

It should be understood that although the steps in the flowcharts involved in the above-mentioned embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this article, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowcharts involved in the above embodiments may include multiple steps or stages. These steps or stages are not necessarily executed at the same time, but may be completed at different times. The execution order of these steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

Based on the same inventive concept, embodiments of the present application also provide a test case test device for implementing the above-mentioned test case test method. The solution to the problem provided by this device is similar to the solution recorded in the above method. Therefore, the specific limitations in the test device embodiments of one or more test cases provided below can be found in the above test case test. The limitations of the method will not be repeated here.

In one embodiment, as shown in Figure 6, a structural block diagram of a test device for a test case is provided, including:

The selection module 10 is configured to respond to the test request of the test case and select a target event from the candidate event script that matches the changed new verification rule when it is determined that the verification rule of the test case has been changed according to the test request. script;

The determination module 20 is used to determine the target test script according to the general test script and the target event script of the test case;

The running module 30 is used to run the target test script to test the test cases.

In one embodiment, the selection module 10 may include:

Extraction unit, used to extract target test requirements from test requests;

The first determination unit is used to determine that the verification rules of the test case have been changed if the target test requirements are inconsistent with the original test requirements of the test case.

In one embodiment, the selection module 10 may also include:

The construction unit is used to build the target event according to the target test requirements; where the target event includes the target event identifier and the new verification rule after the change;

The second determination unit is configured to determine, based on the corresponding relationship between the candidate event identifier and the candidate event script, the target event script in the candidate event script that matches the changed new verification rule according to the target event identifier.

In one embodiment, the selection module 10 may also include:

The display unit is used to display the script generation interface to the test demand side if there is no target event script matching the new verification rule after the change in the candidate event script;

The generation unit is used to generate a target event script that matches the new verification rule based on the input operation on the script generation interface from the test demand side.

In one embodiment, the selection module 10 may also include:

The update unit is used to update the general test script according to the target test requirements in the test request to obtain a target event script that matches the new verification rule if there is no target event script in the candidate event script that matches the new verification rule. target event script.

In one embodiment, see Figure 7. Based on Figure 6, Figure 7 provides a structural block diagram of a test device for another test case. The device also includes:

The summary module 40 is used to summarize the test results of the test cases according to the execution order between the target event scripts corresponding to each new verification rule, and display the summarized test results to the test demand side.

Each module in the test device of the above test case can be implemented in whole or in part by software, hardware and combinations thereof. Each of the above modules may be embedded in or independent of the processor of the computer device in the form of hardware, or may be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be shown in Figure 8 . The computer device includes a processor, memory, and network interfaces connected through a system bus. Wherein, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The non-volatile storage medium stores operating systems, computer programs and databases. This internal memory provides an environment for the execution of operating systems and computer programs in non-volatile storage media. The database of the computer device is used to store script data and test data corresponding to test cases. The network interface of the computer device is used to communicate with external terminals through a network connection. The computer program, when executed by the processor, implements a test case test method.

Those skilled in the art can understand that the structure shown in Figure 8 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Specific computer equipment can May include more or fewer parts than shown, or combine certain parts, or have a different arrangement of parts.

In one embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, it implements the following steps:

In response to the test request of the test case, if it is determined that the verification rule of the test case has been changed according to the test request, select a target event script that matches the changed new verification rule from the candidate event scripts;

Determine the target test script based on the general test script and target event script of the test case;

Run the target test script to test the test cases.

In one embodiment, the processor also implements the following steps when executing the computer program:

Extract the target test requirements from the test request; if the target test requirements are inconsistent with the original test requirements of the test case, it is determined that the verification rules of the test case have changed.

In one embodiment, the processor also implements the following steps when executing the computer program:

Construct the target event according to the target test requirements; wherein the target event includes the target event identifier and the new verification rule after the change; based on the correspondence between the candidate event identifier and the candidate event script, determine the candidate event script and the The target event script matches the new validation rule after the change.

In one embodiment, the processor also implements the following steps when executing the computer program:

If there is no target event script matching the changed new verification rule in the candidate event script, the script generation interface is displayed to the test demand side; according to the input operation of the test demand side on the script generation interface, the new verification rule is generated Matches the target event script.

In one embodiment, the processor also implements the following steps when executing the computer program:

If there is no target event script in the candidate event script that matches the new verification rule after the change, the general event script will be updated according to the target test requirements in the test request to obtain a target event script that matches the new verification rule.

In one embodiment, the processor also implements the following steps when executing the computer program:

According to the execution order between the target event scripts corresponding to each new verification rule, the test results of the test cases are summarized, and the summarized test results are displayed to the test demand side.

In one embodiment, a computer-readable storage medium is provided with a computer program stored thereon. When the computer program is executed by a processor, the following steps are implemented:

In response to the test request of the test case, if it is determined that the verification rule of the test case has been changed according to the test request, select a target event script that matches the changed new verification rule from the candidate event scripts;

Determine the target test script based on the general test script and target event script of the test case;

Run the target test script to test the test cases.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

Extract the target test requirements from the test request; if the target test requirements are inconsistent with the original test requirements of the test case, it is determined that the verification rules of the test case have changed.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

Construct the target event according to the target test requirements; wherein the target event includes the target event identifier and the new verification rule after the change; based on the correspondence between the candidate event identifier and the candidate event script, determine the candidate event script and the The target event script matches the new validation rule after the change.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

If there is no target event script matching the changed new verification rule in the candidate event script, the script generation interface is displayed to the test demand side; according to the input operation of the test demand side on the script generation interface, the new verification rule is generated Matches the target event script.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

If there is no target event script in the candidate event script that matches the new verification rule after the change, the general event script will be updated according to the target test requirements in the test request to obtain a target event script that matches the new verification rule.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

According to the execution order between the target event scripts corresponding to each new verification rule, the test results of the test cases are summarized, and the summarized test results are displayed to the test demand side.

In one embodiment, a computer program product is provided, comprising a computer program that when executed by a processor implements the following steps:

In response to the test request of the test case, if it is determined that the verification rule of the test case has been changed according to the test request, select a target event script that matches the changed new verification rule from the candidate event scripts;

Determine the target test script based on the general test script and target event script of the test case;

Run the target test script to test the test cases.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

Extract the target test requirements from the test request; if the target test requirements are inconsistent with the original test requirements of the test case, it is determined that the verification rules of the test case have changed.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

Construct the target event according to the target test requirements; wherein the target event includes the target event identifier and the new verification rule after the change; based on the correspondence between the candidate event identifier and the candidate event script, determine the candidate event script and the The target event script matches the new validation rule after the change.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

If there is no target event script matching the changed new verification rule in the candidate event script, the script generation interface is displayed to the test demand side; according to the input operation of the test demand side on the script generation interface, the new verification rule is generated Matches the target event script.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

If there is no target event script in the candidate event script that matches the new verification rule after the change, the general event script will be updated according to the target test requirements in the test request to obtain a target event script that matches the new verification rule.

In one embodiment, the computer program, when executed by the processor, also implements the following steps:

According to the execution order between the target event scripts corresponding to each new verification rule, the test results of the test cases are summarized, and the summarized test results are displayed to the test demand side.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage. In the media, when executed, the computer program may include the processes of the above method embodiments. Any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive memory (ReRAM), magnetic variable memory (Magnetoresistive Random) Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene memory, etc. Volatile memory may include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration but not limitation, RAM can be in various forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM). The databases involved in the various embodiments provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include blockchain-based distributed databases, etc., but are not limited thereto. The processors involved in the various embodiments provided in this application may be general-purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to this.

The technical features of the above embodiments can be combined in any way. To simplify the description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, all possible combinations should be used. It is considered to be within the scope of this manual.

The above-described embodiments only express several implementation modes of the present application, and their descriptions are relatively specific and detailed, but should not be construed as limiting the patent scope of the present application. It should be noted that, for those of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all fall within the protection scope of the present application. Therefore, the scope of protection of this application should be determined by the appended claims.

Claims (10)

1. A method for testing a test case, the method comprising:

responding to a test request of a test case, and selecting a target event script matched with a new verification rule after modification from candidate event scripts under the condition that the verification rule of the test case is determined to be modified according to the test request;

determining a target test script according to the universal test script of the test case and the target event script;

And running the target test script to test the test case.

2. The method of claim 1, wherein determining that the validation rule for the test case has changed based on the test request comprises:

extracting a target test requirement from the test request;

and if the target test requirement is inconsistent with the original test requirement of the test case, determining that the verification rule of the test case is changed.

3. The method of claim 2, wherein selecting a target event script from the candidate event scripts that matches the changed new validation rule comprises:

constructing a target event according to the target test requirement; the target event comprises a target event identification and a changed new verification rule;

and determining a target event script matched with the changed new verification rule in the candidate event script according to the target event identifier based on the corresponding relation between the candidate event identifier and the candidate event script.

4. The method of claim 1, wherein selecting a target event script from the candidate event scripts that matches the changed new validation rule comprises:

If the candidate event script does not have the target event script matched with the changed new verification rule, a script generation interface is displayed to the test demand end;

and generating a target event script matched with the new verification rule according to the input operation of the test requirement end on the script generation interface.

5. The method of claim 1, wherein selecting a target event script from the candidate event scripts that matches the changed new validation rule comprises:

if the candidate event script does not have the target event script matched with the changed new verification rule, updating the universal event script according to the target test requirement in the test request to obtain the target event script matched with the new verification rule.

6. The method according to claim 1, wherein in case the number of new validation rules is at least two, the method further comprises:

summarizing the test results of the test cases according to the execution sequence among the target event scripts corresponding to the new verification rules, and displaying the summarized test results to the test requirement end.

7. A test apparatus for testing a case, the apparatus comprising:

the selection module is used for responding to the test request of the test case, and selecting a target event script matched with the new verification rule after the change from candidate event scripts under the condition that the verification rule of the test case is determined to be changed according to the test request;

the determining module is used for determining a target test script according to the universal test script of the test case and the target event script;

and the operation module is used for operating the target test script so as to test the test case.

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.

9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.