WO2021013124A1

WO2021013124A1 - Method and device for managing automated testing resources

Info

Publication number: WO2021013124A1
Application number: PCT/CN2020/103017
Authority: WO
Inventors: 胡文萍
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-07-24
Filing date: 2020-07-20
Publication date: 2021-01-28
Also published as: CN112286651A

Abstract

Disclosed in the embodiments of the present disclosure are a method and device for managing automated testing resources. The method comprises: regularly checking whether an idle resource exists; if an idle resource exists, sorting tasks of resources to be allocated according to weights; calculating whether the idle resource matches the task having the highest weight; and if yes, allocating resources for the sub-task having the highest priority in the task having the highest weight.

Description

Method and device for automatic test resource management

Technical field

The embodiments of the present disclosure relate to, but are not limited to, automated testing technology.

Background technique

Automated testing occupies an increasingly important position in hardware equipment testing, but the scarcity of test resources, especially large hardware equipment and instrument resources, has led to the problem of automated test tasks occupying resources more and more, so how to allocate resources fairly for tasks Has become an urgent problem to be solved.

At present, most of the test resource allocation is to manually occupy resources according to the task level, first come first served, this strategy will not cause imbalance problems when the task execution time is relatively short, but now the time to execute a task may be It lasts for more than 10 to 20 hours. In this process, resources cannot be released, and other tasks can only be in a long waiting process.

In addition, if the task execution completion time is in the middle of the night, such an unattended time, the resources will not be released until the testers are on duty the next day, which will cause waste. This first-come-first-served strategy can also cause important tasks to be delayed or even starve to death.

Summary of the invention

The embodiment of the present disclosure provides a method for automatic test resource management, which includes: regularly checking whether there are idle resources; when there are idle resources, sorting tasks of the resources to be allocated according to weights; and calculating whether the idle resources have the highest weight And when matching, allocate resources to the subtask with the highest priority among the tasks with the highest weight.

The embodiment of the present disclosure also provides a device for automatic test resource management, including: a checking unit, used to periodically check whether there are idle resources; a sorting unit, when there are idle resources, tasks to be allocated resources are performed according to weights Sorting; a calculation unit for calculating whether the idle resource matches the task with the highest weight; and an allocation unit for allocating resources to the subtask with the highest priority in the task with the highest weight when matching.

The embodiment of the present disclosure also provides a device for automated test resource management, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and the computer program is executed by the processor. Implement the above-mentioned resource management method during execution.

The embodiments of the present disclosure also provide a computer-readable storage medium on which an information processing program is stored, and when the information processing program is executed by a processor, the steps of the above resource management method are implemented.

Description of the drawings

The accompanying drawings are used to provide a further understanding of the technical solution of the present disclosure, and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present disclosure, and do not constitute a limitation to the technical solution of the present disclosure. In the attached drawing,

FIG. 1 is a schematic flowchart of a method for automated test resource management according to an embodiment of the present disclosure;

FIG. 2 is another schematic flowchart of a method for automated test resource management according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of the architecture of an automated test resource management system according to an embodiment of the present disclosure; and

Fig. 4 is a schematic structural diagram of an apparatus for automatic test resource management according to an embodiment of the present disclosure.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present disclosure clearer, the embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in this application and the features in the embodiments can be combined with each other arbitrarily if there is no conflict.

The steps shown in the flowchart of the drawings may be executed in a computer system such as a set of computer-executable instructions. In addition, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

FIG. 1 is a schematic flowchart of a method for automated test resource management according to an embodiment of the present disclosure. As shown in FIG. 1, the method includes steps 101 to 104.

In step 101, it is periodically checked whether there are free resources.

In step 102, when there are idle resources, the tasks to be allocated resources are sorted according to their weights.

In step 103, it is calculated whether the idle resource matches the task with the highest weight.

In step 104, when there is a match, resources are allocated to the subtask with the highest priority among the tasks with the highest weight.

After allocating resources to the subtask with the highest priority among the tasks with the highest weight, the method further includes: reducing the weight of the task with the highest weight according to a preset ratio; if there are remaining free resources, waiting again Tasks that allocate resources are sorted by weight; calculate whether the remaining idle resources match the task with the highest weight; when matching, allocate resources to the subtask with the highest priority among the tasks with the highest weight; and so on, until There are no free resources.

