CN111190810A - Method, device, server and storage medium for executing test task - Google Patents
Method, device, server and storage medium for executing test task Download PDFInfo
- Publication number
- CN111190810A CN111190810A CN201910792744.4A CN201910792744A CN111190810A CN 111190810 A CN111190810 A CN 111190810A CN 201910792744 A CN201910792744 A CN 201910792744A CN 111190810 A CN111190810 A CN 111190810A
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- equipment
- idle
- attribute information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
Abstract
The disclosure relates to a method, a device, a server and a storage medium for executing a test task, and belongs to the technical field of distributed scheduling. The method comprises the following steps: acquiring a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively; determining an idle device among the at least one device based on the acquired state information of the at least one device; for each test case, determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case in the idle equipment based on the acquired attribute information of the idle equipment; and respectively sending each test case to the corresponding target equipment. In the embodiment of the disclosure, the server may split the test task into a plurality of test cases, different test cases may be allocated to different target devices, and the test cases may be executed in parallel between different target devices. The overall testing efficiency is higher.
Description
Technical Field
The present disclosure relates to the field of distributed scheduling technologies, and in particular, to a method, an apparatus, a server, and a storage medium for executing a test task.
Background
Before the application is formally released, the application may be tested in multiple devices. Firstly, at least one test task corresponding to an application program needs to be established, and the at least one test task is issued to the currently idle equipment, wherein the equipment issued by each test task is different. Then, the device receiving the test task can execute the test task and output the test result. The time consumed by one device for executing one test task is long, and the overall test efficiency is low.
Disclosure of Invention
In order to overcome the problems in the related art, the present disclosure provides the following technical solutions:
according to a first aspect of embodiments of the present disclosure, there is provided a method of performing a test task, the method comprising:
acquiring a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively;
determining an idle device among the at least one device based on the acquired state information of the at least one device;
for each test case, determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case in the idle equipment based on the acquired attribute information of the idle equipment;
and respectively sending each test case to the corresponding target equipment.
Optionally, the multiple test cases include a test case of a common type and/or a test case of a special type, and a complexity of an equipment requirement condition corresponding to the test case of the special type is higher than a complexity of the equipment requirement condition corresponding to the test case of the common type.
Optionally, the determining, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case, based on the obtained attribute information of the idle device, includes:
for each test case of a special type, preferentially determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case of the special type in the idle equipment based on the acquired attribute information of the idle equipment, and taking the target equipment as equipment allocated to the test case of the special type;
for each common type test case, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the common type test case as equipment allocated to the common type test case in the idle equipment which is not allocated to each special type test case based on the acquired attribute information of the idle equipment which is not allocated to each special type test case.
Optionally, the method further comprises:
acquiring the execution times of the plurality of test cases;
for each test case, determining, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case based on the obtained attribute information of the idle device, including:
and for each test case executed at a time, determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case in the idle equipment based on the acquired attribute information of the idle equipment, and using the target equipment as the equipment which is distributed to execute the test case with the current times.
Optionally, the method further comprises:
acquiring test case grouping information, wherein the test case grouping information is used for indicating at least two test cases which are distributed to be executed in the same equipment in the plurality of test cases and executing sequential execution sequence information of the at least two test cases;
for each test case, determining, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case based on the obtained attribute information of the idle device, including:
for at least two test cases corresponding to the test case grouping information, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the at least two test cases in the idle equipment based on the acquired attribute information of the idle equipment;
for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the test cases in the idle equipment based on the acquired attribute information of the idle equipment;
the sending each test case to the corresponding target device respectively includes:
for at least two test cases corresponding to the test case grouping information, sending the at least two test cases and the corresponding sequential execution sequence information for executing the at least two test cases to corresponding target equipment;
and for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, respectively sending the test case to corresponding target equipment.
According to a second aspect of embodiments of the present disclosure, there is provided an apparatus for performing a test task, the apparatus comprising:
the acquisition module is used for acquiring a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively;
a determining module, configured to determine, based on the obtained status information of the at least one device, an idle device among the at least one device;
the determining module is further configured to determine, for each test case, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case, based on the acquired attribute information of the idle device;
and the sending module is used for sending each test case to the corresponding target equipment.
Optionally, the multiple test cases include a test case of a common type and/or a test case of a special type, and a complexity of an equipment requirement condition corresponding to the test case of the special type is higher than a complexity of the equipment requirement condition corresponding to the test case of the common type.
Optionally, the plurality of test cases include a common type of test case and a special type of test case, and the determining module is configured to:
for each test case of a special type, preferentially determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case of the special type in the idle equipment based on the acquired attribute information of the idle equipment, and taking the target equipment as equipment allocated to the test case of the special type;
for each common type test case, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the common type test case as equipment allocated to the common type test case in the idle equipment which is not allocated to each special type test case based on the acquired attribute information of the idle equipment which is not allocated to each special type test case.
Optionally, the obtaining module is further configured to obtain the execution times of the multiple test cases;
the determining module is configured to determine, for each test case executed at a single time, a target device, in the idle device, of which attribute information can satisfy a device requirement condition corresponding to the test case, based on the acquired attribute information of the idle device, as a device allocated to execute the test case of the current number of times.
Optionally, the obtaining module is further configured to obtain test case grouping information, where the test case grouping information is used to indicate at least two test cases that are allocated to be executed in the same device in the multiple test cases and sequential execution sequence information for executing the at least two test cases;
the determining module is configured to: for at least two test cases corresponding to the test case grouping information, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the at least two test cases in the idle equipment based on the acquired attribute information of the idle equipment; for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the test cases in the idle equipment based on the acquired attribute information of the idle equipment;
the sending module is used for sending the at least two test cases and the corresponding sequential execution sequence information for executing the at least two test cases to corresponding target equipment for the at least two test cases corresponding to the test case grouping information; and for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, respectively sending the test case to corresponding target equipment.
According to a third aspect of embodiments of the present disclosure, there is provided a server comprising a processor, a communication interface, a memory, and a communication bus, wherein:
the processor, the communication interface and the memory complete mutual communication through the communication bus;
the memory is used for storing a computer program;
the processor is used for executing the program stored in the memory so as to realize the method for executing the test task.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium having stored therein a computer program, which when executed by a processor implements the above-mentioned method of performing a test task.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
in the embodiment of the disclosure, the server may split the test task into a plurality of test cases, and allocate target devices capable of meeting device requirement conditions corresponding to the test cases to each test case respectively. Different test cases are distributed to different target devices, and the test cases can be executed in parallel among the different target devices. Therefore, a plurality of target devices simultaneously execute the same test task together, the time consumed by each target device for executing one test case is short, and the target devices execute the same test task together, so that the time consumed by the execution of the same test task is short, and the overall test efficiency is high.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. In the drawings:
FIG. 1 is a block diagram illustrating a system for performing test tasks in accordance with an exemplary embodiment;
FIG. 2 is a flowchart illustrating a method of performing a test task in accordance with an exemplary embodiment;
FIG. 3 is a flowchart illustrating a method of performing a test task in accordance with an exemplary embodiment;
FIG. 4 is a flowchart illustrating a method of performing a test task in accordance with an exemplary embodiment;
FIG. 5 is a flowchart illustrating a method of performing a test task in accordance with an exemplary embodiment;
FIG. 6 is a flowchart illustrating a method of performing a test task in accordance with an exemplary embodiment;
FIG. 7 is a schematic diagram illustrating a parsing test task in accordance with an exemplary embodiment;
FIG. 8 is a schematic view of a test kit shown in accordance with an exemplary embodiment;
FIG. 9 is a flowchart illustrating a method of performing a test task in accordance with an exemplary embodiment;
FIG. 10 is a block diagram illustrating an apparatus for performing test tasks in accordance with an exemplary embodiment;
fig. 11 is a schematic diagram illustrating a configuration of a server according to an example embodiment.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The embodiment of the disclosure provides a method for executing a test task, which may be implemented by a server, and specifically may be implemented by a system for executing a test task. Fig. 1 is a schematic structural diagram of a system for executing a test task according to an embodiment of the present disclosure. In the system, a server, a PC (Personal Computer) terminal, and a device may be included. The server may be configured to schedule the devices, allocate each test case to each device, and may also serve as a scheduler. The PC end may be a single PC end or a PC end cluster, each PC end may run an agent application program, and the PC end cluster may also be referred to as an agent distributed cluster. The device may be a device for testing the test case, and after the test case is executed in the device, the device may output a test result. The equipment can be computer, mobile phone and other equipment. The technician may determine, based on the test results, whether the test case fails to achieve the expected results and is a valid case.
An exemplary embodiment of the present disclosure provides a method for executing a test task, and as shown in fig. 2, a processing flow of the method may include the following steps:
step S201, obtaining a plurality of test cases and device requirement conditions corresponding to the test cases.
In implementation, when a test task needs to be executed by the device, the test task can be uploaded to the server, and the test task and a device requirement condition corresponding to the test task can be carried in a test request in an application and sent to the server. One test task may include a plurality of test cases. For example, the payment test tasks may include logging in test cases, paying out test cases, and logging out test cases.
The test case included in the test task may be independent or dependent. The independent test cases can be tested without depending on other test cases, and the dependent test cases can be tested depending on other test cases. The dependent test cases need to be executed when the preset conditions are reached or in the preset environment, and the preset conditions or the preset environment are obtained after the execution of other test cases is finished.
The server can obtain a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively. The test cases may include a general type of test case and/or a special type of test case. The complexity of the equipment requirement condition corresponding to the special type of test case is higher than that corresponding to the common type of test case.
Each test case corresponds to a device requirement condition of a type of a device operating system, and if one test case is designed for an Android (Android is an operating system based on Linux free and open source code), it needs to be executed with a mobile phone in which the Android operating system is installed, and if one test case is designed for an iOS (iOS is a mobile operating system developed by apple inc.) operating system, it needs to be executed with a mobile phone in which the iOS operating system is installed. The same test case is difficult to be executed in both the Android operating system and the iOS operating system. Therefore, if a test case is not a special type test case, the device requirement condition corresponding to the test case at least includes the type condition of the device operating system. If a test case is a special type test case, the device requirement condition corresponding to the test case may include other conditions besides at least the type condition of the device operating system. Therefore, the complexity of the device requirement condition corresponding to the special type of test case is higher than that corresponding to the common type of test case.
In the embodiment of the present disclosure, the plurality of test cases may individually include a common type test case, may also individually include a special type test case, or may include a common type test case and a special type test case.
Step S202, based on the acquired state information of the at least one device, determining an idle device in the at least one device.
In an implementation, before the server determines an idle device among the at least one device based on the obtained status information of the at least one device, the server may receive the status information of the device reported by the agent distributed cluster.
Each PC end in the agent distributed cluster can monitor the online state and the offline state of a plurality of devices managed by the PC end, and determine the working states of the plurality of devices managed by the PC end.
For each PC side, as shown in fig. 3, device information may be obtained from each device it manages through a polling mechanism. If the device information of any device S can be acquired, it indicates that the device S is in an online state, and if the device information of any device S cannot be acquired, it indicates that the device S is in an offline state. The PC terminal can sequentially acquire the device information of each device, compare the acquired device information with the pre-recorded device information, and if the device information of which device is lacked, indicate that the device corresponding to the lacked device information is in an offline state. The PC terminal can repeatedly execute the steps of sequentially acquiring the equipment information of each equipment according to a preset period and comparing the acquired equipment information of the equipment with the equipment information of the equipment recorded in advance. After the steps are repeatedly executed each time, the PC terminal can determine whether a new device is on line or not through the comparison result. If a new device is online, the new device can be registered with the server, and the local device record is updated. If no new device is online, it may be determined whether a new device is offline. If a new device goes offline, the server may be notified that a new device goes offline while updating the local device record.
For a device that has just come online, its operating state may be set to an idle state. For a device just connected to a test case, the working state of the device can be set to be a busy state. For the device which finishes executing the test case, the working state of the device can be set to be an idle state. The PC can maintain the state information of each device managed by the PC, and report the state information of each device managed by the PC to the server. And when the server receives the reported idle equipment, distributing the test case for the idle equipment.
The server may receive the status information of the devices reported by the agent distributed cluster, and determine an idle device in the at least one device. The idle equipment is used for executing the test cases, the test cases can not be distributed to the busy equipment any more, and after the busy equipment is determined to finish executing the test cases, the test cases are distributed to the equipment changed from busy to idle.
Step S203, for each test case, based on the acquired attribute information of the idle device, determining, in the idle device, a target device whose attribute information can satisfy the device requirement condition corresponding to the test case.
In implementation, the server may obtain each test case one by one, and when a test case is obtained, for a current test case, a target device which has attribute information that can meet a device requirement condition corresponding to the current test case and is not allocated may be determined in an idle device as a device allocated to the current test case.
And step S204, respectively sending each test case to the corresponding target equipment.
In implementation, the server may allocate a corresponding target device to each test case, and the target device may execute the test case and output a test result. The server can send the test case and the device identifier of the corresponding target device to the PC end for managing the target device, and the PC end for managing the target device can forward the received test case to the target device corresponding to the device identifier, so that the target device executes the test case.
In the embodiment of the disclosure, the server may split the test task into a plurality of test cases, and allocate target devices capable of meeting device requirement conditions corresponding to the test cases to each test case respectively. Different test cases are distributed to different target devices, and the test cases can be executed in parallel among the different target devices. Therefore, a plurality of target devices simultaneously execute the same test task together, the time consumed by each target device for executing one test case is short, and the target devices execute the same test task together, so that the time consumed by the execution of the same test task is short, and the overall test efficiency is high.
Based on the same inventive concept, an exemplary embodiment of the present disclosure provides a method for executing a test task, as shown in fig. 4, a processing flow of the method may include the following steps:
step S401, a plurality of test cases and equipment requirement conditions corresponding to the test cases are obtained.
The plurality of test cases comprise common type test cases and special type test cases.
In implementation, when a test task needs to be executed by the device, the test task can be uploaded to the server, and the test task and a device requirement condition corresponding to the test task can be carried in a test request in an application and sent to the server. One test task may include a plurality of test cases.
The test case included in the test task may be independent or dependent. The independent test cases can be tested without depending on other test cases, and the dependent test cases can be tested depending on other test cases. The dependent test cases need to be executed when the preset conditions are reached or in the preset environment, and the preset conditions or the preset environment are obtained after the execution of other test cases is finished.
The server can obtain a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively. The test cases may include a general type of test case and a special type of test case. The complexity of the equipment requirement condition corresponding to the special type of test case is higher than that corresponding to the common type of test case.
Each test case corresponds to a device requirement condition of a type of a device operating system, and if one test case is designed for an Android (Android is an operating system based on Linux free and open source code), it needs to be executed with a mobile phone in which the Android operating system is installed, and if one test case is designed for an iOS (iOS is a mobile operating system developed by apple inc.) operating system, it needs to be executed with a mobile phone in which the iOS operating system is installed. The same test case is difficult to be executed in both the Android operating system and the iOS operating system. Therefore, if a test case is not a special type test case, the device requirement condition corresponding to the test case at least includes the type condition of the device operating system. If a test case is a special type test case, the device requirement condition corresponding to the test case may include other conditions besides at least the type condition of the device operating system. Therefore, the complexity of the device requirement condition corresponding to the special type of test case is higher than that corresponding to the common type of test case.
In the embodiment of the present disclosure, the plurality of test cases may include a common type of test case and a special type of test case. The user can specify the equipment requirement condition corresponding to the test case of the common type and the equipment requirement condition corresponding to the test case of the special type. When a user submits a test task, a scheduling strategy of a special type of test case can be selected. In the equipment requirement condition corresponding to the special type of test case, the attribute information of the equipment required by the test case can be described, for example, "Android mobile phone, 4.4 systems and above, 2G memory and above, mobile phone brand X" is filled in.
Step S402, determining an idle device among the at least one device based on the acquired status information of the at least one device.
In an implementation, before the server determines an idle device among the at least one device based on the obtained status information of the at least one device, the server may receive the status information of the device reported by the agent distributed cluster.
Each PC end in the agent distributed cluster can monitor the online state and the offline state of a plurality of devices managed by the PC end, and determine the working states of the plurality of devices managed by the PC end.
For a device that has just come online, its operating state may be set to an idle state. For a device just connected to a test case, the working state of the device can be set to be a busy state. For the device which finishes executing the test case, the working state of the device can be set to be an idle state. The PC can maintain the state information of each device managed by the PC, and report the state information of each device managed by the PC to the server. And when the server receives the reported idle equipment, distributing the test case for the idle equipment.
The server may receive the status information of the devices reported by the agent distributed cluster, and determine an idle device in the at least one device. The idle equipment is used for executing the test cases, the test cases can not be distributed to the busy equipment any more, and after the busy equipment is determined to finish executing the test cases, the test cases are distributed to the equipment changed from busy to idle.
Step S403, for each test case of a special type, preferentially determining, based on the acquired attribute information of the idle device, a target device, as a device allocated to the test case of the special type, in the idle device, where the attribute information can satisfy a device requirement condition corresponding to the test case of the special type.
In implementation, a task pool and a device pool may be set in the server, a test case to be executed may be stored in the task pool, and a device identifier of a free device may be stored in the device pool. After any test case in the task pool is executed, the test case in the task pool can be deleted. After any free device in the device pool is assigned to a test task, the status information of that device may be set to busy information.
The multiple test cases can comprise common type test cases and special type test cases, and due to the fact that the complexity of equipment requirement conditions corresponding to the special type test cases is high and difficult to meet, proper equipment can be selected for the special type test cases preferentially.
The server can acquire the test cases of the special types one by one, and when one test case of the special type is acquired, for the current test case of the special type, the target device which has attribute information capable of meeting the device requirement condition corresponding to the current test case of the special type and is not allocated can be determined in the idle device to serve as the device allocated to the current test case of the special type.
Step S404, for each common-type test case, based on the obtained attribute information of the device which is not assigned to each special-type test case in the idle devices, determining a target device whose attribute information can satisfy the device requirement condition corresponding to the common-type test case, as the device assigned to the common-type test case, from the devices which are not assigned to each special-type test case in the idle devices.
In implementation, after the server preferentially allocates the corresponding target device to each special type of test case, the corresponding target device may be allocated to each general type of test case in the remaining idle devices.
The server can acquire the test cases of the common types one by one, and when one test case of the common type is acquired, for the current test case of the common type, in the idle equipment which is not allocated to the test cases of the special types, the target equipment which has attribute information capable of meeting the equipment requirement condition corresponding to the current test case of the common type and is not allocated can be determined to be used as the equipment allocated to the current test case of the common type.
As shown in fig. 5, in step S501, the server may obtain the device identifiers of the idle devices in the device pool. Step S502 may obtain a test task in the task pool, analyze the test task, and obtain a plurality of test cases included in the test task. Step S503 may obtain a plurality of test cases in the task pool, and obtain an equipment requirement condition corresponding to each test case. In step S504, the attribute information of each idle device may be traversed. Step S505, finding a test case that each idle device can support. And the idle equipment capable of supporting all test cases is selected preferentially. Step S506, the least idle devices capable of supporting all test cases are placed in the device list. And preferentially selecting the idle device which can support the largest number of test cases. Step S507, putting the most idle devices capable of supporting all test cases into the device list. In the list, the number of idle devices is at most the same as the total number of all test cases, and if the number of idle devices capable of supporting test cases is sufficient, the list includes the same number of idle devices as the total number of all test cases. Step S508, generating data, and labeling the case information of the test case that can be supported by each idle device. The final generated data may be as follows: {1000 { ' special ': 100 ', ' normal ': 102 },1001 { ' special ': 101 }. Wherein, 'special' may be a special type test case, 'normal' may be a general type test case, numerals in square brackets may represent case information, and 1000 and 1001 may represent device identifications. After any test case is executed on the target device, the corresponding entry in the data may be deleted.
Step S405, sending each test case to a corresponding target device.
In implementation, the server may allocate a corresponding target device to each test case, and the target device may execute the test case and output a test result. The server can send the test case and the device identifier of the corresponding target device to the PC end for managing the target device, and the PC end for managing the target device can forward the received test case to the target device corresponding to the device identifier, so that the target device executes the test case.
In the embodiment of the disclosure, the server may split the test task into a plurality of test cases, and allocate target devices capable of meeting device requirement conditions corresponding to the test cases to each test case respectively. Different test cases are distributed to different target devices, and the test cases can be executed in parallel among the different target devices. Therefore, a plurality of target devices simultaneously execute the same test task together, the time consumed by each target device for executing one test case is short, and the target devices execute the same test task together, so that the time consumed by the execution of the same test task is short, and the overall test efficiency is high.
Based on the same inventive concept, an exemplary embodiment of the present disclosure provides a method for executing a test task, as shown in fig. 6, a processing flow of the method may include the following steps:
step S601, obtaining a plurality of test cases and device requirement conditions corresponding to the test cases.
The plurality of test cases comprise common type test cases and special type test cases.
In implementation, when a test task needs to be executed by the device, the test task can be uploaded to the server, and the test task and a device requirement condition corresponding to the test task can be carried in a test request in an application and sent to the server. One test task may include a plurality of test cases.
The test case included in the test task may be independent or dependent. The independent test cases can be tested without depending on other test cases, and the dependent test cases can be tested depending on other test cases. The dependent test cases need to be executed when the preset conditions are reached or in the preset environment, and the preset conditions or the preset environment are obtained after the execution of other test cases is finished.
The server can obtain a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively. The test cases may include a general type of test case and/or a special type of test case. The complexity of the equipment requirement condition corresponding to the special type of test case is higher than that corresponding to the common type of test case.
Each test case corresponds to a device requirement condition of a type of a device operating system, and if one test case is designed for an Android (Android is an operating system based on Linux free and open source code), it needs to be executed with a mobile phone in which the Android operating system is installed, and if one test case is designed for an iOS (iOS is a mobile operating system developed by apple inc.) operating system, it needs to be executed with a mobile phone in which the iOS operating system is installed. The same test case is difficult to be executed in both the Android operating system and the iOS operating system. Therefore, if a test case is not a special type test case, the device requirement condition corresponding to the test case at least includes the type condition of the device operating system. If a test case is a special type test case, the device requirement condition corresponding to the test case may include other conditions besides at least the type condition of the device operating system. Therefore, the complexity of the device requirement condition corresponding to the special type of test case is higher than that corresponding to the common type of test case.
Step S602, obtaining the execution times of a plurality of test cases.
And when any test task is a compatible/adaptive type test task, the test task corresponds to the execution times. In order to verify whether the test task is compatible/adaptable, the test task can be executed in different devices respectively, and if the test task can be successfully executed in each device, the test task is indicated to be compatible/adaptable. For example, a test task includes 10 test cases, which need to be executed in 1000 different devices, and for each test case in the test task, the test case also needs to be executed in 1000 different devices. The number of test case executions may be 1000 at this time.
Step S603, determining an idle device among the at least one device based on the acquired status information of the at least one device.
In an implementation, before the server determines an idle device among the at least one device based on the obtained status information of the at least one device, the server may receive the status information of the device reported by the agent distributed cluster.
Each PC end in the agent distributed cluster can monitor the online state and the offline state of a plurality of devices managed by the PC end, and determine the working states of the plurality of devices managed by the PC end.
For a device that has just come online, its operating state may be set to an idle state. For a device just connected to a test case, the working state of the device can be set to be a busy state. For the device which finishes executing the test case, the working state of the device can be set to be an idle state. The PC can maintain the state information of each device managed by the PC, and report the state information of each device managed by the PC to the server. And when the server receives the reported idle equipment, distributing the test case for the idle equipment.
The server may receive the status information of the devices reported by the agent distributed cluster, and determine an idle device in the at least one device. The idle equipment is used for executing the test cases, the test cases can not be distributed to the busy equipment any more, and after the busy equipment is determined to finish executing the test cases, the test cases are distributed to the equipment changed from busy to idle.
Step S604, for each test case executed at a time, based on the acquired attribute information of the idle device, determining, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case, as a device allocated to execute the test case of the current number of times.
In implementation, when any test task is a compatible/adaptive type test task, a plurality of test cases included in the test task correspond to the execution times N, and each test case needs to be executed N times. Each time any test case is executed, a target device needs to be selected. As shown in fig. 7, the server may obtain one test task, analyze the test task, and obtain a plurality of test cases, including test case 1, test case 2, test cases 3, … …, and test case N.
Optionally, the method provided by the embodiment of the present disclosure may further include: and acquiring test case grouping information.
The test case grouping information is used for indicating at least two test cases which are distributed in the plurality of test cases and executed in the same equipment, and the sequential execution sequence information of the at least two test cases.
In implementation, the test suite may be dynamically configured, and a user may write a test suite configuration file and upload the test suite configuration file to the server. The test suite configuration file may carry test case grouping information. In the test case grouping information, at least two test cases which are used for indicating that a plurality of test cases are distributed to be executed in the same device may be included, and the at least two test cases are dependent test cases. The dependent test cases need to be executed when the preset conditions are reached or in the preset environment, and the preset conditions or the preset environment are obtained after the execution of other test cases is finished. The paths of the dependent test cases are deeper.
The case information of the at least two interdependent test cases can be added to the test suite configuration file, so that the server can allocate the at least two interdependent test cases to execute in the same target device when allocating the target device to the test cases. Meanwhile, if an execution sequence exists between the at least two test cases, the sequential execution sequence information of the at least two test cases can be added into the test suite configuration file, so that the server can send the sequential execution sequence information of the at least two test cases to the target device, and the target device can arrange the execution sequence of the at least two test cases according to the sequential execution sequence information. As shown in fig. 8, the server may obtain a test task, analyze the test task based on the test suite configuration file, and obtain a plurality of test suites and a plurality of test cases, including test suite 1, test suite 2 … …, and case N, where test suite 1 includes test case 1 and test case 2, and test suite 2 includes test case 2 and test case 3. It should be noted that the same test case may be included between different test suites.
Optionally, the method provided by the embodiment of the present disclosure may further include: for at least two test cases corresponding to the test case grouping information, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the at least two test cases in the idle equipment based on the acquired attribute information of the idle equipment; and for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case in the idle equipment based on the acquired attribute information of the idle equipment.
In implementation, at least two test cases in the test suite may be allocated to the same target device, and independent test cases that do not belong to the test suite may be allocated to different target devices.
Step S605, sending each test case to a corresponding target device.
In implementation, the server may allocate a corresponding target device to each test case, and the target device may execute the test case and output a test result. The server can send the test case and the device identifier of the corresponding target device to the PC end for managing the target device, and the PC end for managing the target device can forward the received test case to the target device corresponding to the device identifier, so that the target device executes the test case.
Alternatively, step S605 may include: for at least two test cases corresponding to the test case grouping information, sending the at least two test cases and the corresponding sequential execution sequence information for executing the at least two test cases to corresponding target equipment; and respectively sending the test cases to corresponding target equipment for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases.
In implementation, at least two test cases in the test suite may be allocated to the same target device, the server may send the at least two test cases in the test suite to the target device, and may also send corresponding sequential execution order information to the target device, and the target device may arrange an execution order of the at least two test cases according to the sequential execution order information. The independent test cases not belonging to the test suite can be distributed to different target devices, and the server can send the independent test cases not belonging to the test suite to the corresponding target devices.
As shown in fig. 9, the server may obtain the test task and determine whether the test task is a compatible/adaptive type of test task. Other types of device allocation policies may be implemented if the test task is not a compatible/adaptive type of test task. If the test task is a compatible/adaptive type test task, the device requirement condition list corresponding to a plurality of test cases included in the test task can be read. And determining the corresponding relation between the equipment and the test cases based on the equipment requirement condition list, and generating an equipment and test case list, wherein the list is used for indicating which equipment can execute which test cases. And when detecting that the idle equipment exists, issuing the equipment and the test case list to the agent distributed cluster. The agent distributed cluster determines a test case and device list based on the device and test case list, which is used to indicate which test cases can be executed by which devices. And distributing the test cases to each target device based on the test cases and the device list. And detecting whether all the test cases are executed completely, if not, switching to the step of executing the equipment requirement condition list, determining the corresponding relation between the equipment and the test cases and generating the equipment and test case list. And if all the test cases are completely executed, the test tasks can be determined to be completely executed.
In the embodiment of the disclosure, the server may split the test task into a plurality of test cases, and allocate target devices capable of meeting device requirement conditions corresponding to the test cases to each test case respectively. Different test cases are distributed to different target devices, and the test cases can be executed in parallel among the different target devices. Therefore, a plurality of target devices simultaneously execute the same test task together, the time consumed by each target device for executing one test case is short, and the target devices execute the same test task together, so that the time consumed by the execution of the same test task is short, and the overall test efficiency is high.
Yet another exemplary embodiment of the present disclosure provides an apparatus for performing a test task, as shown in fig. 10, the apparatus including:
an obtaining module 1001, configured to obtain multiple test cases and device requirement conditions corresponding to the test cases respectively;
a determining module 1002, configured to determine, based on the obtained status information of the at least one device, an idle device in the at least one device;
the determining module 1002 is further configured to determine, for each test case, a target device in the idle device, where attribute information of the target device can meet a device requirement condition corresponding to the test case, based on the obtained attribute information of the idle device;
a sending module 1003, configured to send each test case to a corresponding target device respectively.
Optionally, the multiple test cases include a test case of a common type and/or a test case of a special type, and a complexity of an equipment requirement condition corresponding to the test case of the special type is higher than a complexity of the equipment requirement condition corresponding to the test case of the common type.
Optionally, the multiple test cases include a common type test case and a special type test case, and the determining module 1002 is configured to:
for each test case of a special type, preferentially determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case of the special type in the idle equipment based on the acquired attribute information of the idle equipment, and taking the target equipment as equipment allocated to the test case of the special type;
for each common type test case, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the common type test case as equipment allocated to the common type test case in the idle equipment which is not allocated to each special type test case based on the acquired attribute information of the idle equipment which is not allocated to each special type test case.
Optionally, the obtaining module 1001 is further configured to obtain the execution times of the multiple test cases;
the determining module 1002 is configured to, for each test case executed at a single time, determine, based on the acquired attribute information of the idle device, a target device, in the idle device, of which the attribute information can meet a device requirement condition corresponding to the test case, as a device allocated to execute the test case of the current number of times.
Optionally, the obtaining module 1001 is further configured to obtain test case grouping information, where the test case grouping information is used to indicate at least two test cases that are allocated to be executed in the same device in the multiple test cases and sequential execution order information for executing the at least two test cases;
the determining module 1002 is configured to: for at least two test cases corresponding to the test case grouping information, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the at least two test cases in the idle equipment based on the acquired attribute information of the idle equipment; for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the test cases in the idle equipment based on the acquired attribute information of the idle equipment;
the sending module 1003 is configured to send, to at least two test cases corresponding to the test case grouping information, the at least two test cases and corresponding sequential execution order information for executing the at least two test cases to corresponding target devices; and for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, respectively sending the test case to corresponding target equipment.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
In the embodiment of the disclosure, the server may split the test task into a plurality of test cases, and allocate target devices capable of meeting device requirement conditions corresponding to the test cases to each test case respectively. Different test cases are distributed to different target devices, and the test cases can be executed in parallel among the different target devices. Therefore, a plurality of target devices simultaneously execute the same test task together, the time consumed by each target device for executing one test case is short, and the target devices execute the same test task together, so that the time consumed by the execution of the same test task is short, and the overall test efficiency is high.
It should be noted that: in the device for executing a test task according to the above embodiment, when executing a test task, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the server is divided into different functional modules to complete all or part of the functions described above. In addition, the device for executing the test task and the method for executing the test task provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.
Fig. 11 shows a schematic structural diagram of a server 1900 provided in an exemplary embodiment of the present disclosure. The server 1900 may have a large difference due to different configurations or performances, and may include one or more processors (CPUs) 1910 and one or more memories 1920. The memory 1920 has stored therein at least one instruction, which is loaded and executed by the processor 1910 to implement the method for performing testing tasks as described in the above embodiments.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method of performing a test task, the method comprising:
acquiring a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively;
determining an idle device among the at least one device based on the acquired state information of the at least one device;
for each test case, determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case in the idle equipment based on the acquired attribute information of the idle equipment;
and respectively sending each test case to the corresponding target equipment.
2. The method according to claim 1, wherein the plurality of test cases include a test case of a general type and/or a test case of a special type, and a complexity of a device requirement condition corresponding to the test case of the special type is higher than a complexity of the device requirement condition corresponding to the test case of the general type.
3. The method according to claim 2, wherein the plurality of test cases include test cases of a common type and test cases of a special type, and the determining, for each test case, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case in the idle device based on the obtained attribute information of the idle device includes:
for each test case of a special type, preferentially determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case of the special type in the idle equipment based on the acquired attribute information of the idle equipment, and taking the target equipment as equipment allocated to the test case of the special type;
for each common type test case, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the common type test case as equipment allocated to the common type test case in the idle equipment which is not allocated to each special type test case based on the acquired attribute information of the idle equipment which is not allocated to each special type test case.
4. The method of claim 1, further comprising:
acquiring the execution times of the plurality of test cases;
for each test case, determining, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case based on the obtained attribute information of the idle device, including:
and for each test case executed at a time, determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case in the idle equipment based on the acquired attribute information of the idle equipment, and using the target equipment as the equipment which is distributed to execute the test case with the current times.
5. The method of claim 1, further comprising:
acquiring test case grouping information, wherein the test case grouping information is used for indicating at least two test cases which are distributed to be executed in the same equipment in the plurality of test cases and executing sequential execution sequence information of the at least two test cases;
for each test case, determining, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case based on the obtained attribute information of the idle device, including:
for at least two test cases corresponding to the test case grouping information, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the at least two test cases in the idle equipment based on the acquired attribute information of the idle equipment;
for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the test cases in the idle equipment based on the acquired attribute information of the idle equipment;
the sending each test case to the corresponding target device respectively includes:
for at least two test cases corresponding to the test case grouping information, sending the at least two test cases and the corresponding sequential execution sequence information for executing the at least two test cases to corresponding target equipment;
and for each test case except for at least two test cases corresponding to the test case grouping information in the plurality of test cases, respectively sending the test case to corresponding target equipment.
6. An apparatus for performing test tasks, the apparatus comprising:
the acquisition module is used for acquiring a plurality of test cases and equipment requirement conditions corresponding to the test cases respectively;
a determining module, configured to determine, based on the obtained status information of the at least one device, an idle device among the at least one device;
the determining module is further configured to determine, for each test case, in the idle device, a target device whose attribute information can satisfy a device requirement condition corresponding to the test case, based on the acquired attribute information of the idle device;
and the sending module is used for sending each test case to the corresponding target equipment.
7. The apparatus according to claim 6, wherein the plurality of test cases include a test case of a general type and/or a test case of a special type, and a complexity of a device requirement condition corresponding to the test case of the special type is higher than a complexity of the device requirement condition corresponding to the test case of the general type.
8. The apparatus of claim 7, wherein the plurality of test cases comprises a common type of test case and a special type of test case, and wherein the determining module is configured to:
for each test case of a special type, preferentially determining target equipment of which the attribute information can meet the equipment requirement condition corresponding to the test case of the special type in the idle equipment based on the acquired attribute information of the idle equipment, and taking the target equipment as equipment allocated to the test case of the special type;
for each common type test case, determining target equipment of which the attribute information can meet equipment requirement conditions corresponding to the common type test case as equipment allocated to the common type test case in the idle equipment which is not allocated to each special type test case based on the acquired attribute information of the idle equipment which is not allocated to each special type test case.
9. A server, comprising a processor, a communication interface, a memory, and a communication bus, wherein:
the processor, the communication interface and the memory complete mutual communication through the communication bus;
the memory is used for storing a computer program;
the processor is configured to execute the program stored in the memory to implement the method steps of any of claims 1-5.
10. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of the claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910792744.4A CN111190810B (en) | 2019-08-26 | 2019-08-26 | Method, device, server and storage medium for executing test task |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910792744.4A CN111190810B (en) | 2019-08-26 | 2019-08-26 | Method, device, server and storage medium for executing test task |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111190810A true CN111190810A (en) | 2020-05-22 |
| CN111190810B CN111190810B (en) | 2021-09-17 |
Family
ID=70709019
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910792744.4A Active CN111190810B (en) | 2019-08-26 | 2019-08-26 | Method, device, server and storage medium for executing test task |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111190810B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111897722A (en) * | 2020-07-15 | 2020-11-06 | 重庆紫光华山智安科技有限公司 | Automatic test case processing method and device, server and storage medium |
| CN111913884A (en) * | 2020-07-30 | 2020-11-10 | 百度在线网络技术（北京）有限公司 | Distributed test method, device, equipment, system and readable storage medium |
| CN112346965A (en) * | 2020-10-12 | 2021-02-09 | 天津五八到家货运服务有限公司 | Test case distribution method, device and storage medium |
| CN116192922A (en) * | 2023-04-23 | 2023-05-30 | 成都华兴汇明科技有限公司 | Issuing management method, device and system for test cases |
| WO2023185482A1 (en) * | 2022-03-29 | 2023-10-05 | 中兴通讯股份有限公司 | Test method, storage medium and electronic apparatus |
| CN117234952A (en) * | 2023-11-13 | 2023-12-15 | 杭银消费金融股份有限公司 | Distributed automatic test method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978263A (en) * | 2014-04-09 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Mobile terminal application program test method and mobile terminal application program test system |
| US9436586B1 (en) * | 2013-10-04 | 2016-09-06 | Ca, Inc. | Determining code coverage on Z/OS® server |
| CN107766194A (en) * | 2017-11-17 | 2018-03-06 | 深圳市泉眼网络科技有限公司 | Method of testing, device, system, terminal device and computer-readable recording medium |
| CN108287789A (en) * | 2017-12-29 | 2018-07-17 | 五八有限公司 | Batch-automated test method, device and electronic equipment |
| CN109062786A (en) * | 2018-07-16 | 2018-12-21 | 北京百度网讯科技有限公司 | Operation method, device and the terminal of test case |
| CN110083536A (en) * | 2019-04-25 | 2019-08-02 | 厦门网宿有限公司 | Test resource distribution method and device, electronic equipment and storage medium |
-
2019
- 2019-08-26 CN CN201910792744.4A patent/CN111190810B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9436586B1 (en) * | 2013-10-04 | 2016-09-06 | Ca, Inc. | Determining code coverage on Z/OS® server |
| CN104978263A (en) * | 2014-04-09 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Mobile terminal application program test method and mobile terminal application program test system |
| CN107766194A (en) * | 2017-11-17 | 2018-03-06 | 深圳市泉眼网络科技有限公司 | Method of testing, device, system, terminal device and computer-readable recording medium |
| CN108287789A (en) * | 2017-12-29 | 2018-07-17 | 五八有限公司 | Batch-automated test method, device and electronic equipment |
| CN109062786A (en) * | 2018-07-16 | 2018-12-21 | 北京百度网讯科技有限公司 | Operation method, device and the terminal of test case |
| CN110083536A (en) * | 2019-04-25 | 2019-08-02 | 厦门网宿有限公司 | Test resource distribution method and device, electronic equipment and storage medium |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111897722A (en) * | 2020-07-15 | 2020-11-06 | 重庆紫光华山智安科技有限公司 | Automatic test case processing method and device, server and storage medium |
| CN111913884A (en) * | 2020-07-30 | 2020-11-10 | 百度在线网络技术（北京）有限公司 | Distributed test method, device, equipment, system and readable storage medium |
| CN112346965A (en) * | 2020-10-12 | 2021-02-09 | 天津五八到家货运服务有限公司 | Test case distribution method, device and storage medium |
| WO2023185482A1 (en) * | 2022-03-29 | 2023-10-05 | 中兴通讯股份有限公司 | Test method, storage medium and electronic apparatus |
| CN116192922A (en) * | 2023-04-23 | 2023-05-30 | 成都华兴汇明科技有限公司 | Issuing management method, device and system for test cases |
| CN116192922B (en) * | 2023-04-23 | 2023-08-11 | 成都华兴汇明科技有限公司 | Issuing management method, device and system for test cases |
| CN117234952A (en) * | 2023-11-13 | 2023-12-15 | 杭银消费金融股份有限公司 | Distributed automatic test method and system |
| CN117234952B (en) * | 2023-11-13 | 2024-03-22 | 杭银消费金融股份有限公司 | Distributed automatic test method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111190810B (en) | 2021-09-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111190810B (en) | Method, device, server and storage medium for executing test task | |
| CN108537543B (en) | Parallel processing method, device, equipment and storage medium for blockchain data | |
| WO2019037203A1 (en) | Application program performance testing method, device, computer equipment, and storage medium | |
| CN109814910A (en) | Automate gray scale dissemination method, device, computer system and storage medium | |
| CN103620561B (en) | The method and system of interoperability debugging when running for n road | |
| CN107566214B (en) | Performance test method and device | |
| CN110457197B (en) | Service testing method, device, computer equipment and storage medium | |
| CN110311831A (en) | System resource monitoring method and relevant device based on container cloud | |
| CN108270837B (en) | Distributed task scheduling method and system using idle resources | |
| CN110582750A (en) | system and method for task scheduling and device management | |
| CN113672441B (en) | Method and device for testing intelligent equipment | |
| WO2019178957A1 (en) | Distributed system test method and device, computer device and storage medium | |
| CN112581018B (en) | Method, system, device and storage medium for managing process tasks | |
| CN112286723A (en) | Computer room disaster recovery control method, terminal and storage medium | |
| US20180188990A1 (en) | Method, apparatus and system for inserting disk | |
| CN108140035B (en) | Database replication method and device for distributed system | |
| CN109597653A (en) | Method, BIOS and the BMC of BIOS and BMC command interaction | |
| CN112631919A (en) | Comparison test method and device, computer equipment and storage medium | |
| CN109902028A (en) | Automated testing method, device, equipment and the storage medium of ACL characteristic | |
| CN108733545B (en) | Pressure testing method and device | |
| CN112416803A (en) | Automatic testing method and device | |
| WO2016116013A1 (en) | Software upgrade method and system | |
| CN111459631A (en) | Automatic batch processing method and system for server | |
| CN103605610A (en) | System and method for software testing based on Hadoop | |
| CN114356521A (en) | Task scheduling method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |