Terminal performance test method, device, equipment, storage medium and program product

Abstract

This disclosure provides a terminal performance testing method, apparatus, device, storage medium, and program product, relating to the field of computer technology. The method includes: receiving a test task for a terminal, the test task including test case identifiers for multiple test cases; determining the target physical environment and target test equipment required to execute the test task based on the multiple test case identifiers and a pre-defined mapping relationship; and controlling the target test equipment to execute the multiple test cases within the target physical environment to obtain terminal performance test results. This method can quickly determine the corresponding test cases based on the test task, automatically determine the physical environment and test equipment required for different test cases based on the mapping relationship, and then control the test equipment to automatically execute the test cases without manual intervention. This achieves automatic execution of test cases across multiple testing dimensions, greatly improving the efficiency and accuracy of terminal performance testing.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a terminal performance testing method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the development of computer and terminal technologies, users are increasingly reliant on terminal devices, and the performance of these devices is constantly improving to meet user needs. To ensure that terminal devices can meet user requirements, performance testing can be conducted to evaluate their performance. This can be achieved by simulating real-world usage scenarios.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The purpose of this disclosure is to provide a terminal performance testing method, apparatus, device, storage medium, and program product.

[0005] According to a first aspect of the present disclosure, a terminal performance testing method is provided, comprising: receiving a test task for a terminal, the test task including test case identifiers of multiple test cases; determining a target physical environment and a target test device required to execute the test task based on the multiple test case identifiers and a pre-set mapping relationship; and controlling the target test device to execute the multiple test cases in the target physical environment to obtain terminal performance test results.

[0006] In some implementations, the mapping relationship includes: a first mapping relationship consisting of a use case identifier and its corresponding test scenario, and a second mapping relationship consisting of a test scenario and its required test equipment type; wherein, determining the target physical environment and target test equipment required to execute the test task based on multiple use case identifiers and a preset mapping relationship includes: determining the target test scenario corresponding to each use case identifier in the first mapping relationship; determining the target test equipment type corresponding to each target test scenario in the second mapping relationship; and determining the target physical environment and target test equipment required to execute the test task based on each target test equipment type.

[0007] In some implementations, determining the target physical environment and target test equipment required to execute the test task based on each target test equipment type includes: determining idle test equipment contained in an idle physical environment based on the operating status of test equipment in each physical environment; matching each target test equipment type with the idle test equipment contained in the idle physical environment to determine candidate test equipment contained in a candidate physical environment corresponding to each test case; and determining the target physical environment and target test equipment required to execute the test task based on the candidate test equipment contained in the candidate physical environment corresponding to each test case.

[0008] In some implementations, determining the target physical environment and target test equipment required to execute the test task based on the candidate test equipment contained in the candidate physical environment corresponding to each test case includes: forming at least one device allocation strategy based on the candidate test equipment contained in the candidate physical environment corresponding to all test cases; wherein the device allocation strategy includes: the candidate test equipment contained in the candidate physical environment allocated to each test case, and the execution order of the plurality of test cases, the execution order including at least one of parallel execution and serial execution; determining the execution time of the test task under each device allocation strategy; and determining the target physical environment and target test equipment required to execute the test task based on the device allocation strategy with the shortest execution time.

[0009] In some implementations, the physical environment includes at least one shielded space, and the test equipment includes at least the terminal, test server, switch, router, attenuator, and power distribution unit.

[0010] In some implementations, controlling the target testing device to execute the multiple test cases within the target physical environment to obtain terminal performance test results includes: retrieving the test case scripts for each test case; controlling the relevant target testing device to execute the test cases within the relevant target physical environment based on each test case script to obtain test data for each test case; quantifying the test data for each test case to obtain quantization results for each test case; and weighting and summing the quantization results for each test case based on preset weights to obtain terminal performance test results.

[0011] In some implementations, the plurality of test cases includes a first test case, which is used to perform performance testing under a first target test scenario through a first target test device within a first target physical environment; wherein the first target test device includes the terminal and other test devices, and the first target test scenario indicates the test dimension and the network topology for device connection; wherein, based on the test case script, the relevant target test devices are controlled to execute test cases within the relevant target physical environment to obtain test data for each test case, including: controlling the power-on of the first target test device to form the network topology based on the test case script of the first test case, and controlling the terminal to complete initialization; controlling the other test devices to perform data stream transmission with the terminal based on the test case script of the first test case; and determining the test data of the first test case based on the data corresponding to the test dimension recorded during the data stream transmission.

[0012] In some implementations, the test dimensions include one of the following: throughput test, latency test, attenuation signal test, weak signal test, orthogonal frequency division multiple access performance test, multi-terminal coexistence test, and multi-terminal racing test.

[0013] In some implementations, the plurality of test cases includes a second test case; the terminal performance testing method further includes: in response to the invalid execution of the second test case, determining the invalidity type of the invalid execution, and re-executing the second test case using a processing method corresponding to the invalidity type; in response to the number of re-executions reaching a threshold, capturing the corresponding running logs, and reporting an anomaly based on the invalidity type and the running logs.

[0014] According to a second aspect of the present disclosure, a terminal performance testing apparatus is provided, comprising: a task receiving unit for receiving a test task for a terminal, the test task including test case identifiers of multiple test cases; a determining unit for determining a target physical environment and a target testing device required to execute the test task based on the multiple test case identifiers and a pre-set mapping relationship; and an execution unit for controlling the target testing device to execute the multiple test cases within the target physical environment to obtain terminal performance test results.

[0015] In some implementations, the mapping relationship includes: a first mapping relationship consisting of a use case identifier and its corresponding test scenario, and a second mapping relationship consisting of a test scenario and its required test equipment type; wherein, the determining unit determines the target physical environment and target test equipment required to execute the test task based on multiple use case identifiers and a preset mapping relationship, including: determining the target test scenario corresponding to each use case identifier in the first mapping relationship; determining the target test equipment type corresponding to each target test scenario in the second mapping relationship; and determining the target physical environment and target test equipment required to execute the test task based on each target test equipment type.

[0016] In some implementations, the determining unit determines the target physical environment and target test equipment required to execute the test task based on each target test equipment type, including: determining idle test equipment contained in the idle physical environment based on the operating status of test equipment in each physical environment; matching each target test equipment type with the idle test equipment contained in the idle physical environment to determine the candidate test equipment contained in the candidate physical environment corresponding to each test case; and determining the target physical environment and target test equipment required to execute the test task based on the candidate test equipment contained in the candidate physical environment corresponding to each test case.