The method further includes: executing the subtask with the highest priority according to the allocated resources; and releasing the allocated resources when the execution of the subtask with the highest priority is completed or fails.

The method further includes: when there is no match, allocating resources to the subtask with the highest priority among the tasks with the second highest weight.

The method further includes: when there is no subtask that needs to be allocated resources in any task to be allocated resources, deleting the task to be allocated resources.

The method further includes: when the execution of the subtask with the highest priority is completed, saving the execution result; checking whether the task in which the subtask with the highest priority is located is all completed; and when all are completed, collecting all the tasks in the task The execution result of the subtask.

The method further includes: receiving tasks of resources to be allocated; and splitting each task of resources to be allocated into one or more subtasks according to business attributes.

Fig. 2 is another schematic flowchart of a method for automated test resource management according to an embodiment of the present disclosure.

This embodiment is applied to the system shown in FIG. 3. As shown in Figure 3, the system includes: task module, resource module, message queue (MQ), database (database, DB) and resource pool.

Each module entity uses MQ to complete message transmission. This system needs to have multiple MQ channels, using Queue mode.

Specifically, the message queue MQ includes the following queues.

1. The task queue task.queue, which transfers tasks to be allocated resources.

2. The subtask queue subTask.queue, which is used to deliver resource messages to the subtask execution module. After the subtask execution module listens to the message, it will extract the corresponding resource and perform a test operation on the resource.

3. The resource release queue release.resource.queue, which is used to transfer the resource information that needs to be released to the resource management module through the message queue after the execution of the subtask is completed.

4. The execution failed subtask queue subTaskFailed.queue, which is used to inform the resource management module that a certain subtask has failed to execute and resources need to be released.

The task module includes a task management module, which is used to receive tasks for resources to be allocated, and split each task for resources to be allocated into one or more subtasks according to business attributes.

The resource module includes a task collection unit to be assigned and a resource management module.

The resource management module monitors the MQ message, and if it receives the task of the resource to be allocated, it puts it into the local Task List (TL) of the resource to be allocated.

Specifically, the task management module determines all subtasks and the priority order of the subtasks in the task according to user needs, and at the same time assigns an initial weight W to the task, and also needs to specify the environmental conditions (for example, machine Frame, main control, line card, number of boards, etc.). The way to split subtasks needs to be determined according to specific business attributes. The principle is that subtasks must be executable entities, for example, a testable module or a testable group.

The task management module is also used to trigger task execution and generate task queue messages.

Specifically, the task management module issues the task to the task-to-be-allocated collection unit (also called a resource allocation unit) to apply for appropriate resources. The resource allocation unit manages a task queue of resources to be allocated currently, and adds tasks to the resource queue to be allocated after listening to the task queue message.

The distribution engine maintained in the background is a timing worker (for example, it can be processed once a minute, and it can also be modified as appropriate). When the timing window comes, the distribution engine first sorts the task queue according to the weight, and the highest weight is the first. The low-weight ones are ranked last, and then the resource allocation services are accepted according to the weight in turn. After the subtask matches the resource, the subtask resource message is released to the subtask queue.

Specifically, when the time window for the resource management module to allocate workers comes, the resource module first checks whether there are idle resources in the current resource pool, and if there are idle resources, the idle resources are processed in turn. The processing process each time is as follows: The tasks in the list TL are sorted according to the weight W; and the task T1 with the highest weight is obtained, and the idle resource is calculated whether the idle resource matches the task T1. If it matches, the resource is allocated to the highest priority subtask ST1 of the task T1; if it does not match, Then get the task T2 with the second highest weight, and do the same calculation, and so on. Another situation is that if the task has no subtasks that need to be allocated, the task needs to be deleted from the local task list TL of resources to be allocated.

Repeat the above steps until the idle resources in the resource pool are processed.

