WO2018036167A1 - Test task executor assignment method, device, server and storage medium - Google Patents

Abstract

A test task executor assignment method comprises: acquiring test tasks established by each terminal in a test page; adding the acquired test tasks into a task queue according to the order of acquisition; reading the test tasks in the task queue; extracting a number of executors from the read test tasks; finding idle executor identifications in an idle executor identification set according to the number of executors; and assigning executors for the read test tasks according to the found idle executor identifications.

Description

Test task execution machine allocation method, device, server and storage medium

 This application is submitted to the Chinese Patent Office on August 22, 2016, and the application number is 201610704227.3 The title of the invention is the priority of the Chinese patent application entitled "Test Task Execution Machine Assignment Method and Apparatus", the entire contents of which are incorporated herein by reference.

[Technical Field]

The present application relates to the field of computer application technologies, and in particular, to a test task execution machine allocation method, apparatus, server, and storage medium.

【Background technique】

Currently in the field of testing technology, it is necessary to send a test task to an execution machine, and use the execution machine to perform a test task to obtain a test result. However, during the test, when the machine needs to be executed, the tester is required to apply to the executive manager for the execution machine. The executive manager manually assigns the corresponding number of actuators to the tester, and then the tester can execute the test task with the execution machine.

However, when multiple testers are requested to apply for the execution machine, the execution manager needs to manually allocate a corresponding number of execution machines for each tester, so that the test task execution machine allocation process is cumbersome and the execution manager manually assigns The speed and accuracy of the actuator are low, so that the tester cannot quickly and accurately obtain the corresponding number of actuators to perform the test task, resulting in inefficient distribution of the test task actuator.

[Summary of the Invention]

According to various embodiments disclosed herein, a test task execution machine allocation method, apparatus, server, and storage medium are provided.

A test task execution machine allocation method includes:

Obtain test tasks created by each terminal in the test page;

Add the test task to the task queue in the order of acquisition;

Reading test tasks in the task queue;

Extract the number of execution machines from the read test tasks;

Finding an idle execution machine identifier in the idle execution machine identification set according to the number of execution machines; and

An execution machine is assigned to the test task based on the found idle execution machine identification.

A test task actuator distribution device comprising:

The test task obtaining module is configured to obtain a test task created by each terminal in the test page;

a test task adding module, configured to add the test task to the task queue according to the obtaining order;

a task queue reading module, configured to read a test task in the task queue;

An execution quantity extraction module for extracting the number of execution machines from the read test tasks;

An execution identifier identification module, configured to search for an idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines; and

The test task sending module is configured to allocate an execution machine to the test task according to the found idle executable machine identifier.

A server comprising a memory and a processor, the memory storing computer executable instructions that, when executed by the processor, cause the processor to perform the following steps:

Obtain test tasks created by each terminal in the test page;

Add the test task to the task queue in the order of acquisition;

Reading test tasks in the task queue;

Extract the number of execution machines from the read test tasks;

Finding an idle execution machine identifier in the idle execution machine identification set according to the number of execution machines; and

An execution machine is assigned to the test task based on the found idle execution machine identification.

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

Obtain test tasks created by each terminal in the test page;

Add the test task to the task queue in the order of acquisition;

Reading test tasks in the task queue;

Extract the number of execution machines from the read test tasks;

Finding an idle execution machine identifier in the idle execution machine identification set according to the number of execution machines; and

An execution machine is assigned to the test task based on the found idle execution machine identification.

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

[Description of the Drawings]

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present application, and other drawings can be obtained according to the drawings without any creative work for those skilled in the art.

1 is an application environment diagram of a test task execution machine distribution system in an embodiment;

2 is a functional block diagram of a test server in a test task execution machine distribution system in an embodiment;

3 is a schematic flow chart of a test task execution machine allocation method in an embodiment;

4 is a schematic flowchart of a step of searching for an idle execution machine identifier in an embodiment;

5 is a schematic flowchart of a step of updating an execution machine identifier in a test task in an embodiment;

6 is a flow chart showing the steps of periodically detecting an actuator in an embodiment;

Figure 7 is a functional block diagram of a test task actuator distribution device in one embodiment;

Figure 8 is a functional block diagram of a test task actuator distribution device in another embodiment;

9 is a functional block diagram of an execution machine identification finding module in an embodiment;

