WO2019056475A1

WO2019056475A1 - Automated test task management method and apparatus, device, and storage medium

Info

Publication number: WO2019056475A1
Application number: PCT/CN2017/107945
Authority: WO
Inventors: 伍朗; 伍振亮
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-09-21
Filing date: 2017-10-27
Publication date: 2019-03-28
Also published as: CN107766236B; CN107766236A

Abstract

The present application relates to the technical field of automated testing and provides an automated test task management method and apparatus, a device, and a storage medium. The automated test task management method comprises: obtaining a test task to be executed, and obtaining, according to the test task, a test package corresponding thereto; updating a code in the test package according to a newly-added code in a system to obtain the latest version of the test package; and verifying a test environment where the test task is executed, and when the test environment is determined to meet a test condition, executing the test task according to the latest version of the test package. In the present application, when the test environment meets the test condition, the test task is executed according to the latest test package, therefore, the problem of inaccurate testing caused by a wrong version of the test package and a changed test environment is avoided, test efficiency is improved, usage of a test machine is arranged reasonably and effectively, and manpower resources are saved.

Description

Test task automation management method, device, device and storage medium

This patent application is based on the Chinese invention patent application filed on September 21, 2017, with the application number of 201710857314.7, entitled "Test task automation management method, device, equipment and storage medium", and requires its priority.

Technical field

The present application relates to the field of software automated testing technologies, and in particular, to an automated test task management method, apparatus, device, and storage medium.

Background technique

Usually the execution of the test task is manually triggered. Which test package needs to be executed during the test is also manually defined. This method is easy to cause omission, and the test environment and the test machine will not be verified during the manual trigger. The results are very susceptible to the test environment. And the test package is difficult to have a comprehensive check before execution. It is easy to find that the test package version is incorrect after the test is executed, causing the test to run again. Since the execution of automated test packages generally takes a long time, the above defects can cause a lot of manpower waste.

Summary of the invention

The purpose of the application is to provide a test task automation management method, device, device and storage medium, which can update the test package and verify the test environment before performing the test task, thereby saving human resources.

The application is implemented in this way. The first aspect of the present application provides an automated test task management method, where the automated test task management method includes:

Obtaining a test task to be executed, and obtaining a corresponding test package according to the test task;

Update the code in the test package to get the latest version of the test package based on the new code in the system;

Verify the test environment in which the test task is executed. When it is determined that the test environment meets the test conditions, perform the test task according to the latest version of the test package.

The second aspect of the present application provides an automated test task management apparatus, where the automated test task management apparatus includes:

The test package acquisition module acquires a test task to be executed, and obtains a corresponding test package according to the test task;

The test package update module updates the code in the test package according to the new code in the system to obtain the latest version of the test package;

The test environment verification module verifies the test environment in which the test task is executed. When it is determined that the test environment meets the test condition, the test task is executed according to the latest version of the test package.

A third aspect of the present application provides a terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable instructions Implement the following steps:

Update the code in the test package according to the new code in the system to get the latest version of the test package;

Verifying the test environment in which the test task is executed. When it is determined that the test environment meets the test condition, the test task is executed according to the latest version of the test package.

A fourth aspect of the present application provides a computer readable storage medium storing computer readable instructions that, when executed by a processor, implement the following steps:

Verifying the test environment in which the test task is performed, when it is determined that the test environment meets the test condition, The test task is performed according to the latest version of the test package.

An embodiment of the present application provides an automated test task management method, apparatus, device, and storage medium. The test package is obtained according to the obtained test task, and the code in the test package is updated according to the newly added code in the system to obtain the latest test. The package verifies the test environment for executing the test task. When the test environment meets the test conditions, the test task is executed according to the latest test package, the test package version is not correct, and the test environment is inaccurately tested, which improves the test efficiency. Reasonable and effective arrangement of the test machine, saving human resources.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only the present application. For some embodiments, other drawings may be obtained from those of ordinary skill in the art without departing from the drawings.

