Multi-device testing methods, apparatus, electronic equipment, media and products

Abstract

This disclosure relates to a multi-device testing method, apparatus, electronic device, medium, and product. The method includes: receiving data upload requests from a first test device and a second test device, wherein the data upload request from the first test device includes a first call identifier, and the data upload request from the second test device includes a second call identifier; establishing a communication connection between the first test device and the second test device based on the first call identifier and the second call identifier; determining that the first test device and the second test device are in a call state, and performing a call test on the first test device and the second test device. Therefore, it is possible to simultaneously test the calling party's device and the called party's device in a single test, saving testing costs, achieving multi-device simultaneous testing, and effectively improving device testing efficiency.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of testing, and in particular, to a multi-device testing method, device, electronic device, medium and product. BACKGROUND

[0002] With the increase of the demand for call services in terminal devices, the benefits of many call core indicators are gradually consumed, reducing the call quality.

[0003] In the prior art, a manual testing method is usually used to perform call testing on terminal devices in a specified test environment. However, the test environment of the prior art is limited, and the testing efficiency is not high. SUMMARY

[0004] To solve the above technical problems, the present disclosure provides a multi-device testing method, device, electronic device, medium and product.

[0005] In a first aspect, the present disclosure provides a multi-device testing method, comprising:

[0006] receiving a data upload request of a first test device and a second test device, the data upload request of the first test device comprising a first call identifier, the first call identifier being generated by the first test device according to a first task identifier and a first test identifier, the data upload request of the second test device comprising a second call identifier, the second call identifier being generated by the second test device according to a second task identifier and a second test identifier;

[0007] establishing a communication connection between the first test device and the second test device based on the first call identifier and the second call identifier;

[0008] determining that the first test device and the second test device are in a call state, and performing call testing on the first test device and the second test device.

[0009] In a possible design, the establishing a communication connection between the first test device and the second test device based on the first call identifier and the second call identifier comprises:

[0010] determining that the first call identifier is the same as the second call identifier, and establishing a communication connection between the first test device and the second test device.

[0011] In a possible design, before the establishing a communication connection between the first test device and the second test device, the method further comprises:

[0012] determining a calling party and a called party performing a call event from the first test device and the second test device.

[0013] In a possible design, the determining of the caller and the callee of the call event from the first test device and the second test device comprises:

[0014] receiving a call role request of the first test device, the call role request of the first test device comprising a first request time;

[0015] receiving a call role request of the second test device, the call role request of the second test device comprising a second request time;

[0016] comparing the first request time and the second request time, and determining the caller and the callee of the call event.

[0017] In a possible design, the comparing of the first request time and the second request time, and the determining of the caller and the callee of the call event comprises:

[0018] determining the device with the earliest time from the first request time and the second request time as the caller of the call event;

[0019] determining the device with the latest time from the first request time and the second request time as the callee of the call event.

[0020] In a possible design, the determining of the caller and the callee of the call event from the first test device and the second test device comprises:

[0021] determining the caller and the callee of the call event according to a predetermined agreement protocol of the first test device and the second test device.

[0022] In a possible design, before the determining of the caller and the callee of the call event from the first test device and the second test device, the method further comprises:

[0023] obtaining device information of the first test device, and associating the device information of the first test device with the first call identifier;

[0024] obtaining device information of the second test device, and associating the device information of the second test device with the second call identifier.

[0025] In a possible design, the establishing of the communication connection of the first test device and the second test device comprises:

[0026] establishing the communication connection of the caller and the callee in response to a communication connection request of the caller to the callee;

[0027] The communication connection between the calling party and the called party is initiated by the calling party based on device information of the calling party and device information of the second test device.

[0028] In a possible design of the method, the call test performed on the first test device and the second test device comprises:

[0029] calling at least one test program corresponding to the first test identifier;

[0030] performing a call test on the first test device based on the at least one test program, and performing a call test on the second test device based on the at least one test program.

[0031] In a second aspect, the present disclosure provides a multi-device test apparatus, comprising:

[0032] a receiving module configured to receive a data upload request of a first test device and a data upload request of a second test device, wherein the data upload request of the first test device comprises a first call identifier, the first call identifier being generated by the first test device according to a first task identifier and a first test identifier, the data upload request of the second test device comprises a second call identifier, the second call identifier being generated by the second test device according to a second task identifier and a second test identifier;

