CN115221041A

CN115221041A - Multi-device testing method and device, electronic device and storage medium

Info

Publication number: CN115221041A
Application number: CN202210653596.XA
Authority: CN
Inventors: 秦毓; 张斌; 柯华强; 徐阳; 黄文娣
Original assignee: Guangzhou Automobile Group Co Ltd
Current assignee: Guangzhou Automobile Group Co Ltd
Priority date: 2022-06-09
Filing date: 2022-06-09
Publication date: 2022-10-21

Abstract

The embodiment of the application provides a multi-device testing method and device, electronic equipment and a storage medium, and relates to the technical field of equipment testing. The test task list of the plurality of test devices is determined according to the importance degree of the software version to be tested, the priority of the test case and the load state of the plurality of test devices, wherein the test task list comprises the plurality of test tasks and the priorities corresponding to the plurality of test tasks, so that the plurality of test devices execute the test tasks according to the test task list, development and testing can be integrated, manual intervention is not needed, the test efficiency can be effectively improved, in addition, the plurality of test tasks are distributed to the plurality of test devices as required, a plurality of test terminals can simultaneously carry out integrated testing, dynamic distribution of test resources can be realized, and the test efficiency can be effectively improved.

Description

Multi-device testing method and device, electronic device and storage medium

Technical Field

The embodiment of the application relates to the technical field of device testing, in particular to a multi-device testing method and device, an electronic device and a storage medium.

Background

In order to adapt to the change of the electronic and electric appliance architecture of the automobile, the functional modules of the automobile software are gradually changed from a distributed design to a centralized design. With the great increase of the functions of newly added software, the centralized controller is more and more complex, the requirements on the testing efficiency and testing resources of the controller are higher and higher, and how to efficiently integrate and test the controller under the new architecture is a problem to be solved urgently in the high-speed development of the vehicle intelligent network.

Disclosure of Invention

The embodiment of the application provides a multi-device testing method and device, an electronic device and a storage medium, so as to solve the problems.

In a first aspect, an embodiment of the present application provides a method for testing multiple devices, where the method includes: acquiring a software version to be tested, a test case of the software version to be tested and the load states of a plurality of test devices; determining a test task list of the plurality of test devices according to the importance degree of the to-be-tested software version, the priority of the test case and the load states of the plurality of test devices, wherein the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks; and issuing test tasks to the plurality of test devices according to the test task list so as to enable the plurality of test devices to execute the test tasks.

In a second aspect, an embodiment of the present application provides a method for testing multiple devices, where the method includes: acquiring a test task list sent by a server, wherein the test task list is determined by the server according to a software version to be tested, the priority of a test case of the software version to be tested and the load state of the test equipment, and the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks; according to the priorities of the plurality of test tasks, reordering the test tasks to be executed in the test equipment to obtain a new test task execution sequence, wherein the test tasks to be executed comprise the plurality of test tasks in the test task list and the test tasks which are not executed in the test equipment before the test task list is obtained; and sequentially executing the test tasks to be executed according to the new test task execution sequence.

In a third aspect, an embodiment of the present application provides a multi-device testing apparatus, including: the data acquisition module is used for acquiring a to-be-tested software version, a test case of the to-be-tested software version and the load states of a plurality of test devices; the list determining module is used for determining a test task list of the plurality of test devices according to the importance degree of the to-be-tested software version, the priority of the test case and the load states of the plurality of test devices, wherein the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks; and the task issuing module is used for issuing the test tasks to the plurality of test equipment according to the test task list so as to enable the plurality of test equipment to execute the test tasks.

In a fourth aspect, an embodiment of the present application provides a multi-device testing apparatus, including: the system comprises a list acquisition module, a test task list and a test device, wherein the list acquisition module is used for acquiring a test task list sent by a server, the test task list is determined by the server according to a to-be-tested software version, the priority of a test case of the to-be-tested software version and the load state of the test device, and the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks; the sequence adjusting module is used for reordering the to-be-executed test tasks in the test equipment according to the priorities of the plurality of test tasks to obtain a new test task execution sequence, wherein the to-be-executed test tasks comprise the plurality of test tasks in the test task list and the test tasks which are not executed before the test task list is obtained in the test equipment; and the task execution module is used for sequentially executing the test tasks to be executed according to the new test task execution sequence.

In a fifth aspect, an embodiment of the present application provides an electronic device. The electronic device generally includes memory, one or more processors, and one or more applications. Wherein one or more application programs are stored in the memory and configured to execute the multi-device testing method provided by the embodiments of the present application when invoked by one or more processors.

In a sixth aspect, embodiments of the present application provide a computer-readable storage medium. The computer readable storage medium stores program code configured to execute the multi-device testing method provided by the embodiment of the application when the program code is called by the processor.

The embodiment of the application provides a multi-device testing method, a multi-device testing device, electronic equipment and a storage medium, wherein a testing task list of a plurality of testing devices is determined according to the importance degree of a to-be-tested software version, the priority of a testing case and the load states of the testing devices, so that the testing devices execute testing tasks according to the testing task list, development and testing can be integrated, manual intervention is not needed, the testing efficiency can be effectively improved, in addition, the testing tasks are distributed to the testing devices as required, a plurality of testing terminals can simultaneously carry out integrated testing, dynamic distribution of testing resources can be realized, and the testing efficiency can be effectively improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of a multi-device test system provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of multiple roles of the multi-device test system shown in FIG. 1 provided by an exemplary embodiment of the present application;

fig. 3 is a schematic flowchart of a testing method for multiple devices according to an embodiment of the present application;

FIG. 4 is a schematic flowchart of a testing method for multiple devices according to another embodiment of the present application;

fig. 5 is a schematic flowchart of step S230 in a multi-device testing method according to another embodiment of the present application;