10 is a functional block diagram of a test task sending module in an embodiment;

Figure 11 is a functional block diagram of a test task actuator distribution device in still another embodiment.

 【detailed description】

Exemplary embodiments embodying the features and advantages of the present application will be described in detail in the following description. It should be understood that the present invention is capable of various modifications in the various embodiments, and This application.

1 is an application environment diagram of a test task execution machine distribution system in an embodiment. The test task execution machine distribution system includes a plurality of terminals 110, a test server 120 and a plurality of execution machines 130, and the plurality of terminals 110 pass through the network and the test server 120. Connected, a plurality of execution machines 130 are connected to the test server 120 via a network. The test server 120 may also be multiple, and the execution machine 130 may specifically be a virtual machine. The terminal 110 may be a desktop computer or a mobile terminal, and the mobile terminal may specifically be at least one of a tablet computer, a smart phone, and a personal data assistant.

2 is a functional block diagram of the test server 120 in the test task execution machine distribution system of FIG. 1 in one embodiment. As shown in FIG. 2, test server 120 includes a processor coupled through a system bus, a non-volatile storage medium, an internal memory, and a network interface. The processor is used to provide computing and control capabilities to support the operation of the entire test server 120. The non-volatile storage medium of test server 120 stores operating system and computer executable instructions. Computer executable instructions are executable by the processor to implement a test task actuator allocation method provided in the following embodiments. The internal memory in test server 120 provides a cached operating environment for operating systems and computer executable instructions in a non-volatile storage medium. The network interface is used for network communication with the terminal 110 and the execution machine 130. It can be understood that the test server 120 can be implemented by a stand-alone server or a server cluster composed of a plurality of servers.

It will be understood by those skilled in the art that the structure shown in FIG. 2 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 test server to which the solution of the present application is applied. The specific test server may It includes more or less components than those shown in Figure 2, or some components are combined, or have different component arrangements.

As shown in FIG. 3, in one embodiment, a test task execution machine allocation method is provided. The method is illustrated by being applied to the test server 120 in the test task execution machine distribution system of FIG. The test task execution machine allocation program, the test task execution machine allocation program is used to implement the test task execution machine allocation method, and the test task execution machine allocation method specifically includes the following contents:

S302. Acquire a test task created by each terminal in the test page.

Specifically, the test page is displayed in the terminal 110, and the terminal 110 creates a test task in the test page. The test task specifically includes the test case and the number of the execution machine, and specifically includes the execution machine identifier. After the terminal 110 successfully creates a test task in the test page, the terminal 110 sends the test task to the test server 120. The test server 120 receives the test tasks transmitted by the respective terminals 110.

In one embodiment, the terminal 110 sends an access request to the test server 120. The test server 120 returns test page data to the terminal 110 according to the access request, and the terminal 110 renders the test page according to the received test page data.

S304. Add the test task to the task queue according to the acquisition order.

Specifically, after obtaining the test task created by each terminal 110, the test server 120 records the acquisition time of each test task, and adds the test task to the end of the task queue according to the order of the acquisition time.

In one embodiment, the test server 120 acquires one test task, stops acquiring the next test task, adds the obtained test task to the task queue, and acquires the next test task.

In an embodiment, the test task includes a priority, and after obtaining the test task, the test server 120 reads the priority in each test task, and sorts the test tasks according to the priority from high to low, according to the priority. The high to low order adds test tasks to the task queue in turn.

S306. Read a test task in the task queue.

S308. Extract the number of execution machines from the read test task.

Specifically, the test server 120 reads the test task in the task queue, and the test task may include the number of execution machines, the number of execution machines is the number of execution machines required for the test task, and the test server 120 extracts execution from the read test tasks. Number of machines.

S310. Find an idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines.

Specifically, the test server 120 stores an idle execution machine identifier, the idle execution machine identifier constitutes an idle execution machine identifier set, and the idle execution machine identifier corresponding execution machine is in an idle state. After the test server 120 extracts the number of execution machines from the read test tasks, it searches for the idle execution machine identifier in the idle execution machine identification set, and the number of found idle execution machine identifiers is equal to the number of extracted execution machines.