1 is a flowchart of a method for automatically managing a test task according to an embodiment of the present application;

2 is a specific flowchart provided by an implementation manner of step S20 in a method for automatically managing a test task according to an embodiment of the present application;

FIG. 3 is a specific flowchart provided by an implementation manner of step S30 in a method for automatically managing a test task according to an embodiment of the present application;

4 is a specific flowchart provided by another implementation manner of step S30 in a method for automatically managing a test task according to an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a test task automation management apparatus according to another embodiment of the present application; FIG.

6 is a schematic diagram of a specific structure provided by an implementation manner of a test packet update module in a test task automation management apparatus according to another embodiment of the present application;

FIG. 7 is a schematic structural diagram of a terminal device according to another embodiment of the present application.

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.

In order to explain the technical solutions of the present application, the following description will be made by way of specific embodiments.

The embodiment of the present application provides an automated test task management method. As shown in FIG. 1 , the automated test task management method includes step S10, step S20, and step S30. The specific content of each step is as follows:

Step S10: Acquire a test task to be executed, and obtain a corresponding test package according to the test task.

In step S10, the test machine can perform the test according to the user's instruction when executing the test task, or can perform the test according to the time sequence. For example, the test machine is currently in use, and the next test is performed after the test machine executes the current test. Before performing each test task, obtain the environment information and test package of the test task through the test task, which can be obtained by reading the configuration file of the test task.

Step S20. Update the code in the test package according to the code added in the system to obtain the latest version of the test package.

In step S20, for the update of the test package, it may be detected by detecting whether a new code is added in the system, and detecting whether the new code is added is usually obtained by detecting the update status of the software package and whether to increase the manually writeable code. For example, by using the patch package with the patch package version number to update the corresponding software package, the updated software package can be filtered according to the version number of the service package, or the code recorded after manually modifying the software package can be tested. The package is updated.

As an embodiment, as shown in FIG. 2, step S20 specifically includes step S201, step S202, and step S203, and the specific content of each step is as follows:

Step S201. When it is checked that the code server writes the code or downloads a new patch package, the code in the written or new patch package is obtained.

Step S202. Recompile the test package according to the acquired code.

In step S202, when it is detected that the user updates the test package, for example, when there is a new patch package, the test package is recompiled according to the patch package to update the test package.

Step S203. Determine that the recompiled test package is the latest version of the test package.

In step S203, after the test package is recompiled, the latest version of the test package is obtained, and the test package of the latest version is used for testing.

In this step, the test package is updated. The update path includes downloading the patch package and the code on the code server, which avoids the test failure caused by the wrong version of the test package.

Step S30. Verify the test environment in which the test task is executed. When the test environment meets the test condition, perform the test task according to the latest version of the test package.

In step S30, after the test environment and the test package are verified, the test task is executed according to the latest test package. There is a send function during the execution of the test. For example, when a test error occurs, an alert message is sent to the user. When the test is completed, the test results are sent to the user.

The embodiment of the present application provides an automated test task management method, which obtains a corresponding test package according to the obtained test task, updates the code in the test package according to the newly added code in the system to obtain the latest test package, and verifies the execution of the test task. Test environment, when the test environment meets the test conditions, perform test tasks according to the latest test package. Avoid problems with incorrect test code versions, find environmental problems early and improve efficiency, and arrange the use of test machines reasonably.

For the step S30 in the foregoing embodiment, as an implementation manner, as shown in FIG. 3, after the test environment and the test package are verified, the test task is executed according to the latest test package, including:

Step S301. Verify that the hardware device, the network status, and the software version of the test task meet the test conditions. If yes, go to step S303. If no, go to step S302.

In step S301, the test environment verification may be basic verification, for example, whether the test machine is idle, the CPU usage status, the memory usage status, the disk space status, the network status, and the software version may also serve as a basic verification point. In addition to the basic verification, you can also call the verification script in the test package to verify the preconditions required by the test package. For example, to execute a test package that includes a login, you can verify that the user used to log in exists.

Step S302: Acquire the level code corresponding to the alarm information when the alarm information is sent, obtain the processing priority according to the level code, and transfer the processing to the automatic response processing flow under the corresponding level code according to the processing priority, and return to step S301. .

In step S302, the alarm information refers to the alarm signal information corresponding to the abnormality that occurs, that is, according to the alarm signal information, it can be clearly known what kind of abnormality is abnormal, and the content of the alarm information can be known through the level code, according to the level. The code acquisition processing priority refers to obtaining the priority flag code according to the level code, and prioritizing the higher priority level according to the flag code, and the automatic response processing process refers to the specific problem that the exception can be obtained according to the level code, and the specific problem is solved for the specific problem. After the processing scheme is executed, the processing scheme is executed, and then the processing returns to step S301 to perform the detection again.

Step S303. Verify the test package, determine whether there is a conflict between the test package corresponding to the test task to be executed and the test package corresponding to the test task being executed. If yes, go to step S304, otherwise go to step S305.

In step S303, the test package conflict means that some steps of the test package to be executed may have an impact on the steps of the test package that are currently being executed, which may result in an error or execution failure of the test package being executed or interference with the verification result.

In step S304, the conflicting test packet is managed, and the process returns to step S301.

In step S304, the management of the conflict is managed by the test script management system. For example, a test package can add, modify, or delete an excluded test package through a script management system.

Step S305. After the verification is passed, the task is performed according to the latest version of the test package.

In this embodiment, the test environment and the test package are verified, and the test failure caused by external factors and the test package itself can be avoided.

For the step S30 in the above embodiment, as another implementation manner, as shown in FIG. 4, the test task is executed according to the latest test package, and then includes:

Step S3021. When the test task is executed on the test machine, the operation completion flag is set for the test machine according to the execution state of the test task, wherein when the test task is completed, the operation completion flag is set to 1, when the test task is not completed, Set the operation completion flag to 0.

Step S3022. When the high priority test task with the priority level higher than the current test task accesses the test machine, query whether the test machine operation completion flag is set to 1, if yes, execute step S3023, if no, execute step S3024. .

In step S3022, when the test task is executed, each test task corresponds to a priority level, and the priority level of the test task can be queried by means of a table lookup. When the high priority test task is accessed, the flag judgment test is completed by the query operation. Whether the machine is performing a task, if the task is being executed, the current task is interrupted and a high-level test task is executed.

Step S3023. Access the test machine, execute a high-level test task, and clear the operation completion flag.

In step S3023, when the operation completion flag is set to 1, the test machine is in an idle state, the test can directly execute a new test task, and when the test task is executed, the operation completion flag is cleared to 0, indicating that the operation is being Execute the test task status.

Step S3024. Interrupt the current test task and access the test machine, and set the access violation flag to 1.

In step S3024, after the current test task is interrupted, when the new high priority test task is executed, the access conflict flag is set to 1, and the access conflict flag is set to 1 that the test task is being executed, and the interrupt instruction is no longer received, since To interrupt a test task, to avoid waiting for too many tasks, set the access violation flag to 1, perform the current test task and then perform other test tasks.

Step S3025. When the high priority test task is completed, the interrupted test task is continued to be executed, and the access conflict flag is set to zero.

In step S3025, setting the access violation flag to 0 means that an interrupt can be performed, that is, it can continue to be interrupted when the test task is executed.

This embodiment is a specific conflict management when there is a conflict in the test package. When the test is performed on the test machine, an access conflict flag is set for the test machine, when the low priority task accesses the test machine, and the test machine operation completion flag is cyclically queried. Whether it is set to 1, the interrupt service routine or high priority task interrupts the low priority task and accesses the test machine. After the query to test machine operation completion flag is set to 1, it is cleared to 0, and the access violation flag is set. 1, as the interrupt returns or the task is rescheduled, the low priority task continues to execute, it will detect that the test machine operation completion flag is 0, but the access violation flag is 1, then the loop query is exited. Retry access to the test machine. Through this management, test failures caused by test packet conflicts can be effectively avoided.

For the step S30 in the above embodiment, as another embodiment, after the test environment and the latest version of the test package are verified, the test task is executed according to the latest test package, and the user is alerted when a test error occurs during the execution of the test. You can test the code in the test package to get the problematic code, and identify the problematic code in the user alarm, so that the user can quickly modify the problematic code. The specific test process is as follows:

Compare the current version with the code of the last successful running version; specifically, for a test script that fails to run, the code in the test script is mainly the code of some class methods, and there is a tree-level hierarchical calling relationship between the methods. All methods can form a method call relationship tree. During the running of the test script, each time before running to enter a method, the output flag records the calling relationship between this method and other methods. By this method, the record is recorded. Test the call relationship between all the methods in the script, and finally form the method call hierarchy, compare the methods in the file according to the hierarchical relationship of the method call, for example, there are three files that record the current version of the class method code, respectively file A1 , file B1, file C1, at this time you also need to get the version code of the last three successful files, such as file A2, file B2, file C2, and then A1 and A2, B1 according to the hierarchical relationship in each file. Compare B2, C1, and C2 to find out if the code in the two versions has changed. Mark the change code found and compare the tagged code to the reason why the run failed.

Further, the tagged code is formed into a code set, and there may be multiple places where the changed code is marked by the above method, and the code set is repeatedly tested by sequentially reducing the code of the tag in the code set, and the code set is set from the code set. Remove the code of a tag, test the remaining code, and if it passes the test, identify the removed code. If not, remove the code of the next tag until the remaining code in the code set passes. Testing, for example, testing 1) removing the code of the first tag in the code set, identifying the code of the first tag by testing, entering the test by failing 2) removing the code of the second tag in the code set, The test identifies the code of the second tag, and so on until the remaining code in the code set passes the test.

By removing the code that changes the markup in the code set separately, you can accurately mark the problematic code in the code set.

Another embodiment of the present application provides a test task automation management apparatus 40. As shown in FIG. 5, the test task automation management apparatus 40 includes:

The test package obtaining module 401 obtains a test task to be executed, and obtains a corresponding test package according to the test task;

The test package update module 402 updates the code in the test package according to the newly added code in the system to obtain the latest version of the test package;

The test environment verification module 403 verifies the test environment in which the test task is executed. When the test environment satisfies the test condition, the test task is executed according to the latest version of the test package.

Further, as shown in FIG. 6, as an implementation manner, the test package update module 402 includes:

The code obtaining module 410 acquires the code in the written or new patch package when it is checked that the code server writes the code or downloads a new patch package;

The code compiling module 420 recompiles the test package according to the acquired code;

The test package validation module 430 determines that the recompiled test package is the latest test package.

The test environment verification module 401 verifies the test environment in which the test task is executed, and determines that the test environment meets the test conditions, including:

Determining that the test environment meets the test condition when verifying that the hardware device, the network state, and the software version that perform the test task meet the test condition;

Alternatively, when it is verified that the hardware device, the network state, and the software version of the test task satisfy the test condition, and it is determined that there is no conflict between the test package corresponding to the test task to be executed and the test package corresponding to the test task being executed, The test environment satisfies the test conditions.

For the specific working process of the module in the foregoing terminal device, reference may be made to the corresponding process in the foregoing method embodiment, and details are not described herein again.

Another embodiment of the present application provides a computer readable storage medium having computer readable instructions stored thereon, the computer readable instructions being executed by a processor to implement an automated test task management method in the above embodiments To avoid repetition, we will not repeat them here. Alternatively, when the computer readable instructions are executed by the processor, the functions of the modules/units in the test task automation management apparatus in the above embodiments are implemented. To avoid repetition, details are not described herein again.

