WO2019095580A1

WO2019095580A1 - Test method and apparatus, computer device, and readable storage medium

Info

Publication number: WO2019095580A1
Application number: PCT/CN2018/077273
Authority: WO
Inventors: 余巍
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-11-16
Filing date: 2018-02-26
Publication date: 2019-05-23
Also published as: CN107861876A

Abstract

A test method and apparatus, a computer device, and a readable storage medium. The method comprises: acquiring constructed test tasks; selecting automated test cases that correspond to the constructed test tasks; executing the automated test cases according to the constructed test tasks; when the execution of all the automated test cases is completed, selecting manual test cases corresponding to the constructed test tasks; and selecting an unexecuted manual test case from the manual test cases according to the selected automated test cases, and outputting the unexecuted manual test case for manual testing.

Description

Test method, device, computer device and readable storage medium

This application claims the priority of the Chinese Patent Application entitled "Test Methods, Apparatus, Computer Equipment, and Readable Storage Media" by the Chinese Patent Office, filed on November 16, 2017, with the application number of 2017111365099, the entire contents of which are incorporated by reference. Combined in this application.

Technical field

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

Background technique

The test is to test various performance indicators of the system by testing various normal, peak and abnormal load conditions. Traditionally, the tests for the system and the like are manually tested, that is, the test cases need to be manually input into the system to be tested one by one, and then the test results are judged according to the output of the system to be tested, and the test of multiple test cases is counted. The number of successes to get the test success rate, the process needs to be tested one by one, resulting in lower test efficiency.

Summary of the invention

In accordance with various embodiments disclosed herein, a test method, apparatus, computer apparatus, and readable storage medium are provided.

A test method, the method comprising:

Get the test task built;

Select an automated test case that corresponds to the test task being built;

Performing the automated test case in accordance with the built test task;

When the automated test cases are all completed, the manual test cases corresponding to the constructed test tasks are selected; and

An unexecuted manual test case is selected from the manual test case according to the selected automated test case, and the unexecuted manual test case is output for manual testing.

A test device, the device comprising:

a test task acquisition module for obtaining a test task constructed;

An automated test case selection module for selecting automated test cases corresponding to the constructed test tasks;

An execution module for executing the automated test case according to the built test task;

a manual test case selection module, configured to select a manual test case corresponding to the constructed test task when the automated test cases are all executed; and

And an output module, configured to select an unexecuted manual test case from the manual test case according to the selected automated test case, and output the unexecuted manual test case for manual test.

A computer device comprising a memory, a processor, on which is stored computer readable instructions, and the processor, when executing the computer readable instructions, implements the following steps:

Get the test task built;

Select an automated test case that corresponds to the test task being built;

Performing the automated test case in accordance with the built test task;

One or more computer readable non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of:

Get the test task built;

Select an automated test case that corresponds to the test task being built;

Performing the automated test case in accordance with the built test task;

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features and advantages of the present invention will be apparent from the description, drawings and claims.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings to be used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without any creative work.

1 is an application environment diagram of a test method in an embodiment;

2 is a flow chart of a test method in an embodiment;

Figure 3 is a flow chart of step S206 in the embodiment shown in Figure 2;

4 is an interface diagram of a new test task in an embodiment;

Figure 5 is an interface diagram of all test tasks in an embodiment;

6 is a statistical diagram of test results in an embodiment;

7 is a schematic structural view of a test device in an embodiment;

FIG. 8 is a schematic structural diagram of a computer device in an embodiment.

Detailed ways

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

Before the embodiments in accordance with the present application are described in detail, it should be noted that the described embodiments are primarily a combination of steps and system components associated with test methods, apparatus, computer devices, and readable storage media. Accordingly, the system components and method steps have been shown in the drawings by the conventional symbols in the appropriate positions, and only the details related to the understanding of the embodiments of the present application are shown to avoid the benefit of the present application. Those details apparent to those of ordinary skill in the art obscure the disclosure of the present application.

In this context, relational terms such as left and right, up and down, before and after, first and second are only used to distinguish one entity or action from another entity or action, without necessarily requiring or implying such Any actual relationship or order between entities or actions. The terms "comprising," "comprising," or "include" or "includes" or "includes" or "includes" or "includes" or "includes" An element, or an element inherent to such a process, method, item, or device.

Please refer to FIG. 1. FIG. 1 is an application environment diagram of a test method in an embodiment, including a computer device, a database, and a plurality of execution nodes, wherein the computer device is configured to receive the constructed test task, and test the test case according to the test task. Sended to several execution nodes, the execution node performs test tasks, the computer device collects the test results of the execution nodes, and stores the test results in the database, and the test results of the manual test are stored in the manual test result storage system, such as DPM system, TESTLINK The system, the WIZARD system, or the JENKINS system, etc., can obtain the test results stored in the manual test result storage system, and store the test results in a database for the user to query or generate reports.

Referring to FIG. 2, in one embodiment, a test method is provided. This embodiment is exemplified by applying the method to the computer device in FIG. 1 above. A test readable instruction is run on the computer device, and the test method is implemented by the test readable instruction. The method specifically includes the following steps:

S202: Acquire a test task constructed.

Specifically, the user can build a test task on the computer device, and an operation interface of the automated test can be provided on the computer device, and the task list, the node list, and the statistical report related to the automated test can be displayed on the operation interface, when the user opens the task list. You can add new test tasks to the task list, or delete the built test tasks, or modify the built test tasks, such as modifying the execution nodes of the built test tasks. The node list is a server that can perform test tasks, and the like. A statistical report is a report that shows the test results of a test task and test parameters, which can be displayed in a tabular or other graphical manner.

S204: Select an automated test case corresponding to the constructed test task.

Specifically, when the built test task is obtained, the test case corresponding to the test task is obtained, for example, the automatic test case may be selected according to the version information of the test version of the built test task, and then according to the test type. For example, interface type or interface type, select the corresponding type of automated test case from the corresponding version of the automated test case. Optionally, the step may be performed by using a timed task. For example, after obtaining the built test task, setting a timed task, and then selecting an automated test case according to the start time of the timed task, thereby performing an automated test. This is because when there are many test tasks, there may be higher-priority test tasks. For this reason, the currently built test tasks cannot be performed in time, but can be preset according to the possible duration of the higher-priority test tasks. The timed task can ensure that the current test task can be executed in time after the higher priority test task is completed, without manual or machine real-time monitoring whether the higher priority test task has been completed, which can save human resources, and Computer equipment does not require a large amount of resources to monitor higher-priority test tasks in real time, reducing waste of resources.

S206: Perform an automated test use case according to the built test task.

Specifically, when an automated test case is obtained, the automated test case is executed to complete the built test task.

S208: When the automated test cases are all completed, the manual test cases corresponding to the constructed test tasks are selected.

Specifically, when the automated test cases are all completed, the automated test of the test task is completed. In order to ensure the correctness of the test, each test involves not only the automated test but also the manual test, so the computer device obtains To the manual test case corresponding to the test task being built, the manual test case can also be stored in a manual test result storage system, such as a DPM system, a TESTLINK system, a WIZARD system, or a JENKINS system, etc., and the computer device can access these systems. Get all the manual test cases.

S210: Select an unexecuted manual test case from the manual test case according to the selected automated test case, and output an unexecuted manual test case for manual test.

Specifically, the automated test case set is a subset of the manual test case set. All automated test cases are manual test cases. When the automated test case has been executed, the automated test case is no longer needed to be executed again. The manual test case is not executed, so the computer device outputs the unexecuted manual test case, and the manual test case is manually executed by the user.

The above test method first selects an automated test case corresponding to the constructed test task, then executes the automated test case, and then selects a manual test case corresponding to the constructed test task, and according to the automated test case that has been executed, from the manual Selecting unexecuted manual test cases from the test cases can greatly reduce the number of manual tests, thereby improving the test efficiency. Because the quality of the test scripts is highly dependent on the quality of the test scripts and the test scripts are of poor quality, the test results will not be Reliable, the manual solution is also introduced in the technical solution, that is, the test process is not completely dependent on the automatic test, and the reliability of the test result is guaranteed.