fig. 6 is another schematic flowchart of step S230 in the multi-device testing method according to another embodiment of the present application;

FIG. 7 is a schematic flowchart illustrating a method for testing multiple devices according to yet another embodiment of the present application;

FIG. 8 is a flowchart of a method for testing multiple devices provided by an exemplary embodiment of the present application;

FIG. 9 is a block diagram of a multi-device testing apparatus according to an embodiment of the present disclosure;

FIG. 10 is a block diagram of a multi-device testing apparatus according to another embodiment of the present application;

fig. 11 is a block diagram of an electronic device provided in an embodiment of the present application;

fig. 12 is a block diagram of a computer-readable storage medium according to an embodiment of the present disclosure.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

Referring to fig. 1, fig. 1 is a schematic diagram of a multi-device testing system according to an embodiment of the present disclosure. The multi-device test system 10 includes a test version release module 11, a test case release module 12, a server 13, and a test device 14. The server 13 is in communication connection with the test version release module 11 and the test case release module 12, respectively, so as to implement data interaction between the server 13 and the test version release module 11 or the test case release module 12. The server 13 is in communication connection with the testing device 14 to enable data interaction between the server 13 and the testing device 14. The test device 14 is in communication connection with the test version release module 11 and the test case release module 12, respectively, so as to implement data interaction between the test device 14 and the test version release module 11 or the test case release module 12.

The test version release module 11 may send a software update request to the server 13, and the software update request may include software version information, verification information, and the like. After the server 13 receives the software update request, it may be determined whether the software version exists in the version information base of the server 13. If the version information base of the server 13 has the software version, a negative response is replied, and after receiving the negative response, the test version release module 11 ends the request operation and does not send the software package corresponding to the software version to the server 13. If the software version does not exist in the version information base of the server 13, a positive response is replied, and after receiving the positive response, the test version release module 11 sends the software package corresponding to the software version to the server 13. After receiving the software package corresponding to the software version, the server 13 sends a reception completion instruction to the test version release module 11, and the test version release module 11 responds to the reception completion instruction to end the request operation. The positive response, the negative response, and the receiving completion instruction are all preset instructions, and may be customized by a user, for example, the three may be different binary codes, and the embodiment of the present application is not limited specifically herein.

In some embodiments, the software update request may be initiated by a developer through the test version release module 11. In some embodiments, the software update request may be automatically initiated by the test version release module 11. As an example, the test version issuing module 11 may detect whether a developed but untested software version exists in the development software library in real time or at preset time intervals, determine, if it is detected that a developed but untested software version exists in the development software library, the detected developed but untested software version as a target software version, generate a software update request corresponding to the target software version, and send a software update request corresponding to the target software version to the server 13 and the test case issuing module 12. If the software version which is developed but not tested is not detected to exist in the development software library, the step of detecting whether the software version which is developed but not tested exists in the development software library is continuously executed. The preset time period may be set according to actual needs, for example, 24 hours or a week, and the embodiment of the present application is not specifically limited herein.

The test case issuing module 12 may send a test case uploading request to the server 13, where the test case uploading request includes software version information, test cases, test case priorities, test script information corresponding to the test cases, and the like. After receiving the test case request, the server 13 sends a reception completion instruction to the test case issuing module 12, and the test case issuing module 12 responds to the reception completion instruction to end the request operation. The receiving completion instruction is a preset instruction, and may be customized by a user, for example, the receiving completion instruction may be a string of binary codes, and the embodiment of the present application is not limited in this embodiment.

In some embodiments, the test case upload request may be initiated by a tester through the test case issuing module 12. In some embodiments, the test case upload request may also be automatically initiated by the test case publishing module 12. As an example, the test case issuing module 12 may receive the software update request sent by the test version issuing module 11, and may send the test case corresponding to the target software version in the software update request to the server 13.

In some embodiments, a developer or a tester may issue a test task directly to the test device 14 through either the test version release module 11 or the test case release module 12. The test task directly issued by the developer or the tester to the test device 14 is a specified test task to be mentioned later, and the test device having the specified test task is a specified test device to be mentioned later. It should be noted that the designated test task has the highest priority, and when the designated test device is executing the designated test task, the server does not allow the test task to be issued to the designated test device. When the specified test device receives the specified test task, the specified test device may suspend executing the current test task and start executing the specified test task, or the specified test device may arrange an execution order of the specified test task before all tasks to be executed, so that the specified test task is executed after the current test task is executed. By setting the designated test task, the workflow of the test system is allowed to be directly intervened manually, a means for developers and testers to take over certain test equipment temporarily is provided, the emergency task can be processed, and the workflow redundancy of the system is enhanced.

The server 13 may be one server or include multiple servers, where the server may be a network access server, a database server, a cloud server, and the like, and the embodiment of the present application is not limited in this embodiment. The server 13 may determine a test task list of the test device 14 according to the software version released by the test version release module 11, the priority of the test case released by the test case release module 12, and the load state of the test device 14, and dynamically allocate the test tasks to the test device 13 through the test task list in the parallel test process of multiple test devices, so as to fully utilize the test resources and maximize the test efficiency. The implementation details of how the server 13 specifically allocates the test task will be described in the following method embodiments.

The server 13 may manage the software version to issue the test tasks to the test devices 14 in a task release form of a test task binding software package. The testing device 14 cannot reject the release of the testing task, and only can feed back the load status, that is, the server 13 has the decision right of task allocation after processing the load status fed back by the testing device 14. By issuing the test tasks to the test equipment 14 in the form of binding the test tasks to the software package, the sustainable integration test of each test equipment can be realized, and thus an integrated connection scheme from software issuing to test execution can be realized. The Service Oriented Architecture (SOA) is used, the server 13 plays a role of a Service agent, the number and the range of services in the whole system can be managed swiftly, new personnel or test equipment is added/deleted, only corresponding services need to be added/deleted, the failure of the test equipment or the personnel cannot cause the stagnation of the system work, and the deployment of the test system is provided with sufficient flexibility.

The test device 14 includes a plurality of test devices, and as shown in fig. 1, the test device 14 may include

test devices

141, 142, 143, and 144, and the embodiment of the present application does not limit the specific number of test devices. The test device may be a controller, for example, an on-board Electronic Control Unit (ECU). The test equipment 14 may reorder the execution sequence of all the test tasks to be executed of the test equipment 14 itself according to the priority of the test tasks issued by the server 13, execute the test tasks to be executed according to the execution sequence after reordering, update the test policy in real time, and preferentially execute the test tasks with high priority, thereby achieving efficient completion of important test work and maximum utilization of test resources. The test device 14 generates a test report from the test result and sends the test report to the server 13 after completing a test task, the server 13 archives the test report, and when receiving a test report query request, the test report corresponding to the test report query request is fed back to the sender, so that the test report with the test completed can be queried at any time, and is not limited to the process of executing the test.

Referring to fig. 2, fig. 2 is a schematic diagram of a polygon of the multi-device testing system shown in fig. 1 according to an exemplary embodiment of the present application. The multi-device test system 10 performs interaction between the roles in a service manner based on the SOA architecture. The server 13, the tester, the developer and the test equipment 14 can simultaneously take the roles of a service requester (client) and a service provider, and perform service provision or service request in different scenes. In a conventional workflow, a developer and a tester release a software package and a test requirement to a server 13 in the form of a service provider through a test version release module 11 and a test case release module 12, respectively. The server 13 requests the state of the test device 14 in the form of a client, performs integration output of a task list according to the received software version, the priority of the test case, and the state of the test device 14, and issues a test task to the test device 14 in the form of a service provider. The test device 14 receives the test tasks, rearranges the test execution sequence according to the priorities of the test tasks, executes the test tasks according to the new execution sequence, and issues test results and reports to the server 13 in the form of the service provider after the execution is completed. In special cases, developers and testers allow test tasks to be issued directly to specified test equipment in the form of service providers, with temporary occupation of the specified test equipment. The server 13 may also act as a service agent providing service registration and service lookup functions to manage the services that can be provided by the overall system.

The multi-device test system provided by the embodiment of the application is based on an SOA (service oriented architecture), the message mode of each role piece is constructed in a service mode, a tester and a developer serve as demand providers, a main server serves as a decision processing method, and test equipment serves as a task executing party. The server is used as a decision processing party to collect information of a demand party and an execution party, and test tasks and software versions are bound and issued to each test device through decision operation according to preset allocation rules, so that the sustainability test is realized. The test equipment can receive the new task in real time and reorder the task sequence to be executed, dynamically update the test strategy and improve the test efficiency. Various aspects of the multi-device test system have a loose coupling characteristic, and can be separated from or added into a system architecture in a service registration or logout mode, so that flexibility of system deployment is realized.

Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a testing method for multiple devices according to an embodiment of the present disclosure. The multi-device testing method can be applied to the server 13 shown in fig. 1 or the apparatus 400 shown in fig. 9, which will be mentioned later. The multi-device testing method may include the following steps S110 to S130.

S110, acquiring the version of the software to be tested, the test case of the version of the software to be tested and the load states of a plurality of test devices.

The software version to be tested may be a developed untested software version, and the software version to be tested may be one software version or include multiple software versions. The same software version to be tested comprises a plurality of test cases, and the plurality of test cases with the dependency relationship of the same software version to be tested can form a test task. The plurality of test cases with dependency relationship refer to a plurality of test cases which can realize the same function.

Wherein the load status characterizes resource usage of the plurality of test devices. The load states of the plurality of test devices may include task states and execution states of the plurality of test devices. The task state refers to a state in which the test device reorders all test tasks to be executed of the test device according to the priority of the test tasks issued by the server. The execution state refers to a state in which the test device executes a test task.

In some embodiments, the server may obtain the software version to be tested and the software package of the software version to be tested, which are released by the developer through the test version release module. The server can obtain the test cases of the software version to be tested, which are released by the tester through the test case release module. The server may obtain load states of a plurality of test devices. For a part of the server that obtains the version of the software to be tested, the test case of the version of the software to be tested, and the load status of the multiple test devices, which is not described in detail, please refer to the description related to fig. 1, which is not described herein again in this embodiment of the present application.

In some embodiments, if a test device with a specified test task is detected in a plurality of test devices, determining the test device with the specified test task as the specified test device, wherein the specified test task is a task directly issued to the specified test device through a preset specified module; and forbidding the test task from being issued to the specified test equipment. The preset appointed module comprises the test version release module and the test case release module. By setting the appointed test task, the method allows the manual work to directly intervene the workflow of the test system, provides a means for developers and testers to temporarily take over certain test equipment, can be used for processing the emergency task, and enhances the workflow redundancy of the system.

And S120, determining a test task list of the plurality of test equipment according to the importance degree of the software version to be tested, the priority of the test case and the load states of the plurality of test equipment, wherein the test task list comprises the plurality of test tasks and the priorities corresponding to the plurality of test tasks.

The version number of the software version to be tested can represent the importance degree of the software version to be tested. In the embodiment of the application, the smaller the version number of the version of the software to be tested is, the more important the software to be tested is. For example, version number "1.0" of version 1.0 is less than version number "1.1" of version 1.1, then version 1.0 is more important than version 1.1.

The test cases can be numbered, so that the test case priorities are represented by the test case numbers. In the embodiment of the application, the smaller the number of the test case is, the higher the priority of the test case is. For example, if the number "1" of test case 1 is smaller than the number "2" of test case 2, the priority of test case 1 is higher than that of test case 2.

The test task list of each test device comprises a plurality of test tasks and priorities corresponding to the test tasks.

For a detailed embodiment of how to determine the test task list of the plurality of test devices in step S120, please refer to steps S220 to S230, which will be mentioned later.

And S130, issuing the test tasks to the plurality of test devices according to the test task list so that the plurality of test devices execute the test tasks.

In some embodiments, the server may issue test tasks to the plurality of test devices through the test task manifest. In some embodiments, the server may divide the test task list into a plurality of test task sub-lists, each test task sub-list corresponding to one test device, each test task sub-list including a plurality of test tasks and priorities of the plurality of test tasks.

In some embodiments, the server may issue the test tasks to the plurality of test devices in a form of packaging the software package and the test tasks according to the test task list.

In some embodiments, after performing step S130, the multi-device testing method may further include the steps of: acquiring test reports generated after a plurality of test devices execute test tasks; acquiring a test report query request initiated by a preset specified module, and analyzing the test report query request to obtain a target software version and a target test case; and sending the test report corresponding to the target software version and the target test case in the test report to a preset specified module. The preset appointed module comprises a test software version release module and a test case release module. In the embodiment of the present application, a developer or a tester may request to acquire any completed test report through the test software version release module and the test case release module at any time, and is not limited to request to acquire a test report in each execution workflow.

According to the multi-device testing method provided by the embodiment of the application, the testing task lists of the plurality of testing devices are determined according to the importance degree of the to-be-tested software version, the priority of the testing case and the load states of the plurality of testing devices, so that the plurality of testing devices execute the testing tasks according to the testing task lists, development and testing can be integrated, manual intervention is not needed, the testing efficiency can be effectively improved, in addition, the plurality of testing tasks are distributed to the plurality of testing devices as required, a plurality of testing terminals can simultaneously carry out integrated testing, dynamic distribution of testing resources can be realized, and the testing efficiency can be effectively improved.

Referring to fig. 4, fig. 4 is a flowchart illustrating a multi-device testing method according to another embodiment of the present application, where the multi-device testing method can be applied to the server 13 shown in fig. 1 or the apparatus 400 shown in fig. 9 mentioned later. The multi-device testing method may include the following steps S210 to S240.

Step S210, acquiring a to-be-tested software version, a test case of the to-be-tested software version and load states of a plurality of test devices.

For details of step S210, please refer to step S110, which is not repeated herein.

Step S220, determining a plurality of test tasks according to the to-be-tested software version and the test cases, where each test task in the plurality of test tasks includes an associated test case, and the associated test cases are a plurality of test cases with dependency relationships of the same to-be-tested software version.

Step S230, determining a test task list of the plurality of test devices according to the importance degree of the to-be-tested software version, the priorities of the plurality of test tasks, and the load states of the plurality of test devices.

In some embodiments, the idle level of the plurality of test devices may be determined based on a load status of the plurality of test devices. As described above, the load status includes a task status and an execution status, and in some embodiments, the idle levels of the plurality of test devices may be determined according to the number of test tasks in the task status of the plurality of test devices and the remaining available memory in the execution status of the plurality of test devices.

TABLE 1

Number of test tasks (X)	Surplus available memory ratio (Y)	Idle level of test equipment
			0≤X≤5	Y<50％	First idle level
5<X<10	Y<50％	Second idle level
			X≥10	Y<50％	Third Idle level

As an example, referring to table 1, idle levels of test devices of 0 ≦ X ≦ 5 and Y <50% may be determined as a first idle level, idle levels of test devices of 5- <x-10 and Y <50% may be determined as a second idle level, idle levels of test devices of X ≦ 10 and Y <50% may be determined as a third idle level, where X is a positive integer greater than or equal to 0 and Y is a percentage greater than 0. The idle degree of the test equipment of the first idle level, the second idle level and the third idle level is reduced in sequence. The number of test tasks which can be received by the test equipment of the first idle level, the second idle level and the third idle level is reduced in sequence.

Referring to fig. 5, fig. 5 is a schematic flowchart illustrating step S230 in a multi-device testing method according to another embodiment of the present disclosure. Step S230 may include the following steps S231A to S234A.

Step S231A, determining a first priority of each of the plurality of test tasks according to the importance degree of the to-be-tested software version, wherein the first priorities of the test tasks of the same to-be-tested software version are the same.

In some embodiments, according to the importance degree of the software version to be tested, the first priority of the test tasks of different software versions to be tested can be determined, so as to perform priority distribution on the test tasks of the software version to be tested with high importance degree.

Step S232A, preliminarily determining a preliminary test task list of the plurality of test devices according to the first priority of each test task and the load states of the plurality of test devices.

As shown in table 2, the preliminary test task includes a mapping relationship among a software version to be tested, a plurality of test tasks, and a plurality of test devices.

TABLE 2

In some embodiments, the plurality of test tasks may be arranged in order of the first priority from high to low; arranging the test equipment in sequence according to the idle degree of the idle grade from high to low; according to the number of the test tasks which can be received by the test equipment, the plurality of test tasks are sequentially distributed to the plurality of test equipment according to the sequence from high priority to low priority, and a preliminary test task list is obtained.

As an example, referring to table 2, the software version to be tested includes version 1.0, version 1.1, and version 1.2, the test tasks of version 1.0 include a, B, and C, and the first priorities of the test tasks a, B, and C of version 1.0 are the same. The test tasks of the version 1.1 comprise D, E, F and G, and the first priorities of the test tasks of the version 1.1 are the same. The test tasks of version 1.2 comprise H, I and J, and the first priorities of the test tasks of version 1.2 are the same. The first priority of the test task of version 1.0, the test task of version 1.1 and the test task of version 1.2 is reduced in sequence. The test equipment comprises four test equipment with idle levels from high to low, namely T1, T2, T3 and T4. And arranging the plurality of test tasks in sequence according to the first priority from high to low. And arranging the test equipment in sequence according to the idle degree of the idle level from high to low. According to the number of the test tasks which can be received by the test equipment, the plurality of test tasks are sequentially distributed to the plurality of test equipment according to the sequence from high priority to low priority, and a preliminary test task list shown in table 2 is obtained.

Step S233A, determining a second priority of each test task according to the priority of the associated test case included in each test task, wherein the first priority is higher than the second priority.

As shown in table 2, the priorities among the test tasks with the same first priority are not determined, and after the test tasks of different software versions to be tested are distributed, a plurality of test tasks of the same software version to be tested can be distributed.

In some embodiments, the second priority of each test task in the test tasks with the same first priority may be determined according to the priority of the associated test case included in each test task. Specifically, an average value of the priorities of the associated test cases included in each test task may be used as the second priority of each test task. For example, if the test task a includes test cases 1, 2, and 3, the second priority of the test task a is 2.

Step S234A, determining a test task list of a plurality of test devices according to the second priority of each test task and the preliminary test task list.

In some embodiments, the test task lists of the plurality of test devices may be obtained by exchanging the order of the test tasks with the same first priority in the preliminary test task list according to the second priority of each test task in the test tasks with the same first priority (the test tasks with the same software version to be tested). Specifically, each of the test tasks with the same first priority may be sequentially arranged in the preliminary test task list according to the sequence from the highest second priority to the lowest second priority, so as to obtain a new test task arrangement sequence. And according to the number of the test tasks which can be received by the test equipment and the new test task arrangement sequence, sequentially distributing the plurality of test tasks to the plurality of test equipment to obtain a test task list of the plurality of test equipment.

TABLE 3

As an example, the second priorities of the test tasks a, C, and B in table 2 are sequentially lowered, the second priorities of the test tasks D, F, E, and G are sequentially lowered, and the second priorities of the test tasks H, I, and J are sequentially lowered. And (3) sequentially arranging each test task in the test tasks with the same first priority in the preliminary test task list according to the sequence from the second priority from high to low, so as to obtain a new test task arrangement sequence shown in table 3. According to the number of test tasks that can be received by the test equipment, the plurality of test tasks are sequentially distributed to the plurality of test equipment according to the new test task arrangement sequence, and a test task list of the plurality of test equipment as shown in table 3 can be obtained.

Referring to fig. 6, fig. 6 is another schematic flow chart of step S230 in a multi-device testing method according to another embodiment of the present application. Step S230 may further include the following steps S231B to S234B.

Step S231B, determining a first priority of each of the plurality of test tasks according to the importance degree of the to-be-tested software version.

Step S232B, determining the second priority of each test task according to the priority of the associated test case included in each test task, wherein the first priority is higher than the second priority.

Step S233B, determining the target priority of each test task according to the weights of the first priority and the second priority.

The weights of the first priority and the second priority may be set by a user according to actual needs, for example, the weights of the first priority and the second priority are 0.8 and 0.2, respectively, and are not limited herein.

Step S234B, determining a test task list of the plurality of test devices according to the target priority of each test task and the load states of the plurality of test devices.

In some embodiments, each test task may be sequentially ordered according to the target priority from high to low; sequencing a plurality of test devices in sequence from high idle level to low idle level; and according to the number of the test tasks which can be received by the plurality of test devices, the test tasks are distributed in sequence from high target priority to low target priority.

Step S240, issuing a test task to the plurality of test devices according to the test task list, so that the plurality of test devices execute the test task.

For a detailed description of step S240, please refer to step S130, which is not repeated herein.

According to the multi-device testing method provided by the embodiment of the application, the testing task lists of the plurality of testing devices are determined according to the importance degree of the to-be-tested software version, the priority of the testing case and the load states of the plurality of testing devices, so that the plurality of testing devices execute the testing tasks according to the testing task lists, development and testing can be integrated, manual intervention is not needed, the testing efficiency can be effectively improved, in addition, the plurality of testing tasks are distributed to the plurality of testing devices as required, a plurality of testing terminals can simultaneously carry out integrated testing, dynamic distribution of testing resources can be realized, and the testing efficiency can be effectively improved. According to the method and the device for testing the software version, the software version with the important degree and the testing tasks with the high priority are preferentially distributed according to the priority of the software version and the priority of the testing tasks, and therefore efficient completion of important testing work and maximum utilization of testing resources can be achieved.

Referring to fig. 7, fig. 7 is a schematic flowchart illustrating a method for testing multiple devices according to another embodiment of the present application. The multi-device testing method can be applied to the testing device 14 shown in fig. 1 or the apparatus 500 shown in fig. 10, which will be mentioned later. The multi-device testing method may include the following steps S310 to S330.

Step S310, a test task list sent by the server is obtained, the test task list is determined by the server according to the version of the software to be tested, the priority of the test case of the version of the software to be tested and the load state of the test equipment, and the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks.

In some embodiments, the test task list includes test tasks of all the test devices, and as shown in table 3, when the test device acquires the test task list, the test device may intercept a test task sub-list corresponding to the test device from the test task list. For example, when the test device is T1, the test task sub-list corresponding to the test device T1 shown in table 4 may be intercepted from the test task list shown in table 3.

TABLE 4

TABLE 5

In some embodiments, the server has partitioned the test task list into a plurality of test task sub-lists, each test task sub-list corresponding to one of the test devices, each test task sub-list including a plurality of test tasks and priorities for the plurality of test tasks. The test device may directly receive the test task sub-list corresponding to the test device, for example, the test device is T1, and then as shown in table 5, the test task sub-list may be a single test list corresponding to the test device T1.

Step S320, according to the priorities of the multiple test tasks, re-ordering the test tasks to be executed in the test device to obtain a new test task execution sequence, where the test tasks to be executed include the multiple test tasks in the test task list and the test tasks in the test device that are not executed before the test task list is obtained.

TABLE 6

In some embodiments, the test tasks to be executed may be reordered in the order of priority from high to low, so as to obtain a new test task execution order. For example, the test device is T1, and the test tasks to be executed are sequentially reordered from high to low in priority, so that a new test task execution order shown in table 6 can be obtained, where the test tasks L, M, and N are test tasks that are not executed before the test task list is obtained.

And step S330, executing the test tasks to be executed in sequence according to the new test task execution sequence.

In some embodiments, a software version of a current test task to be executed in the test tasks to be executed may be obtained; verifying the software version of the current test task to be executed to generate a verification result; if the verification result represents that the verification is successful, executing the current test task to be executed; and if the verification result represents that the verification fails, burning the software version of the current test task to be executed, and executing the step of verifying the software version of the current test task to be executed after burning. By checking the software version of the current test task to be executed, the software version of the current test task to be executed can be ensured to be consistent with the software version of the test equipment.

In some embodiments, if the specified test task directly issued to the device to be tested through the preset specified module is obtained, the specified test task may be arranged before the test task to be executed, so that the specified test task is executed after the current test task is executed. The preset appointed module comprises a test software version release module and a test case release module.

In some embodiments, if the specified test task directly issued to the device to be tested through the preset specified module is obtained, the execution of the current test task may be stopped, and the specified test task may be started.

According to the multi-device testing method provided by the embodiment of the application, the testing task lists of the plurality of testing devices are determined according to the importance degree of the to-be-tested software version, the priority of the testing case and the load states of the plurality of testing devices, so that the plurality of testing devices execute the testing tasks according to the testing task lists, development and testing can be integrated, manual intervention is not needed, the testing efficiency can be effectively improved, in addition, the plurality of testing tasks are distributed to the plurality of testing devices as required, a plurality of testing terminals can simultaneously carry out integrated testing, dynamic distribution of testing resources can be realized, and the testing efficiency can be effectively improved. In addition, through two reordering of the main server and the test terminal, the test strategy can be updated in real time, so that the high-efficiency completion of important test work and the maximum utilization of test resources are realized.

Referring to fig. 8, fig. 8 is a flowchart illustrating a method for testing multiple devices according to an exemplary embodiment of the present disclosure. The multi-device test method can be applied to the multi-device test system 10 shown in fig. 1. The testing method of the device may include the following steps one to nine.

Step one, a developer sends a software version and a software package to a server through a test version release module.

And step two, the tester sends the test requirement to the server through the test case release module, namely sends the test case corresponding to the software version.

And step three, the server receives the load states of the software version, the software package, the test case and the test equipment, wherein the load states comprise a task state and an execution state.

And step four, the server determines a plurality of test tasks according to the software version and the test cases, wherein each test task comprises a plurality of test cases with incidence relation of the same software version.

And step five, the server distributes the plurality of test tasks to the plurality of test equipment according to the importance degree of the software version, the priority of the test case and the load state of the test equipment to generate a test task list of the plurality of test equipment.

And step six, the server packs the test tasks and the software packages and sends the test tasks and the software packages to the plurality of test equipment according to the test task list, so that the test equipment can test according to the software packages and the test tasks.

And step seven, the test equipment reorders the test tasks to be executed according to the tasks sent by the server to obtain a new execution sequence, and executes the tasks to be executed according to the execution sequence.

Step eight, the server detects whether the specified test equipment with the specified test task exists in the plurality of test equipment, and if the specified test equipment exists, the test task is not sent to the specified test equipment. The specified test task is directly sent to a specified test device by a tester or a developer through the test case release module or the test software version release module.

Step nine, if the test equipment receives an appointed test task which is directly sent to the test equipment by a tester through the test case issuing module, stopping executing the current test task and starting executing the appointed test task; or if the specified test task which is directly sent to the test equipment by the tester through the test case publishing module is received, arranging the specified tester before all the test tasks to be executed, so that the test equipment executes the specified test task after executing the current test task.

For the parts not described in detail in the first to ninth steps, please refer to the corresponding parts in the foregoing embodiments, which are not described herein again.

Referring to fig. 9, fig. 9 is a block diagram illustrating a structure of a multi-device testing apparatus according to an embodiment of the present disclosure. The multi-device test apparatus 400 can be applied to the server 13 shown in fig. 1. The multi-device testing apparatus 400 includes a data acquisition module 410, a list determination module 420, and a task issuing module 430 connected to each other. The data obtaining module 410 is configured to obtain a software version to be tested, a test case of the software version to be tested, and load states of a plurality of test devices. The list determining module 420 is configured to determine a test task list of the multiple test devices according to the importance degree of the software version to be tested, the priority of the test case, and the load states of the multiple test devices, where the test task list includes multiple test tasks and priorities corresponding to the multiple test tasks. The task issuing module 430 is configured to issue a test task to the multiple test devices according to the test task list, so that the multiple test devices execute the test task.

In some implementations, the manifest determination module 420 includes a task determination sub-module, a manifest determination sub-module. The task determination submodule is used for determining the plurality of test tasks according to the to-be-tested software version and the test cases, wherein each test task in the plurality of test tasks comprises an associated test case, and the associated test cases are a plurality of test cases with dependency relationships of the same to-be-tested software version. The list determining submodule is used for determining a test task list of the plurality of test equipment according to the importance degree of the software version to be tested, the priorities of the plurality of test tasks and the load states of the plurality of test equipment.

In some embodiments, the list determination sub-module comprises a priority determination unit, a list determination unit. The priority determining unit is used for determining the first priority of each test task in the plurality of test tasks according to the importance degree of the software version to be tested, wherein the first priorities of the test tasks of the same software version to be tested are the same. The list determining unit is used for preliminarily determining a preliminary test task list of the plurality of test devices according to the first priority of each test task and the load states of the plurality of test devices. The priority determining unit is further configured to determine a second priority of each test task according to a priority of an associated test case included in each test task, where the first priority is higher than the second priority. The list determining unit is further configured to determine a test task list of the plurality of test devices according to the second priority of each test task and the preliminary test task list.

In some embodiments, the priority determining unit is further configured to determine a first priority of each of the plurality of test tasks according to the importance degree of the software version to be tested; determining a second priority of each test task according to the priority of the associated test case included by each test task, wherein the first priority is higher than the second priority; and determining the target priority of each test task according to the weights of the first priority and the second priority. The list determining unit is further used for determining the target priority of each test task according to the weights of the first priority and the second priority.

In some embodiments, the multi-device testing apparatus 400 further comprises a detection module and a disabling module. The detection module is used for determining that the test equipment with the specified test task is the specified test equipment if the test equipment with the specified test task is detected in the plurality of test equipment, wherein the specified test task is a task directly issued to the specified test equipment through a preset specified module. The forbidding module is used for forbidding the test task to be issued to the specified test equipment.

In some embodiments, the data obtaining module 410 is further configured to determine, if a test device with a specified test task is detected in the plurality of test devices, that the test device with the specified test task is the specified test device, where the specified test task is a task directly issued to the specified test device through the preset specifying module. The task issuing module 430 is further configured to prohibit issuing a test task to a specified test device.

In some embodiments, the multi-device testing apparatus 400 further comprises a test result query module. The test result query module is used for acquiring test reports generated after the test tasks are executed by the plurality of test devices; acquiring a test report query request initiated by a preset specified module, and analyzing the test report query request to obtain a target software version and a target test case; and sending the test report corresponding to the target software version and the target test case in the test report to a preset specified module.

Referring to fig. 10, fig. 10 is a block diagram of a multi-device testing apparatus according to another embodiment of the present disclosure. The multi-device test apparatus 500 may be applied to the test device 14 shown in fig. 1. The multi-device testing apparatus 500 includes a list acquiring module 510, a sequence adjusting module 520, and a task executing module 530 connected to each other. The list obtaining module 510 is configured to obtain a test task list sent by a server, where the test task list is determined by the server according to a to-be-tested software version, a priority of a test case of the to-be-tested software version, and a load state of the test device, and the test task list includes a plurality of test tasks and priorities corresponding to the plurality of test tasks. The sequence adjusting module 520 is configured to reorder, according to the priorities of the plurality of test tasks, the test tasks to be executed in the test equipment to obtain a new test task execution sequence, where the test tasks to be executed include the plurality of test tasks in the test task list and the test tasks that are not executed before the test task list is obtained in the test equipment. The task execution module 530 is configured to execute the test tasks to be executed in sequence according to the new test task execution sequence.

In some embodiments, the sequence adjusting module 520 is further configured to, if a specified test task directly issued to the device to be tested through a preset specified module is obtained, rank the specified test task before the test task to be executed, so as to execute the specified test task after the current test task is executed.

In some embodiments, the task execution module 530 is further configured to, if a specified test task directly issued to the device to be tested through the preset specified module is obtained, terminate execution of the current test task, and start execution of the specified test task.

In some embodiments, the task execution module 530 is further configured to obtain a software version of a current test task to be executed in the test tasks to be executed; verifying the software version of the current test task to be executed to generate a verification result; if the verification result represents that the verification is successful, executing the current test task to be executed; and if the verification result represents that the verification fails, burning the software version of the current test task to be executed, and executing the step of verifying the software version of the current test task to be executed after burning.

It is clear to those skilled in the art that the

multi-device testing apparatuses

400 and 500 provided in the embodiments of the present application can respectively implement the multi-device testing method provided in the embodiments of the present application. The specific working processes of the above apparatus and modules may refer to the processes corresponding to the multi-device testing method in the embodiments of the present application, and are not described herein again.

In the embodiments provided in this application, the coupling, direct coupling or communication connection between the modules shown or discussed may be an indirect coupling or communication coupling through some interfaces, devices or modules, and may be in an electrical, mechanical or other form, which is not limited in this application.

In addition, each functional module in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a functional module of software, which is not limited in this application.

Referring to fig. 11, fig. 11 is a block diagram of an electronic device according to an embodiment of the present disclosure. The electronic device 600 may include one or more of the following components: the memory 610, the one or more processors 620, and the one or more applications, wherein the one or more applications may be stored in the memory 610 and configured to cause the one or more processors 620 to perform the method for testing the multiple devices provided by the embodiments of the present application when called by the one or more processors 620.

Processor 620 may include one or more processing cores. The processor 620 interfaces with various components throughout the electronic device 600 using various interfaces and lines to execute or perform instructions, programs, code sets, or instruction sets stored in the memory 610 and to invoke the execution or execution of data stored in the memory 610 to perform various functions of the electronic device 600 and to process data. Alternatively, the processor 620 may be implemented in hardware using at least one of Digital Signal Processing (DSP), field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 620 may integrate one or a combination of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing display content; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 620, but may be implemented by a communication chip.

The Memory 610 may include a Random Access Memory (RAM) or a Read-Only Memory (ROM). The memory 610 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 610 may include a program storage area and a data storage area. Wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function, instructions for implementing the various method embodiments described above, and the like. The storage data area may store data created during use of the electronic device 600, and the like.

Referring to fig. 12, fig. 12 is a block diagram of a computer readable storage medium according to an embodiment of the present disclosure. The computer readable storage medium 700 has program code 710 stored therein, and the program code 710 is configured to, when called by the processor, cause the processor to execute the method for testing multiple devices provided by the embodiment of the present application.

