Application testing systems, methods, apparatus, computer equipment and media

Abstract

This application discloses an application testing system, method, apparatus, computer equipment, and medium, belonging to the field of computer technology. The method includes: a first control device displaying at least one shared device identifier; the first control device, in response to a selection operation on the displayed first shared device identifier, sending a test request to a test server; the test server sending an application test task to the first shared device corresponding to the first shared device identifier; and the first shared device executing the application test task. This method enables remote access to shared devices for application testing without requiring testers to purchase or borrow them, saving time associated with borrowing shared devices, improving testing efficiency, and fully utilizing the capabilities of shared devices.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an application testing system, method, apparatus, computer equipment, and medium. Background Technology

[0002] With the development of computer technology, there are more and more types of smart hardware devices and applications. Considering that the same application needs to run on different types of devices, in order to ensure the running effect, it is necessary to use different types of testing equipment to test the application.

[0003] Testers typically configure multiple devices by purchasing or borrowing them. They then install the application to be tested on each device and perform operations on it to perform testing. However, this testing method requires testers to purchase or borrow equipment, which incurs high costs and consumes a significant amount of time, resulting in low testing efficiency. Summary of the Invention

[0004] This application provides an application testing system, method, apparatus, computer equipment, and medium, which improves testing efficiency. The technical solution is as follows:

[0005] On the one hand, an application testing system is provided, the system including a test server, multiple control devices and multiple shared devices;

[0006] A first control device is configured to display at least one shared device identifier, wherein the first control device is any control device in the system;

[0007] The first control device is further configured to send a test request to the test server in response to a selection operation on a displayed first shared device identifier, the test request carrying the first shared device identifier;

[0008] The test server is used to send application test tasks to the first shared device corresponding to the first shared device identifier;

[0009] The first shared device is used to perform the application testing task.

[0010] Optionally, the second control device is further configured to obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0011] Optionally, a third control device is used to display a graphic code, the graphic code including the group identifier, and the third control device is any control device in the system;

[0012] The second shared device is used to scan the graphic code to obtain the group identifier.

[0013] Optionally, the test server is further configured to obtain the first control device identifier associated with the group identifier, and send a connection notification message to the first control device corresponding to the first control device identifier. The connection notification message includes the second shared device identifier and is used to indicate that the second shared device has established a communication connection with the test server.

[0014] The first control device is configured to display the identifier of the second shared device according to the connection notification message.

[0015] Optionally, the third control device is used for:

[0016] If the shared device identifier is not included in the group corresponding to the group identifier, the graphic code is displayed; or,

[0017] If the shared device identifier is already included in the group corresponding to the group identifier, the graphic code and the shared device identifier included in the group are displayed.

[0018] Optionally, the first control device is further configured to send a control association request to the test server, the control association request carrying the group identifier and the first control device identifier;

[0019] The test server is also used to associate the first control device identifier with the group identifier.

[0020] Optionally, the first control device is configured to display the device identifier and device status of the at least one shared device, wherein the device status is either available or unavailable.

[0021] Optionally, the test server is further configured to determine the device status of the at least one shared device and send the device status of the at least one shared device to the first control device.

[0022] Optionally, each of the plurality of shared devices is used to send a status signal to the test server;

[0023] The test server is also configured to determine the device status of any shared device as unavailable if it has not received a status signal from any shared device within a preset time period prior to the current moment.

[0024] Optionally, the test server is further configured to obtain the group identifier associated with the first shared device identifier;

[0025] The test server is also used to obtain at least one control device identifier associated with the group identifier and send the test result to the control device corresponding to the at least one control device identifier.

[0026] Optionally, the first control device is configured to send a test result acquisition request to the test server, the test result acquisition request carrying at least one application test task;

[0027] The test server is also used to send the test results corresponding to the at least one application test task to the first control device.

[0028] On the other hand, an application testing method is provided, applied to an application testing system, the system including a test server, multiple control devices, and multiple shared devices; the method includes:

[0029] The first control device displays at least one shared device identifier, and the first control device is any control device in the system;

[0030] In response to a selection operation on the displayed first shared device identifier, the first control device sends a test request to the test server, the test request carrying the first shared device identifier;

[0031] The test server sends an application test task to the first shared device corresponding to the first shared device identifier;

[0032] The first shared device performs the application testing task.

[0033] Optionally, before the first control device displays at least one shared device identifier, the method further includes:

[0034] The first control device sends an identifier query request to the test server, the identifier query request carrying the identifier of the first control device;

[0035] The test server sends the at least one shared device identifier to the first control device corresponding to the first control device identifier.

[0036] Optionally, the test server sends the at least one shared device identifier to the first control device corresponding to the first control device identifier, including:

[0037] The first control device acquires the group identifier, and the identifier query request also carries the group identifier;

[0038] The test server queries the group corresponding to the group identifier, the group being used to record the shared device identifier associated with the group identifier, and sends the shared device identifier in the group to the first control device.

[0039] Optionally, the test server sends an application test task to the first shared device corresponding to the first shared device identifier, including:

[0040] When the test server establishes a communication connection with the first shared device, it sends the application test task to the first shared device; or...

[0041] The test server queries the second control device identifier associated with the first shared device identifier, the second control device identifier referring to the second control device that has established a communication connection with the first shared device; and sends a task issuance instruction to the second control device, the task issuance instruction carrying the application test task and the first shared device identifier.

[0042] The second control device sends the application test task to the first shared device corresponding to the first shared device identifier.

[0043] Optionally, before the test server queries the second control device identifier associated with the first shared device identifier, the method further includes:

[0044] The second control device establishes a communication connection with the first shared device, obtains the identifier of the first shared device, and sends a device association request to the test server. The device association request carries the identifier of the first shared device and the identifier of the second control device.

[0045] The test server associates the first shared device identifier and the second control device identifier.

[0046] Optionally, before the test server queries the second control device identifier associated with the first shared device identifier, the method further includes:

[0047] The second control device acquires the group identifier, and the device association request also carries the group identifier;

[0048] The test server adds the first shared device identifier to the group corresponding to the group identifier.

[0049] Optionally, the second control device sends the application test task to the first shared device corresponding to the first shared device identifier, including:

[0050] The second control device obtains the test interface information of the first shared device, and sends the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0051] Optionally, before the first control device displays at least one shared device identifier, the method further includes:

[0052] The second sharing device obtains the group identifier and sends a sharing association request to the test server. The sharing association request carries the group identifier and the second sharing device identifier. The second sharing device can be any sharing device in the system.

[0053] The test server adds the second shared device identifier to the group corresponding to the group identifier and establishes a communication connection with the second shared device. The group is used to record the shared device identifier associated with the group identifier.

[0054] Optionally, the second sharing device obtains the packet identifier, including:

[0055] The third control device displays a graphic code, which includes the group identifier. The third control device can be any control device in the system.

[0056] The second sharing device scans the graphic code to obtain the group identifier.

[0057] Optionally, the third control device displays a graphic code, including:

[0058] If the third control device does not include a shared device identifier in the group corresponding to the group identifier, it displays the graphic code; or...

[0059] If the shared device identifier is already included in the group corresponding to the group identifier, the third control device displays the graphic code and the shared device identifier included in the group.

[0060] Optionally, after the test server adds the second shared device identifier to the group corresponding to the group identifier, the method further includes:

[0061] The test server obtains the first control device identifier associated with the group identifier and sends a connection notification message to the first control device corresponding to the first control device identifier. The connection notification message includes the second shared device identifier and is used to indicate that the second shared device has established a communication connection with the test server.

[0062] The first control device displays the identifier of the second shared device according to the connection notification message.

[0063] Optionally, before the test server obtains the first control device identifier associated with the group identifier, the method further includes:

[0064] The first control device sends a control association request to the test server, the control association request carrying the group identifier and the first control device identifier;

[0065] The test server associates the first control device identifier with the group identifier.

[0066] Optionally, in response to a selection operation on the displayed first shared device identifier, the first control device sends a test request to the test server, including:

[0067] The first control device sends a test request to the test server through the target application to be tested. The test request also carries the target application identifier of the target application. The application test task includes the target application identifier.

[0068] The first shared device performs the application testing task, including:

[0069] The first sharing device determines the target application corresponding to the target application identifier, and executes the application testing task through the target application.

[0070] Optionally, the first control device displays at least one shared device identifier, including:

[0071] The first control device displays the device identifier and device status of the at least one shared device, wherein the device status is either available or unavailable.

[0072] Optionally, before the first control device displays the device identifier and device status of the at least one shared device, the method further includes:

[0073] The test server determines the device status of the at least one shared device and sends the device status of the at least one shared device to the first control device.

[0074] Optionally, before the test server determines the device status of the at least one shared device, the method further includes:

[0075] Each of the plurality of shared devices sends a status signal to the test server;

[0076] If the test server does not receive a status signal from any shared device within a preset time period prior to the current moment, it determines the device status of any shared device as unavailable.

[0077] Optionally, after the first shared device executes the application testing task, the method further includes:

[0078] The first shared device sends the test results corresponding to the application test task to the test server;

[0079] The test server stores the test results in correspondence with the application test tasks.

[0080] Optionally, after the test server stores the test results corresponding to the application test task, the method further includes:

[0081] The test server obtains the group identifier associated with the first shared device identifier;

[0082] The test server obtains at least one control device identifier associated with the group identifier and sends the test result to the control device corresponding to the at least one control device identifier.

[0083] Optionally, after the test server stores the test results corresponding to the application test task, the method further includes:

[0084] The first control device sends a test result retrieval request to the test server, the test result retrieval request carrying at least one application test task;

[0085] The test server sends the test results corresponding to the at least one application test task to the first control device.

[0086] On the other hand, an application testing method is provided, applied to a first control device in an application testing system. The system includes a test server, multiple control devices, and multiple shared devices. The first control device is any one of the control devices in the system. The method includes:

[0087] Display at least one shared device identifier;

[0088] In response to the selection operation of the first shared device identifier displayed, a test request is sent to the test server, the test request carrying the first shared device identifier;

[0089] The test server is used to send application test tasks to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test tasks.

[0090] Optionally, before displaying at least one shared device identifier, the method further includes:

[0091] The test server sends an identifier query request to the test server, the identifier query request carrying a first control device identifier, and the test server is also used to send the at least one shared device identifier to the first control device corresponding to the first control device identifier.

[0092] Optionally, the identifier query request also carries a group identifier, and the test server is further used to query the group corresponding to the group identifier, the group being used to record the shared device identifier associated with the group identifier, and to send the shared device identifier in the group to the first control device.

[0093] Optionally, before displaying at least one shared device identifier, the method further includes:

[0094] The display graphic code includes the group identifier, and the second sharing device is used to scan the graphic code to obtain the group identifier.