In one embodiment, referring to FIG. 3, FIG. 3 is a flowchart of step S206 in the embodiment shown in FIG. 2, which may include: performing steps of performing an automated test case according to the constructed test task:

S302: Select an online idle node from the execution node according to the constructed test task.

Specifically, referring to FIG. 4 and FIG. 5, FIG. 4 is an interface diagram of a new test task in an embodiment, and FIG. 5 is an interface diagram of all test tasks in an embodiment. In FIG. 4, when a test task is added, The execution node is selected, and the selection of the execution node first needs to match the constructed test task, and secondly, the execution node is to be online. The execution node is matched with the built test task, and the execution node is required to install a test system or a test framework corresponding to the test task. Optionally, a table may be set, where the table includes a node identifier of the execution node and Execute the test system or test framework installed in the node. The node identifier of the execution node may be the MAC address of the execution node, etc., which can uniquely identify the attributes of the execution node. The test system or test framework installed by the execution node may use keywords. Or label the way to identify, in order to facilitate the query. In Fig. 5, a plurality of test tasks are given, which have been executed, and the status of the execution node, such as online or offline, can still be displayed in the execution node column, so that the user can perform the test task again.

S304: When there is no online idle node in the execution node, the execution node that selects the maximum number of connections is greater than or equal to two and the current number of connections is less than the maximum number of connections.

Specifically, when there is no online idle node in the execution node, since the current test needs to be performed, and each execution node can perform multiple test tasks at the same time, the maximum connection number can be selected to be greater than or equal to 2, and the current connection number is less than the maximum. The number of execution nodes of the connection, so as to ensure that a limited number of execution nodes perform a large number of test tasks, thereby improving the utilization rate of the execution nodes. Specifically, it is assumed that there are three nodes A, B, and C; if the maximum number of connections of the A node is 1, the maximum number of connections of the B node is 3, and two test tasks are currently connected, and the maximum number of connections of the C node is 3. . When the computer device is performing the test task, the execution node needs to be selected. If the C node is not online, the node can only be selected from the A node and the B node; if the A node is online and idle, the A node is directly selected as the execution node. If the A node is online but not in the idle state, it needs to be selected from other nodes. In this case, the maximum number of connections of the B node is 3, which is greater than the number of test tasks that it is currently connected to. Therefore, the C node is selected as the execution node of the current test task. If the number of execution nodes of the currently selected test task is greater than or equal to 2, it is output to the interface in a list manner, and the user selects one of the nodes as the execution node of the current test task.

S306: Send the automated test case to the selected execution node and execute the automated test case.

Specifically, the automated test case is sent to the selected execution node, and the execution node invokes the corresponding script to execute the automated test case for automated testing.

In the above embodiment, when the execution node is selected, the current state of the execution node and the maximum number of connections of the execution node are fully considered, and the resources of the execution node can be fully utilized to improve the efficiency of the test.

In one embodiment, the testing method may further include obtaining a first quantity of the automated test case whose execution result is successful; obtaining a second quantity of the manual test case whose execution result is successful from the manual test result storage system; A number, a second quantity, and a number of manual use cases corresponding to the constructed test task are calculated to obtain a test success rate of the constructed test task; when the test success rate is lower than a preset value, the result of the test failure is output.