Fig. 7 is a schematic diagram of a terminal device in this embodiment. As shown in FIG. 7, the terminal device 6 includes a processor 60, a memory 61, and computer readable instructions 62 stored in the memory 61 and operable on the processor 60. The processor 60 executes the computer readable instructions 62 to implement the various steps of the test task automation management method of the above-described embodiments, such as steps S10, S20, and S30 shown in FIG. Alternatively, when the processor 60 executes the computer readable instructions 62, the functions of the modules/units of the automated test task management apparatus in the above embodiments are implemented, as shown in FIG. 6, the test package acquisition module 401, the test package update module 402, and the test environment verification module. 403 features.

Illustratively, computer readable instructions 62 may be partitioned into one or more modules/units (such as forming an instruction segment), one or more modules/units being stored in memory 61 and executed by processor 60 to complete The data processing process of the present application.

The terminal device 6 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The terminal device may include, but is not limited to, the processor 60, the memory 61. It will be understood by those skilled in the art that FIG. 7 is only an example of the terminal device 6, and does not constitute a limitation of the terminal device 6, and may include more or less components than those illustrated, or combine some components, or different components. For example, the terminal device may further include an input/output device, a network access device, a bus, and the like.

The processor 60 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. General purpose processor can be micro The processor or the processor can also be any conventional processor or the like.

The memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or a memory of the terminal device 6. The memory 61 may also be an external storage device of the terminal device 6, such as a plug-in hard disk provided on the terminal device 6, a smart memory card (SMC), a Secure Digital (SD) card, and a flash memory card (Flash). Card) and so on. Further, the memory 61 may also include both an internal storage unit of the terminal device 6 and an external storage device. The memory 61 is used to store computer readable instructions and other programs and data required by the terminal device. The memory 61 can also be used to temporarily store data that has been output or is about to be output.

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units according to needs. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above. Each functional unit and module in the embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit, and the integrated unit may be implemented by hardware. Formal implementation can also be implemented in the form of software functional units. In addition, the specific names of the respective functional units and modules are only for the purpose of facilitating mutual differentiation, and are not intended to limit the scope of protection of the present application. For the specific working process of the unit and the module in the foregoing system, reference may be made to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the above embodiments, the descriptions of the various embodiments are different, and the parts that are not detailed or described in the specific embodiments may be referred to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

In the embodiments provided by the present application, it should be understood that the disclosed apparatus/terminal device and method, It can be implemented in other ways. For example, the device/terminal device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units. Or components may be combined or integrated into another system, or some features may be omitted or not performed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium. The computer readable instructions, when executed by a processor, may implement the steps of the various method embodiments described above. Wherein, the computer readable instructions comprise computer readable instruction code, which may be in the form of source code, an object code form, an executable file or some intermediate form or the like. The computer readable medium can include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard drive, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read-Only) Memory), random access memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media. It should be noted that the content contained in the computer readable medium may be appropriately increased according to the requirements of legislation and patent practice in the jurisdiction. Subtract, for example, in certain jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims

A test task automation management method, characterized in that the test task automation management method comprises:

Obtaining a test task to be executed, and obtaining a corresponding test package according to the test task;

Update the code in the test package according to the new code in the system to get the latest version of the test package;

Verifying the test environment in which the test task is executed. When it is determined that the test environment meets the test condition, the test task is executed according to the latest version of the test package.
The test task automation management method according to claim 1, wherein the code in the test package is updated according to the code added in the system to obtain the latest version of the test package, including:

Obtain the code in the written or new patch package when it is checked that the code server writes the code or downloads a new patch package;

Recompile the test package based on the code obtained;

Make sure the recompiled test package is the latest version of the test package.
The test task automation management method according to claim 1, wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