[0017] In some implementations, the determining unit determines the target physical environment and target test equipment required to execute the test task based on the candidate test equipment contained in the candidate physical environment corresponding to each test case. This includes: forming at least one device allocation strategy based on the candidate test equipment contained in the candidate physical environment corresponding to all test cases; wherein the device allocation strategy includes: the candidate test equipment contained in the candidate physical environment allocated to each test case, and the execution order of the plurality of test cases, the execution order including at least one of parallel execution and serial execution; determining the execution time of the test task under each device allocation strategy; and determining the target physical environment and target test equipment required to execute the test task based on the device allocation strategy with the shortest execution time.

[0018] In some implementations, the physical environment includes at least one shielded space, and the test equipment includes at least the terminal, test server, switch, router, attenuator, and power distribution unit.

[0019] In some implementations, the execution unit controls the target testing device to execute the plurality of test cases within the target physical environment to obtain terminal performance test results, including: retrieving the test case scripts for each test case; controlling the relevant target testing device to execute the test cases within the relevant target physical environment based on each test case script to obtain test data for each test case; quantifying the test data for each test case to obtain quantization results for each test case; and weighting and summing the quantization results for each test case based on preset weights to obtain terminal performance test results.

[0020] In some implementations, the plurality of test cases includes a first test case, which is used to perform performance testing under a first target test scenario through a first target test device within a first target physical environment; wherein the first target test device includes the terminal and other test devices, and the first target test scenario indicates the test dimension and the network topology for device connection; wherein the execution unit controls the relevant target test devices to execute test cases within the relevant target physical environment based on each test case script to obtain test data for each test case, including: controlling the power-on of the first target test device to form the network topology based on the test case script of the first test case, and controlling the terminal to complete initialization; controlling the other test devices to perform data stream transmission with the terminal based on the test case script of the first test case; and determining the test data of the first test case based on the data corresponding to the test dimension recorded during the data stream transmission.

[0021] In some implementations, the test dimensions include one of the following: throughput test, latency test, attenuation signal test, weak signal test, orthogonal frequency division multiple access performance test, multi-terminal coexistence test, and multi-terminal racing test.

[0022] In some implementations, the plurality of test cases includes a second test case; the execution unit is further configured to: in response to the invalidation of the second test case, determine the invalidation type of the invalidation, and re-execute the second test case using a processing method corresponding to the invalidation type; in response to the number of re-executions reaching a threshold, capture the corresponding running log, and report an exception based on the invalidation type and the running log.

[0023] According to a third aspect of the present disclosure, an electronic device is provided, characterized in that it includes: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to implement the terminal performance testing method described above.

[0024] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is enabled to execute a terminal performance testing method. The method includes: receiving a test task for the terminal, the test task including test case identifiers of multiple test cases; determining a target physical environment and a target test device required to execute the test task based on the multiple test case identifiers and a pre-defined mapping relationship; and controlling the target test device to execute the multiple test cases within the target physical environment to obtain terminal performance test results.

[0025] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the terminal performance testing method described above.

[0026] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0027] This disclosure can quickly identify the corresponding test cases based on the test case identifiers in the test task, ensuring the accurate execution of the test task; it can also automatically determine the physical environment and test equipment required for different test cases based on the mapping relationship, providing specific test environment conditions and necessary hardware equipment support that meet the requirements for the execution of different test cases; and after the physical environment and test equipment are determined, the test equipment can be controlled to automatically execute test cases without manual intervention, thereby realizing the automatic execution of test cases in multiple test dimensions, which greatly improves the efficiency and accuracy of terminal performance testing.

[0028] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0029] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0030] Figure 1 This is a flowchart illustrating a terminal performance testing method according to some embodiments of the present disclosure.

[0031] Figure 2 This is a schematic diagram illustrating a second mapping relationship in a terminal performance testing method according to some embodiments of the present disclosure.

[0032] Figure 3 This is a flowchart illustrating a terminal performance testing method according to some embodiments of the present disclosure.

[0033] Figure 4This is a flowchart illustrating the determination of the target physical environment and target test equipment in a terminal performance testing method according to some embodiments of the present disclosure.

[0034] Figure 5 This is a flowchart illustrating the determination of the target physical environment and target test equipment in another terminal performance testing method according to some embodiments of the present disclosure.

[0035] Figure 6 This is a schematic diagram of the physical environment of a terminal performance testing method including a test device, according to some embodiments of the present disclosure.

[0036] Figure 7 This is a flowchart illustrating the execution of test cases based on test case scripts in a terminal performance testing method according to some embodiments of this disclosure.

[0037] Figure 8 This is a block diagram illustrating a terminal performance testing apparatus according to some embodiments of the present disclosure.

[0038] Figure 9 This is a block diagram illustrating an apparatus for terminal performance testing according to some embodiments of the present disclosure. Detailed Implementation

[0039] Exemplary embodiments of this disclosure will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings denote the same or similar elements unless otherwise indicated. Various changes, modifications, and equivalents of the methods, apparatus, and / or systems described herein will become apparent upon understanding this disclosure. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but can be changed as will become apparent upon understanding this disclosure, except for operations that must be performed in a particular order. Furthermore, for clarity and brevity, descriptions of features known in the art may be omitted.

[0040] The embodiments described below, which are examples of some of the embodiments of this disclosure, do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0041] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0042] Figure 1 This is a flowchart illustrating a terminal performance testing method according to some embodiments of this disclosure, such as... Figure 1As shown, the terminal performance testing method can be applied to electronic devices, including but not limited to desktop computers, laptops and other terminal devices, and may also include local servers.

[0043] Terminal performance testing methods may include the following steps.

[0044] In step S110, a test task for the terminal is received, the test task including test case identifiers for multiple test cases.

[0045] In this embodiment, the terminal can be a mobile phone or tablet configured with an Android system, and the test task can be a task to test the WiFi (Wireless Fidelity) performance of the terminal. Correspondingly, test cases can be used to evaluate specific performance indicators of the terminal under different WiFi network environments. Different network environments can include, for example, different signal strengths, different connection states, and different network configurations. Specific performance indicators can include, for example, response time, throughput, and resource utilization. The test task can be a performance test task for a specific terminal, and the test task can instruct the execution of multiple test cases, each of which can be distinguished by a unique case ID.

[0046] Each test case in the multiple test cases can be included in a separate test task, and these test tasks will be issued simultaneously. Alternatively, multiple test cases can be included in a single overall test task, which may include subtasks corresponding to each test case. The form of the test tasks is not limited in this embodiment.

[0047] In an exemplary embodiment, test tasks can be generated and issued by various upstream systems. For example, test tasks can be issued through a test case library platform, which can maintain multiple test cases, each with a unique test case script and test case identifier. A tag indicating whether a test case is used for automated testing can be configured for each test case in the test case library platform; that is, the tag can indicate whether the corresponding test case is used for automated testing through different tag values. Based on this, the "one-click select all" function in the test case library platform can be used to determine all test cases whose tag values ​​indicate they are suitable for automated testing as test cases to be executed. Then, test tasks are generated for all these test cases to be executed and issued.