[0033] a establishing module configured to establish a communication connection between the first test device and the second test device based on the first call identifier and the second call identifier;

[0034] a test module configured to determine that the first test device and the second test device are in a call state, and perform a call test on the first test device and the second test device.

[0035] In a possible design of the establishing module, the establishing module is specifically configured to:

[0036] determine that the first call identifier is identical to the second call identifier, and establish the communication connection between the first test device and the second test device.

[0037] In a possible design, the apparatus further comprises a determining module.

[0038] a determining module configured to determine a calling party and a called party performing a call event from the first test device and the second test device.

[0039] In a possible design of the determining module, the determining module comprises a receiving unit and a determining unit.

[0040] The receiving unit is configured to receive a call role request of the first test device, and the call role request of the first test device comprises a first request time.

[0041] The receiving unit is further configured to receive a call role request of the second test device, and the call role request of the second test device comprises a second request time.

[0042] The determining unit is configured to compare the first request time and the second request time, and determine a caller and a callee of the call event.

[0043] In a possible design, the determining unit is specifically configured to:

[0044] determine a device with an earlier time among the first request time and the second request time as the caller of the call event;

[0045] determine a device with a later time among the first request time and the second request time as the callee of the call event.

[0046] In a possible design, the determining module is specifically configured to:

[0047] determine the caller and the callee of the call event according to a predetermined agreement protocol of the first test device and the second test device.

[0048] In a possible design, the apparatus further includes an obtaining unit.

[0049] The obtaining unit is configured to obtain device information of the first test device, and associate the device information of the first test device with the first call identifier.

[0050] obtain device information of the second test device, and associate the device information of the second test device with the second call identifier.

[0051] In a possible design, the establishing module is specifically configured to:

[0052] establish a communication connection between the caller and the callee in response to a communication connection request of the caller to the callee;

[0053] The communication connection between the caller and the callee is initiated by the caller based on the device information of the caller and the device information of the second test device.

[0054] In a possible design, the test module is specifically configured to:

[0055] invoke at least one test program corresponding to the first test identifier;

[0056] The first test device is tested based on the at least one test procedure, and the second test device is tested based on the at least one test procedure.

[0057] In a third aspect, the present disclosure provides an electronic device, comprising: a memory and a processor; the memory is configured to store program instructions; and the processor is configured to invoke the program instructions in the memory to enable the electronic device to execute the multi-device testing method in the first aspect and any possible design of the first aspect.

[0058] In a fourth aspect, the present disclosure provides a computer storage medium, comprising computer instructions, when the computer instructions are executed on an electronic device, enabling the electronic device to execute the multi-device testing method in the first aspect and any possible design of the first aspect.

[0059] In a fifth aspect, the present disclosure provides a computer program product, when the computer program product is executed on a computer, enabling the computer to execute the multi-device testing method in the first aspect and any possible design of the first aspect.

[0060] The multi-device testing method, device, electronic device, medium and product provided by the embodiments of the present disclosure can receive a data upload request of a first test device and a second test device, wherein the data upload request of the first test device comprises a first call identifier, the first call identifier is generated by the first test device according to a first task identifier and a first test identifier, the data upload request of the second test device comprises a second call identifier, and the second call identifier is generated by the second test device according to a second task identifier and a second test identifier; based on the first call identifier and the second call identifier, a communication connection of the first test device and the second test device is established; it is determined that the first test device and the second test device are in a call state, and the call test of the first test device and the second test device is performed. Thus, the simultaneous test of the device of the calling party and the device of the called party can be realized in one test process, the test cost is saved, the overall data of the multi-device is tested at one time, and the test efficiency of the device is effectively improved. BRIEF DESCRIPTION OF DRAWINGS

[0061] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present disclosure and, together with the specification, serve to explain the principles of the present disclosure.

[0062] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0063] Figure 1A flowchart of a multi-device testing method provided by an embodiment of the present disclosure is shown in FIG. 1.

[0064] Figure 2 A flowchart of another multi-device testing method provided by an embodiment of the present disclosure is shown in FIG. 2.

[0065] Figure 3 An interaction diagram of a multi-device and a server provided by an embodiment of the present disclosure is shown in FIG. 3.

[0066] Figure 4 A structural diagram of a multi-device testing apparatus provided by an embodiment of the present disclosure is shown in FIG. 4. DETAILED DESCRIPTION

[0067] In order to more clearly understand the above-mentioned purposes, features and advantages of the present disclosure, the solutions of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0068] In the following description, many specific details are set forth in order to fully understand the present disclosure, but the present disclosure can also be implemented in other ways different from those described herein; obviously, the embodiments in the description are only some of the embodiments of the present disclosure, not all the embodiments.

[0069] Exemplarily, the present disclosure provides a multi-device testing method, apparatus, electronic device, medium and product, which receives a data uploading request of a first testing device and a second testing device, wherein the data uploading request of the first testing device comprises a first call identifier, the first call identifier is generated by the first testing device according to a first task identifier and a first testing identifier, the data uploading request of the second testing device comprises a second call identifier, the second call identifier is generated by the second testing device according to a second task identifier and a second testing identifier; a communication connection of the first testing device and the second testing device is established based on the first call identifier and the second call identifier; it is determined that the first testing device and the second testing device are in a call state, and a call test is performed on the first testing device and the second testing device. Thus, the simultaneous testing of the device of the calling party and the device of the called party can be realized in one testing process, the testing cost is saved, the one-time testing of multiple devices is realized, and the testing efficiency of the device is effectively improved.

[0070] It should be noted that the multi-device testing provided by the present disclosure can be applied to the testing scene of the device, and does not involve the real call information of the user, that is, the communication data of the user in the communication can be the pre-designed test data.

[0071] The multi-device testing method of the present disclosure is executed by a client installed in an electronic device. The electronic device can be a tablet, a mobile phone, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), a smart television, a smart screen, a high-definition television, a 4K television, a smart speaker, a smart projector, and the like. The present disclosure does not limit the specific type of the electronic device.

[0072] The present disclosure does not limit the type of operating system of the electronic device. For example, the operating system can be an Android system, a Linux system, a Windows system, an iOS system, and the like.

[0073] Referring to Figure 1 , Figure 1 A flowchart of a multi-device testing method provided by an embodiment of the present disclosure is shown in FIG. 1. As shown in FIG. 1, the multi-device testing method provided by the present disclosure can include the following steps. Figure 1

[0074] S110, receiving a data upload request of a first testing device and a second testing device, the data upload request of the first testing device including a first call identifier, and the data upload request of the second testing device including a second call identifier.

[0075] The first call identifier is generated by the first testing device according to a first task identifier and a first testing identifier, and the second call identifier is generated by the second testing device according to a second task identifier and a second testing identifier.

[0076] The first task identifier can be a type of task that the first testing device and the second testing device need to perform, such as a device performance testing task, a device updating task, and the like. The first testing identifier can be a specific testing item corresponding to the task identifier, such as a call page display duration, a call duration, a first frame arrival duration of call voice, a success rate of adding a room for a calling party and a called party, a call ring duration of the calling party requesting the called party, and the like.

[0077] It should be noted that the first testing device and the second testing device can initiate a call to the called party by the calling party. The first testing device or the second testing device can initiate the creation of a pre-call room to the server, thereby completing the call between the calling party and the called party.

[0078] ​For example, when the first test device is the caller and the second test device is the callee, the first test device can generate a unique first call identifier according to the first task identifier and the first test identifier, the first call identifier can be used to represent a room key value of a pre-call room, and the room key value can be used to uniquely represent the pre-call room to be created, and a room creation request carrying the room key value is sent to the server.

[0079] For example, when the first test device is the callee and the second test device is the caller, the second test device can generate a unique room key value according to the second task identifier and the second test identifier, the room key value can be used to uniquely represent the call room to be created, and a room creation request carrying the room key value is sent to the server.

[0080] It should be noted that when a test under a task is performed, the task identifier and the test identifier are the same, that is, for the same task identifier and the same test identifier, the room key value (i.e., the call identifier) obtained is the same.

[0081] S120, based on the first call identifier and the second call identifier, a communication connection between the first test device and the second test device is established.

[0082] The server can establish a pre-call room on the server according to the received first call identifier and second call identifier, so as to facilitate the communication connection between the first test device and the second test device.

[0083] For example, a plurality of candidate rooms can be pre-stored in the server, so as to randomly allocate a candidate room from the plurality of candidate rooms as a target room corresponding to the first call identifier / second call identifier; or the server can create a new call room as the target room based on the received first call identifier / second call identifier.

[0084] S130, determining that the first test device and the second test device are in a call state, and performing a call test on the first test device and the second test device.

[0085] The call between the first test device and the second test device can include a plurality of states, such as a call state, a pre-call state, and a non-call state, and can include the following various display modes.

[0086] In some embodiments, when the first test device initiates a call request to the second test device, and the second test device successfully establishes a call connection with the first test device, it can be determined that the first test device and the second test device are in a call state.

[0087] In some embodiments, when the first test device initiates a call request to the second test device, and the second test device answers the call request but fails to successfully establish a call connection with the first test device, it can be determined that the first test device and the second test device are in a pre-call state.

[0088] In some embodiments, when the first test device initiates a call request to the second test device, and the second test device answers the call request but fails to successfully establish a call connection with the first test device, it can be determined that the first test device and the second test device are in a pre-call state.

[0089] It should be noted that the call between the first test device and the second test device can switch between different states in real time, such as from a non-call state to a pre-call state, or from a pre-call state to a call state.

[0090] In some embodiments, the call test can include testing the performance parameters of the first test device and the second test device during the call between the first test device and the second test device.

[0091] In some embodiments, the call test performed on the first test device and the second test device can include:

[0092] calling at least one test program corresponding to the first test identifier;

[0093] performing a call test on the first test device based on the at least one test program, and performing a call test on the second test device based on the at least one test program.

[0094] In some embodiments, the server can perform a call test on the test device by calling a test program corresponding to a test identifier required during the test, thereby enabling simultaneous testing of multiple devices during the call.

[0095] It should be noted that the test identifier can correspond to one or more test programs, and when there are multiple test programs, the call test corresponding to the test identifier can be implemented after all the test programs have completed the test.

[0096] The multi-device testing method provided by the embodiments of the present disclosure receives a data upload request of a first testing device and a data upload request of a second testing device, wherein the data upload request of the first testing device comprises a first call identifier, the first call identifier is generated by the first testing device according to a first task identifier and a first testing identifier, the data upload request of the second testing device comprises a second call identifier, and the second call identifier is generated by the second testing device according to a second task identifier and a second testing identifier; a communication connection of the first testing device and the second testing device is established based on the first call identifier and the second call identifier; it is determined that the first testing device and the second testing device are in a call state, and a call test is performed on the first testing device and the second testing device. Thus, the simultaneous testing of the device of the calling party and the device of the called party can be realized in one testing process, the testing cost is saved, one-time testing of multiple devices is realized, and the testing efficiency of the device is effectively improved.

[0097] Figure 2 The flowchart of another multi-device testing method provided by the embodiments of the present disclosure is shown. The embodiment is based on the above-mentioned embodiment, and a possible implementation of S120 is as follows:

[0098] S1201, it is determined that the first call identifier is the same as the second call identifier, and a communication connection of the first testing device and the second testing device is established.

[0099] Wherein, when the server determines that the first call identifier sent by the first testing device is the same as the second call identifier sent by the second testing device, it is determined that the first testing device and the second testing device meet the call condition, and a communication connection of the first testing device and the second testing device is established, so as to facilitate the first testing device and the second testing device to perform a call event.

[0100] Wherein, the interaction schematic diagram between the first testing device, the second testing device and the server can be referred to Figure 3 as shown in the example.

[0101] Figure 3 In the above-mentioned embodiment, rack machine A can correspond to the first testing device, rack machine C can correspond to the second testing device, scheduling device A can control rack machine A to register device A in the server, scheduling device B can control rack machine C to register device B in the server, rack machine A binds the device information of device A to a target room created by the server, rack machine C binds the device information of device B to the target room created by the server, and according to the application time, it is determined that device A is the calling party in the target room and device B is the called party in the target room. Device A can attempt to call device B multiple times, and after device B answers the call, the test case is executed on the two testing devices, so as to obtain the test result of rack machine A and the test result of rack machine C.

[0102] Optionally, before establishing the communication connection between the first test device and the second test device, the method can further include:

[0103] From the first test device and the second test device, the caller and the callee of the call event are determined.

[0104] The server can determine the caller and the callee of the call event according to the pre-set conditions / rules.

[0105] The pre-set conditions / rules can include the application time of the terminal device (the first test device or the second test device) to the server, the agreement between one terminal device and another terminal device, the random selection principle of the server, etc.

[0106] In addition, if there are multiple call event records, the server can change or not change the caller and the callee of the current call event each time the call event occurs.

[0107] For example, in the historical call record, the caller is the first test device and the callee is the second test device. When the first test device and the second test device perform the call event again, the server can continue to take the first test device as the caller and the second test device as the callee, or can determine the caller and the callee again according to the above-mentioned screening rules.

[0108] Based on the above-mentioned embodiments, the caller and the callee of the call event are determined from the first test device and the second test device, which can include the following multiple implementation manners.

[0109] In some embodiments, the caller and the callee of the call event can be determined by receiving the call role request of the first test device, the call role request of the first test device including a first request time; receiving the call role request of the second test device, the call role request of the second test device including a second request time; and comparing the first request time and the second request time.

[0110] The first test device and the second test device can send the call role request to the server, so that the server determines the caller and the callee of the call event.

[0111] The first request time is the sending time of the call role request of the first test device to the server, and the second request time is the sending time of the call role request of the second test device to the server.

[0112] Thus, by comparing the sending time of the call role request of the first test device and the sending time of the call role request of the second test device, the calling party and the called party performing the call event are determined, and the calling party and the called party performing the call event are effectively determined.

[0113] Optionally, comparing the first request time and the second request time to determine the calling party and the called party performing the call event comprises:

[0114] determining the device with the earliest time in the first request time and the second request time as the calling party performing the call event;

[0115] determining the device with the latest time in the first request time and the second request time as the called party performing the call event.

[0116] Optionally, the server can measure the initiative of the device based on the sending time of the call role request of the first test device and the sending time of the call role request of the second test device, and thus, the device with the earliest sending time in the sending time of the call role request of the first test device and the sending time of the call role request of the second test device is determined as the calling party, and the device with the latest sending time in the sending time of the call role request of the first test device and the sending time of the call role request of the second test device is determined as the called party, so as to effectively determine the calling party and the called party performing the call event.

[0117] In some other embodiments, the calling party and the called party performing the call event can be determined according to a predetermined agreement protocol of the first test device and the second test device.

[0118] Optionally, the agreement protocol comprises the device to which the calling party belongs and the device to which the called party belongs.

[0119] Optionally, the agreement protocol can be predetermined by the user of the first test device and the user of the second test device, so that the server can quickly determine the calling party and the called party performing the call event based on the agreement protocol.

[0120] Optionally, before determining the calling party and the called party performing the call event from the first test device and the second test device, the method further comprises:

[0121] obtaining device information of the first test device, and associating the device information of the first test device with the first call identifier;

[0122] obtaining device information of the second test device, and associating the device information of the second test device with the second call identifier.

[0123] The server can obtain the device information of the first test device and the device information of the second test device, and associate them with the first call identifier and the second call identifier respectively, so as to facilitate the first test device and the second test device to successfully establish a call connection.

[0124] The communication connection between the first test device and the second test device is established, including:

[0125] In response to a communication connection request of the caller to the callee, a communication connection between the caller and the callee is established.

[0126] The communication connection between the caller and the callee is initiated by the caller to the callee based on the device information of the caller and the device information of the second test device.

[0127] When the caller calls the callee through the device information of the callee, the caller can call the callee through the video / voice call button in the private message page of the callee, so as to display a call station incoming call prompt in the private message page of the callee, and facilitate the callee to click / answer the call station incoming call prompt to establish a call connection with the caller.