Specifically, the test method also needs to calculate the test success rate, as shown in FIG. 6. FIG. 6 is a schematic diagram of a test report in an embodiment, including a system name, a task type, a build time, a duration, a manual use case, and an automatic execution. Number, automatic coverage, success number, and number of failures, etc., where the system name is the system name of the system corresponding to the test task being built, and the task type includes interface test and interface test, etc. The build time is the time and duration of the test task establishment. The time used to execute the automated test case, the number of manual use cases is the total number of test cases, the number of automated executions is the number of automated test cases, and the automated test coverage is the ratio of the number of automated test cases to the number of manual test cases. The success number is the first number of successful executions in the automated test case and the second number of successes in the manual test case. The number of failures is the number of manual cases minus the first quantity and the second quantity. Then is the ratio of the sum of the first quantity and the second quantity to the number of manual use cases. When the success rate is lower than the preset value, the test is considered to be failed, so the result of the test failure may be output to prompt the user, for example, the user may send a short message, a WeChat or send an email, make a call, etc., or directly output to the interface, The user is prompted.

The first quantity is the result of the automated test, which can be obtained directly from the execution node. The second quantity may exist in different manual test result storage systems, and therefore needs to be obtained from different manual test result storage systems, and is configured in this embodiment. Different interfaces are connected to different manual test result storage systems, and different templates are configured to adapt to different manual test result storage systems, so that test results can be obtained directly from different manual test result storage systems, from statistical manual test cases. The result of the execution is the second number of successes to facilitate subsequent calculation of the test success rate.

In the above embodiment, the first quantity of the automated test case whose execution result is successful is obtained; and the second quantity of the manual test case whose execution result is successful is obtained from the manual test result storage system, according to the first quantity, the second quantity, and The number of manual use cases corresponding to the test task is calculated to obtain the test success rate of the constructed test task, and the operation is simple and reliable.

In one embodiment, the testing method may further include: when the test success rate is not lower than the preset value, acquiring a historical test task associated with the constructed test task; when the test success rate is lower than the historical test task When the test success rate is successful, the result of the test failure is indicated.

Specifically, the computer device can also obtain the automatic test success rate of the historical version, and calculate the automatic test success rate of the current version. When the current version of the automated test success rate is less than the historical version of the automated test success rate, the current automation is prompted. There is a problem with the test. Since the version is in the process of upgrading each time, the test success rate should be higher and higher. If the test success rate is lower than the historical test success rate, the task version upgrade fails and the test fails. The same test version of the same version before and after, the success rate of the latter test should also be higher than the success rate of the previous test, if it is low, the result of the test failure.

In the above embodiment, the test success rate of the historical version is combined to determine whether the test of the current version is successful, the relationship between the versions is strengthened, and the accuracy of the test is improved.

In one embodiment, the testing method may further include: counting the number of all types of test cases in the automated test case; calculating each number according to the number of all types of test cases in the automated test case and the number of manual test cases The coverage of a type of test case; when there is a coverage type of a test case whose coverage is lower than the coverage threshold, it prompts to increase a certain type of test case.

Specifically, referring to FIG. 6, FIG. 6 is a statistical diagram of test results in an embodiment, which may include a version build graph, a version success rate graph, a use case coverage graph, and a use case type map. The abscissa of the version build graph is the version number of the build version, the ordinate is the build success rate, different fold lines can identify different items, and the computer device automatically counts the success rate of each version of each item and displays it, without manual intervention. Statistical data has greatly improved efficiency. The version success rate chart can use a pie chart in which the total number of automated test cases is the denominator, the number of successful automated test runs, the number of automated test cases that failed to execute, and the number of unexecuted automated test cases are numerators. The number of manual use cases in the use case coverage chart is the denominator. The number of test rates for each type is numerator, such as the number of interface test cases and the number of interface test cases. When there is a certain type of test case, the coverage is lower than that. When the coverage threshold is used, it prompts to increase a certain type of test case, which can ensure the sufficiency of the test case and improve the accuracy of the test. The use case type map can be a pie chart.

In the above embodiment, the number of all types of test cases in the automated test case is counted; the coverage of each type of test case is calculated according to the number of all types of test cases in the automated test case and the number of manual test cases; When the coverage of a certain type of test case is lower than the coverage threshold, it prompts to increase a certain type of test case, which can ensure the sufficiency of the test case and improve the accuracy of the test.