[0048] For example, test tasks can be issued through an automated testing platform. This platform can maintain multiple test cases, each with a unique test case script and identifier. The automated testing platform can provide a function to actively select test cases. On the corresponding page, users can manually select the required test cases or select test cases in batches by test dimension to determine the test cases to be executed. Then, test tasks are generated for all these test cases and issued.

[0049] In this system, the test case identifiers maintained by different upstream systems for the same test case are the same. In this way, when a test task is received from different upstream systems, the corresponding test case script can be quickly located and executed based on the unified test case identifier, avoiding problems such as test confusion, duplicate execution or omission due to inconsistent test case identifiers.

[0050] In an exemplary embodiment, the test task can be issued via a test link. After receiving the test link, the electronic device executing this terminal performance testing method can obtain information containing test case identifiers of multiple test cases based on the test link, and then execute the terminal performance testing method provided in this disclosure. Furthermore, the test link can redirect to a related visualization page, which can display execution information of the multiple test cases included in the test task, such as a list of multiple test cases, the execution order of the multiple test cases, how they will be executed, and the execution progress.

[0051] In step S120, the target physical environment and target test equipment required to perform the test task are determined based on multiple use case identifiers and pre-defined mapping relationships.

[0052] In this embodiment of the disclosure, the specific conditions required to execute a specific test case can be quickly located based on a pre-established mapping relationship, namely the required target physical environment and target test equipment. Both the target physical environment and the target test equipment can be pre-arranged. The target physical environment refers to a pre-built physical space, such as a shielded box or shielded room, used to provide specific test environment conditions; the target test equipment refers to the necessary hardware equipment required for testing, such as the terminal under test, test server, router, and switch.

[0053] Different test cases can correspond to different test dimensions, such as whether the WiFi function works properly, the WiFi connection response time, and the data throughput under the WiFi service. The physical environment and test equipment required for different test dimensions may differ.

[0054] By maintaining the mapping relationship, we can flexibly respond to changes in testing requirements. We can configure different physical environments and testing equipment according to different testing requirements to serve as supporting conditions for performance testing, and match the supporting conditions with the applicable test cases to establish a good mapping relationship.

[0055] With pre-defined mapping relationships and flexible test case management, it is easy to respond to changes in testing requirements, quickly adjust the testing environment and equipment, and meet the needs of different testing scenarios.

[0056] In step S130, the target test device is controlled to execute the multiple test cases within the target physical environment to obtain terminal performance test results.

[0057] In this embodiment of the disclosure, automated testing tools or scripts can be used to directly control the target test equipment in the target physical environment to automatically execute test cases. For example, the power supply of the target test equipment, the connection method between target test equipment, and the execution of preset initialization instructions can be controlled. This eliminates the need for real-time deployment of the test environment, and instead enables fully automated execution of test cases based on the selected pre-deployed physical environment and test equipment, reducing human intervention and improving testing efficiency and accuracy.

[0058] In this embodiment of the disclosure, after all test cases have been executed, the terminal performance test results can be collected and organized. These results may include performance metrics (such as response time, throughput, etc.), error logs, crash information, etc.

[0059] As can be seen from the above steps, the terminal performance testing method provided in this disclosure can accurately locate the physical environment and testing equipment required for the testing task based on the test case identifier indicated in the test task and in combination with the preset mapping relationship, and effectively control the testing equipment to automatically execute test cases in the specified physical environment. It is evident that this solution can quickly determine the corresponding test cases based on the test case identifier in the test task, ensuring the accurate execution of the test task; it can also automatically determine the physical environment and testing equipment required for different test cases based on the mapping relationship, providing specific test environment conditions and necessary hardware support that meet the requirements for the execution of different test cases; and, after determining the physical environment and testing equipment, it can control the testing equipment to automatically execute test cases without manual intervention, thereby realizing the automatic execution of test cases across multiple testing dimensions, greatly improving the efficiency and accuracy of terminal performance testing.

[0060] In some embodiments of this disclosure, the target physical environment and the target test equipment may be selected from an existing physical environment that includes test equipment. The physical environment includes at least one shielded space, and the test equipment includes at least the terminal, other test equipment, a test server, a switch, a router, an attenuator, a power distribution unit, and a turntable.

[0061] In this embodiment of the disclosure, the shielded space may include a shielded box or a shielded room, which can be a closed environment for isolating external electromagnetic interference. This environment ensures the accuracy of the test results because external signals will not interfere with the test process, and the test signal will not leak to the outside. The interior of the shielded space can be configured to simulate different wireless propagation environments, such as urban, suburban, or indoor physical environments. In different physical environments that have been constructed, each physical environment may have one or more shielded spaces to simulate different physical environments.

[0062] In this embodiment of the disclosure, the terminal is the subject of the test, which may include smartphones, tablets, IoT devices or any other wireless communication devices. The WiFi performance of the terminal (such as throughput, latency, signal reception capability) is the focus of the test.

[0063] Other testing equipment may include other terminals of the same or different types as the stated terminal, such as comparison units or auxiliary units, to be used for performance comparison or auxiliary testing in multi-device simulated scenarios. For example, in comparison testing, multiple comparison units of the same or different types can be used simultaneously to execute the same data stream transmission instructions to compare their performance differences. Auxiliary units may be used to provide additional signal sources, simulate network conditions, or perform specific test tasks to support the performance testing of the main testing equipment. For example, a Bluetooth board can provide Bluetooth connectivity for the terminal during testing, or another terminal can provide the function of inter-terminal data transmission during testing.

[0064] The test server can be used to control and manage the testing process, including the execution of test scripts, data collection, and analysis.

[0065] Switches and routers are key components of network infrastructure, used to create and manage network topologies in test environments. They support data transmission between multiple devices and can be used to simulate different network conditions, such as bandwidth limitations, latency, or packet loss.

[0066] Attenuators are used to simulate signal attenuation during transmission to test the performance of a device under weak signal conditions. They can help evaluate the device's receiving sensitivity and communication capabilities in edge coverage areas.

[0067] Power distribution units (PDUs) can be used to power necessary equipment in a test environment and provide a stable and reliable power supply. PDUs can also have overload protection, remote control and monitoring functions to ensure the safety and controllability of the test process.

[0068] A turntable is a rotating platform used to change the orientation of a terminal or antenna during testing. By rotating the turntable, the communication performance of the device at different angles can be simulated, and the omnidirectional or directional communication capabilities of the device can be evaluated. Furthermore, a turntable can also be used to simulate the communication performance of a device while it is in motion, such as a rotating mobile phone or vehicle-mounted communication device.