The matching work can be completed by the entity of the matching module (not shown in the figure, the matching module can be set in the resource module). The matching module obtains the resource requirements of the task, that is, the resource requirements of the task. For example, the resource requirements of the task are: at least one device, a line card of a coil detector (visual leak detector, VLD), and a master control of the T1042, and no attention is paid to other attributes. According to task requirements and each attribute requirement, the resources of the resource pool are matched one by one. If it can be matched, the subtask assigned to the resource is returned to the subtask execution module, and if it does not match, the next resource is replaced.

The task module also includes a subtask execution module, which is used to occupy resources for test execution. The execution process is done at the granularity of subtasks. Therefore, each subtask will occupy different test resources, and the results of the execution will be written into the database.

When the subtask is completed, the task module will check whether the parent task of the subtask is completed, and if it is completed, it will collect the results of all the subtasks and send emails to notify the relevant parties.

After the execution of the subtask is completed, a resource release message will be generated to the resource release queue release.resource.queue. After the resource pool management module reads the resource release message, it releases the resource and reclaims the resource into the resource pool.

As shown in Figure 2, the method includes the following steps.

Step 1. Task generation.

Specifically, the system user creates a task with a version number in the task module, and then executes step 1.1 to write to the database.

Step 2. Query task.

Specifically, it includes: step 2.1, query the database; step 2.2, the database returns the query result (with execution status); and step 2.3, return the result.

Step 3. Start the task.

Step 4. The task module adds tasks to the task queue.

The resource management module executes step 0, that is, after monitoring the task queue message, executes step 4.1 to add the task to the task list (Task List). For example, the priority (weight) of a task is 100 by default, and the weight of a subtask is reduced by 1.

Step 5. Find the task after matching the resource.

The resource management module executes step 0, that is, starts the worker every minute to determine whether there are idle resources. After matching the resource (that is, there is an idle resource), sort the tasks to be allocated resources according to the weight; calculate whether the idle resource matches the task with the highest weight; when it matches, it is the priority among the tasks with the highest weight The highest subtask allocates resources.

Step 6. When the resource meets the subtask execution condition, add the subtask to the subtask queue.

Perform step 6.1 to modify the status of the subtask.

The execution module proceeds to step 0, that is, monitoring.

That is, after listening to the subtask queue message, proceed to step 7.

Step 7. Execution step.

Step 0 in Figure 2 indicates that this step is the following worker task thread, which is similar to a daemon thread, which always exists and will be executed once every minute, and has no relationship with other steps.

In addition, the resource management module is a big module name, which is used to manage all resources. The local resource management module is a module that records the current task resources and resource information in the resource management module. It can be said that the local resource management module is resource management The most important part of the module.

The technical solution provided by this embodiment can realize fine-grained execution and scheduling of task execution, overcome the extensive scheduling dimension of using tasks as the scheduling unit in resource scheduling in the prior art, and can complete dynamic and intelligent allocation of resources And management, through intelligent resource occupation and release solutions to solve the problem of inefficient resource occupation caused by manual occupation. It solves the problem of dynamic resource allocation of automated tasks in the distributed environment of hardware automated testing, and can effectively avoid long-term occupation of resources by large tasks with a long execution time in the non-discriminatory mode, leading to "starvation" of other tasks with higher priority .

Fig. 4 is a schematic structural diagram of an apparatus for automatic test resource management according to an embodiment of the present disclosure. As shown in FIG. 4, the device includes: a checking unit for checking whether there are idle resources at regular intervals; a sorting unit for sorting tasks to be allocated resources according to weights when there are idle resources; a calculation unit for calculating Whether the idle resource matches the task with the highest weight; and an allocation unit configured to allocate resources to the subtask with the highest priority among the tasks with the highest weight when matching.

The device also includes: a weight management unit, configured to reduce the weight of the task with the highest weight according to a preset ratio after allocating resources to the subtask with the highest priority among the tasks with the highest weight; the ranking unit also uses If there are remaining free resources, the tasks to be allocated are again sorted according to their weights; the calculation unit is also used to calculate whether the remaining free resources match the task with the highest weight; the allocation unit also uses When matching, resources are allocated to the subtask with the highest priority among the tasks with the highest weight. And so on, until there are no free resources.