[0095] Optionally, the display graphic code includes:

[0096] If the shared device identifier is not included in the group corresponding to the group identifier, the graphic code is displayed; or,

[0097] If the shared device identifier is already included in the group corresponding to the group identifier, the graphic code and the shared device identifier included in the group are displayed.

[0098] Optionally, before displaying at least one shared device identifier, the method further includes:

[0099] The system receives a connection notification message sent by the test server. The connection notification message includes the identifier of the second shared device and is used to indicate that the second shared device has established a communication connection with the test server.

[0100] The second shared device identifier is displayed according to the connection notification message;

[0101] The test server is further configured to obtain the first control device identifier associated with the group identifier and send the connection notification message to the first control device corresponding to the first control device identifier.

[0102] Optionally, before receiving the connection notification message sent by the test server, the method further includes:

[0103] A control association request is sent to the test server. The control association request carries the group identifier and the first control device identifier. The test server is also used to associate the first control device identifier with the group identifier.

[0104] Optionally, sending a test request to the test server includes:

[0105] The first shared device sends a test request to the test server through the target application to be tested. The test request also carries the target application identifier of the target application. The application test task includes the target application identifier. The first shared device is used to determine the target application corresponding to the target application identifier and execute the application test task through the target application.

[0106] Optionally, displaying at least one shared device identifier includes:

[0107] Display the device identifier and device status of the at least one shared device, wherein the device status is either available or unavailable.

[0108] Optionally, before displaying the device identifier and device status of the at least one shared device, the method further includes:

[0109] Receive the device status of at least one shared device sent by the test server;

[0110] The test server is also used to determine the device status of the at least one shared device and send the device status of the at least one shared device to the first control device.

[0111] Optionally, after sending the test request to the test server, the method further includes:

[0112] A test result retrieval request is sent to the test server, the test result retrieval request carrying at least one application test task, and the test server is also used to send the test results corresponding to the at least one application test task to the first control device.

[0113] On the other hand, an application testing method is provided, applied to a test server in an application testing system, the system including the test server, multiple control devices, and multiple shared devices, the method comprising:

[0114] The system receives a test request sent by a first control device, the test request carrying a first shared device identifier. The first control device can be any control device in the system. The first control device is used to display at least one shared device identifier. In response to a selection operation on the displayed first shared device identifier, the system sends the test request to the test server.

[0115] An application test task is sent to the first shared device corresponding to the first shared identifier, and the first shared device is used to execute the application test task.

[0116] Optionally, before receiving the test request sent by the first control device, the method further includes:

[0117] Receive an identifier query request sent by the first control device, wherein the identifier query request carries the identifier of the first control device;

[0118] Send the at least one shared device identifier to the first control device corresponding to the first control device identifier.

[0119] Optionally, the query request further carries a group identifier, and sending the at least one shared device identifier to the first control device corresponding to the first control device identifier includes:

[0120] Query the group corresponding to the group identifier, whereby the group is used to record the shared device identifier associated with the group identifier;

[0121] Send the shared device identifier in the packet to the first control device;

[0122] The first control device is also used to acquire the group identifier.

[0123] Optionally, sending the application test task to the first sharing device corresponding to the first sharing identifier includes:

[0124] If a communication connection is established between the test server and the first shared device, the application test task is sent to the first shared device; or...

[0125] The system queries the second control device identifier associated with the first shared device identifier, sends a task delivery instruction to the second control device corresponding to the second control device identifier, establishes a communication connection between the second control device and the first shared device, and the task delivery instruction carries the application test task and the first shared device identifier. The second control device is used to send the application test task to the first shared device corresponding to the first shared device identifier.

[0126] Optionally, before querying the second control device identifier associated with the first shared device identifier, the method further includes:

[0127] The second control device receives a device association request sent by the second control device. The device association request carries the first shared device identifier and the second control device identifier. The second control device is used to establish a communication connection with the first shared device and obtain the first shared device identifier.

[0128] Associate the first shared device identifier with the second control device identifier.

[0129] Optionally, the second control device is further configured to obtain a group identifier, the device association request further carries the group identifier, and after receiving the device association request sent by the second control device, the method further includes;

[0130] Add the first shared device identifier to the group corresponding to the group identifier.

[0131] Optionally, the second control device is further configured to obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0132] Optionally, before receiving the test request sent by the first control device, the method further includes:

[0133] The system receives a sharing association request sent by a second sharing device. The sharing association request carries a group identifier and a second sharing device identifier. The second sharing device can be any sharing device in the system. The second sharing device is used to obtain the group identifier and send the sharing association request to the test server.

[0134] The second shared device identifier is added to the group corresponding to the group identifier, and a communication connection is established with the second shared device. The group is used to record the shared device identifier associated with the group identifier.

[0135] Optionally, after establishing a communication connection with the second shared device, the method further includes:

[0136] Obtain the first control device identifier associated with the group identifier, and send a connection notification message to the first control device corresponding to the first control device identifier. The connection notification message includes the second shared device identifier and is used to indicate that the second shared device has established a communication connection with the test server. The first control device is used to display the second shared device identifier according to the connection notification message.

[0137] Optionally, before obtaining the first control device identifier associated with the group identifier, the method further includes:

[0138] Receive a control association request sent by the first control device, wherein the control association request carries the group identifier and the identifier of the first control device;

[0139] Associate the first control device identifier with the group identifier.

[0140] Optionally, before receiving the test request sent by the first control device, the method further includes:

[0141] The device status of the at least one shared device is determined, and the device status of the at least one shared device is sent to the first control device. The first control device is used to display the device identifier and device status of the at least one shared device, wherein the device status is an available status or an unavailable status.

[0142] Optionally, determining the device status of the at least one shared device includes:

[0143] Receive the status signal sent by each of the plurality of shared devices;

[0144] If no status signal is received from any shared device within a preset time period prior to the current moment, the device status of any shared device is determined to be unavailable.

[0145] Optionally, after sending the application test task to the first sharing device corresponding to the first sharing identifier, the method further includes:

[0146] Receive the test results corresponding to the application test task sent by the first shared device;

[0147] The test results are stored in correspondence with the application test tasks.

[0148] Optionally, after storing the test results in correspondence with the application test task, the method further includes:

[0149] Obtain the group identifier associated with the first shared device identifier;

[0150] Obtain at least one control device identifier associated with the group identifier, and send the test result to the control device corresponding to the at least one control device identifier.

[0151] Optionally, after storing the test results in correspondence with the application test task, the method further includes:

[0152] Receive a test result acquisition request sent by the first control device, wherein the test result acquisition request carries at least one application test task;

[0153] Send the test results corresponding to the at least one application test task to the first control device.

[0154] On the other hand, an application testing method is provided, applied to a second control device in an application testing system, the system including a test server, multiple control devices, and multiple shared devices, the method comprising:

[0155] Receive a task distribution instruction sent by the test server, the task distribution instruction carrying an application test task and a first shared device identifier;

[0156] The application test task is sent to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test task.

[0157] The second control device establishes a communication connection with the first shared device; the test server is used to receive a test request sent by the first control device carrying the identifier of the first shared device, query the identifier of the second control device associated with the identifier of the first shared device, and send the task issuance instruction to the second control device corresponding to the identifier of the second control device.

[0158] Optionally, before receiving the task issuance instruction sent by the test server, the method further includes:

[0159] Establish a communication connection with the first shared device, obtain the identifier of the first shared device, and send a device association request to the test server. The device association request carries the identifier of the first shared device and the identifier of the second control device.

[0160] The test server is also used to associate the first shared device identifier and the second control device identifier.

[0161] Optionally, sending the application test task to the first shared device corresponding to the first shared device identifier includes:

[0162] Obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0163] On the other hand, an application testing apparatus is provided, the apparatus comprising:

[0164] A display module is used to display at least one shared device identifier;

[0165] A test request sending module is configured to send a test request to the test server in response to a selection operation on the first shared device identifier displayed, the test request carrying the first shared device identifier;

[0166] The test server is used to send application test tasks to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test tasks.

[0167] Optionally, the device further includes:

[0168] The query request sending module is used to send an identifier query request to the test server. The identifier query request carries a first control device identifier. The test server is also used to send the at least one shared device identifier to the first control device corresponding to the first control device identifier.

[0169] Optionally, the identifier query request also carries a group identifier, and the test server is further used to query the group corresponding to the group identifier, the group being used to record the shared device identifier associated with the group identifier, and to send the shared device identifier in the group to the first control device.

[0170] Optionally, the display module is further configured to display a graphic code, the graphic code including the group identifier, and the second sharing device is configured to scan the graphic code to obtain the group identifier.

[0171] Optionally, the display module is further configured to:

[0172] If the shared device identifier is not included in the group corresponding to the group identifier, the graphic code is displayed; or,

[0173] If the shared device identifier is already included in the group corresponding to the group identifier, the graphic code and the shared device identifier included in the group are displayed.

[0174] Optionally, the device further includes:

[0175] A notification receiving module is used to receive a connection notification message sent by the test server. The connection notification message includes the identifier of the second shared device and is used to indicate that the second shared device has established a communication connection with the test server.

[0176] The display module is used to display the second shared device identifier according to the connection notification message; wherein, the test server is further used to obtain the first control device identifier associated with the group identifier and send the connection notification message to the first control device corresponding to the first control device identifier.

[0177] Optionally, the device further includes:

[0178] The association request sending module is used to send a control association request to the test server. The control association request carries the group identifier and the first control device identifier. The test server is also used to associate the first control device identifier with the group identifier.

[0179] Optionally, the association request sending module is used to send a test request to the test server through the target application to be tested. The test request also carries the target application identifier of the target application. The application test task includes the target application identifier. The first shared device is used to determine the target application corresponding to the target application identifier and execute the application test task through the target application.

[0180] Optionally, the display module is used to display the device identifier and device status of the at least one shared device, wherein the device status is an available status or an unavailable status.

[0181] Optionally, the device further includes:

[0182] A status receiving module is used to receive the device status of the at least one shared device sent by the test server; wherein, the test server is further used to determine the device status of the at least one shared device and send the device status of the at least one shared device to the first control device.

[0183] Optionally, the device further includes:

[0184] The request sending module is used to send a test result retrieval request to the test server. The test result retrieval request carries at least one application test task. The test server is also used to send the test results corresponding to the at least one application test task to the first control device.

[0185] On the other hand, an application testing apparatus is provided, the apparatus comprising:

[0186] A test request receiving module is used to receive a test request sent by a first control device. The test request carries a first shared device identifier. The first control device is any control device in the system. The first control device is used to display at least one shared device identifier. In response to a selection operation on the displayed first shared device identifier, the first control device sends the test request to the test server.