The computer-readable storage medium 700 may be an electronic Memory such as a flash Memory, an Electrically-Erasable Programmable Read-Only-Memory (EEPROM), an Erasable Programmable Read-Only-Memory (EPROM), a hard disk, or a ROM. Optionally, the Computer-Readable Storage Medium 700 includes a Non-volatile Computer-Readable Medium (Non-Transitory Computer-Readable Storage Medium, non-TCRSM). The computer readable storage medium 700 has storage space for program code 710 for performing any of the method steps of the method described above. The program code 710 can be read from or written to one or more computer program products. The program code 710 may be compressed in a suitable form.

To sum up, according to the multi-device testing method, the multi-device testing device, the electronic device and the storage medium, the test task lists of the multiple testing devices are determined according to the importance degree of the software version to be tested, the priority of the test case and the load states of the multiple testing devices, so that the multiple testing devices execute the testing tasks according to the test task lists, development and testing can be integrated, manual intervention is not needed, testing efficiency can be effectively improved, in addition, the multiple testing tasks are distributed to the multiple testing devices as required, so that the multiple testing terminals can perform integrated testing simultaneously, dynamic distribution of testing resources can be realized, and testing efficiency can be effectively improved.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art will appreciate that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A method for testing multiple devices, comprising:

acquiring a software version to be tested, a test case of the software version to be tested and the load states of a plurality of test devices;

determining a test task list of the plurality of test devices according to the importance degree of the to-be-tested software version, the priority of the test case and the load states of the plurality of test devices, wherein the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks;

and issuing test tasks to the plurality of test devices according to the test task list so as to enable the plurality of test devices to execute the test tasks.

2. The method according to claim 1, wherein the determining the test task list of the plurality of test devices according to the importance of the to-be-tested software version, the priority of the test case, and the load status of the plurality of test devices comprises:

determining the plurality of test tasks according to the to-be-tested software version and the test cases, wherein each test task in the plurality of test tasks comprises an associated test case, and the associated test cases are a plurality of test cases with dependency relationship of the same to-be-tested software version;

and determining a test task list of the plurality of test devices according to the importance degree of the software version to be tested, the priorities of the plurality of test tasks and the load states of the plurality of test devices.

3. The method according to claim 2, wherein the determining a list of test tasks for the plurality of test devices according to the importance of the software version to be tested, the priorities of the plurality of test tasks, and the load statuses of the plurality of test devices comprises:

determining a first priority of each test task in the plurality of test tasks according to the importance degree of the software version to be tested, wherein the first priorities of the test tasks of the same software version to be tested are the same;

according to the first priority of each test task and the load states of the plurality of test devices, preliminarily determining a preliminary test task list of the plurality of test devices;

determining a second priority of each test task according to the priority of the associated test case included in each test task, wherein the first priority is higher than the second priority;

and determining the test task list of the plurality of test devices according to the second priority of each test task and the preliminary test task list.

4. The method of any of claims 1-3, wherein after said obtaining the load status of the plurality of test devices, the method further comprises:

if a test device with a specified test task is detected in the plurality of test devices, determining the test device with the specified test task as a specified test device, wherein the specified test task is a task directly issued to the specified test device through a preset specified module;

and forbidding to issue the test task to the specified test equipment.

5. A method for testing multiple devices, comprising:

acquiring a test task list sent by a server, wherein the test task list is determined by the server according to a software version to be tested, the priority of a test case of the software version to be tested and the load state of the test equipment, and the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks;

according to the priorities of the plurality of test tasks, reordering the test tasks to be executed in the test equipment to obtain a new test task execution sequence, wherein the test tasks to be executed comprise the plurality of test tasks in the test task list and the test tasks which are not executed before the test task list is obtained in the test equipment;

and sequentially executing the test tasks to be executed according to the new test task execution sequence.

6. The method of claim 5, further comprising:

if a specified test task directly issued to the equipment to be tested through a preset specified module is obtained, arranging the specified test task in front of the test task to be executed so as to execute the specified test task after the current test task is executed; or

And if the specified test task directly issued to the equipment to be tested through the preset specified module is obtained, stopping executing the current test task and starting executing the specified test task.

7. A multi-device testing apparatus, comprising:

the data acquisition module is used for acquiring a software version to be tested, a test case of the software version to be tested and the load states of a plurality of test devices;

the list determining module is used for determining a test task list of the plurality of test devices according to the importance degree of the to-be-tested software version, the priority of the test case and the load states of the plurality of test devices, wherein the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks;

and the task issuing module is used for issuing the test tasks to the plurality of test equipment according to the test task list so as to enable the plurality of test equipment to execute the test tasks.

8. A multi-device testing apparatus, comprising:

the system comprises a list acquisition module, a test task list and a test device, wherein the list acquisition module is used for acquiring a test task list sent by a server, the test task list is determined by the server according to a to-be-tested software version, the priority of a test case of the to-be-tested software version and the load state of the test device, and the test task list comprises a plurality of test tasks and the priorities corresponding to the plurality of test tasks;

the sequence adjusting module is used for reordering the to-be-executed test tasks in the test equipment according to the priorities of the plurality of test tasks to obtain a new test task execution sequence, wherein the to-be-executed test tasks comprise the plurality of test tasks in the test task list and the test tasks which are not executed before the test task list is obtained in the test equipment;

and the task execution module is used for sequentially executing the test tasks to be executed according to the new test task execution sequence.

9. An electronic device, comprising:

a memory;

one or more processors;

one or more applications, wherein the one or more applications are stored in the memory and configured to, when invoked by the one or more processors, cause the one or more processors to perform a method of testing a multi-device as recited in any of claims 1-6.

10. A computer-readable storage medium, wherein a program code is stored therein, the program code being configured to cause a processor to execute a method of testing a multi-device according to any one of claims 1 to 6 when called by the processor.