In an embodiment, the step S210 further includes the step of updating the idle execution machine identifier set, where the step specifically includes: counting the number of identifiers in the idle execution machine identifier set; comparing the number of execution machines with the number of identifiers; If the number of the identifiers is greater than the number of the identifiers, the identifiers of the executables corresponding to the executables in the idle state are re-acquired, and the obtained executable identifiers are stored in the idle executable identifier set.

Specifically, after extracting the number of execution machines in the test task, the test server 120 counts the number of identifiers in the idle execution machine identifier set, compares the number of statistics obtained by the statistics with the number of executed execution machines, and performs an identifier according to the idle execution machine. The number of identifiers in the set determines whether there is enough execution machine assigned to the test task. If the number of identifiers obtained by the statistics is greater than or equal to the number of executed machines, it means that there are enough actuators assigned to the test task; if the number of identifiers obtained by statistics is less than The number of executed execution machines indicates that there is not enough execution machine assigned to the test task, and the test server 120 re-detects the execution machine in the idle state and acquires the execution machine identifier corresponding to the execution machine in the idle state, which will be obtained. The execution machine identification is stored in the idle execution machine identification set.

S312. Assign an execution machine to the test task according to the found idle execution machine identifier.

Specifically, after finding the idle execution machine identifier, the test server 120 allocates the found execution machine 130 corresponding to the idle execution machine identifier to the test task read from the task queue, and reads the information from the task queue. The test task is sent to the executed execution machine 130 corresponding to the found idle executable identifier. After the execution machine 130 receives the test task, the test task is executed to generate a test result.

In this embodiment, after receiving the test task created by each terminal in the test page, the test task is added to the task queue according to the acquisition order, and the test task in the task queue is read to ensure that the test task is read in a certain order. This avoids the situation where the test task is congested and the test task is not processed for a long time. When the test task in the task queue is read, the idle execution machine identifier is searched from the idle execution machine identification set according to the number of execution machines in the read test task, and the idle task identifier is allocated according to the found idle execution machine identifier. Executing the corresponding machine of the machine identification, thereby simplifying the test task execution machine allocation operation process, quickly and accurately assigning the execution machine to the test task, and improving the test task execution machine allocation efficiency.

As shown in FIG. 4, in an embodiment, S310 specifically includes the step of searching for an idle execution machine identifier, and the step specifically includes the following content:

S402. Generate an execution machine scheduling request according to the number of execution machines.

Specifically, after the test server 120 extracts the number of execution machines from the read test tasks, the number of execution machines is encapsulated in the execution machine scheduling request, and the test server 120 can also encrypt the number of execution machines and encrypt the number of execution machines. The number of execution machines is encapsulated in the execution machine scheduling request. The scheduling server monitors the state of the execution machine, acquires the execution machine identifier corresponding to the execution machine in the idle state, and stores the obtained execution machine identifier in the idle execution machine identifier set.

S404. Send an execution schedule scheduling request to the scheduling server.

Specifically, after the test server 120 sends the execution scheduling request to the scheduling server, the timing starts. When the calculated time reaches the preset time, the test server 120 extracts the execution machine scheduling request, and sends the execution machine scheduling request to the scheduling server again.

S406. Receive an idle execution machine identifier returned by the scheduling server, where the idle execution machine identifier is obtained by the scheduling server in the idle execution machine identifier set according to the execution machine scheduling request.

Specifically, after the execution server scheduling request is generated according to the number of execution machines, the test server 120 sends an execution machine scheduling request to the scheduling server, where the scheduling server stores the idle execution machine identifier, and the idle execution machine identifier constitutes the idle execution machine identifier set. After receiving the execution machine scheduling request, the scheduling server extracts the number of execution machines in the execution machine scheduling request, searches for the idle execution machine identifier in the idle execution machine identification set according to the number of execution machines, and the scheduling server sends the found idle execution machine identifier. To the test server 120, the number of found idle performer IDs is equal to the number of extracted performers.

In this embodiment, after the scheduling server receives the execution machine scheduling request, the scheduling server searches for the idle execution machine identifier from the idle execution machine identifier set according to the number of execution machines in the execution machine scheduling request, and receives the found idle execution returned by the scheduling server. The machine identifier is used to search for the idle execution machine identifier by using the dispatching server, and the executed execution machine corresponding to the idle idle machine identifier is allocated to the test task, thereby improving the use efficiency of the execution machine.

As shown in FIG. 5, in an embodiment, S312 specifically includes the step of updating the execution machine identifier in the test task, and the step specifically includes the following content:

S502. Update the executable identifier in the read test task according to the found idle executable identifier.

Specifically, when the test server 120 detects that there is an execution machine identifier in the test task, the execution server identifier in the test task is deleted, and the found idle execution machine identifier is added to the test task to obtain the updated test task; When the server 120 does not detect that there is an execution machine identifier in the test task, the server finds the idle execution machine identifier to be added to the test task, and obtains the updated test task.

S504: Send the updated test task to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted execution machine corresponding to the idle execution machine identifier to the updated test task.

Specifically, the test server 120 sends the updated test task to the scheduling server. After receiving the test task sent by the test server 120, the scheduling server parses the test task, extracts the idle execution machine identifier in the test task, and schedules idle execution. The execution machine 130 corresponding to the machine identifier assigns the execution machine to the test task, and synchronously sends the received test task to the execution machine corresponding to the idle execution machine identifier, so that the execution machine performs the test task and generates the test result.

In an embodiment, the updated test task may further include verification information, and after receiving the updated test task, the scheduling server extracts the verification information in the updated test task, and verifies the verification information, after the verification is passed. The scheduling server extracts the idle execution machine identifier in the updated test task, and allocates an execution machine to the updated test task according to the extracted idle execution identifier.

In this embodiment, the executable identifier in the read test task is updated according to the found idle execution machine identifier, and after the updated test task is sent to the scheduling server, the scheduling server is caused to perform the idle execution machine according to the test task. The identification assigns an actuator to the test task, which increases the speed and accuracy of the assigned actuator.

As shown in FIG. 6, in an embodiment, a test task execution machine allocation method is provided. The method further includes the step of periodically detecting an execution machine, and the step specifically includes the following content:

S602. Regularly check whether the resource occupancy rate of each execution machine is less than a preset threshold.

Specifically, the test server 120 periodically acquires the resource occupancy rate of each execution machine according to the preset duration, and compares the resource occupancy rate of each execution machine with a preset threshold. When the resource occupancy rate is less than the preset threshold, the execution server is in the The idle state; when the resource occupancy rate is greater than or equal to the preset threshold, it indicates that the execution machine is in a state of performing a test task, and is not in an idle state. The resource occupancy rate may specifically be a thread occupancy rate.

S604. When it is detected that the resource occupancy rate of the execution machine is less than a preset threshold, extracting the detected execution machine identifier corresponding to the execution machine.

Specifically, the test server 120 adds an idle flag to the executable identifier corresponding to the execution machine whose resource occupancy is less than the preset threshold, and extracts the identifier of the executable carrying the idle token.

S606. Store the extracted execution machine identifier into the idle execution machine identifier set.

Specifically, the test server 120 stores the extracted execution machine identification into the idle execution machine identification set as the idle execution machine identification.

In this embodiment, by periodically detecting the resource occupancy rate of each execution machine, comparing the resource occupancy rate of each execution machine with a preset threshold to determine an execution machine in an idle state, and extracting an execution machine identifier of the idle execution machine, the extraction will be performed. The obtained execution machine identifier is stored in the idle execution machine identification set as the idle execution machine identification, so that the idle execution machine can be allocated again, improving the utilization efficiency of the idle execution machine.

As shown in FIG. 7, in one embodiment, a test task execution device distribution device 700 is provided. The device specifically includes: a test task acquisition module 702, a test task addition module 704, a task queue reading module 706, and an execution machine number. The extraction module 708, the execution machine identification lookup module 710, and the test task transmission module 712.

The test task obtaining module 702 is configured to obtain a test task created by each terminal in the test page.

The test task adding module 704 is configured to add the test task to the task queue in the order of acquisition.

The task queue reading module 706 is configured to read the test task in the task queue.

The execution machine quantity extraction module 708 is configured to extract the number of execution machines from the read test tasks.

The execution machine identifier finding module 710 is configured to search for an idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines.

The test task sending module 712 is configured to allocate an execution machine to the test task according to the found idle executable machine identifier.

In this embodiment, after receiving the test task created by each terminal in the test page, the test task is added to the task queue according to the acquisition order, and the test task in the task queue is read to ensure that the test task is read in a certain order. This avoids the situation where the test task is congested and the test task is not processed for a long time. When the test task in the task queue is read, the idle execution machine identifier is searched from the idle execution machine identification set according to the number of execution machines in the read test task, and the idle task identifier is allocated according to the found idle execution machine identifier. Executing the corresponding machine of the machine identification, thereby simplifying the test task execution machine allocation operation process, quickly and accurately assigning the execution machine to the test task, and improving the test task execution machine allocation efficiency.

As shown in FIG. 8 , in one embodiment, the test task execution device allocation device 700 further includes an identifier quantity statistics module 714 , an identifier quantity comparison module 716 , and an identifier reacquisition module 718 .

The identifier quantity statistics module 714 is configured to count the number of identifiers in the idle executable machine identifier set.

The identification quantity comparison module 716 is configured to compare the number of execution machines with the number of identifications.

The identifier re-acquisition module 718 is configured to re-acquire the execution machine identifier corresponding to the execution machine in the idle state when the number of execution machines is greater than the number of identifiers, and store the acquired execution machine identifier into the idle execution machine identifier set.

In this embodiment, after counting the number of identifiers in the idle execution machine identifier set, the number of execution machines required for the test task is compared with the number of statistical identifiers, and when the number of execution machines is greater than the number of identifiers, re-acquiring the idle state. Executing the machine identifier corresponding to the execution machine, storing the obtained execution machine identifier into the idle execution machine identifier set, so that there are enough idle execution machine identifiers in the idle execution machine identifier set, and ensuring that there are enough executions in the idle state. Machines can be assigned to test tasks, increasing the utilization of the actuators and increasing the success rate of assigning actuators to test tasks.

As shown in FIG. 9, in an embodiment, the execution machine identification lookup module 710 specifically includes a scheduling request generation module 710a, a scheduling request sending module 710b, and an execution machine identification receiving module 710c.

The scheduling request generating module 710a is configured to generate an execution machine scheduling request according to the number of executing machines.

The scheduling request sending module 710b is configured to send an execution machine scheduling request to the scheduling server.

The execution machine identifier receiving module 710c is configured to receive the idle execution machine identifier returned by the scheduling server, where the idle execution machine identifier is obtained by the scheduling server in the idle execution machine identifier set according to the execution machine scheduling request.

In this embodiment, after the scheduling server receives the execution machine scheduling request, the scheduling server searches for the idle execution machine identifier from the idle execution machine identifier set according to the number of execution machines in the execution machine scheduling request, and receives the found idle execution returned by the scheduling server. The machine identifier is used to search for the idle execution machine identifier by using the dispatching server, and the executed execution machine corresponding to the idle idle machine identifier is allocated to the test task, thereby improving the use efficiency of the execution machine.

As shown in FIG. 10, in one embodiment, the test task sending module 712 specifically includes a test task update module 712a and a test task synchronization module 712b.

The test task update module 712a is configured to update the execution machine identifier in the test task according to the found idle executable machine identifier.

The test task synchronization module 712b is configured to send the updated test task to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted idle execution machine to the updated test task. Identify the corresponding actuator.

In this embodiment, the executable identifier in the read test task is updated according to the found idle execution machine identifier, and after the updated test task is sent to the scheduling server, the scheduling server is caused to perform the idle execution machine according to the test task. The identification assigns an actuator to the test task, which increases the speed and accuracy of the assigned actuator.

As shown in FIG. 11 , in one embodiment, the test task execution device allocation device 700 further includes an execution machine detection module 720 , an execution machine identification extraction module 722 , and an execution machine identification storage module 724 .

The execution machine detection module 720 is configured to periodically detect whether the resource occupancy rate of each execution machine is less than a preset threshold.

The execution machine identifier extraction module 722 is configured to: when detecting that the resource occupancy rate of the execution machine is less than a preset threshold, extract the detected execution machine identifier corresponding to the execution machine;

The executable identifier storage module 724 is configured to store the extracted executable identifier into the idle executable identifier set.

In this embodiment, by periodically detecting the resource occupancy rate of each execution machine, comparing the resource occupancy rate of each execution machine with a preset threshold to determine an execution machine in an idle state, and extracting an execution machine identifier of the idle execution machine, the extraction will be performed. The obtained execution machine identifier is stored in the idle execution machine identification set as the idle execution machine identification, so that the idle execution machine is allocated again, and the utilization efficiency of the idle execution machine is improved.

Each of the above-described test task actuator distribution devices may be implemented in whole or in part by software, hardware, and combinations thereof. The network interface may be an Ethernet or a wireless network card. Each of the above modules may be embedded in a hardware form or independent of a processor in the server, or may be stored in a memory of the server in a software form, so that the processor calls to perform operations corresponding to the above modules. The processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.

One of ordinary skill in the art can understand that all or part of the process of implementing the foregoing embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM) or Random Access Memory (RAM).

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 is only the preferred embodiment of the present application, and is not intended to limit the embodiments of the present application. Those skilled in the art can make corresponding modifications or modifications in accordance with the main concepts and spirit of the present application. The scope of protection of the application shall be subject to the scope of protection required by the claims.

Claims (20)

A method for distributing test task execution machines, including: Obtain test tasks created by each terminal in the test page; Add the test task to the task queue in the order of acquisition; Reading test tasks in the task queue; Extract the number of execution machines from the read test tasks; Finding an idle execution machine identifier in the idle execution machine identification set according to the number of execution machines; and The execution machine is assigned to the read test task according to the found idle execution machine identifier. The method according to claim 1, wherein the method further includes: before the finding the idle execution machine identifier in the idle execution machine identifier set according to the number of the execution machines, the method further comprises: Counting the number of identifiers in the idle executable identifier set; Comparing the number of the execution machines with the number of the identifications; and If the number of the execution machines is greater than the number of the identifiers, the execution machine identifier corresponding to the execution machine in the idle state is re-acquired, and the obtained execution machine identifier is stored in the idle execution machine identifier set. The method according to claim 1, wherein the finding an idle execution machine identifier in the idle execution machine identification set according to the number of execution machines comprises: Generating an execution machine scheduling request according to the number of execution machines; Transmitting the execution machine scheduling request to a scheduling server; and Receiving an idle execution machine identifier returned by the scheduling server, where the idle execution machine identifier is obtained by the scheduling server in the idle execution machine identifier set according to the execution machine scheduling request. The method according to claim 1, wherein the assigning an execution machine to the read test task according to the found idle execution machine identifier comprises: Updating the executable identifier in the read test task according to the found idle executable identifier; and The updated test task is sent to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted execution machine corresponding to the idle execution machine identifier to the updated test task. The method of claim 1 further comprising: Regularly check whether the resource occupancy rate of each execution machine is less than a preset threshold; Extracting an execution machine identifier corresponding to the detected execution machine when detecting that the resource occupancy rate of the execution machine is less than a preset threshold; and The extracted execution machine identification is stored in the idle execution machine identification set. A test task actuator distribution device comprising: The test task obtaining module is configured to obtain a test task created by each terminal in the test page; a test task adding module, configured to add the test task to the task queue according to the obtaining order; a task queue reading module, configured to read a test task in the task queue; An execution quantity extraction module for extracting the number of execution machines from the read test tasks; An execution identifier identification module, configured to search for an idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines; and The test task sending module is configured to allocate an execution machine to the test task according to the found idle executable machine identifier. The device according to claim 6, further comprising: An identifier quantity statistics module, configured to count the number of identifiers in the idle executable identifier set; An identifier quantity comparison module, configured to compare the number of the execution machines with the number of the identifiers; and And an identifier re-acquisition module, configured to: when the number of the execution machines is greater than the number of the identifiers, re-acquire the identifier of the execution machine corresponding to the execution machine in the idle state, and store the acquired execution machine identifier to the idle execution machine identifier. In the collection. The device according to claim 6, wherein the execution device identification lookup module comprises: a scheduling request generating module, configured to generate an execution machine scheduling request according to the number of executing machines; a scheduling request sending module, configured to send the execution machine scheduling request to a scheduling server; and The execution machine identifier receiving module is configured to receive an idle execution machine identifier returned by the scheduling server, where the idle execution machine identifier is obtained by the scheduling server in the idle execution machine identifier set according to the execution machine scheduling request. The device according to claim 6, wherein the test task sending module comprises: a test task update module, configured to update an executable identifier in the test task according to the found idle executable identifier; and a test task synchronization module, configured to send the updated test task to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted idle execution to the updated test task. The machine corresponds to the actuator. The device according to claim 6, further comprising: The machine detection module is configured to periodically check whether the resource occupancy rate of each execution machine is less than a preset threshold; The execution machine identifier extraction module is configured to: when detecting that the resource occupancy rate of the execution machine is less than a preset threshold, extract an execution machine identifier corresponding to the detected execution machine; and The executable identifier storage module is configured to store the extracted executable identifier into the idle executable identifier set. A server comprising a memory and a processor, the memory storing computer executable instructions, the computer executable instructions being executed by the processor, such that the processor performs the following steps: Obtain test tasks created by each terminal in the test page; Add the test task to the task queue in the order of acquisition; Reading test tasks in the task queue; Extract the number of execution machines from the read test tasks; Finding an idle execution machine identifier in the idle execution machine identification set according to the number of execution machines; and The execution machine is assigned to the read test task according to the found idle execution machine identifier. The server according to claim 11, wherein said computer executable instructions are executed by said processor before said idle execution machine identification is found in said idle execution machine identification set according to said number of execution machines Having the processor perform the following steps: Counting the number of identifiers in the idle executable identifier set; Comparing the number of the execution machines with the number of the identifications; and If the number of the execution machines is greater than the number of the identifiers, the execution machine identifier corresponding to the execution machine in the idle state is re-acquired, and the obtained execution machine identifier is stored in the idle execution machine identifier set. The server according to claim 11, wherein the finding an idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines comprises: Generating an execution machine scheduling request according to the number of execution machines; Transmitting the execution machine scheduling request to a scheduling server; and Receiving an idle execution machine identifier returned by the scheduling server, where the idle execution machine identifier is obtained by the scheduling server in the idle execution machine identifier set according to the execution machine scheduling request. The server according to claim 11, wherein the assigning an execution machine to the read test task according to the found idle execution machine identifier comprises: Updating the executable identifier in the read test task according to the found idle executable identifier; and The updated test task is sent to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted execution machine corresponding to the idle execution machine identifier to the updated test task. The server of claim 11 wherein said computer executable instructions, when executed by said processor, further cause said processor to perform the steps of: Regularly check whether the resource occupancy rate of each execution machine is less than a preset threshold; Extracting an execution machine identifier corresponding to the detected execution machine when detecting that the resource occupancy rate of the execution machine is less than a preset threshold; and The extracted execution machine identification is stored in the idle execution machine identification set. One or more non-volatile storage media storing computer-executable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps: Obtain test tasks created by each terminal in the test page; Add the test task to the task queue in the order of acquisition; Reading test tasks in the task queue; Extract the number of execution machines from the read test tasks; Finding an idle execution machine identifier in the idle execution machine identification set according to the number of execution machines; and The execution machine is assigned to the read test task according to the found idle execution machine identifier. The non-volatile storage medium according to claim 16, wherein said computer executable instructions are one or more prior to finding an idle execution machine identifier in the idle execution machine identification set according to said number of execution machines When the processors are executed, the one or more processors are caused to perform the following steps: Counting the number of identifiers in the idle executable identifier set; Comparing the number of the execution machines with the number of the identifications; and If the number of the execution machines is greater than the number of the identifiers, the execution machine identifier corresponding to the execution machine in the idle state is re-acquired, and the obtained execution machine identifier is stored in the idle execution machine identifier set. The non-volatile storage medium according to claim 16, wherein the finding the idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines comprises: Generating an execution machine scheduling request according to the number of execution machines; Transmitting the execution machine scheduling request to a scheduling server; and Receiving an idle execution machine identifier returned by the scheduling server, where the idle execution machine identifier is obtained by the scheduling server in the idle execution machine identifier set according to the execution machine scheduling request. The non-volatile storage medium according to claim 16, wherein the assigning an execution machine to the read test task according to the found idle execution machine identifier comprises: Updating the executable identifier in the read test task according to the found idle executable identifier; and The updated test task is sent to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted execution machine corresponding to the idle execution machine identifier to the updated test task. The non-volatile storage medium of claim 16, wherein the computer-executable instructions are executed by one or more processors such that the one or more processors perform the following steps: Regularly check whether the resource occupancy rate of each execution machine is less than a preset threshold; Extracting an execution machine identifier corresponding to the detected execution machine when detecting that the resource occupancy rate of the execution machine is less than a preset threshold; and The extracted execution machine identification is stored in the idle execution machine identification set.