[0069] Through the embodiments disclosed herein, this configuration provides a comprehensive and controllable environment for performance testing of wireless communication and network devices. The variety of test equipment greatly enriches the test scenarios and dimensions. By performing tests within these devices and environments, device performance can be accurately evaluated, providing strong support for network optimization, device selection, and technology development. Simultaneously, this configuration also supports combined testing of multiple test dimensions to meet diverse testing needs and scenarios. By appropriately selecting and using these devices, the performance of wireless communication and network devices can be evaluated more accurately.

[0070] In some embodiments of this disclosure, the mapping relationship includes: a first mapping relationship consisting of a use case identifier and its corresponding test scenario, and a second mapping relationship consisting of a test scenario and its required test equipment type.

[0071] In this embodiment of the disclosure, the first mapping relationship consists of a test case identifier and its associated test scenario. Each test case can correspond to a test scenario, which describes the network environment and test dimensions required for that test case. The second mapping relationship consists of a test scenario and its required test device type. This means that each test scenario specifies which types of devices need to be executed in which network environment.

[0072] In some embodiments of this disclosure, the test scenario indicates the network topology and test dimensions used for device connectivity.

[0073] Network topology describes how devices are connected, including the layout of network nodes (such as devices and servers) and the links between them. Network topology defines how data flows within the network and the communication paths between devices. Network topology directly impacts key factors in the test environment, such as network performance, latency, and bandwidth.

[0074] In some embodiments of this disclosure, the test dimensions include one of the following: throughput test, latency test, attenuation signal test, weak signal test, orthogonal frequency division multiple access performance test, multi-terminal coexistence test, and multi-terminal racing test.

[0075] In this embodiment of the disclosure, these test dimensions can all be performed in a WiFi network environment. Test dimensions are the core of the testing activity, defining the functions, performance, or security aspects that need to be verified for the terminal. Test dimensions can be associated with the inputs, expected outputs, and execution steps in the test.

[0076] Among these, throughput testing can be used to evaluate the amount of data a terminal can successfully transmit and receive per unit time. Delay testing can be used to measure the time required for a terminal to respond to a request. Signal attenuation testing can be used to measure the weakening of a signal during transmission. Weak signal testing can be used to evaluate the terminal's performance when receiving weak signals. Orthogonal Frequency Division Multiple Access (OFDM) performance testing can be used to measure and evaluate the terminal's transmission efficiency, anti-interference capability, and spectral efficiency when using OFDM technology.

[0077] Multi-terminal coexistence testing can be used to evaluate the performance of the target terminal when multiple terminal devices are running simultaneously in the same network or frequency band. This test aims to understand whether the terminal can maintain stable communication quality in a multi-device environment and whether it can avoid mutual interference.

[0078] Terminal race testing can be used to evaluate the performance of multiple terminal devices competing for network resources. This test helps to understand the processing power of terminals under high load and the behavior of terminal devices when resources are limited.

[0079] The multiple terminal devices include the target terminal and auxiliary terminals that constitute the multi-device environment. The auxiliary terminals and the target terminal can be of the same or different types.

[0080] Figure 2 This is a schematic diagram illustrating a second mapping relationship in a terminal performance testing method according to some embodiments of this disclosure. For example... Figure 2 The second mapping relationship shown includes the interrelationships between the physical environment (i.e., physical resources), the network topology used for device connectivity (i.e., Topo), the test dimensions (i.e., test cases), and the test devices (i.e., devices).

[0081] There is a mapping relationship between the network topology and the test dimensions, and this mapping relationship can form a variety of test scenarios.

[0082] The network topology implies the required device types, and the network topology can be further connected to the required test devices through connected test dimensions.

[0083] Based on the space volume that the test equipment required for the network topology may occupy in practical applications, and the actual environments in which the test dimensions typically occur, shielded spaces of different volumes and quantities can be configured to represent different physical environments. The space volume of a shielded room will be larger than that of a shielded enclosure.

[0084] In an exemplary embodiment, test cases for throughput and delay dimensions can be tested using a shielded room environment, test cases for weak signal testing dimension can be tested using a shielded box environment with attenuators, and test cases for RvR (a performance test that can control signal attenuation) dimension can be tested using a shielded box environment with attenuators and turntables.

[0085] Figure 3 This is a flowchart illustrating a terminal performance testing method according to some embodiments of the present disclosure.

[0086] In this embodiment of the disclosure, Figure 3 In the terminal performance testing method shown, steps S310 and S350 are respectively related to... Figure 1 Steps S110 and S130 in the terminal performance testing method shown correspond to each other and will not be repeated here.

[0087] In this embodiment of the disclosure, Figure 1 Based on the terminal performance testing method shown, Figure 3 The terminal performance testing method shown may also include the following steps.

[0088] In step S320, the target test scenario corresponding to each use case identifier in the first mapping relationship is determined.

[0089] The first mapping relationship consists of a use case identifier and its corresponding test scenario.

[0090] Step S330: Determine the target test device type corresponding to each target test scenario in the second mapping relationship.

[0091] The second mapping relationship consists of the test scenario and the type of test equipment required.

[0092] In this embodiment of the disclosure, firstly, based on multiple test case identifiers in the test task, their respective corresponding target test scenarios can be found through a first mapping relationship. Then, for each found target test scenario, the required test equipment type, i.e., the test equipment type needed for each test case, can be found through a second mapping relationship.

[0093] Step S340: Determine the target physical environment and target test equipment required to perform the test task according to each target test equipment type.

[0094] In this embodiment of the disclosure, based on the type of test equipment found, the corresponding test equipment can be located in the actual physical environment. Specifically, the status of equipment already deployed in the physical environment (such as a laboratory or testing center) can be checked to confirm which equipment meets the testing requirements and is usable. Combining this information, the specific physical environment and test equipment required to perform the testing task can be determined.

[0095] In an exemplary embodiment, it may be permissible for some test cases to be tested using the same type of test equipment.

[0096] Through the embodiments of this disclosure, it can be ensured that the test task can find the most suitable physical environment and test equipment according to the specific requirements of each test case, and then schedule these physical environments and test equipment in a unified and efficient manner, reducing test delays or failures caused by equipment or environment mismatch, and greatly improving the accuracy, effectiveness and efficiency of testing.

[0097] Figure 4 This is a flowchart illustrating the determination of the target physical environment and target test equipment in a terminal performance testing method according to some embodiments of the present disclosure.

[0098] like Figure 4 As shown, in some embodiments of this disclosure, determining the target physical environment and target test equipment required to perform the test task according to each target test equipment type may include the following steps.

[0099] Step S410: Based on the operating status of the test equipment in each physical environment, determine the idle test equipment included in the idle physical environment.

