CN116303084A - Scheduling method and system for test cases of multi-terminal interaction - Google Patents

Abstract

The invention provides a scheduling method and a scheduling system for test cases with multi-terminal interaction, which relate to the field of automatic testing and comprise the following steps: sequentially setting corresponding priority weights for the analyzed test cases and adding the corresponding priority weights into a queue to be executed; the test cases in the queue to be executed are arranged in descending order according to the priority weight; after the arrangement is completed, sequentially popping up the test cases from the head of the queue to be executed and inquiring the matching agent machine, and executing the test cases in the selected agent after the matching agent machine is matched with the acceptable agent machine according to the dependent terminal of the test cases until all the test cases in the queue to be executed are executed; the execution efficiency of the agent machine in scheduling the test cases in the multi-terminal mode can be improved.

Description

A scheduling method and system for multi-terminal interactive test cases

technical field

The invention relates to the field of automated testing, in particular to a scheduling method and system for multi-terminal interactive test cases.

Background technique

Now the live broadcast industry is in full swing, such as the live broadcast classroom, which involves multi-terminal interaction scenarios. To achieve multi-terminal interaction, U l automation testing in the form of multi-role and multi-terminal forms is usually required. Usually, automated testing involves multiple terminal devices, such as browsers and iOS devices. , Android device, and client. These devices play roles to complete one or more test cases. If you want to ensure that the agent machine used to execute the test case can have four types of terminals at the same time, then the agent machine needs to mount multiple corresponding external devices, but not all use cases involve the role of four different terminal forms, and not all agent machines are equipped with a full set of equipment to support all terminals, so according to the dependence of the test case on the device, and then choose the most suitable An efficient scheduling scheme is particularly important for agent machines to execute use cases.

Therefore, the present invention proposes a method and system for scheduling test cases of multi-terminal interaction.

Contents of the invention

Aiming at the deficiencies of the prior art, the present invention proposes a multi-terminal interactive test case scheduling method and its system, which can improve the execution efficiency of an agent machine when scheduling multi-terminal test cases.

Technical scheme of the present invention is realized like this:

A method for dispatching test cases of multi-terminal interaction, comprising the steps of:

Add multiple test cases that need to rely on the terminal after analysis, and add them to the queue to be executed in turn, and set the corresponding priority weight. The priority weight is a configuration that can be decremented when there is no matching agent for polling and matching; each test case When entering the queue, the test cases in the queue to be executed are sorted in descending order according to the priority weight;

After the arrangement is completed, the test cases pop up sequentially from the head of the queue to be executed and query the matching agent machines, match the acceptable agent machines according to their dependent terminals and execute them in the selected agent, and the agent machines can be expanded and registered; The queue to be executed is used for enqueuing test cases and is in a polling state;

Wherein, the test case pops up sequentially from the head of the queue to be executed and queries the matching agent machine, further comprising:

After the test case at the head of the team pops up, query the state of the registered agent machine. If no agent machine is idle, the priority weight of the corresponding test case will be lowered, and the weighted test case will be re-entered into the waiting list. Execute the queue and arrange it in descending order in the queue to be executed; if there is an idle agent machine found in the query, it is necessary to further search for an agent machine that can carry the execution of the current test case according to its dependent side;

After querying, if all idle agent machines have no ability to undertake the current test case, the priority weight of the corresponding test case will be reduced, and the reduced test case will be put into the queue to be executed again and executed in the queue to be executed. Arrange in descending order; if there is an idle agent machine with the ability to undertake the current test case, then the agent machine that satisfies the conditions will be arranged in ascending order according to its carrying capacity, and the test case will be executed after selecting the first agent machine after the arrangement. The selected agent machine is set to an occupied state, that is, there is no idle state;

After the execution of the test case is completed, the agent machine that undertakes it is released and set to an idle state, waiting for the next query to match.

Preferably, after the test case file is acquired and parsed from the gitlab code base, the key information corresponding to the test case is stored into the database scheduling system.

Preferably, the key information includes the test case file name, description, author, and test case dependent end.

Preferably, the agent machine is registered in the dispatching system before execution, and registers the carrying capacity, and the carrying capacity of the agent machine includes a web end, an android end, an iOS end, and a client end.

The present invention also proposes a scheduling system for multi-terminal interactive test cases, including a suite management module, an agent machine management module, a task queue module, an environment module, and an execution record module, and the suite management module is used to obtain from the gitlab code base And analyze multiple test cases; the agent machine management module is used to register the agent machine and register its ability to undertake; the task queue module is used to set corresponding priority weights in turn for all test cases parsed from the suite management module and add them to be executed The queue is arranged, and is used for test case query and matching agent machines to execute on the selected agent machine; the environment module is used to manage the execution environment of the agent machine; the execution recording module is used to record test cases in the task queue The log of the execution process in the module and the report of the execution completion.