[0128] Figure 4 A structural schematic diagram of a multi-device test device provided by the present disclosure is shown in FIG. 4. Figure 4 The multi-device test device 400 of the present embodiment includes a receiving module 410, an establishing module 420 and a testing module 430, wherein:

[0129] The receiving module 410 is configured to receive data upload requests of a first test device and a second test device, wherein the data upload request of the first test device includes a first call identifier, the first call identifier is generated by the first test device according to a first task identifier and a first test identifier, the data upload request of the second test device includes a second call identifier, and the second call identifier is generated by the second test device according to a second task identifier and a second test identifier.

[0130] The establishing module 420 is configured to establish a communication connection between the first test device and the second test device based on the first call identifier and the second call identifier.

[0131] The testing module 430 is configured to determine that the first test device and the second test device are in a call state, and perform a call test on the first test device and the second test device.

[0132] In the present embodiment, the establishing module 420 is specifically configured to:

[0133] Once it is determined that the first call identifier and the second call identifier are the same, a communication connection is established between the first test device and the second test device.

[0134] In this embodiment, optionally, the device further includes: a determining module;

[0135] The determination module is used to determine the calling party and the called party who performed the call event from the first test device and the second test device.

[0136] In this embodiment, optionally, the determining module includes: a receiving unit and a determining unit;

[0137] A receiving unit is configured to receive a call role request from the first test device, wherein the call role request from the first test device includes a first request time.

[0138] The receiving unit is also configured to receive a call role request from the second test device, wherein the call role request from the second test device includes a second request time.

[0139] The determining unit is used to compare the first request time and the second request time to determine the calling party and the called party who performed the call event.

[0140] In this embodiment, optionally, the determining unit is specifically used for:

[0141] The device with the earliest time between the first request time and the second request time is determined as the calling party that executes the call event;

[0142] The device with the latest time between the first request time and the second request time is identified as the called party that executes the call event.

[0143] In this embodiment, optionally, the determining module is specifically used for:

[0144] According to the pre-determined agreement between the first test device and the second test device, the calling party and the called party who will execute the call event are determined.

[0145] In this embodiment, optionally, the device further includes: an acquisition unit;

[0146] The acquisition unit is used to acquire the device information of the first test device and associate the device information of the first test device with the first call identifier;

[0147] Obtain the device information of the second test device and associate the device information of the second test device with the second call identifier.

[0148] In this embodiment, optionally, the establishment module 420 is specifically used for:

[0149] establishing a communication connection between the calling party and the called party in response to the calling party's communication connection request to the called party;

[0150] The communication connection between the calling party and the called party is initiated by the calling party to the called party based on the device information of the calling party and the device information of the second test device.

[0151] In this embodiment, the test module 430 is specifically configured to:

[0152] invoke at least one test program corresponding to the first test identifier;

[0153] perform a call test on the first test device based on the at least one test program, and perform a call test on the second test device based on the at least one test program.

[0154] The multi-device test apparatus provided by the present disclosure can execute the method embodiments described above, and the specific implementation principles and technical effects can be referred to the method embodiments described above, which will not be described here again.

[0155] Illustratively, the present disclosure provides an electronic device, comprising: one or more processors; a memory; and one or more computer programs; wherein the one or more computer programs are stored in the memory; the one or more processors, when executing the one or more computer programs, cause the electronic device to implement the multi-device test method of the foregoing embodiments.

[0156] Illustratively, the present disclosure provides a chip system, which is applied to an electronic device comprising a memory and a sensor; the chip system comprises: a processor; when the processor executes the multi-device test method of the foregoing embodiments.

[0157] Illustratively, the present disclosure provides a computer-readable storage medium, which stores a computer program; when the computer program is executed by a processor, the electronic device implements the multi-device test method of the foregoing embodiments.

[0158] Illustratively, the present disclosure provides a computer program product, which, when running on a computer, causes the computer to execute the multi-device test method of the foregoing embodiments.

[0159] In the above embodiments, all or part of the functions can be implemented by software, hardware, or a combination of software and hardware. When implemented by software, all or part of the functions can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. containing one or more available media sets. The available media can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