[0187] The task sending module is used to send an application test task to the first shared device corresponding to the first shared identifier, and the first shared device is used to execute the application test task.

[0188] Optionally, the device further includes:

[0189] The query request receiving module is used to receive an identifier query request sent by the first control device, wherein the identifier query request carries the identifier of the first control device;

[0190] The identifier sending module is used to send the at least one shared device identifier to the first control device corresponding to the first control device identifier.

[0191] Optionally, the query request also carries a group identifier, and the identifier sending module is used to:

[0192] Query the group corresponding to the group identifier, whereby the group is used to record the shared device identifier associated with the group identifier;

[0193] The first control device sends the shared device identifier in the packet to the first control device; wherein the first control device is further configured to obtain the packet identifier.

[0194] Optionally, the task sending module is configured to:

[0195] If a communication connection is established between the test server and the first shared device, the application test task is sent to the first shared device; or...

[0196] The system queries the second control device identifier associated with the first shared device identifier, sends a task delivery instruction to the second control device corresponding to the second control device identifier, establishes a communication connection between the second control device and the first shared device, and the task delivery instruction carries the application test task and the first shared device identifier. The second control device is used to send the application test task to the first shared device corresponding to the first shared device identifier.

[0197] Optionally, the device further includes:

[0198] The association request receiving module is used to receive a device association request sent by the second control device. The device association request carries the first shared device identifier and the second control device identifier. The second control device is used to establish a communication connection with the first shared device and obtain the first shared device identifier.

[0199] The association module is used to associate the first shared device identifier and the second control device identifier.

[0200] Optionally, the second control device is further configured to acquire a group identifier, and the device further includes;

[0201] The grouping module is used to add the first shared device identifier to the group corresponding to the group identifier.

[0202] Optionally, the second control device is further configured to obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0203] Optionally, the association request receiving module is further configured to receive a sharing association request sent by a second sharing device, the sharing association request carrying a group identifier and a second sharing device identifier, the second sharing device being any sharing device in the system, the second sharing device being configured to obtain the group identifier and send the sharing association request to the test server;

[0204] The association module is further configured to add the second shared device identifier to the group corresponding to the group identifier, and establish a communication connection with the second shared device. The group is used to record the shared device identifier associated with the group identifier.

[0205] Optionally, the device further includes:

[0206] The connection module is used to obtain the first control device identifier associated with the group identifier, and send a connection notification message to the first control device corresponding to the first control device identifier. The connection notification message includes the second shared device identifier and is used to indicate that the second shared device has established a communication connection with the test server. The first control device is used to display the second shared device identifier according to the connection notification message.

[0207] Optionally, the association request receiving module is further configured to receive a control association request sent by the first control device, wherein the control association request carries the group identifier and the identifier of the first control device;

[0208] The association module is further configured to associate the first control device identifier with the group identifier.

[0209] Optionally, the device further includes:

[0210] A status determination module is used to determine the device status of the at least one shared device and send the device status of the at least one shared device to the first control device. The first control device is used to display the device identifier and device status of the at least one shared device, wherein the device status is an available status or an unavailable status.

[0211] Optionally, the state determination module is used to:

[0212] Receive the status signal sent by each of the plurality of shared devices;

[0213] If no status signal is received from any shared device within a preset time period prior to the current moment, the device status of any shared device is determined to be unavailable.

[0214] Optionally, the device further includes:

[0215] The result receiving module is used to receive the test results corresponding to the application test task sent by the first shared device;

[0216] The result storage module is used to store the test results in correspondence with the application test tasks.

[0217] Optionally, the device further includes:

[0218] The identifier acquisition module is used to acquire the group identifier associated with the identifier of the first shared device;

[0219] The result sending module is used to obtain at least one control device identifier associated with the group identifier and send the test result to the control device corresponding to the at least one control device identifier.

[0220] Optionally, the device further includes:

[0221] The request receiving module is used to receive a test result acquisition request sent by the first control device, wherein the test result acquisition request carries at least one application test task;

[0222] The result sending module is also used to send the test results corresponding to the at least one application test task to the first control device.

[0223] On the other hand, an application testing apparatus is provided, the apparatus comprising:

[0224] The instruction receiving module is used to receive the task distribution instruction sent by the test server, wherein the task distribution instruction carries the application test task and the identifier of the first shared device;

[0225] The task sending module is used to send the application test task to the first shared device corresponding to the first shared device identifier;

[0226] The second control device establishes a communication connection with the first shared device. The test server is used to receive a test request sent by the first control device carrying the identifier of the first shared device, query the identifier of the second control device associated with the identifier of the first shared device, and send the task issuance instruction to the second control device corresponding to the identifier of the second control device.

[0227] Optionally, the device further includes:

[0228] The association module is used to establish a communication connection with the first shared device, obtain the identifier of the first shared device, and send a device association request to the test server. The device association request carries the identifier of the first shared device and the identifier of the second control device.

[0229] The test server is also used to associate the first shared device identifier and the second control device identifier.

[0230] Optionally, the task sending module is used to obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0231] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to perform the operations performed in the application testing method as described above.

[0232] On the other hand, a server is provided, the server including a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to perform the operations performed in the application testing method as described above.

[0233] On the other hand, a computer-readable storage medium is provided that stores at least one piece of program code, which is loaded and executed by a processor to perform the operations performed in the application testing method described above.

[0234] On the other hand, a computer program product or computer program is provided, the computer program product or computer program including computer program code stored in a computer-readable storage medium, wherein a processor of the computer device reads the computer program code from the computer-readable storage medium, and the processor executes the computer program code, causing the computer device to perform the operations performed in the application testing method described above.

[0235] The beneficial effects of the technical solutions provided in this application include at least the following:

[0236] The application testing system, method, apparatus, computer equipment, and medium provided in this application embodiment allow the control device to remotely invoke the corresponding shared device and send application testing tasks to the corresponding shared device simply by displaying the shared device identifier and operating on the displayed shared device identifier. Application testing can then be performed on the shared device without requiring testers to purchase or borrow the shared device, thus saving time and improving testing efficiency, while fully leveraging the role of the shared device. Attached Figure Description

[0237] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0238] Figure 1 This is a schematic diagram of an application testing system provided in an embodiment of this application;

[0239] Figure 2 This is a schematic diagram of another application testing system provided in an embodiment of this application;

[0240] Figure 3 This is a flowchart of a shared device grouping method provided in an embodiment of this application;

[0241] Figure 4 This is a schematic diagram of an application interface provided in an embodiment of this application;

[0242] Figure 5 This is a schematic diagram of a connection interface provided in an embodiment of this application;

[0243] Figure 6 This is a schematic diagram of a device connection process provided in an embodiment of this application;

[0244] Figure 7 This is a flowchart of an application testing method provided in an embodiment of this application;

[0245] Figure 8 This is a schematic diagram of an identifier query process provided in an embodiment of this application;

[0246] Figure 9 This is a schematic diagram of another connection interface provided in an embodiment of this application;

[0247] Figure 10 This is a schematic diagram of a testing process provided in an embodiment of this application;

[0248] Figure 11 This is a flowchart of another shared device grouping method provided in an embodiment of this application;

[0249] Figure 12 This is a flowchart of another application testing method provided in the embodiments of this application;

[0250] Figure 13 This is a schematic diagram of the structure of an application testing device provided in an embodiment of this application;

[0251] Figure 14 This is a schematic diagram of another application testing device provided in the embodiments of this application;

[0252] Figure 15 This is a schematic diagram of another application testing device provided in the embodiments of this application;

[0253] Figure 16 This is a schematic diagram of another application testing device provided in the embodiments of this application;

[0254] Figure 17 This is a schematic diagram of another application testing device provided in the embodiments of this application;

[0255] Figure 18 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0256] Figure 19 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Specific implementation methods

[0257] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation method of this application will be further described in detail below with reference to the accompanying drawings.

[0258] It is understood that the terms "first," "second," etc., used in this application may be used to describe various concepts herein, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of this application, the first control device may be referred to as the second control device, and the second control device may be referred to as the first control device.

[0259] As used in this application, the terms "multiple", "each", "at least", etc., mean that "multiple" includes two or more, "each" refers to each of the corresponding multiples, and "at least" refers to one, two or more of the multiples. For example, multiple shared devices include 20 shared devices, and "each shared device" refers to each of the 20 shared devices, and "at least one shared device" refers to one, two or more of the 20 shared devices.

[0260] Cloud technology refers to a hosting technology that unifies hardware, software, and network resources within a wide area network (WAN) or local area network (LAN) to achieve data computing, storage, processing, and sharing. Based on the cloud computing business model, cloud technology encompasses network technology, information technology, integration technology, management platform technology, and application technology. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will require robust system support, which can only be achieved through cloud computing.

[0261] Cloud storage is a new concept that extends and develops from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as a storage system) refers to a storage system that uses cluster applications, grid technology and distributed storage file systems to bring together a large number of storage devices of various types in the network (storage devices are also called storage nodes) to work together through application software or application interfaces to provide data storage and business access functions to the outside world.

[0262] Figure 1 This is a schematic diagram of an application testing system provided in an embodiment of this application. See also... Figure 1 The application testing system includes a test server 101 and multiple control devices 102. Figure 1 (Taking 4 as an example) and multiple shared devices 103 ( Figure 1 (Taking four as an example).

[0263] The test server 101 is used to provide test services for the control device 102 and the shared device 103. The control device 102 is used to initiate application tests, and the shared device 103 is used to perform application tests.

[0264] The test server 101 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The control device 102 and the sharing device 103 can be computers, mobile phones, tablets, or other terminals.

[0265] In one possible implementation, the control device 102 and the shared device 103 are equipped with a target application. The control device 102 is used to initiate a test of the target application, and the shared device 103 is used to test the target application.

[0266] In one possible implementation, the test server 101 can connect to multiple control devices 102 via wired or wireless networks, and can also connect to multiple shared devices 103 via wireless or wired networks. After any control device 102 initiates a test, it can forward the application test task to any shared device 103 through the test server 101 connected to that control device 102, and the shared device 103 will perform the test.

[0267] In another possible implementation, see Figure 2 The test server 101 is connected to multiple control devices 102 via wired or wireless networks, and the multiple control devices 102 are connected to the sharing device 103 via wireless or wired networks. That is, after any one of the multiple control devices 102 initiates a test, it can send application test tasks to other control devices 102 through the test server 101 connected to that control device 102. The other control devices 102 then forward the application test tasks to any connected sharing device 103, which performs the test.

[0268] The method provided in this application embodiment can be applied to application testing scenarios. When performance testing or other tests are required on a target application, the application testing method provided in this application embodiment can be used to control multiple shared devices to perform application testing through remote control.

[0269] In this embodiment of the application, application testing is performed based on shared devices in groups. Before conducting application testing, the shared devices should first be grouped, and then application testing is performed based on shared devices in any of the grouped groups. The following is based on... Figure 1 The application testing system shown illustrates the process of grouping shared devices.

[0270] Figure 3 This is a flowchart illustrating a shared device grouping method provided in an embodiment of this application. The interaction entities in this embodiment are a test server, a third control device, and a second shared device. See also... Figure 3 The method includes:

[0271] 301. The third control device displays graphic codes.

[0272] The third control device is any one of multiple control devices. The graphic code can be a QR code, barcode, or other form of graphic code.

[0273] The graphic code includes a group identifier, which represents a group of shared devices. The group identifier can be a combination of any numbers, letters, or other symbols. Optionally, the group identifier is an identifier automatically generated by the third control device, or an identifier entered by the user in the third control device.

[0274] In one possible implementation, if the group identifier is a user-input identifier, the third control device obtains the user-input group identifier and generates a graphic code based on it. Since the graphic code is generated by the third control device, it also includes the control device identifier of the third control device. This control device identifier may include identifiers such as the device name or the user's login username.

[0275] Optionally, if the shared device identifier is not included in the group corresponding to the group identifier, that is, the group identifier is an initial group identifier and the group corresponding to the group identifier has not yet been established, the third control device directly displays the graphic code based on the group identifier; or, if the shared device identifier is already included in the group corresponding to the group identifier, that is, the group corresponding to the group identifier has been established, the third control device displays the graphic code and the shared device identifier included in the group based on the group identifier.

[0276] In one possible implementation, after the third control device obtains the group identifier, it sends an identifier query request carrying the group identifier to the test server. After receiving the query request, the test server queries the group corresponding to the group identifier. If no corresponding group is found, the server returns a query failure message to the third control device, at which point the third control device only displays a graphic code. If a corresponding group is found, the server returns the found shared device identifier to the third control device, at which point the third control device displays both the graphic code and the received shared device identifier.

[0277] In one possible implementation, the third control device is equipped with a target application, which obtains the group identifier and generates a corresponding graphic code. In this case, the graphic code also includes the application identifier of the target application to indicate that the graphic code was generated by the target application.

[0278] Optionally, the third control device displays the application interface of the target application before displaying the graphic code, see [link to relevant documentation]. Figure 4 The application interface 400 includes a connection button, which currently indicates that it is not connected, meaning that the third control device has not yet obtained the shared device identifier of the shared device used for testing. When the user clicks the connection button, the third control device detects the click operation and displays the connection interface.

[0279] Optionally, see Figure 5 The connection interface 500 is used to display graphic codes and group identifiers. Figure 5 The graphic code in the image is a QR code, with the group identifier 8AC-639, and the connection interface also displays the prompt message "Please use the XX application to scan the QR code below".

[0280] Optionally, after the third control device detects a click on the connection button, it automatically generates a group identifier and generates a graphic code based on the group identifier. The group corresponding to the automatically generated group identifier does not include the shared device identifier; or, the user enters a user identifier in the connection interface, and the third control device also generates a graphic code based on the entered group identifier.

[0281] 302. The second shared device scans the graphic code to obtain the group identifier.

[0282] The second shared device is any one of the multiple shared devices.

[0283] In one possible implementation, when the third control device displays a graphic code through the target application and the second sharing device also has the target application installed, the second sharing device scans the graphic code through the target application to obtain the group identifier.

[0284] Optionally, the second sharing device directly scans the graphic code displayed by the third control device; or, the third control device sends the graphic code to other devices for display, and the second sharing device scans the graphic code displayed by the other devices; or, the third control device sends the graphic code to the second sharing device, and the second sharing device scans it; or, if there are multiple control devices, the third control device can send a group identifier to other control devices, the other control devices generate graphic codes based on the group identifiers, and the second sharing device scans the graphic codes generated by the other control devices.

[0285] If a graphic code is generated by another control device based on a group identifier, the generated graphic code includes the group identifier and the control device identifier of the control device that generated the graphic code. Optionally, if multiple control devices belong to different users, and multiple shared devices also belong to different users, the control device identifier is the username set by the user, and the control device identifier can represent the user to which the control device belongs.

[0286] For example, if control device A1 and shared device A2 belong to user A3, and control device B1 and shared device B2 belong to user B3, then if control device A1 generates graphic code A4 based on the group identifier, and control device B1 generates graphic code B4 based on the same group identifier, then both graphic code A4 and graphic code B4 include the group identifier. Graphic code A4 also includes the control device identifier A5 of control device A1, and graphic code B4 also includes the control device identifier B5 of control device B1.

[0287] 303. The second sharing device sends a sharing association request to the test server.

[0288] The shared association request carries a group identifier and a second shared device identifier. This shared association request is used to request the test server to add the carried shared device identifier to the group corresponding to the group identifier.

[0289] 304. The test server adds the second shared device identifier to the group corresponding to the group identifier and establishes a communication connection with the second shared device.

[0290] The group is used to record the shared device identifier associated with the group identifier. After receiving the sharing association request, the test server creates the group corresponding to the group identifier and adds the second sharing identifier to the created group. In addition, the test server establishes a communication connection with the second shared device, so that the test server can directly send application test tasks to the second shared device or receive test results sent by the second shared device through the established communication connection.

[0291] In one possible implementation, the sharing association request also carries the control device identifier of the control device. The test server further stores the control device identifier and the shared device identifier in correspondence to indicate that the control device identifier and the shared device identifier are associated. The shared device corresponding to the shared device identifier is a group identifier obtained by scanning the graphic code generated by the control device corresponding to the control device identifier. If the control device identifier represents the user to whom the control device belongs, then storing the control device identifier and the shared device identifier in correspondence can identify the user to whom the shared device corresponding to the shared device identifier belongs.

[0292] In one possible implementation, the third control device can also send a control association request to the test server. The control association request carries a group identifier and a third control device identifier of the third control device. After receiving the control association request, the test server associates the third control device identifier with the group identifier to indicate that the third control device controls the shared device identifier in the group corresponding to the group identifier. When the test server needs to send the shared device identifier or test results to the control device in the future, it can determine which control device to send them to based on the control device identifier associated with the shared identifier.

[0293] It should be noted that the association process is executed after step 301. The process of associating the control device with the group identifier is executed first, followed by the process of establishing a group with the second shared device; or the process of establishing a group with the second shared device is executed first, followed by the process of associating the control device with the group identifier; or the two processes are executed simultaneously. This application embodiment does not restrict the order of execution of the steps.

[0294] Another point to note is that the embodiments in this application are only used as an example to illustrate the process of grouping the second shared devices by displaying graphic codes on the third control device. In another embodiment, any control device and any shared device can be grouped using the above implementation method.

[0295] For example, see Figure 6 The diagram shows a system comprising four control devices and four shared devices, each capable of connecting to a test server. Control devices A1, B1, A2, and B2 correspond to the same group identifier A3, as do control devices C1, D1, C2, and D2. The test server associates control device identifiers A4 and B4 with group identifier A3, adds shared device identifiers A5 and B5 to the group corresponding to group identifier A3, associates control device identifiers C4 and D4 with group identifier C3, and adds shared device identifiers C5 and D5 to the group corresponding to group identifier C3.

[0296] Another point to note is that the embodiments of this application are only illustrated by adding the second shared device identifier to a group. In another embodiment, a similar implementation method to the second shared identifier can be used to add any shared device identifier to any group, and the shared devices included in different groups can be the same or different.

[0297] In the method provided in this application embodiment, the shared device can establish a communication connection with the test server by scanning a code. The test server adds the shared device identifier of the connected shared device to the corresponding group, realizing centralized management of multiple shared devices. This facilitates the control device to remotely call the shared device corresponding to the shared device identifier in the group through the test server during subsequent application testing.

[0298] Using the above Figure 3 After establishing the shared device grouping method shown, any control device can obtain the shared device identifier in any group based on the established grouping, and remotely call the shared device corresponding to the shared identifier to perform application testing. The following describes the method based on the above... Figure 3 The process of creating groups for application testing is explained.

[0299] Figure 7 This is a flowchart illustrating an application testing method provided in an embodiment of this application. The interactive entities in this embodiment are a test server, a first control device, and a first shared device. See also... Figure 7 The method includes:

[0300] 701. The first control device acquires at least one shared identifier.

[0301] Wherein, the first control device can be any control device in the system, and optionally, it is related to the above-mentioned... Figure 3 The third control device in the illustrated embodiments may be the same or different.

[0302] In one possible implementation, the first control device sends an identifier query request to the test server. The test server receives the query request, queries the shared device identifiers of shared devices already connected to the test server, and sends at least one shared device identifier to the first control device, thereby obtaining at least one shared device identifier. The identifier query request carries the first control device identifier, and the test server can send the shared device identifier to the corresponding first control device based on this first control device identifier.

[0303] Optionally, the first control device obtains the group identifier, and the identifier query request also carries the group identifier; the test server queries the group corresponding to the group identifier, obtains the shared device identifier in the group, and sends the shared device identifier in the group to the first control device.

[0304] Among them, see Figure 8 The test server stores the group identifier as a mapping to the shared device identifier, and also stores the group identifier as a mapping to the control device identifier. When the test server receives an identifier query request carrying the group identifier, it can query the shared device identifier stored corresponding to that group identifier.

[0305] In another possible implementation, the test server sends the shared device identifier from the packet to the first control device. If the packet identifier and the control device identifier have already been associated, as shown in step 304 of the above embodiment, when the test server detects that a new second shared device identifier has been added to the packet corresponding to the packet identifier, the test server obtains the first control device identifier associated with the packet identifier and sends a connection notification message to the first control device corresponding to the first control device identifier. This connection notification message includes the second shared device identifier; the first control device displays the second shared device identifier based on the connection notification message. The connection notification message indicates that the second shared device has established a communication connection with the test server.

[0306] It should be noted that the above embodiments are only illustrated using the second shared device identifier as an example. In another embodiment, the shared device identifier added to the group can also be other shared device identifiers.

[0307] 702. The first control device displays at least one shared device identifier.

[0308] The first control device displays at least one shared device identifier, and the user can select from the displayed shared device identifiers to conduct subsequent application testing.

[0309] In one possible implementation, the connection interface also includes the device status of each shared device. Specifically, the first control device displays the shared device identifier and device status of at least one shared device, which is either available or unavailable. An available status means the shared device can execute application test tasks, while an unavailable status means the shared device cannot execute application test tasks. For a shared device in an unavailable state, even if an application test task is subsequently sent to that shared device, the shared device will not be able to execute the received application test task.

[0310] In one possible implementation, each of the multiple shared devices sends a status signal to a test server. The test server, in response to not receiving a status signal from any shared device within a preset time period prior to the current moment, determines the device status of any shared device as unavailable. The test server, in response to receiving a status signal from any shared device at preset time intervals, determines the device status of any shared device as available. After determining the device status of at least one shared device, the test server sends the device status of at least one shared device to a first control device. Upon receiving the device status of at least one shared device, the first control device displays the device status of that at least one shared device. The preset time period can be any duration, such as 1 minute, 2 minutes, or other durations.

[0311] Optionally, if the shared device is powered off, is performing other application testing tasks, or the target application is being used, the shared device will not send status information to the test server.

[0312] For example, see Figure 9 The connection interface 900 shown includes four shared device identifiers and the device status corresponding to each identifier. Specifically, the device icon corresponding to shared device identifier A indicates that the shared device is currently connected; the device icon corresponding to shared device identifier C indicates that the shared device is currently unavailable; and the icons corresponding to shared device identifiers B and D indicate that these two shared devices are available.

[0313] Optionally, the first control device can send a status acquisition request to the test server every preset time interval. The status acquisition request carries a group identifier. After receiving the status acquisition request, the test server sends the device status of the shared device in the group corresponding to the group identifier to the first control device; or, the test server sends the device status of at least one shared device to the first control device every preset time interval.

[0314] In one possible implementation, the connection interface also displays a group identifier display area, where the user can input other group identifiers. The connection interface will then display the shared device identifiers in the corresponding groups based on the input other group identifiers.

[0315] 703. In response to the selection operation of the displayed first shared device identifier, the first control device sends a test request to the test server.

[0316] The user selects a first shared device identifier from at least one shared device identifier. After detecting the selection operation, the first control device sends a test request to the test server. The test request carries the first shared device identifier and the application test task.

[0317] In one possible implementation, the first control device sends a test request to the test server through the target application to be tested. The test request also carries the target application identifier of the target application, and the application test task includes the target application identifier.

[0318] Optionally, the target application's display interface shows application test tasks to be tested. The user selects an application test task and then selects a first shared device identifier. The first control device then sends a test request carrying the first shared device identifier and the application test task.

[0319] 704. The test server receives the test request and sends the application test task to the first shared device corresponding to the first shared device identifier.

[0320] After receiving a test request, the test server retrieves the application test task and the first shared device identifier carried in the test request, and sends the application test task to the first shared device corresponding to the first shared device identifier. Optionally, the test server may also store the application test task.

[0321] 705. The first shared device performs application testing tasks.

[0322] In one possible implementation, when the application test task includes a target application identifier, the first shared device determines the target application corresponding to the target application identifier and executes the application test task through the target application.

[0323] For example, if the application test task is a playback test, then the application test task will include a target video to be played. The first shared device plays the target video through the target application and obtains test results such as the resolution and playback duration.

[0324] 706. The first shared test device sends the test results corresponding to the application test task to the test server.

[0325] 707. The test server stores the test results and corresponding application test tasks.

[0326] 708. The test server sends the test results to the first control device.

[0327] In one possible implementation, the test server obtains a group identifier associated with a first shared device identifier; it then obtains at least one control device identifier associated with the group identifier and sends test results to the control devices corresponding to the at least one control device identifier. That is, the test server sends test results to the control devices. Sending test results to at least one control device enables test result sharing; that is, if any control device initiates an application test task, other control devices can also obtain the test results of that application test task.

[0328] In another possible implementation, the first control device sends a test result retrieval request to the test server, the test result retrieval request carrying at least one application test task; the test server sends the test results corresponding to at least one application test task to the first control device.

[0329] For example, see Figure 10 Control device A4 sends a test request to the test server, the test server sends an application test task to shared device B3, shared device B3 returns the test results to the test server, and the test server sends the test results back to control device A4.

[0330] It should be noted that the embodiments in this application only use the first shared device as an example for illustration. In another embodiment, multiple shared device identifiers can be selected, and application testing can be performed using the shared devices corresponding to these multiple shared device identifiers. The process of application testing for each shared device is similar to the process of application testing for the first shared device described above, and will not be repeated here.

[0331] The method provided in this application embodiment allows the control device to remotely invoke the corresponding shared device and send application test tasks to the corresponding shared device simply by displaying the shared device identifier and operating on the displayed shared device identifier. Application testing can then be performed on the shared device without requiring testers to purchase or borrow the shared device, thus saving time, improving testing efficiency, and fully leveraging the role of the shared device.

[0332] The above Figure 3 and Figure 7 The illustrated embodiment uses grouping via QR code scanning to achieve device sharing as an example to explain the grouping process and application testing process. In another embodiment, a control device is used as an intermediary device. By connecting the control device to the shared devices and the control device to the test server, the shared devices are grouped. The following is based on... Figure 2The application test system shown illustrates another type of shared device grouping process.

[0333] Figure 11 This is a flowchart of another shared device grouping method provided in an embodiment of this application. The interaction entities in this embodiment are a test server, a second control device, and a first shared device. See also... Figure 11 The method includes:

[0334] 1101. The second control device establishes a communication connection with the first shared device and obtains the identifier of the first shared device.

[0335] The second control device can be any one of a plurality of control devices. Optionally, the second control device may be the same as or different from the first and third control devices mentioned above.

[0336] The second control device can be connected to the first control device via wired or wireless methods, such as establishing a communication connection through a data cable or Bluetooth. After the second control device is connected to the first sharing device, it can directly obtain the first sharing device identifier of the first sharing device.

[0337] In one possible implementation, the second control device is equipped with a device management application. The second control device establishes a communication connection with the first shared device through the device management application. After the connection is established, the first shared device identifier of the first shared device will be displayed in the display interface of the device management application.

[0338] 1102. The second control device acquires the group identifier.

[0339] Optionally, the second control device acquires the group identifier input by the user, or the second control device automatically generates the group identifier.

[0340] In one possible implementation, the user enters the group identifier in the display interface of the device management application, or the group identifier is automatically generated by the device management application.

[0341] Among them, the group identifier is the same as the above. Figure 3 The group identifiers in the illustrated embodiments are similar.

[0342] 1103. The second control device sends a device association request to the test server.

[0343] The device association request carries a first shared device identifier and a second control device identifier. This device association request is used to request the test server to associate the first shared device identifier and the second control device identifier, indicating that the first shared device corresponding to the first shared device identifier is connected to the second control device corresponding to the second control device identifier.

[0344] In one possible implementation, the device association request also carries a group identifier to request the test server to add the first shared device identifier to the group corresponding to the group identifier.

[0345] 1104. The test server associates the first shared device identifier and the second control device identifier, and adds the first shared device identifier to the group corresponding to the group identifier.

[0346] After receiving the device association request, the test server stores the first shared device identifier and the second control device identifier accordingly, indicating that the second control device is an intermediary device between the first shared device and the test server. Subsequently, the test server needs to send application test tasks to the first shared device through the second control device, and the first shared device needs to send test results to the test server through the second control device. The test server also creates a group corresponding to the group identifier and adds the first shared device identifier to the group.

[0347] In one possible implementation, the test server sends an association success message to the second control device, notifying the second control device that the first shared device identifier and the second control device identifier have been associated.

[0348] It should be noted that the embodiments in this application are only illustrated by connecting the first shared device and the second control device. In another embodiment, the first shared device can also be connected to other control devices.

[0349] Another point to note is that any shared device can use the above... Figure 3 or Figure 11 You can use any of the grouping methods to group, or you can use the two grouping methods mentioned above to add them to different groups respectively.

[0350] Another point to note is that, optionally, all shared device identifiers within any group can be identified using [a specific identifier]. Figure 3 Add the grouping method shown to the group; or, use all of them. Figure 11 Add the grouping method shown to the group; or, partially use the grouping method shown. Figure 3 The grouping method shown is added to this group, and another part uses... Figure 11 The grouping method shown is added to this group.

[0351] In the method provided in this application embodiment, the shared device can establish a communication connection with the control device, add the shared device identifier of the shared device to the corresponding group, realize centralized management of multiple shared devices, and facilitate the remote calling of the shared device corresponding to the shared device identifier in the group through the test server and the connected control device during subsequent application testing.

[0352] Using the above Figure 11 After establishing the shared device grouping method shown, any control device can obtain the shared device identifier in any group based on the established grouping, and remotely call the shared device corresponding to the shared identifier to perform application testing. The following describes the method based on the above... Figure 11 The process of creating groups for application testing is explained.

[0353] Figure 12 This is a flowchart of another application testing method provided in an embodiment of this application. The interactive entities in this embodiment are a test server, a control device, and a sharing device. See also... Figure 12 The method includes:

[0354] 1201. The first control device acquires at least one shared identifier.

[0355] 1202. The first control device displays at least one shared device identifier.

[0356] 1203. In response to the selection operation of the displayed first shared device identifier, the first control device sends a test request to the test server.

[0357] The implementation methods of steps 1201-1203 are the same as those described above. Figure 7 The implementation methods of steps 701-703 in the illustrated embodiment are similar and will not be repeated here.

[0358] 1204. The test server queries the second control device identifier associated with the first shared device identifier.

[0359] The second control device identifier refers to the second control device that has established a communication connection with the first shared device. That is, the test server needs to find the second control device identifier in order to forward test tasks to the first shared device through the second control device.

[0360] 1205. The test server sends a task assignment instruction to the second control device.

[0361] The task issuance instruction carries the application test task and the first shared device identifier, that is, instructs the second control device to send the test task to the first shared device corresponding to the first shared device identifier.

[0362] 1206. The second control device sends an application test task to the first shared device corresponding to the first shared device identifier.

[0363] In one possible implementation, after the second control device connects to the first sharing device, the second control device can acquire and store the test interface information of the first sharing device. The second control device can then send application test tasks to the first sharing device by calling the test interface indicated by the test interface information.

[0364] 1207. The first shared device performs application testing tasks.

[0365] 1208. The first shared test device sends the test results corresponding to the application test task to the second control device.

[0366] 1209. The second control device sends the test results to the test server.

[0367] 1210. The test server stores the test results and corresponding application test tasks.

[0368] 1211. The test server sends the test results to the first control device.

[0369] The implementation methods of steps 1205-1211 are the same as those described above. Figure 7 The implementation methods of steps 704-708 in the illustrated embodiment are similar, except that the application test task needs to be forwarded to the first shared device through the second control device.

[0370] Furthermore, if the shared device corresponding to the shared device identifier is connected to the first control device, the first control device can directly send application test tasks to the shared device without needing to send a test request carrying the shared device identifier to the test server. Subsequently, after receiving the test results, the first control device will still send the test results to the test server.

[0371] It should be noted that any of the above application testing methods can be used for any application testing task. Optionally, if it is necessary to test a specific performance aspect of the target application, the above methods can be used. Figure 7 The application testing methods shown above are used for application testing; if it is necessary to test the compatibility of the target application with respect to the operating system or other operating system-related performance of the target application, the above methods can be used. Figure 12 The application testing method shown is used for application testing.

[0372] The method provided in this application embodiment allows the control device to remotely invoke the corresponding shared device and send application test tasks to the corresponding shared device simply by displaying the shared device identifier and operating on the displayed shared device identifier. Application testing can then be performed on the shared device without requiring testers to purchase or borrow the shared device, thus saving time, improving testing efficiency, and fully leveraging the role of the shared device.

[0373] Figure 13 This is a schematic diagram of the structure of an application testing device provided in an embodiment of this application. See also... Figure 13 The device includes:

[0374] Display module 1301 is used to display at least one shared device identifier;

[0375] The test request sending module 1302 is used to send a test request to the test server in response to the selection operation of the first shared device identifier displayed. The test request carries the first shared device identifier.

[0376] The test server is used to send application test tasks to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test tasks.

[0377] Optionally, see Figure 14 The device also includes:

[0378] The query request sending module 1303 is used to send an identifier query request to the test server. The identifier query request carries the identifier of the first control device. The test server is also used to send at least one shared device identifier to the first control device corresponding to the first control device identifier.

[0379] Optionally, the identifier query request also carries a group identifier, and the test server is also used to query the group corresponding to the group identifier. The group is used to record the shared device identifier associated with the group identifier and send the shared device identifier in the group to the first control device.

[0380] Optionally, the display module 1301 is also used to display a graphic code, which includes a group identifier. The second shared device is used to scan the graphic code to obtain the group identifier.

[0381] Optionally, the display module 1301 is also used for:

[0382] If the shared device identifier is not included in the group corresponding to the group identifier, display the graphic code; or...

[0383] If the shared device identifier is already included in the group corresponding to the group identifier, display the graphic code and the shared device identifier included in the group.

[0384] Optionally, see Figure 14 The device also includes:

[0385] The notification receiving module 1304 is used to receive a connection notification message sent by the test server. The connection notification message includes the identifier of the second shared device and is used to indicate that the second shared device has established a communication connection with the test server.

[0386] Display module 1301 is used to display the identifier of the second shared device according to the connection notification message;

[0387] The test server is also used to obtain the first control device identifier associated with the group identifier and send a connection notification message to the first control device corresponding to the first control device identifier.

[0388] Optionally, see Figure 14 The device also includes:

[0389] The association request sending module 1305 is used to send a control association request to the test server. The control association request carries a group identifier and a first control device identifier. The test server is also used to associate the first control device identifier with the group identifier.

[0390] Optionally, see Figure 14 The associated request sending module 1305 is used to send a test request to the test server through the target application to be tested. The test request also carries the target application identifier of the target application. The application test task includes the target application identifier. The first shared device is used to determine the target application corresponding to the target application identifier and execute the application test task through the target application.

[0391] Optionally, the display module 1301 is used to display the device identifier and device status of at least one shared device, wherein the device status is either available or unavailable.

[0392] Optionally, see Figure 14 The device also includes:

[0393] The status receiving module 1306 is used to receive the device status of at least one shared device sent by the test server; wherein, the test server is also used to determine the device status of at least one shared device and send the device status of at least one shared device to the first control device.

[0394] Optionally, see Figure 14 The device also includes:

[0395] The request sending module 1307 is used to send a test result retrieval request to the test server. The test result retrieval request carries at least one application test task. The test server is also used to send the test results corresponding to at least one application test task to the first control device.

[0396] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0397] It should be noted that the application testing device provided in the above embodiments is only used as an example to illustrate the division of the above functional modules when testing applications. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the control device can be divided into different functional modules to complete all or part of the functions described above. In addition, the application testing device and the application testing method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0398] Figure 15 This is a schematic diagram of the structure of an application testing device provided in an embodiment of this application. See also... Figure 15 The device includes:

[0399] The test request receiving module 1501 is used to receive a test request sent by the first control device. The test request carries a first shared device identifier. The first control device is any control device in the system. The first control device is used to display at least one shared device identifier. In response to the selection operation of the displayed first shared device identifier, the first control device sends a test request to the test server.

[0400] The task sending module 1502 is used to send an application test task to the first shared device corresponding to the first shared identifier, and the first shared device is used to execute the application test task.

[0401] Optionally, see Figure 16 The device also includes:

[0402] The query request receiving module 1503 is used to receive the identifier query request sent by the first control device, wherein the identifier query request carries the identifier of the first control device;

[0403] The identifier sending module 1504 is used to send at least one shared device identifier to the first control device corresponding to the first control device identifier.

[0404] Optionally, the query request also carries a group identifier, which is sent by the identifier sending module 1504 for:

[0405] Query the group corresponding to the group identifier. The group is used to record the shared device identifier associated with the group identifier.

[0406] Send the shared device identifier in the packet to the first control device; wherein, the first control device is also used to obtain the packet identifier.

[0407] Optionally, the task sending module 1502 is used for:

[0408] Once a communication connection is established between the test server and the first shared device, an application test task is sent to the first shared device; or...

[0409] The system queries the second control device identifier associated with the first shared device identifier, sends a task delivery instruction to the second control device corresponding to the second control device identifier, establishes a communication connection between the second control device and the first shared device, and carries the application test task and the first shared device identifier in the task delivery instruction. The second control device is used to send the application test task to the first shared device corresponding to the first shared device identifier.

[0410] Optionally, see Figure 16 The device also includes:

[0411] The association request receiving module 1505 is used to receive a device association request sent by the second control device. The device association request carries the identifier of the first shared device and the identifier of the second control device. The second control device is used to establish a communication connection with the first shared device and obtain the identifier of the first shared device.

[0412] The association module 1506 is used to associate the first shared device identifier and the second control device identifier.

[0413] Optionally, the second control device is also used to acquire the group identifier, see [link to relevant documentation]. Figure 16 The device also includes;

[0414] The grouping module 1507 is used to add the first shared device identifier to the group corresponding to the group identifier.

[0415] Optionally, the second control device is also used to obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0416] Optionally, the association request receiving module 1505 is further configured to receive a sharing association request sent by the second sharing device. The sharing association request carries a group identifier and a second sharing device identifier. The second sharing device can be any sharing device in the system. The second sharing device is used to obtain the group identifier and send the sharing association request to the test server.

[0417] The association module 1506 is also used to add the second shared device identifier to the group corresponding to the group identifier and establish a communication connection with the second shared device. The group is used to record the shared device identifier associated with the group identifier.

[0418] Optionally, see Figure 16 The device also includes:

[0419] The connection module 1508 is used to obtain the first control device identifier associated with the group identifier, and send a connection notification message to the first control device corresponding to the first control device identifier. The connection notification message includes a second shared device identifier and is used to indicate that the second shared device has established a communication connection with the test server. The first control device is used to display the second shared device identifier according to the connection notification message.

[0420] Optionally, the association request receiving module 1505 is further configured to receive a control association request sent by the first control device, wherein the control association request carries a group identifier and a first control device identifier;

[0421] The association module 1506 is also used to associate the first control device identifier with the group identifier.

[0422] Optionally, see Figure 16 The device also includes:

[0423] The status determination module 1509 is used to determine the device status of at least one shared device and send the device status of at least one shared device to the first control device. The first control device is used to display the device identifier and device status of at least one shared device, and the device status is either available or unavailable.

[0424] Optionally, see Figure 16 The status determination module 1509 is used for:

[0425] Receive status signals sent by each of the multiple shared devices;

[0426] If no status signal is received from any shared device within a preset time period prior to the current moment, the device status of any shared device is determined to be unavailable.

[0427] Optionally, see Figure 16 The device also includes:

[0428] The result receiving module 1510 is used to receive the test results corresponding to the application test task sent by the first shared device.

[0429] The result storage module 1511 is used to store the test results and the corresponding application test tasks.

[0430] Optionally, see Figure 16 The device also includes:

[0431] The identifier acquisition module 1512 is used to acquire the group identifier associated with the identifier of the first shared device;

[0432] The result sending module 1513 is used to obtain at least one control device identifier associated with the group identifier and send the test result to the control device corresponding to the at least one control device identifier.

[0433] Optionally, see Figure 16 The device also includes:

[0434] The request receiving module 1514 is used to receive a test result acquisition request sent by the first control device. The test result acquisition request carries at least one application test task.

[0435] The result sending module 1513 is also used to send at least one test result corresponding to an application test task to the first control device.

[0436] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0437] It should be noted that the application testing device provided in the above embodiments is only used as an example to illustrate the division of the above functional modules when testing applications. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the test server can be divided into different functional modules to complete all or part of the functions described above. In addition, the application testing device and the application testing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0438] Figure 17 This is a schematic diagram of the structure of an application testing device provided in an embodiment of this application. See also... Figure 17 The device includes:

[0439] The instruction receiving module 1701 is used to receive the task distribution instruction sent by the test server. The task distribution instruction carries the application test task and the identifier of the first shared device.

[0440] Task sending module 1702 is used to send application test tasks to the first shared device corresponding to the first shared device identifier;

[0441] The second control device establishes a communication connection with the first shared device. The test server is used to receive a test request sent by the first control device carrying the identifier of the first shared device, query the identifier of the second control device associated with the identifier of the first shared device, and send a task issuance instruction to the second control device corresponding to the identifier of the second control device.

[0442] Optionally, the device further includes:

[0443] The association module is used to establish a communication connection with the first shared device, obtain the identifier of the first shared device, and send a device association request to the test server. The device association request carries the identifier of the first shared device and the identifier of the second control device. The test server is also used to associate the identifier of the first shared device and the identifier of the second control device.

[0444] Optionally, the task sending module is used to obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

[0445] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0446] It should be noted that the application testing device provided in the above embodiments is only used as an example to illustrate the division of the above functional modules when testing applications. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the control device can be divided into different functional modules to complete all or part of the functions described above. In addition, the application testing device and the application testing method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0447] Figure 18 A structural block diagram of a terminal 1800 provided in an exemplary embodiment of this application is shown. The terminal 1800 may be a portable mobile terminal, such as a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The terminal 1800 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or other names.

[0448] Typically, terminal 1800 includes a processor 1801 and a memory 1802.

[0449] Processor 1801 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1801 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1801 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1801 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1801 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0450] The memory 1802 may include one or more computer-readable storage media, which may be non-transitory. The memory 1802 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1802 is used to store at least one instruction, which is executed by the processor 1801 to implement the application testing method provided in the method embodiments of this application.

[0451] In some embodiments, the terminal 1800 may also optionally include a peripheral device interface 1803 and at least one peripheral device. The processor 1801, memory 1802, and peripheral device interface 1803 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1803 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: radio frequency circuitry 1804, display screen 1805, camera assembly 1806, audio circuitry 1807, and power supply 1809.

[0452] Peripheral interface 1803 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1801 and memory 1802. In some embodiments, processor 1801, memory 1802 and peripheral interface 1803 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1801, memory 1802 and peripheral interface 1803 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0453] The radio frequency (RF) circuit 1804 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1804 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1804 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1804 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 1804 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1804 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0454] Display screen 1805 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 1805 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1801 for processing. In this case, display screen 1805 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 1805, disposed on the front panel of terminal 1800; in other embodiments, there may be at least two display screens, disposed on different surfaces of terminal 1800 or in a folded design; in still other embodiments, display screen 1805 may be a flexible display screen, disposed on a curved or folded surface of terminal 1800. Furthermore, display screen 1805 may also be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 1805 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0455] The camera assembly 1806 is used to acquire images or videos. Optionally, the camera assembly 1806 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1806 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0456] The audio circuit 1807 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting them into electrical signals that are input to the processor 1801 for processing, or to the radio frequency circuit 1804 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal 1800. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 1801 or the radio frequency circuit 1804 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 1807 may also include a headphone jack.

[0457] Power supply 1809 is used to power the various components in terminal 1800. Power supply 1809 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 1809 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, and a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0458] In some embodiments, the terminal 1800 further includes one or more sensors 1810. The one or more sensors 1810 include, but are not limited to: an acceleration sensor 1811, a gyroscope sensor 1812, a pressure sensor 1813, an optical sensor 1815, and a proximity sensor 1816.

[0459] Accelerometer 1811 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by terminal 1800. For example, accelerometer 1811 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 1801 can control display screen 1805 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 1811. Accelerometer 1811 can also be used for games or for acquiring user motion data.

[0460] The gyroscope sensor 1812 can detect the orientation and rotation angle of the terminal 1800. The gyroscope sensor 1812, in conjunction with the accelerometer sensor 1811, can collect 3D motion data from the user on the terminal 1800. Based on the data collected by the gyroscope sensor 1812, the processor 1801 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0461] The pressure sensor 1813 can be disposed on the side bezel of the terminal 1800 and / or on the lower layer of the display screen 1805. When the pressure sensor 1813 is disposed on the side bezel of the terminal 1800, it can detect the user's grip signal on the terminal 1800, and the processor 1801 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1813. When the pressure sensor 1813 is disposed on the lower layer of the display screen 1805, the processor 1801 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 1805. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0462] An optical sensor 1815 is used to collect ambient light intensity. In one embodiment, the processor 1801 can control the display brightness of the display screen 1805 based on the ambient light intensity collected by the optical sensor 1815. Specifically, when the ambient light intensity is high, the display brightness of the display screen 1805 is increased; when the ambient light intensity is low, the display brightness of the display screen 1805 is decreased. In another embodiment, the processor 1801 can also dynamically adjust the shooting parameters of the camera assembly 1806 based on the ambient light intensity collected by the optical sensor 1815.

[0463] The proximity sensor 1816, also known as a distance sensor, is typically located on the front panel of the terminal 1800. The proximity sensor 1816 is used to detect the distance between the user and the front of the terminal 1800. In one embodiment, when the proximity sensor 1816 detects that the distance between the user and the front of the terminal 1800 is gradually decreasing, the processor 1801 controls the display screen 1805 to switch from a screen-on state to a screen-off state; when the proximity sensor 1816 detects that the distance between the user and the front of the terminal 1800 is gradually increasing, the processor 1801 controls the display screen 1805 to switch from a screen-off state to a screen-on state.

[0464] Those skilled in the art will understand that Figure 18 The structure shown does not constitute a limitation on terminal 1800 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0465] Figure 19This is a schematic diagram of a server structure provided in an embodiment of this application. The server 1900 can vary significantly due to different configurations or performance. It may include one or more Central Processing Units (CPUs) 1901 and one or more memories 1902. The memory 1902 stores at least one line of program code, which is loaded and executed by the processor 1901 to implement the methods provided in the various method embodiments described above. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated upon here.

[0466] Server 1900 can be used to execute the steps performed by the test server in the above application testing methods.

[0467] This application also provides a computer device, which includes a processor and a memory. The memory stores at least one piece of program code, which is loaded and executed by the processor to implement the operations performed in the application testing method of the above embodiments.

[0468] This application also provides a computer-readable storage medium storing at least one piece of program code, which is loaded and executed by a processor to implement the operations performed in the application testing method of the above embodiments.

[0469] This application also provides a computer program product or computer program, which includes computer program code stored in a computer-readable storage medium. A processor of a computer device reads the computer program code from the computer-readable storage medium and executes the computer program code, causing the computer device to perform the operations executed in the application testing method of the above embodiments.

[0470] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0471] The above are merely optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present application should be included within the protection scope of the present application.

Claims

1. An application testing system, characterized in that, The system includes a test server, multiple control devices, and multiple shared devices; The third control device is used to obtain the group identifier, query the group corresponding to the group identifier through the test server, and display a graphic code including the group identifier, wherein the group identifier represents a group of the shared device; the third control device can be any control device in the system; The second sharing device is used to scan the graphic code to obtain the group identifier and send a sharing association request to the test server. The test server is configured to, upon receiving the sharing association request, create a group corresponding to the group identifier, and add the second sharing device identifier of the second sharing device to the created group; A first control device is configured to acquire the group identifier, query the group corresponding to the group identifier through the test server, and display at least one shared device identifier in the group. The first control device can be any control device in the system. The first control device is further configured to send a test request to the test server in response to a selection operation on a displayed first shared device identifier, the test request carrying the first shared device identifier; The test server is used to send application test tasks to the first shared device corresponding to the first shared device identifier; The first shared device is used to perform the application testing task.

2. The application testing system according to claim 1, characterized in that, The first control device is further configured to send an identifier query request to the test server, the identifier query request carrying the identifier of the first control device; The test server is also configured to send the at least one shared device identifier to the first control device corresponding to the first control device identifier.

3. The application testing system according to claim 2, characterized in that, The identifier query request also carries the group identifier; The test server is also used to query the group corresponding to the group identifier, the group being used to record the shared device identifier associated with the group identifier, and to send the shared device identifier in the group to the first control device.

4. The application testing system according to claim 1, characterized in that, The test server is used for: If a communication connection is established between the test server and the first shared device, the application test task is sent to the first shared device; or... Query the second control device identifier associated with the first shared device identifier, where the second control device identifier refers to the second control device that has established a communication connection with the first shared device; A task distribution instruction is sent to the second control device. The task distribution instruction carries the application test task and the identifier of the first shared device, so that the second control device sends the application test task to the first shared device corresponding to the first shared device identifier.

5. The application testing system according to claim 4, characterized in that, The second control device is used to establish a communication connection with the first shared device, obtain the identifier of the first shared device, and send a device association request to the test server. The device association request carries the identifier of the first shared device and the identifier of the second control device. The test server is also used to associate the first shared device identifier and the second control device identifier.

6. The application testing system according to claim 5, characterized in that, The second control device is further configured to obtain a group identifier, and the device association request also carries the group identifier; The test server is also used to add the first shared device identifier to the group corresponding to the group identifier.

7. The application testing system according to claim 1, characterized in that, The second sharing device is used to obtain the group identifier and send a sharing association request to the test server. The sharing association request carries the group identifier and the second sharing device identifier. The second sharing device is any sharing device in the system. The test server is further configured to add the second shared device identifier to the group corresponding to the group identifier and establish a communication connection with the second shared device. The group is used to record the shared device identifier associated with the group identifier.

8. The application testing system according to claim 1, characterized in that, The first control device is configured to send a test request to the test server through the target application to be tested, the test request also carrying the target application identifier of the target application, and the application test task includes the target application identifier; The first shared device is used to determine the target application corresponding to the target application identifier, and to execute the application testing task through the target application.

9. The application testing system according to claim 1, characterized in that, The first shared device is also used to send the test results corresponding to the application test task to the test server; The test server is also used to store the test results in correspondence with the application test tasks.

10. The application testing system according to claim 4, characterized in that, The second control device is further configured to acquire the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

11. The application testing system according to claim 1, characterized in that, The test server is further configured to obtain the first control device identifier associated with the group identifier, and send a connection notification message to the first control device corresponding to the first control device identifier. The connection notification message includes the second shared device identifier and is used to indicate that the second shared device has established a communication connection with the test server.

12. The application testing system according to claim 11, characterized in that, The first control device is configured to display the identifier of the second shared device according to the connection notification message.

13. The application testing system according to claim 1, characterized in that, The third control device is used to display the graphic code when the shared device identifier is not included in the group corresponding to the group identifier; or, If the shared device identifier is already included in the group corresponding to the group identifier, the graphic code and the shared device identifier included in the group are displayed.

14. The application testing system according to claim 11, characterized in that, The first control device is further configured to send a control association request to the test server, the control association request carrying the group identifier and the first control device identifier; The test server is also used to associate the first control device identifier with the group identifier.

15. The application testing system according to claim 1, characterized in that, The first control device is used to display the device identifier and device status of the at least one shared device, wherein the device status is either available or unavailable.

16. The application testing system according to claim 15, characterized in that, The test server is also used to determine the device status of the at least one shared device and send the device status of the at least one shared device to the first control device.

17. The application testing system according to claim 16, characterized in that, Each of the plurality of shared devices is used to send a status signal to the test server; The test server is also configured to determine the device status of any shared device as unavailable if it has not received a status signal from any shared device within a preset time period prior to the current moment.

18. The application testing system according to claim 9, characterized in that, The test server is also used to obtain the group identifier associated with the first shared device identifier; The test server is also used to obtain at least one control device identifier associated with the group identifier and send the test result to the control device corresponding to the at least one control device identifier.

19. The application testing system according to claim 9, characterized in that, The first control device is used to send a test result acquisition request to the test server, the test result acquisition request carrying at least one application test task; The test server is also used to send the test results corresponding to the at least one application test task to the first control device.

20. An application testing method, characterized in that, A first control device is applied in an application testing system, the system including a test server, multiple control devices, and multiple shared devices, wherein the first control device is any control device in the system, and the method includes: After obtaining the group identifier, the test server is used to query the group corresponding to the group identifier; a graphic code including the group identifier is displayed, whereby the group identifier represents a group of shared devices; The second sharing device is used to scan the graphic code to obtain the group identifier and send a sharing association request to the test server; after receiving the sharing association request, the test server is used to create a group corresponding to the group identifier and add the second sharing device identifier of the second sharing device to the created group; Obtain the group identifier, query the group corresponding to the group identifier through the test server, and display at least one shared device identifier in the group; In response to the selection operation of the first shared device identifier displayed, a test request is sent to the test server, the test request carrying the first shared device identifier; The test server is used to send application test tasks to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test tasks.

21. The application testing method according to claim 20, characterized in that, Before displaying at least one shared device identifier in the group, the method further includes: The test server sends an identifier query request to the test server, the identifier query request carrying a first control device identifier, and the test server is also used to send the at least one shared device identifier to the first control device corresponding to the first control device identifier.

22. The application testing method according to claim 21, characterized in that, The identifier query request also carries the group identifier, which is used to record the shared device identifier associated with the group identifier.

23. The application testing method according to claim 20, characterized in that, The display includes graphic codes for group identification, including: If the shared device identifier is not included in the group corresponding to the group identifier, the graphic code is displayed; or, If the shared device identifier is already included in the group corresponding to the group identifier, the graphic code and the shared device identifier included in the group are displayed.

24. The application testing method according to claim 20, characterized in that, Before displaying at least one shared device identifier in the group, the method further includes: The system receives a connection notification message sent by the test server. The connection notification message includes the identifier of the second shared device and is used to indicate that the second shared device has established a communication connection with the test server. The second shared device identifier is displayed according to the connection notification message; The test server is further configured to obtain the first control device identifier associated with the group identifier and send the connection notification message to the first control device corresponding to the first control device identifier.

25. The application testing method according to claim 24, characterized in that, Before receiving the connection notification message sent by the test server, the method further includes: A control association request is sent to the test server. The control association request carries the group identifier and the first control device identifier. The test server is also used to associate the first control device identifier with the group identifier.

26. The application testing method according to claim 20, characterized in that, Sending a test request to the test server includes: The first shared device sends a test request to the test server through the target application to be tested. The test request also carries the target application identifier of the target application. The application test task includes the target application identifier. The first shared device is used to determine the target application corresponding to the target application identifier and execute the application test task through the target application.

27. The application testing method according to claim 20, characterized in that, The step of displaying at least one shared device identifier in the group includes: Display the device identifier and device status of the at least one shared device, wherein the device status is either available or unavailable.

28. The application testing method according to claim 27, characterized in that, Before displaying the device identifier and device status of the at least one shared device, the method further includes: Receive the device status of at least one shared device sent by the test server; The test server is also used to determine the device status of the at least one shared device and send the device status of the at least one shared device to the first control device.

29. The application testing method according to claim 20, characterized in that, After sending the test request to the test server, the method further includes: A test result retrieval request is sent to the test server, the test result retrieval request carrying at least one application test task, and the test server is also used to send the test results corresponding to the at least one application test task to the first control device.

30. An application testing method, characterized in that, A test server is used in an application testing system, the system including the test server, multiple control devices, and multiple shared devices, the method including: The third control device queries the group corresponding to the group identifier obtained by the third control device; the third control device is used to display a graphic code including the group identifier according to the query result of the test server, the group identifier representing a group of the shared device; the third control device can be any control device in the system; Receive a sharing association request sent by the second sharing device; the sharing association request is sent by the second sharing device after obtaining the group identifier by scanning the graphic code; Create a group corresponding to the group identifier, and add the second shared device identifier of the second shared device to the created group; The first control device queries the group corresponding to the group identifier obtained from the first control device; the first control device is used to display at least one shared device identifier in the group; The system receives a test request sent by the first control device, the test request carrying a first shared device identifier, the first control device being any control device in the system, and the first control device sending the test request to the test server in response to a selection operation of the displayed first shared device identifier. An application test task is sent to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test task.

31. The application testing method according to claim 30, characterized in that, Before receiving the test request sent by the first control device, the method further includes: Receive an identifier query request sent by the first control device, wherein the identifier query request carries the identifier of the first control device; Send the at least one shared device identifier to the first control device corresponding to the first control device identifier.

32. The application testing method according to claim 31, characterized in that, The identifier query request also carries the group identifier, and sending the at least one shared device identifier to the first control device corresponding to the first control device identifier includes: Query the group corresponding to the group identifier, whereby the group is used to record the shared device identifier associated with the group identifier; Send the shared device identifier in the packet to the first control device.

33. The application testing method according to claim 30, characterized in that, Sending the application test task to the first shared device corresponding to the first shared device identifier includes: If a communication connection is established between the test server and the first shared device, the application test task is sent to the first shared device; or... The system queries the second control device identifier associated with the first shared device identifier, sends a task delivery instruction to the second control device corresponding to the second control device identifier, establishes a communication connection between the second control device and the first shared device, and the task delivery instruction carries the application test task and the first shared device identifier. The second control device is used to send the application test task to the first shared device corresponding to the first shared device identifier.

34. The application testing method according to claim 33, characterized in that, Before querying the second control device identifier associated with the first shared device identifier, the method further includes: The second control device receives a device association request sent by the second control device. The device association request carries the first shared device identifier and the second control device identifier. The second control device is used to establish a communication connection with the first shared device and obtain the first shared device identifier. Associate the first shared device identifier with the second control device identifier.

35. The application testing method according to claim 34, characterized in that, The second control device is further configured to obtain a group identifier, and the device association request further carries the group identifier. After receiving the device association request sent by the second control device, the method further includes: Add the first shared device identifier to the group corresponding to the group identifier.

36. The application testing method according to claim 33, characterized in that, The second control device is also used to obtain the test interface information of the first shared device, and send the application test task to the first shared device by calling the test interface indicated by the test interface information.

37. The application testing method according to claim 30, characterized in that, Before receiving the test request sent by the first control device, the method further includes: The sharing association request carries a group identifier and a second sharing device identifier. The second sharing device is any sharing device in the system. The second sharing device is used to obtain the group identifier and send the sharing association request to the test server. The second shared device identifier is added to the group corresponding to the group identifier, and a communication connection is established with the second shared device. The group is used to record the shared device identifier associated with the group identifier.

38. The application testing method according to claim 37, characterized in that, After establishing a communication connection with the second shared device, the method further includes: Obtain the first control device identifier associated with the group identifier, and send a connection notification message to the first control device corresponding to the first control device identifier. The connection notification message includes the second shared device identifier and is used to indicate that the second shared device has established a communication connection with the test server. The first control device is used to display the second shared device identifier according to the connection notification message.

39. The application testing method according to claim 38, characterized in that, Before obtaining the first control device identifier associated with the group identifier, the method further includes: Receive a control association request sent by the first control device, wherein the control association request carries the group identifier and the identifier of the first control device; Associate the first control device identifier with the group identifier.

40. The application testing method according to claim 30, characterized in that, Before receiving the test request sent by the first control device, the method further includes: The device status of the at least one shared device is determined, and the device status of the at least one shared device is sent to the first control device. The first control device is used to display the device identifier and device status of the at least one shared device, wherein the device status is an available status or an unavailable status.

41. The application testing method according to claim 40, characterized in that, Determining the device status of the at least one shared device includes: Receive the status signal sent by each of the plurality of shared devices; If no status signal is received from any shared device within a preset time period prior to the current moment, the device status of any shared device is determined to be unavailable.

42. The application testing method according to claim 30, characterized in that, After sending the application test task to the first shared device corresponding to the first shared device identifier, the method further includes: Receive the test results corresponding to the application test task sent by the first shared device; The test results are stored in correspondence with the application test tasks.

43. The application testing method according to claim 42, characterized in that, After storing the test results in correspondence with the application test task, the method further includes: Obtain the group identifier associated with the first shared device identifier; Obtain at least one control device identifier associated with the group identifier, and send the test result to the control device corresponding to the at least one control device identifier.

44. The application testing method according to claim 42, characterized in that, After storing the test results in correspondence with the application test task, the method further includes: Receive a test result acquisition request sent by the first control device, wherein the test result acquisition request carries at least one application test task; Send the test results corresponding to the at least one application test task to the first control device.

45. An application testing device, characterized in that, A first control device is used in an application testing system, the system including a test server, multiple control devices, and multiple shared devices, wherein the first control device is any one of the control devices in the system, and the device includes: The query request sending module is used to obtain the group identifier and then query the group corresponding to the group identifier through the test server. The display module is used to display a graphic code including a group identifier, wherein the group identifier represents a group of shared devices; the second shared device is used to scan the graphic code to obtain the group identifier and send a sharing association request to the test server; the test server is used to, after receiving the sharing association request, create a group corresponding to the group identifier and add the second shared device identifier of the second shared device to the created group; Modules used to perform the following steps: obtain the group identifier, and query the group corresponding to the group identifier through the test server; A display module is used to display the identifier of at least one shared device in the group; A test request sending module is configured to send a test request to the test server in response to a selection operation on the first shared device identifier displayed, the test request carrying the first shared device identifier; The test server is used to send application test tasks to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test tasks.

46. ​​An application testing device, characterized in that, A test server used in an application testing system, the system including the test server, multiple control devices, and multiple shared devices, the device comprising: The identifier sending module is used to query the group corresponding to the group identifier obtained by the third control device; the third control device is used to display a graphic code including the group identifier according to the query result of the test server, wherein the group identifier represents a group of the shared device; the third control device can be any control device in the system; The association request receiving module is used to receive a sharing association request sent by the second sharing device; the sharing association request is sent by the second sharing device after obtaining the group identifier by scanning the graphic code; The grouping module is used to create a group corresponding to the group identifier and add the second shared device identifier of the second shared device to the created group; The identifier sending module is further configured to query the group corresponding to the group identifier based on the group identifier obtained by the first control device; the first control device is configured to display at least one shared device identifier in the group; A test request receiving module is used to receive a test request sent by the first control device. The test request carries a first shared device identifier. The first control device is any control device in the system. In response to the selection operation of the displayed first shared device identifier, the first control device sends the test request to the test server. The task sending module is used to send an application test task to the first shared device corresponding to the first shared device identifier, and the first shared device is used to execute the application test task.

47. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to perform the operations performed in the application testing method as described in any one of claims 20 to 29, or to perform the operations performed in the application testing method as described in any one of claims 30 to 44.

48. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the operations performed in the application testing method as described in any one of claims 20 to 29, or to implement the operations performed in the application testing method as described in any one of claims 30 to 44.

49. A computer program product comprising computer program code stored in a computer-readable storage medium, wherein a processor of a computer device reads the computer program code from the computer-readable storage medium, and executes the computer program code such that the computer device performs an operation performed in the application testing method as described in any one of claims 20 to 29, or performs an operation performed in the application testing method as described in any one of claims 30 to 44.

Images