The device also includes: an execution unit for executing the subtask with the highest priority according to the allocated resources; and a release unit for releasing the subtask when the execution of the subtask with the highest priority is completed or fails. The resources allocated.

The matching unit is further configured to allocate resources to the subtask with the highest priority among the tasks with the second highest weight when there is no match.

The matching unit is further configured to delete any task to be allocated when there is no subtask that needs to be allocated in any task to be allocated.

The device also includes: a saving unit for saving the execution result when the execution of the subtask with the highest priority is completed; a checking unit for checking whether the task of the subtask with the highest priority is all completed; and collecting The unit is used to collect the execution results of all subtasks in the task when all are completed.

The device also includes: a task management unit for receiving tasks of resources to be allocated; and splitting each task of resources to be allocated into one or more subtasks according to business attributes.

The checking unit, sorting unit, calculating unit, allocation unit, releasing unit, checking unit, and collecting unit in this embodiment can be set in the resource module shown in FIG. 3.

The weight management unit, execution unit, and task management unit in this embodiment can be set in the task module shown in FIG. 3.

The embodiment of the present disclosure also provides a device for automated test resource management, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and the computer program is executed by the processor. When executed, the processor implements the resource management method according to the foregoing embodiment of the present disclosure.

The embodiments of the present disclosure also provide a computer-readable storage medium having an information processing program stored on the computer-readable storage medium. When the information processing program is executed by a processor, the processor implements the foregoing implementation according to the present disclosure. Examples of resource management methods.

A person of ordinary skill in the art can understand that all or some of the steps, functional modules/units in the system, and apparatus in the methods disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may consist of several physical components. The components are executed cooperatively. Some or all components may be implemented as software executed by a processor, such as a digital signal processor or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Flexible, removable and non-removable media. Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media .

Claims

A method for automated test resource management, including:

Regularly check whether there are idle resources;

In response to the existence of idle resources, sort the tasks to be allocated resources according to their weights;

Calculate whether the idle resource matches the task with the highest weight; and

In response to the match, resources are allocated to the subtask with the highest priority among the tasks with the highest weight.
The method according to claim 1, wherein after the step of allocating resources to the subtask with the highest priority among the tasks with the highest weight, the method further comprises:

Reduce the weight of the task with the highest weight according to a preset ratio;

In response to remaining idle resources, the tasks to be allocated resources are again sorted according to their weights;

Calculating whether the remaining idle resources match the task with the highest weight;

In response to matching, resources are allocated to the subtask with the highest priority among the tasks with the highest weight,

And so on, until there are no free resources.
The method according to claim 1, further comprising:

Execute the subtask with the highest priority according to the allocated resources; and

In response to the completion or failure of the execution of the subtask with the highest priority, the allocated resources are released.
The method according to claim 1, further comprising:

In response to the mismatch, resources are allocated to the subtask with the highest priority among the tasks with the second highest weight.
The method according to claim 1, further comprising:

In response to that there is no subtask requiring resource allocation among the tasks to be allocated resources, the task to be allocated resources is deleted.
The method according to claim 3, further comprising:

In response to the completion of the execution of the subtask with the highest priority, save the execution result;

Check whether the tasks of the subtasks with the highest priority are all completed; and

In response to all completion, the execution results of all subtasks in the task are collected.
The method according to claim 1, further comprising:

Receiving the task of the resource to be allocated;

Split the task of the resource to be allocated into one or more subtasks according to the business attributes.
An automatic test resource management device, including:

The checking unit is used to periodically check whether there are idle resources;

The sorting unit is used to sort tasks to be allocated resources according to their weights when there are idle resources;

A calculation unit for calculating whether the idle resource matches the task with the highest weight; and

The allocation unit is configured to allocate resources to the subtask with the highest priority among the tasks with the highest weight when matching.
A device for automatic test resource management includes a memory, a processor, and a computer program stored on the memory and capable of running on the processor. When the computer program is executed by the processor, the processor A method for implementing resource management according to any one of claims 1-7.
A computer-readable storage medium having an information processing program stored thereon, and when the information processing program is executed by a processor, the processor implements the resource management method according to any one of claims 1-7.