[0160] It should be noted that, in this document, relational terms such as "first" and "second", and the like, are used solely to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without more limitations, an element defined by the phrase "comprising a..." does not exclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0161] The above description is merely one specific implementation of the present disclosure, and thus the skilled in the art can understand or implement the present disclosure without departing from the spirit or scope of the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other embodiments without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A multi-device testing method, characterized by, The method comprises the following steps: receiving a data upload request of a first test device and a second test device, the data upload request of the first test device comprising a first call identifier, the first call identifier being generated by the first test device according to a first task identifier and a first test identifier, the first task identifier being a type of task that the first test device and the second test device need to perform, and the first test identifier being a corresponding test item under the first task identifier, the data upload request of the second test device comprising a second call identifier, the second call identifier being generated by the second test device according to a second task identifier and a second test identifier; based on the first call identifier and the second call identifier, establishing a communication connection of the first test device and the second test device; determining that the first test device and the second test device are in a call state, and performing a call test on the first test device and the second test device.

2. The method of claim 1, wherein, The step of establishing the communication connection of the first test device and the second test device based on the first call identifier and the second call identifier comprises: determining that the first call identifier is the same as the second call identifier, and establishing the communication connection of the first test device and the second test device.

3. The method of claim 2, wherein, Before the step of establishing the communication connection of the first test device and the second test device, the method further comprises: determining a calling party and a called party that perform a call event from the first test device and the second test device.

4. The method of claim 3, wherein, The step of determining the calling party and the called party that perform the call event from the first test device and the second test device comprises: receiving a call role request of the first test device, the call role request of the first test device comprising a first request time; receiving a call role request of the second test device, the call role request of the second test device comprising a second request time; comparing the first request time and the second request time to determine the calling party and the called party that perform the call event.

5. The method of claim 4, wherein, The step of comparing the first request time and the second request time to determine the calling party and the called party that perform the call event comprises: determining the device with the earliest time among the first request time and the second request time as the calling party that performs the call event; determining the device with the latest time among the first request time and the second request time as the called party that performs the call event.

6. The method of claim 4, wherein, The step of determining the calling party and the called party that perform the call event from the first test device and the second test device comprises: determining the calling party and the called party that perform the call event according to a predetermined agreement protocol of the first test device and the second test device.

7. The method according to any one of claims 4-6, characterized in that, Before the step of determining the calling party and the called party that perform the call event from the first test device and the second test device, the method further comprises: obtaining device information of the first test device, and associating the device information of the first test device with the first call identifier; obtaining device information of the second test device, and associating the device information of the second test device with the second call identifier.

8. The method of claim 7, wherein, The establishing of the communication connection of the first test device and the second test device comprises: In response to the communication connection request of the caller to the callee, the communication connection of the caller and the callee is established; The communication connection of the caller and the callee is initiated by the caller to the callee based on the device information of the caller and the device information of the second test device.

9. The method of claim 1, wherein, The call test of the first test device and the second test device comprises: Calling at least one test program corresponding to the first test identifier; Based on the at least one test program, the call test of the first test device and the second test device is performed.

10. A multi-device test apparatus, characterized by, Comprise: The receiving module is used for receiving the data upload request of the first test device and the second test device, the data upload request of the first test device comprises a first call identifier, the first call identifier is generated by the first test device according to a first task identifier and a first test identifier, the first task identifier is the type of task that the first test device and the second test device need to perform, the first test identifier is the corresponding test item under the first task identifier, the data upload request of the second test device comprises a second call identifier, and the second call identifier is generated by the second test device according to a second task identifier and a second test identifier; The establishing module is used for establishing the communication connection of the first test device and the second test device based on the first call identifier and the second call identifier; The test module is used for determining that the first test device and the second test device are in a call state, and performing the call test of the first test device and the second test device.

11. An electronic device comprising: One or more processors; Memory; And one or more computer programs; wherein the one or more computer programs are stored in the memory; characterized in that, the one or more processors execute the one or more computer programs, so that the electronic device realizes the multi-device test method of any one of claims 1-9.

12. A computer storage medium, characterized in that Comprise computer instructions, when the computer instructions run on an electronic device, make the electronic device execute the multi-device test method of any one of claims 1-9.

13. A computer program product, characterised in that, When the computer program product runs on a computer, the computer executes the multi-device test method of any one of claims 1-9.

Images