Compared with the prior art, the present invention has the following advantages:

With this scheme, when dealing with the scheduling of multi-terminal interactive test cases, there is no need to match the succession relationship between the test case and the execution machine in advance, and each test case is matched when it is executed, that is, according to the actual situation of the agent machine. Select the optimal agent machine that satisfies the conditions at the moment to avoid the uneven distribution of task matching numbers in multiple queues caused by early allocation, and resource utilization cannot be maximized, thereby improving the execution efficiency of the agent machine when scheduling multi-terminal test cases .

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

Fig. 1 is the flow chart of the scheduling method of a kind of multi-terminal interactive test case of the present invention;

FIG. 2 is a system block diagram of a scheduling system for multi-terminal interactive test cases according to the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer" etc. The indicated orientation or positional relationship is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the referred device or element must have a specific orientation, or in a specific orientation. construction and operation, therefore, should not be construed as limiting the invention. In addition, the terms "first", "second", "third", "fourth", etc. are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

In the description of the present invention, it should be noted that unless otherwise specified and limited, the terms "installation", "connection" and "connection" should be understood in a broad sense, for example, it can be a fixed connection or a detachable connection. Connected, or integrally connected; it may be mechanically connected or electrically connected; it may be directly connected or indirectly connected through an intermediary, and it may be the internal communication of two components. Those of ordinary skill in the art can understand the specific meanings of the above terms in the present invention in specific situations.

Example 1

This embodiment proposes a scheduling method for a multi-terminal interactive test case, as shown in FIG. 1 , including the following steps:

Add multiple test cases that need to rely on the terminal after analysis, and add them to the queue to be executed in turn, and set the corresponding priority weight. The priority weight is a configuration that can be decremented when there is no matching agent for polling and matching; each test case When entering the queue, the test cases in the queue to be executed are sorted in descending order according to the priority weight;

After the arrangement is completed, the test cases pop up sequentially from the head of the queue to be executed and query the matching agent machines, match the acceptable agent machines according to their dependent terminals, and then execute them in the selected agent. The agent machines can be expanded and registered at any time , and is executed in a distributed manner; the queue to be executed is ready for test cases to enter the queue at any time, and is in the state of polling at any time; there is no need to match the succession relationship between the test case and the execution machine in advance, and it is not necessary to consider the differences in the embodiment Whether there is a concurrent relationship between;

Wherein, the test case pops up sequentially from the head of the queue to be executed and queries the matching agent machine, further comprising:

After the test case at the head of the team pops up, query the state of the registered agent machine. If no agent machine is idle, the priority weight of the corresponding test case will be lowered, and the weighted test case will be re-entered into the waiting list. Execute the queue and arrange it in descending order in the queue to be executed; if there is an idle agent machine found in the query, it is necessary to further search for an agent machine that can carry the execution of the current test case according to its dependent side;

After querying, if all idle agent machines have no ability to undertake the current test case, the priority weight of the corresponding test case will be reduced, and the reduced test case will be put into the queue to be executed again and executed in the queue to be executed. Arrange in descending order; if there is an idle agent machine with the ability to undertake the current test case, then the agent machine that satisfies the conditions will be arranged in ascending order according to its carrying capacity, and the test case will be executed after selecting the first agent machine after the arrangement. The selected agent machine is set to an occupied state, that is, there is no idle state;

After the execution of the test case is completed, the agent machine that undertakes it is released and set to an idle state, waiting for the next query to match.

In this embodiment, the agent machine needs to be registered in the dispatching system before execution, and register the undertaking capability. The undertaking capability of the agent machine includes a web terminal, an android terminal, an iOS terminal, and a client terminal.

This embodiment also proposes a scheduling system for multi-terminal interactive test cases, including a suite management module, an agent machine management module, a task queue module, an environment module, and an execution record module, and the suite management module is used to extract from the gitlab code base Get and parse multiple test cases;

The agent machine management module is used to register the agent machine and register its ability to undertake;

The task queue module is used for all test cases parsed from the suite management module to set corresponding priority weights in turn and join the queue to be executed for arrangement, and is also used for test case query and matching agent machines to be executed on the selected agent machine;

The environment module is used to manage the execution environment of the agent machine;

The execution recording module is used for recording the log of the execution process of the test case in the task queue module and the report of the execution completion.

Example 2

In this embodiment, three typical use cases of the interactive classroom are added to the execution at the same time, and the scheduling process is as follows

1. Use Case Scenario

2. Agent list

The background is as above, and the scheduling process is as follows:

1. Click to execute the three use cases, and when they are added to the queue to be executed, according to the numerical weight, the priority order is: classroom answer, classroom sign-in, and classroom countdown;