[0100] In this embodiment of the disclosure, the granularity of selecting the pre-deployed physical environment and the test equipment therein can be "one set of test environments," that is, all test equipment deployed in a physical environment can be considered as one set of test environments. Each physical environment can have the same or different shielding spaces, and the number or type of candidate test equipment contained in each physical environment can also be the same or different. When selecting, the physical environment and the test equipment therein can be considered as a whole.

[0101] Idle test devices contained within an idle physical environment can be considered as a set of idle test environments. The idle test devices in each physical environment can be identified by filtering based on their operational status. An idle state means that these devices are not currently occupied by other test cases and can therefore be used to execute new test cases (i.e., test cases in the current test task).

[0102] In an exemplary embodiment, for some test cases that test terminal functions (such as checking whether the terminal has WiFi functionality), since it is only necessary to detect whether the terminal has or does not have a certain function, these functional test cases can be performed simultaneously. Therefore, if the current functional test case exists in the current test task, the test environment occupied by other functional test cases can also be considered idle for the current functional test case.

[0103] Step S420: Match each target test device type with the idle test devices contained in the idle physical environment to determine the candidate test devices contained in the candidate physical environment corresponding to each test case.

[0104] In this embodiment of the disclosure, each target test device type (i.e., the device type specified by the test case) can be matched with the selected idle test devices contained in the idle physical environment to determine which idle test devices meet the device type requirements of the test cases. The matching result can be one or more candidate test devices that are both idle and meet the device type requirements of the test task. The candidate test devices contained in the candidate physical environment are selected from one or more sets of idle test environments and can also be considered as a complete set of candidate test environments.

[0105] In an exemplary embodiment, the selected candidate test environment can be able to cover the target test device type without being a complete match. That is, there may be devices in the candidate physical environment that are not used by the test cases, as long as the target test device type exists in all candidate physical environments.

[0106] For example, combining Figure 2 It is evident that throughput and latency, as two testing dimensions, have different requirements for the physical environment and testing equipment, but if Figure 2 The "one belt four shielded box" provided in the test kit contains all types of test equipment. Therefore, test cases for both throughput and latency test dimensions can use this physical environment. However, there will be equipment in this physical environment that is not used by the test cases.

[0107] Step S430: Determine the target physical environment and target test equipment required to execute the test task based on the candidate test equipment contained in the candidate physical environment corresponding to each test case.

[0108] In this embodiment of the disclosure, the target physical environment and target test equipment required to perform the test task can be determined based on the matching results. Here, "target test equipment" refers to the specific equipment selected from candidate test equipment that will be used to perform the test task. "Target physical environment" refers to the physical environment containing the target test equipment.

[0109] This process involves evaluating the feasibility and priority of using the test environment for each test case, considering factors such as network topology support, test equipment performance, and whether the test cases can be executed together. Ultimately, based on these evaluation results, the target physical environment and target test equipment required to execute the test tasks are determined.

[0110] In an exemplary embodiment, different test cases can have different sharing principles (compatibility principles). For example, some functional test cases can be tested using the same test environment (i.e., the physical environment and the test equipment within it). Within the physical environment corresponding to the jointly executed test cases, the test equipment required for these test cases can be the same or different.

[0111] In an exemplary embodiment, when determining the target physical environment and target test equipment, resource utilization can be optimized as much as possible to avoid resource waste and conflicts. For example, multiple test cases can share the same physical environment or test equipment through reasonable scheduling and configuration.

[0112] Through the embodiments of this disclosure, devices that are both idle and meet the requirements of test cases can be identified from a large pool of test equipment, and their physical environment can be determined for executing test tasks. This allows for more effective management and utilization of test resources, helping to improve the efficiency and accuracy of test task execution, while also reducing test costs and maintenance complexity.

[0113] Figure 5 This is a flowchart illustrating the determination of the target physical environment and target test equipment in another terminal performance testing method according to some embodiments of this disclosure. Figure 5 In the flowchart shown, steps S510 and S520 of determining the target physical environment and target test equipment are respectively related to... Figure 4 Steps S410 and S420 in the process of determining the target physical environment and target test equipment are shown and will not be repeated here.

[0114] In some embodiments of this disclosure, in Figure 4 Based on the process shown for determining the target physical environment and target testing equipment, Figure 5 The process for determining the target physical environment and target test equipment may also include the following steps.

[0115] Step S530: Based on the candidate test devices contained in the candidate physical environment corresponding to all test cases, form at least one device allocation strategy; wherein, the device allocation strategy includes: the candidate test devices contained in the candidate physical environment allocated to each test case, and the execution order of the multiple test cases, the execution order including at least one of parallel execution and serial execution.

[0116] In an exemplary embodiment, each test case may have shared information, which may indicate whether it can be shared with other test cases, and with which test cases or types of test cases. The shared information may be used to determine the execution order of multiple test cases in a resource allocation strategy.

[0117] Step S540: Determine the execution time of the test task under the allocation strategy of each device.

[0118] In this embodiment of the disclosure, for each device allocation strategy, the total time for executing the test task can be estimated. This time can take into account factors such as the execution time of the test cases, communication latency between devices (if parallel execution exists), and possible device preparation (such as initialization) and data cleanup time.

[0119] Step S550: Determine the target physical environment and target test equipment required to execute the test task according to the device allocation strategy with the shortest execution time.

[0120] In this embodiment of the disclosure, among all possible device allocation strategies, the strategy with the shortest execution time is selected, and the specific target physical environment and target test equipment required to execute the test task are determined based on this strategy with the shortest execution time.

[0121] This disclosure provides an optimal test execution plan by comprehensively considering the execution order of test cases and device allocation, thereby completing the test task in the shortest possible time. This is particularly important for scenarios requiring efficient use of test resources and shortened test cycles.

[0122] Figure 6 This is a schematic diagram of the physical environment of a terminal performance testing method including a test device, according to some embodiments of the present disclosure.

[0123] like Figure 6 As shown, a physical environment may include the following test equipment: 1-Master PC, 2-Test PC, 3A-2.5G power switch, 3B-Switch, 3C-PDU, 4-Test machine, 5-Packet capture machine, 6-ESP32_LyraT, 7-Attenuator, 8-Turntable, 9A-Main router, 9B-Sub-router. The Master PC (1) determines the physical environment and test equipment required for each test case. Then, the Master PC (1) notifies the Test PC (2) within that physical environment, which executes the test case script to control other test equipment in that physical environment to execute the corresponding test cases.

[0124] like Figure 6The physical environment shown can include a shielded room structure and a shielded box structure. The shielded room structure can contain a set of connectors 2, 3A, 3B, 3C, 9A, 9B, 4, 5, and 6. Connector 2 can be connected to connectors 3C, 9A, and 9B via network cables through connectors 3A and 3B, and can also be connected to connectors 4, 5, and 6 via USB cables. The shielded box structure can contain a set of connectors 2, 3A, 3B, 3C, 7, 8, 9A, 9B, 4, 5, and 6. Connector 2 can be connected to connectors 3C, 7, 8, 9A, and 9B via network cables through connectors 3A and 3B, and can also be connected to connectors 4, 5, and 6 via USB cables. Within box 9B, a cable connects the signal to the box containing connector 4.