2 and 3 are schematic flowcharts of a method according to an embodiment of the present application. It should be understood that although the various steps in the flowcharts of FIGS. 2 and 3 are sequentially displayed in accordance with the indication of the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and may be performed in other sequences. Moreover, at least some of the steps in FIGS. 2 and 3 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, and the execution order thereof is also It is not necessarily performed sequentially, but may be performed alternately or alternately with at least a portion of other steps or sub-steps or stages of other steps.

Referring to FIG. 7, FIG. 7 is a schematic structural diagram of a testing device in an embodiment, where the testing device includes:

The test task acquisition module 100 is configured to acquire the constructed test task.

The automated test case selection module 200 is configured to select an automated test case corresponding to the constructed test task.

The execution module 300 is configured to execute an automated test case according to the built test task.

The manual test case selection module 400 is configured to select a manual test case corresponding to the constructed test task when the automated test cases are all executed.

The output module 500 is configured to select an unexecuted manual test case from the manual test case according to the selected automated test case, and output an unexecuted manual test case for manual testing.

In one embodiment, the execution module 300 can include:

The first node selection unit is configured to select an online idle node from the execution node according to the constructed test task.

The second node selection unit is configured to: when there is no online idle node in the execution node, select, from the execution node, a node whose maximum connection number is greater than or equal to two and the current connection number is less than the maximum connection number.

An execution unit that sends automated test cases to selected nodes and executes automated test cases.

In one embodiment, the testing device may further include:

The first test result obtaining unit is configured to obtain the first quantity of the automated test case whose execution result is successful.

The second test result obtaining unit is configured to obtain, from the manual test result storage system, a second quantity of the manual test case whose execution result is successful.

The calculating unit is configured to calculate a test success rate of the constructed test task according to the first quantity, the second quantity, and the number of manual use cases corresponding to the constructed test task.

The first output unit is configured to output a result of the test failure when the test success rate is lower than a preset value.

In one embodiment, the testing device may further include:

The historical test task acquisition module is configured to acquire a historical test task associated with the constructed test task when the test success rate is not lower than a preset value.

The output module 500 can also be used to indicate the result of the test failure when the test success rate is lower than the test success rate of the historical test task.

In one embodiment, the testing device may further include:

A statistical module that counts the number of all types of test cases in an automated test case.

Coverage calculation module for calculating the coverage of each type of test case based on the number of all types of test cases in the automated test case and the number of manual test cases.

The output module 500 can also be used to prompt to add a certain type of test case when there is a certain type of test case whose coverage is lower than the coverage threshold.

For the specific definition of the test device, reference may be made to the above definition of the test method, and details are not described herein again. Each of the above test devices may 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 in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules. The processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like. The above test apparatus can be implemented in the form of a computer readable instruction that can be executed on a computer device as shown in FIG.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in FIG. The computer device includes a processor, memory, network interface, and database connected by a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for operation of an operating system and computer programs in a non-volatile storage medium. The database of the computer device is used to store test results. The network interface of the computer device is used to communicate with an external terminal via a network connection. The computer program is executed by the processor to implement a test method.

It will be understood by those skilled in the art that the structure shown in FIG. 8 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied. The specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.

In one embodiment, a computer apparatus is provided, comprising a memory, a processor, on which the computer readable instructions are stored, and when the processor executes the computer readable instructions, the following steps are performed: acquiring the constructed test task; An automated test case corresponding to the test task being built; an automated test case is executed according to the built test task; when the automated test case is executed, the manual test case corresponding to the constructed test task is selected; The automated test case selects unexecuted manual test cases from manual test cases and outputs unexecuted manual test cases for manual testing.

With continued reference to FIG. 8, there is also provided a computer readable storage medium having stored thereon computer readable instructions, such as the nonvolatile storage medium shown in FIG. 8, wherein the readable instructions are executed by a processor Implement the following steps: obtain the built test task; select the automated test case corresponding to the built test task; execute the automated test case according to the built test task; when the automated test case is completed, select and build The manual test case corresponding to the test task; the unexecuted manual test case is selected from the manual test case according to the selected automated test case, and the unexecuted manual test case is output for manual test.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by computer readable instructions, which can be stored in a non-transitory computer. In the storage medium, the computer readable instructions, when executed, may include the flow of an embodiment of the methods described above. Any reference to a memory, storage, database or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain. Synchlink DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be considered as the scope of this manual.