2. Pop out the use case classroom answering queue of the team leader, look for the agent machine, and find out the idle agents are: agent1, agent2, agent3;

3. According to the dependent terminal of the classroom answering use case as web/Android/iOS and the ability to undertake the agent, filter out the agent machines that can undertake the execution as agent1 and agent2;

4. Sort the machines filtered in step 3 according to the positive order of capacity: agent1, agent2;

5. Give the classroom answering use case to agent1 for execution, and set the status of agent1 as occupied;

6. Repeat step 2. At this time, the use case of the leader of the team is classroom sign-in, and the idle devices that rely on web/Android/iOS are agent2 and agent3;

7. After capability matching, the device that can be accepted is agent2, and the use case is handed over to agent2 for execution, and the status of agent2 is set to occupied;

8. Repeat step 2. At this time, the use case of the team leader is classroom countdown, the dependent end is client, and the idle device is agent3;

9. According to the ability matching, there is no agent machine that can take over for the time being. After the class countdown weight is -10, re-join the queue and sort the weight. The first use case looks for a machine. If no other use cases are added at this time, the classroom countdown use case will poll until agent2 (only agent2 can take over the client side) and release the idle state after executing the current task, and hand over the use case to the agent until all the use cases in the queue are executed. complete.

That is, when there are many single UI automation test cases involving an uncertain number of multiple terminals, in the case that the services with different execution capabilities are dynamically scalable, the scheduling method of the test cases for multi-terminal interaction is used to improve the agent Efficiency in the execution of test cases.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. within the scope of protection.

Claims (5)

1. A scheduling method of test cases of multi-terminal interaction is characterized by comprising the following steps: the method comprises the following steps:

sequentially adding a plurality of test cases of the analyzed dependent terminal into a queue to be executed, and setting corresponding priority weights, wherein the priority weights are configured in a manner that the polling matching is descending when no adaptive agent exists; when each test case is enqueued, the test cases in the queue to be executed are arranged in descending order according to the priority weight;

after the arrangement is completed, sequentially popping up the test cases from the head of the queue to be executed, inquiring the matched agent machines, and executing the test cases in the selected agent machines after the matched agent machines are matched with the acceptable agent machines according to the dependent terminals of the test cases, wherein the agent machines can be expanded and registered; the queue to be executed is used for enqueuing the test cases and is in a polling state;

the test case sequentially pops up and inquires the matching agent machine from the head of the queue to be executed, and the method further comprises the following steps:

after the test case at the head of the queue pops up, inquiring the state of the registered agent machine, if no idle agent machine is inquired, reducing the weight of the priority of the corresponding test case, and re-entering the test case after the weight reduction into a queue to be executed and performing descending arrangement in the queue to be executed; if the idle agent machine is inquired, the agent machine capable of bearing and executing is further required to be searched for the current test case according to the dependent end;

through inquiry, if all the idle agent machines do not have the capability of accepting the current test case, the priority weight of the corresponding test case is reduced, and the test case after the weight reduction is put into the queue to be executed again and is arranged in the queue to be executed in a descending order; if the spare agent machines have the capability of accepting the current test case, the agent machines meeting the conditions are arranged in an ascending order according to the bearing capability, the test case starts to execute after the first agent machine after the test case is selected to be arranged is accepted, and the selected agent machines are set to be in an occupied state, namely in a non-idle state;

after the test case is executed, the agent machine adapting to the test case is released and set to be in an idle state, and the next query is matched.

2. The method for scheduling test cases for multi-terminal interaction according to claim 1, wherein the method comprises the following steps:

and after the test case file is acquired and analyzed from the gitlab code base, the key information corresponding to the test case is put into a scheduling system.

3. The method for scheduling test cases with multi-terminal interaction according to claim 2, wherein the key information comprises a test case file name, a description, an author and a test case dependent end.

4. The method for scheduling test cases for multi-terminal interaction of claim 1, wherein the agent machine is registered in a scheduling system before execution, and performs registration of a receiving capability, wherein the receiving capability of the agent machine comprises a web side, an android side, an iOS side and a client side.

5. The scheduling system applying the scheduling method of the multi-terminal interactive test cases according to any one of claims 1-4 is characterized by comprising a suite management module, a reagent machine management module, a task queue module, an environment module and an execution record module, wherein the suite management module is used for acquiring and analyzing a plurality of test cases from a gitlab code base;

the agent machine management module is used for registering the agent machine and registering the carrying capacity of the agent machine;

the task queue module is used for arranging the digital priority weights of all the test cases analyzed from the suite management module, adding the test cases into a queue to be executed, and executing the test cases in the selected agent machine after inquiring and matching the agent machine;

the environment module is used for managing the execution environment of the agent machine;

the execution recording module is used for recording log of the execution process of the test case in the task queue module and a report of execution completion.

Images