And verifying the test environment that performs the test task, when it is determined that the test environment meets the test condition, performing the test task according to the latest version of the test package, including:

Verify the hardware device, network status, and software version that performed the test task;

When the hardware device, the network status, and the software version meet the test condition, the test task is performed according to the latest version of the test package.
The test task automation management method according to claim 1, wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

Verifying a test environment in which the test task is executed. When the test environment meets the test condition, the test task is executed according to the latest version of the test package, including:

Verify that the hardware device, network status, and software version that performed the test task meet the test conditions When it is determined that there is no conflict between the test package corresponding to the test task to be executed and the test package corresponding to the test task being executed, it is determined that the test environment satisfies the test condition.
The test task automation management method according to claim 1, wherein the performing the test task according to the latest test package further comprises:

When the test task is executed on the test machine, the operation completion flag is set for the test machine according to the execution state of the test task, wherein when the test task is completed, the operation completion flag is set to 1, and when the test task is not completed, the operation is completed. The flag is set to 0;

When the high priority test task with a higher priority than the current test task accesses the test machine, query whether the test machine operation completion flag is set to 1;

If the operation completion flag is set to 1, access the test machine and clear the operation completion flag to 0;

If the operation completion flag is set to 0, the current test task is interrupted and the test machine is accessed, and the access violation flag is set to 1;

When the high priority test task is completed, the interrupted test task continues to be executed and the access violation flag is set to zero.
A test task automation management device, wherein the automated test task management device comprises:

a test package obtaining module, configured to acquire a test task to be executed, and obtain a corresponding test package according to the test task;

a test package update module for updating code in the test package according to new code in the system to obtain the latest version of the test package;

And a test environment verification module, configured to verify a test environment that executes the test task, and when it is determined that the test environment meets the test condition, execute the test task according to the latest version of the test package.
The test task automation management apparatus according to claim 6, wherein the test package update module comprises:

a code obtaining unit, configured to acquire code in the written or new patch package when checking that the code server writes the code or downloads a new patch package;

a code compilation unit for recompiling the test package according to the acquired code;

The test package confirmation unit is used to determine that the recompiled test package is the latest test package.
The test task automation management apparatus according to claim 6, wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

The test environment verification module, the test environment for executing the test task is verified, and when the test environment meets the test condition, the test task is executed according to the latest version of the test package, including:

When it is verified that the hardware device, the network state, and the software version that perform the test task meet the test conditions, it is determined that the test environment satisfies the test condition.
The test task automation management apparatus according to claim 6, wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

The test environment verification module verifies the test environment in which the test task is executed. When the test environment meets the test condition, the test task is executed according to the latest version of the test package, including:

Determining the test when the hardware device, the network state, and the software version of the test task satisfy the test condition, and it is determined that the test package corresponding to the test task to be executed does not conflict with the test package corresponding to the test task being executed. The environment meets the test conditions.
The test task automation management apparatus according to claim 6, wherein the test environment verification module is further configured to:

When the test task is executed on the test machine, the operation completion flag is set for the test machine according to the execution state of the test task, wherein when the test task is completed, the operation completion flag is set to 1, and when the test task is not completed, the operation is completed. The flag is set to 0;

When the high priority test task with a higher priority than the current test task accesses the test machine, query whether the test machine operation completion flag is set to 1;

If the operation completion flag is set to 1, access the test machine and clear the operation completion flag to 0;

If the operation completion flag is set to 0, the current test task is interrupted and the test machine is accessed, and the access violation flag is set to 1;

When the high priority test task is completed, the interrupted test task continues to be executed, and the The access violation flag is set to 0.
A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, wherein the processor executes the computer readable instructions as follows step:

Obtaining a test task to be executed, and obtaining a corresponding test package according to the test task;

Update the code in the test package according to the new code in the system to get the latest version of the test package;

Verifying the test environment in which the test task is executed. When it is determined that the test environment meets the test condition, the test task is executed according to the latest version of the test package.
The terminal device according to claim 11, wherein the code in the test package is updated according to a code added in the system to obtain a latest version of the test package, including:

Obtain the code in the written or new patch package when it is checked that the code server writes the code or downloads a new patch package;

Recompile the test package based on the code obtained;

Make sure the recompiled test package is the latest version of the test package.
The terminal device according to claim 11, wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

And verifying the test environment that performs the test task, when it is determined that the test environment meets the test condition, performing the test task according to the latest version of the test package, including:

Verify the hardware device, network status, and software version that performed the test task;

When the hardware device, the network status, and the software version meet the test condition, the test task is performed according to the latest version of the test package.
The terminal device according to claim 11, wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

Verifying a test environment in which the test task is executed. When the test environment meets the test condition, the test task is executed according to the latest version of the test package, including:

Determining the test when the hardware device, the network state, and the software version of the test task satisfy the test condition, and it is determined that the test package corresponding to the test task to be executed does not conflict with the test package corresponding to the test task being executed. The environment meets the test conditions.
The terminal device according to claim 11, wherein the performing the test task according to the latest test package further comprises:

When the test task is executed on the test machine, the operation completion flag is set for the test machine according to the execution state of the test task, wherein when the test task is completed, the operation completion flag is set to 1, and when the test task is not completed, the operation is completed. The flag is set to 0;

When the high priority test task with a higher priority than the current test task accesses the test machine, query whether the test machine operation completion flag is set to 1;

If the operation completion flag is set to 1, access the test machine and clear the operation completion flag to 0;

If the operation completion flag is set to 0, the current test task is interrupted and the test machine is accessed, and the access violation flag is set to 1;

When the high priority test task is completed, the interrupted test task continues to be executed and the access violation flag is set to zero.
A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by a processor, implement the following steps:

Obtaining a test task to be executed, and obtaining a corresponding test package according to the test task;

Update the code in the test package according to the new code in the system to get the latest version of the test package;

Verifying the test environment in which the test task is executed. When it is determined that the test environment meets the test condition, the test task is executed according to the latest version of the test package.
The computer readable storage medium of claim 16 wherein the code in the test package is updated according to new code in the system to obtain the latest version of the test package, including:

Obtain the code in the written or new patch package when it is checked that the code server writes the code or downloads a new patch package;

Recompile the test package based on the code obtained;

Make sure the recompiled test package is the latest version of the test package.
The computer readable storage medium of claim 16 wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

And verifying the test environment that performs the test task, when it is determined that the test environment meets the test condition, performing the test task according to the latest version of the test package, including:

Verify the hardware device, network status, and software version that performed the test task;

When the hardware device, the network status, and the software version meet the test condition, the test task is performed according to the latest version of the test package.
The computer readable storage medium of claim 16 wherein the test environment comprises a hardware device, a network state, and a software version of the test task;

Verifying a test environment in which the test task is executed. When the test environment meets the test condition, the test task is executed according to the latest version of the test package, including:

Determining the test when the hardware device, the network state, and the software version of the test task satisfy the test condition, and it is determined that the test package corresponding to the test task to be executed does not conflict with the test package corresponding to the test task being executed. The environment meets the test conditions.
The computer readable storage medium of claim 16, wherein the performing the test task according to the latest test package further comprises:

When the test task is executed on the test machine, the operation completion flag is set for the test machine according to the execution state of the test task, wherein when the test task is completed, the operation completion flag is set to 1, and when the test task is not completed, the operation is completed. The flag is set to 0;

When the high priority test task with a higher priority than the current test task accesses the test machine, query whether the test machine operation completion flag is set to 1;

If the operation completion flag is set to 1, access the test machine and clear the operation completion flag to 0;

If the operation completion flag is set to 0, the current test task is interrupted and the test machine is accessed, and the access violation flag is set to 1;

When the high priority test task is completed, the interrupted test task continues to be executed and the access violation flag is set to zero.