The above-mentioned embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims

A test method, the method comprising:

Get the test task built;

Select an automated test case that corresponds to the test task being built;

Performing the automated test case in accordance with the built test task;

When the automated test cases are all completed, the manual test cases corresponding to the constructed test tasks are selected; and

An unexecuted manual test case is selected from the manual test case according to the selected automated test case, and the unexecuted manual test case is output for manual testing.
The method of claim 1 wherein said step of executing said automated test case in accordance with said constructed test task comprises:

Selecting an online idle node from the execution node according to the constructed test task;

When there is no online idle node in the execution node, selecting an execution node that has a maximum number of connections greater than or equal to two and a current connection number is less than the maximum number of connections; and

The automated test case is sent to the selected execution node and the automated test case is executed.
The method of claim 1 further comprising:

Get the first number of automated test cases with successful execution results;

Obtaining a second number of successful manual test cases from the manual test result storage system;

Calculating a test success rate of the constructed test task according to the first quantity, the second quantity, and the number of the manual use cases corresponding to the constructed test task; and

When the test success rate is lower than the preset value, the result of the test failure is output.
The method of claim 3, wherein the method further comprises:

When the test success rate is not lower than the preset value, acquiring a historical test task associated with the constructed test task; and

When the test success rate is lower than the test success rate of the historical test task, the result of the test failure is prompted.
The method of claim 1 further comprising:

Counting the number of all types of test cases in the automated test case;

Calculating the coverage of each type of test case according to the number of all types of test cases in the automated test case and the number of the manual test cases; and

When there is a coverage type of a test case whose coverage is lower than the coverage threshold, it is prompted to increase the test case of the certain type.
A testing device, characterized in that the device comprises:

a test task acquisition module for obtaining a test task constructed;

An automated test case selection module for selecting automated test cases corresponding to the constructed test tasks;

An execution module for executing the automated test case according to the built test task;

a manual test case selection module, configured to select a manual test case corresponding to the constructed test task when the automated test cases are all executed; and

And an output module, configured to select an unexecuted manual test case from the manual test case according to the selected automated test case, and output the unexecuted manual test case for manual test.
The apparatus according to claim 6, wherein the execution module comprises:

a first node selection unit, configured to select an online idle node from the execution node according to the constructed test task;

a second node selection unit, configured to: when there is no online idle node in the execution node, select, from the execution node, a node whose maximum connection number is greater than or equal to two and the current connection number is less than the maximum connection number; and

An execution unit for transmitting the automated test case to the selected node and executing the automated test case.
The device according to claim 6, wherein the device further comprises:

a first test result obtaining unit, configured to obtain a first quantity of the automated test case in which the execution result is successful;

a second test result obtaining unit, configured to obtain, from the manual test result storage system, a second quantity of the manual test case whose execution result is successful;

a calculating unit, configured to calculate, according to the first quantity, the second quantity, and the number of the manual use cases corresponding to the constructed test task, a test success rate of the constructed test task; and

And an output unit, configured to output a result of the test failure when the test success rate is lower than a preset value.
The device according to claim 8, wherein the device further comprises:

a history test task obtaining module, configured to acquire a historical test task associated with the constructed test task when the test success rate is not lower than the preset value; and

The output module is further configured to prompt the result of the test failure when the test success rate is lower than the test success rate of the historical test task.
The device according to claim 6, wherein the device further comprises:

a statistics module for counting the number of all types of test cases in the automated test case;

a coverage calculation module, configured to calculate coverage of each type of test case according to the number of all types of test cases in the automated test case and the number of the manual test cases; and