[0125] In some embodiments of this disclosure, controlling the target testing device to execute the plurality of test cases within the target physical environment to obtain terminal performance test results includes: retrieving the test case scripts for each test case; controlling the relevant target testing device to execute the test cases within the relevant target physical environment based on each test case script to obtain test data for each test case; quantifying the test data for each test case to obtain quantization results for each test case; and weighting and summing the quantization results for each test case based on preset weights to obtain terminal performance test results.

[0126] In this embodiment of the disclosure, test case scripts for all test cases to be executed can be stored in a specific database. Instructions are sent to the target test device in the corresponding target physical environment according to the script of each test case to execute the test case, and then the test data of each test case is obtained.

[0127] The collected test data is typically raw and diverse, requiring quantification for comparison and evaluation. Quantification can be performed based on the test scenario of each test case, or by standardizing the values, converting resource consumption into percentages or specific numerical values. The quantified results more intuitively reflect the terminal's performance in each test case.

[0128] In this embodiment, since different test cases may have varying degrees of impact on terminal performance, different weights can be assigned to the quantification results of each test case. These weights are typically determined based on factors such as the importance of the test case, its impact on user experience, or the current focus of terminal performance development. The weighted summation process involves multiplying the quantification result of each test case by its corresponding weight, and then summing all weighted results to obtain the final terminal performance test result. This result can be a comprehensive score or a report containing scores across multiple dimensions, used to comprehensively evaluate the performance of the test device.

[0129] Through the embodiments disclosed herein, the overall performance of a terminal can be systematically and quantitatively evaluated, providing strong data support for subsequent optimization and improvement.

[0130] In some embodiments of this disclosure, the plurality of test cases include a first test case, which is used to perform performance testing under a first target test scenario through a first target test device within a first target physical environment; wherein, the first target test device includes the terminal and other test devices, and the first target test scenario indicates the test dimension and the network topology for device connection.

[0131] Figure 7 This is a flowchart illustrating the execution of test cases based on test case scripts in a terminal performance testing method according to some embodiments of this disclosure. Figure 7 As shown, the process of controlling the relevant target test equipment to execute test cases within the relevant target physical environment based on each test case script to obtain the test data of each test case may include the following steps.

[0132] Step S710: Based on the use case script of the first use case, control the power-on of the first target test device to form the network topology, and control the terminal to complete the initialization.

[0133] In this embodiment, the power supply to the first target test device can be turned on first. This includes the terminal under test (DUT) and other test devices. Then, the connections between devices can be configured according to the network topology specified in the test case script. This may involve configuring network parameters such as IP addresses, subnet masks, and gateways to ensure correct communication between devices. After the network topology is constructed, the DUT can also be controlled to complete initialization, such as starting the operating system, loading necessary test applications, configuring test parameters, turning off Bluetooth, and enabling airplane mode.

[0134] Step S720: Based on the test case script of the first test case, control the data stream transmission between the other test devices and the terminal.

[0135] In this embodiment of the disclosure, data stream transmission between other test devices (such as a test server) and the terminal under test can be controlled according to instructions in the test case script. This data stream transmission can include various types of data transmission, such as uploading, downloading, real-time video streaming, and voice calls. The purpose of this data stream transmission is to simulate network activity in real-world usage scenarios in order to evaluate the performance of the terminal under test under specific test dimensions.

[0136] Step S730: Determine the test data for the first use case based on the data corresponding to the test dimension recorded during the data stream transmission process.

[0137] In this embodiment of the disclosure, during the data stream transmission process, data corresponding to the test dimension can be recorded, such as transmission rate, latency, packet loss rate, CPU utilization, memory usage, etc.

[0138] Through the embodiments of this disclosure, the first target test device can be precisely and orderly controlled to execute the first test case in the first target physical environment, and the data corresponding to the test dimension can be accurately recorded as an important basis for evaluating the performance of the terminal under test.

[0139] In an exemplary embodiment, combined with Figure 6 The test PC can execute the main program of the test case (taking throughput testing as an example) to send out test tasks, realizing the process of controlling the test device to execute test cases based on the test case script. Specifically, it can include the following:

[0140] (1) The test machine (i.e. the terminal mentioned above) first automatically flashes the version of the software to be tested and installs the test apk by issuing a task, and then opens the test apk; the apk can be used for GPPC communication of the mobile phone.

[0141] (2) The test PC receives test tasks through the agent and loads multiple cases, and arranges the execution order of the cases according to the threshold topology.

[0142] (3) The test PC calls the interface through the main program to control the PDU power manager program and turns on the power supply of the corresponding test protocol router according to the execution case.

[0143] (4) The test machine executes the preconditions of the test case (i.e., initialization, such as turning off Bluetooth and turning on flight mode).

[0144] (5) Test PC to execute the command to start the iperf server and start the server.

[0145] (6) The test machine executes the command to start the iperf client to start the client and start the data stream. It can test three times in a row, each time for 1 minute. Record the average value of each test during this process, and judge whether the test case passes according to the standard and record the test results.

[0146] In some embodiments of this disclosure, the plurality of test cases includes a second test case; the terminal performance testing method further includes: in response to the invalid execution of the second test case, determining the invalidity type of the invalid execution, and re-executing the second test case using a processing method corresponding to the invalidity type; in response to the number of re-executions reaching a threshold, capturing the corresponding running log, and reporting an anomaly based on the invalidity type and the running log.

[0147] In this embodiment of the disclosure, invalid types may include, for example, issues such as substandard performance values, network outages, and connection failures. The threshold for the number of attempts can be a value set based on actual needs (such as the importance of the test cases), such as 3, 4, or 5 attempts.

[0148] Different handling methods can be set according to different invalidity types. For example, for invalidity caused by crash exception, the terminal can be restarted and the current test case can be re-executed.

[0149] In this embodiment of the disclosure, the second test case and the first test case mentioned above can be the same test case or different test cases, both referring to a certain test case in the test task.

[0150] Through the embodiments of this disclosure, when test cases are executed ineffectively, an appropriate processing method can be selected based on the type of ineffectiveness, and the test cases can be re-executed if necessary. If the problem cannot be resolved within a specified number of attempts, runtime logs can be captured and exceptions reported, thereby helping to ensure the accuracy and effectiveness of testing, while improving testing efficiency and problem-solving speed.

[0151] Combination Figure 6 In some embodiments of this disclosure, the terminal performance testing method may include the following process.

[0152] After the test task is sent from the test platform, the 1-master PC automatically pulls WiFi automated performance test cases (i.e., multiple test cases) from the automated test cloud platform according to the sent link, selects an idle environment (i.e., the target physical environment and the target test device in it) that matches the test case scenario on the automated test cloud platform, installs the test APK on the 4-test machine and puts it into the idle test environment, and then sends the test task to the 2-test PC through the cloud platform.

[0153] During testing, the 2-test PC can first execute the WiFitest power control module, and control the power switch of the corresponding test case 9B-sub-router via the 3C-PDU.

[0154] During the testing period, the 4-test machine (i.e., the terminal) can automatically connect to and enable the WiFi hotspot of the 9B-sub-router and automatically configure the routing-related parameters to complete the WiFi performance test for different test cases.

[0155] After all test tasks are completed, the test results can be processed and judged. The log files and related data generated during the test can be sent back to the automated test cloud platform, and the results can be visualized.

[0156] In addition, it can automatically report abnormal issues of the 4-test machine to the designated abnormal handling platform, record test results in the enterprise test platform link, generate product module quality reports according to the set quality model formula, and finally send them to relevant personnel via email and Lark notification.

[0157] This disclosure enables the automation of the entire business process, including test deployment, resource scheduling, test execution, exception handling, data integration, result evaluation, and uploading to the exception handling platform. It allows for the automatic retrieval of corresponding test cases based on test task links, automatic selection of idle environments for test task execution, and monitoring of test status by testers on the automated testing cloud platform. If exceptions occur during testing, corresponding logs can be automatically captured and uploaded to the exception handling platform. Furthermore, after test execution, multi-dimensional test results can be displayed on the automated testing cloud platform, and the results can be sent back to the enterprise testing platform. Finally, a test report is generated and sent to relevant personnel via corporate email.

[0158] It should be noted that the above figures are merely illustrative representations of the processes included in methods according to some embodiments of this disclosure, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0159] The following are embodiments of the apparatus disclosed herein, which can be used to execute embodiments of the method disclosed herein. For details not disclosed in the apparatus embodiments of this disclosure, please refer to the embodiments of the method disclosed herein.

[0160] Figure 8 This is a block diagram illustrating a terminal performance testing apparatus according to some embodiments of the present disclosure. (Refer to...) Figure 8 The device includes a task receiving unit 801, a determining unit 802, and an execution unit 803.

[0161] The task receiving unit 801 is used to receive a test task for the terminal, the test task including test case identifiers of multiple test cases; the determining unit 802 is used to determine the target physical environment and target test equipment required to execute the test task according to the multiple test case identifiers and a preset mapping relationship; the execution unit 803 is used to control the target test equipment to execute the multiple test cases in the target physical environment to obtain the terminal performance test results.

[0162] In some embodiments of this disclosure, the mapping relationship includes: a first mapping relationship consisting of a use case identifier and its corresponding test scenario, and a second mapping relationship consisting of a test scenario and its required test equipment type; wherein, the determining unit 802 determines the target physical environment and target test equipment required to execute the test task based on multiple use case identifiers and a preset mapping relationship, including: determining the target test scenario corresponding to each use case identifier in the first mapping relationship; determining the target test equipment type corresponding to each target test scenario in the second mapping relationship; and determining the target physical environment and target test equipment required to execute the test task based on each target test equipment type.

[0163] In some embodiments of this disclosure, the determining unit 802 determines the target physical environment and target test equipment required to execute the test task based on each target test equipment type, including: determining idle test equipment contained in the idle physical environment based on the operating status of test equipment in each physical environment; matching each target test equipment type with the idle test equipment contained in the idle physical environment to determine the candidate test equipment contained in the candidate physical environment corresponding to each test case; and determining the target physical environment and target test equipment required to execute the test task based on the candidate test equipment contained in the candidate physical environment corresponding to each test case.

[0164] In some embodiments of this disclosure, the determining unit 802 determines the target physical environment and target test equipment required to execute the test task based on the candidate test equipment contained in the candidate physical environment corresponding to each test case, including: forming at least one device allocation strategy based on the candidate test equipment contained in the candidate physical environment corresponding to all test cases; wherein, the device allocation strategy includes: the candidate test equipment contained in the candidate physical environment allocated to each test case, and the execution order of the plurality of test cases, the execution order including at least one of parallel execution and serial execution; determining the execution time of the test task under each device allocation strategy; and determining the target physical environment and target test equipment required to execute the test task based on the device allocation strategy with the shortest execution time.

[0165] In some embodiments of this disclosure, the target physical environment includes at least one shielded space, and the target test equipment includes at least the terminal, test server, switch, router, attenuator, and power distribution unit.

[0166] In some embodiments of this disclosure, the execution unit 803 controls the target testing device to execute the plurality of test cases in the target physical environment to obtain terminal performance test results, including: retrieving the test case scripts for each test case; controlling the relevant target testing device to execute the test cases in the relevant target physical environment based on each test case script to obtain test data for each test case; quantifying the test data for each test case to obtain quantization results for each test case; and performing a weighted summation of the quantization results for each test case based on preset weights to obtain terminal performance test results.

[0167] In some embodiments of this disclosure, the plurality of test cases includes a first test case, which is used to perform performance testing under a first target test scenario through a first target test device within a first target physical environment; wherein, the first target test device includes the terminal and other test devices, and the first target test scenario indicates the test dimension and the network topology for device connection; wherein, the execution unit 803 controls the relevant target test devices to execute test cases within the relevant target physical environment based on each test case script to obtain test data for each test case, including: controlling the power-on of the first target test device to form the network topology based on the test case script of the first test case, and controlling the terminal to complete initialization; controlling the other test devices to perform data stream transmission with the terminal based on the test case script of the first test case; and determining the test data of the first test case based on the data corresponding to the test dimension recorded during the data stream transmission.

[0168] In some embodiments of this disclosure, the test dimensions include one of the following: throughput test, latency test, attenuation signal test, weak signal test, orthogonal frequency division multiple access performance test, multi-terminal coexistence test, and multi-terminal racing test.

[0169] In some embodiments of this disclosure, the plurality of test cases include a second test case; the execution unit 803 is further configured to: in response to the invalid execution of the second test case, determine the invalidity type of the invalid execution, and re-execute the second test case using a processing method corresponding to the invalidity type; in response to the number of re-executions reaching a threshold, capture the corresponding running log, and report an anomaly based on the invalidity type and the running log.

[0170] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0171] Figure 9This is a block diagram illustrating an apparatus 900 for terminal performance testing according to some embodiments of the present disclosure. For example, apparatus 900 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0172] Reference Figure 9 The device 900 may include one or more of the following components: a processing component 902, a memory 904, a power component 906, a multimedia component 908, an audio component 910, an input / output (I / O) interface 912, a sensor component 914, and a communication component 916.

[0173] Processing component 902 typically controls the overall operation of device 900, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 902 may include one or more processors 920 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 902 may include one or more modules to facilitate interaction between processing component 902 and other components. For example, processing component 902 may include a multimedia module to facilitate interaction between multimedia component 908 and processing component 902.

[0174] Memory 904 is configured to store various types of data to support the operation of device 900. Examples of this data include instructions for any application or method operating on device 900, contact data, phonebook data, messages, pictures, videos, etc. Memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0175] The power supply component 906 provides power to the various components of the device 900. The power supply component 906 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device 900.

[0176] Multimedia component 908 includes a screen that provides an output interface between the device 900 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 908 includes a front-facing camera and / or a rear-facing camera. When the device 900 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0177] Audio component 910 is configured to output and / or input audio signals. For example, audio component 910 includes a microphone (MIC) configured to receive external audio signals when device 900 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 904 or transmitted via communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.

[0178] I / O interface 912 provides an interface between processing component 902 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0179] Sensor assembly 914 includes one or more sensors for providing status assessments of various aspects of device 900. For example, sensor assembly 914 may detect the on / off state of device 900, the relative positioning of components such as the display and keypad of device 900, changes in position of device 900 or a component of device 900, the presence or absence of user contact with device 900, orientation or acceleration / deceleration of device 900, and temperature changes of device 900. Sensor assembly 914 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 914 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 914 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0180] Communication component 916 is configured to facilitate wired or wireless communication between device 900 and other devices. Device 900 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, other communication standards, or combinations thereof. In some embodiments of this disclosure, communication component 916 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In some embodiments of this disclosure, communication component 916 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0181] In some embodiments of this disclosure, the apparatus 900 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0182] In some embodiments of this disclosure, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including instructions that can be executed by a processor 920 of device 900 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0183] A non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to execute a terminal performance testing method. The method includes: receiving a test task for the terminal, the test task including test case identifiers for multiple test cases; determining a target physical environment and a target test device required to execute the test task based on the multiple test case identifiers and a pre-defined mapping relationship; and controlling the target test device to execute the multiple test cases within the target physical environment to obtain terminal performance test results.

[0184] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0185] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method of testing the performance of a terminal, characterized by, include: Receive a test task for the terminal, the test task including test case identifiers for multiple test cases; Based on multiple use case identifiers and pre-defined mapping relationships, determine the target physical environment and target test equipment required to execute the test task; The target testing device is controlled to execute the multiple test cases within the target physical environment to obtain terminal performance test results.

2. The method of claim 1, wherein, The mapping relationship includes: a first mapping relationship consisting of a use case identifier and its corresponding test scenario, and a second mapping relationship consisting of a test scenario and its required test equipment type; Specifically, based on multiple use case identifiers and pre-defined mapping relationships, the target physical environment and target test equipment required to execute the test task are determined, including: Determine the target test scenario corresponding to each use case identifier in the first mapping relationship; Determine the target test device type corresponding to each target test scenario in the second mapping relationship; The target physical environment and target test equipment required to perform the test task are determined based on the type of target test equipment.

3. The method of claim 2, wherein, The target physical environment and target test equipment required to perform the test tasks are determined based on the type of target test equipment, including: Based on the operating status of the test equipment in each physical environment, determine the idle test equipment included in the idle physical environment; Each target test device type is matched with the idle test devices contained in the idle physical environment to determine the candidate test devices contained in the candidate physical environment corresponding to each test case. Based on the candidate test devices included in the candidate physical environment corresponding to each test case, determine the target physical environment and target test device required to execute the test task.

4. The method of claim 3, wherein, Based on the candidate test devices included in the candidate physical environment corresponding to each test case, determine the target physical environment and target test devices required to execute the test task, including: Based on the candidate test devices contained in the candidate physical environment corresponding to all test cases, at least one device allocation strategy is formed; wherein, the device allocation strategy includes: the candidate test devices contained in the candidate physical environment allocated to each test case, and the execution order of the multiple test cases, the execution order including at least one of parallel execution and serial execution; Determine the execution duration of the test task under each device allocation strategy; The target physical environment and target test equipment required to execute the test task are determined based on the device allocation strategy with the shortest execution time.

5. The method of claim 3, wherein, The physical environment includes at least one shielded space, and the test equipment includes at least the terminal, test server, switch, router, attenuator, and power distribution unit.

6. The method of claim 1, wherein, Controlling the target testing device to execute the multiple test cases within the target physical environment to obtain terminal performance test results, including: Retrieve the test case scripts for each test case; Based on each test case script, the relevant target test equipment is controlled to execute test cases within the relevant target physical environment to obtain test data for each test case; The test data of each test case is quantified to obtain the quantification results of each test case; The quantitative results of each test case are weighted and summed based on preset weights to obtain the terminal performance test results.

7. The method of claim 6, wherein, The plurality of test cases include a first test case, which is used to perform performance testing under a first target test scenario through a first target test device within a first target physical environment; wherein, the first target test device includes the terminal and other test devices, and the first target test scenario indicates the test dimensions and the network topology for device connection; Specifically, based on each test case script, the relevant target test equipment is controlled to execute test cases within the relevant target physical environment, obtaining test data for each test case, including: The test case script based on the first test case controls the power-on of the first target test device to form the network topology, and controls the terminal to complete initialization; The test case script based on the first test case controls the data stream transmission between the other test devices and the terminal; The test data for the first use case is determined based on the data corresponding to the test dimension recorded during the data stream transmission.

8. The method of claim 7, wherein, The testing dimensions include one of the following: throughput test, latency test, attenuation signal test, weak signal test, orthogonal frequency division multiple access performance test, multi-terminal coexistence test, and multi-terminal racing test.

9. The method of claim 1, wherein, The plurality of test cases includes a second test case; the method further includes: In response to the invalidation of the second use case, the invalidation type is determined, and the second use case is executed again using the processing method corresponding to the invalidation type; In response to the number of re-executions reaching the threshold, the corresponding runtime logs are retrieved, and an exception is reported based on the invalidity type and the runtime logs.

10. A terminal performance testing apparatus, characterized by comprising: include: The task receiving unit is used to receive test tasks for the terminal, wherein the test task includes test case identifiers for multiple test cases; The determining unit is used to determine the target physical environment and target test equipment required to execute the test task based on the multiple use case identifiers and the pre-defined mapping relationship; An execution unit is used to control the target test device to execute the multiple test cases within the target physical environment to obtain terminal performance test results.

11. An electronic device, comprising: include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the steps of the method according to any one of claims 1-9.

12. A non-transitory computer-readable storage medium, wherein when instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is enabled to perform the steps of the method as described in any one of claims 1-9.

13. A computer program product comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-9.

Images