The output module is further configured to prompt to increase the test case of the certain type when there is a coverage of a certain type of test case below a coverage threshold.
A computer device comprising a memory, a processor, and computer readable instructions stored on the memory and executable on the processor, wherein the processor, when executing the computer readable instructions, implements the following steps:

Get the test task built;

Select an automated test case that corresponds to the test task being built;

Performing the automated test case in accordance with the built test task;

When the automated test cases are all completed, the manual test cases corresponding to the constructed test tasks are selected; and

An unexecuted manual test case is selected from the manual test case according to the selected automated test case, and the unexecuted manual test case is output for manual testing.
The computer device according to claim 11, wherein the step of executing the automated test case according to the constructed test task implemented by the processor when the computer readable instructions are executed comprises:

Selecting an online idle node from the execution node according to the constructed test task;

When there is no online idle node in the execution node, selecting an execution node that has a maximum number of connections greater than or equal to two and a current connection number is less than the maximum number of connections; and

The automated test case is sent to the selected execution node and the automated test case is executed.
The computer apparatus according to claim 11, wherein said processor further implements the following steps when said computer readable instructions are executed:

Get the first number of automated test cases with successful execution results;

Obtaining a second number of successful manual test cases from the manual test result storage system; and

Calculating a test success rate of the constructed test task according to the first quantity, the second quantity, and the number of the manual use cases corresponding to the constructed test task;

When the test success rate is lower than the preset value, the result of the test failure is output.
The computer apparatus according to claim 13, wherein said processor further implements the following steps when said computer readable instructions are executed:

When the test success rate is not lower than the preset value, acquiring a historical test task associated with the constructed test task; and

When the test success rate is lower than the test success rate of the historical test task, the result of the test failure is prompted.
The computer apparatus according to claim 11, wherein said processor further implements the following steps when said computer readable instructions are executed:

Counting the number of all types of test cases in the automated test case;

Calculating the coverage of each type of test case according to the number of all types of test cases in the automated test case and the number of the manual test cases; and

When there is a coverage type of a test case whose coverage is lower than the coverage threshold, it is prompted to increase the test case of the certain type.
One or more computer readable non-volatile storage media storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause one or more processors to perform the following step:

Get the test task built;

Select an automated test case that corresponds to the test task being built;

Performing the automated test case in accordance with the built test task;

When the automated test cases are all completed, the manual test cases corresponding to the constructed test tasks are selected; and

An unexecuted manual test case is selected from the manual test case according to the selected automated test case, and the unexecuted manual test case is output for manual testing.
A storage medium according to claim 16 wherein said computer readable instructions are executed by one or more processors such that said one or more processors execute said executions in accordance with said constructed test tasks The steps of an automated test case include:

Selecting an online idle node from the execution node according to the constructed test task;

When there is no online idle node in the execution node, selecting an execution node that has a maximum number of connections greater than or equal to two and a current connection number is less than the maximum number of connections; and

The automated test case is sent to the selected execution node and the automated test case is executed.
The storage medium of claim 16 wherein when said computer readable instructions are executed by one or more processors, the one or more processors further cause the following steps:

Get the first number of automated test cases with successful execution results;

Obtaining a second number of successful manual test cases from the manual test result storage system;

Calculating a test success rate of the constructed test task according to the first quantity, the second quantity, and the number of the manual use cases corresponding to the constructed test task; and

When the test success rate is lower than the preset value, the result of the test failure is output.
The storage medium of claim 18, wherein when the computer readable instructions are executed by one or more processors, the one or more processors further cause the following steps:

When the test success rate is not lower than the preset value, acquiring a historical test task associated with the constructed test task; and

When the test success rate is lower than the test success rate of the historical test task, the result of the test failure is prompted.
The storage medium of claim 16 wherein when said computer readable instructions are executed by one or more processors, the one or more processors further cause the following steps:

Counting the number of all types of test cases in the automated test case;

Calculating the coverage of each type of test case according to the number of all types of test cases in the automated test case and the number of the manual test cases; and

When there is a coverage type of a test case whose coverage is lower than the coverage threshold, it is prompted to increase the test case of the certain type.