Tablet computer automatic testing system and testing method

Abstract

This invention relates to the field of tablet computer technology, and in particular to an automated testing system and method for tablet computers. The system includes a test management module, a device access module, a scenario-driven module, a data acquisition module, a result judgment module, and a report traceability module. The device access module establishes a communication connection with the tablet computer under test and acquires its model identifier, hardware configuration information, system version information, and interface status information. The test management module generates a set of test tasks and a test execution order corresponding to the tablet computer under test based on the model identifier, hardware configuration information, and system version information. This invention not only automates and standardizes the tablet computer testing process but also improves test coverage, result accuracy, environmental adaptability, and fault traceability.

Description

Technical Field

[0001] This invention relates to the field of tablet computer technology, and in particular to an automatic testing system and method for tablet computers. Background Technology

[0002] With the widespread application of tablet computers in office, education, entertainment and industrial terminals, products typically need to undergo multiple tests before leaving the factory, after system upgrades and after maintenance, including display, touch, audio, communication, sensor and overall stability tests, to ensure that the devices function normally and operate stably.

[0003] Current tablet PC testing methods mainly include manual testing and script-based semi-automatic testing. Manual testing relies on operators to execute test items one by one, which is not only inefficient but also easily affected by factors such as operator experience and operating habits, resulting in poor consistency, strong subjectivity, and a high rate of missed tests. While script-based semi-automatic testing can improve testing efficiency to some extent, it typically uses fixed test procedures and fixed judgment rules, making it less adaptable to different models, hardware configurations, and system versions. When the device model or software version changes, it is often necessary to readjust the test scripts and test parameters, resulting in high maintenance costs.

[0004] Furthermore, existing testing solutions often focus on independent testing of single functions, lacking coverage of complex usage scenarios and abnormal situations, making it difficult to detect coupled faults arising from the coordinated operation of multiple modules. Simultaneously, current technologies typically rely solely on single test return values ​​or fixed thresholds for result judgment, lacking comprehensive analysis of log information, operating parameters, response timing, and environmental factors, making them prone to misjudgments or omissions under conditions such as network fluctuations, system load changes, or power consumption variations. Therefore, there is an urgent need for a method that enables adaptive testing for different device models and versions, automated execution across multiple scenarios, comprehensive result judgment, and test result traceability and continuous optimization. Summary of the Invention

[0005] To address the aforementioned issues, this invention provides an automated testing system and method for tablet computers that not only automates and standardizes the tablet computer testing process but also improves test coverage, result accuracy, environmental adaptability, and fault tracing capabilities.

[0006] The technical solution adopted in this invention is: an automatic testing system for tablet computers, including a test management module, a device access module, a scenario-driven module, a data acquisition module, a result judgment module, and a report traceability module; The device access module is used to establish a communication connection with the tablet computer under test and to obtain the model identifier, hardware configuration information, system version information and interface status information of the tablet computer under test. The test management module is used to generate a set of test tasks and a test execution order corresponding to the tablet computer under test based on the model identifier, hardware configuration information and system version information; The scenario driving module is used to call the system interface, driver interface or application layer interface of the tablet computer under test to trigger at least one test scenario among display test, touch test, audio test, camera test, sensor test, communication test, storage test and power consumption test; The data acquisition module is used to collect the operating logs, status parameters, event response data and performance data of the tablet computer under test during the testing process; The result determination module is used to analyze the execution results of each test scenario based on the data collected by the data acquisition module, and output the determination results of qualified, unqualified or re-inspection. The report traceability module is used to generate test reports and associate the test results with the unique identifier of the tablet computer under test.

[0007] A further improvement to the above solution is that the test management module includes a test template submodule, a task orchestration submodule, and a version adaptation submodule; The test template submodule is used to create configurable test templates according to different models; The task orchestration submodule is used to orchestrate multiple test items sequentially, in parallel, or under conditional triggering based on preset dependencies. The version adaptation submodule is used to dynamically adapt the test script, test parameters, and judgment thresholds according to the system version or firmware version of the tablet computer under test.

[0008] A further improvement to the above solution is that the scene-driven module includes an interface call unit, an event injection unit, and a state switching unit; The interface calling unit is used to call the underlying driver interface or upper-layer application interface of the tablet computer under test to execute preset test instructions; The event injection unit is used to inject simulated touch events, key events, rotation events, network events, or abnormal interruption events into the tablet computer under test. The state switching unit is used to control the tablet computer under test to switch between at least two modes among normal mode, power saving mode, high performance mode, airplane mode and sleep wake-up mode, so as to test the functional stability under different working states.

[0009] A further improvement to the above scheme is that the data acquisition module includes a log acquisition unit, a parameter acquisition unit, and a time-series monitoring unit; The log collection unit is used to collect system logs, driver logs, and application logs; The parameter acquisition unit is used to acquire at least one of the following operating parameters: CPU utilization, memory utilization, battery current, battery temperature, wireless signal strength, frame rate, and storage read / write speed. The timing monitoring unit is used to record the test command issuance time, event response time, test completion time, and anomaly occurrence time to generate test timing data.

[0010] A further improvement to the above solution is that the scene-driven module is configured to execute a combined test task, which includes at least one of the following: simultaneously triggering a touch test during the execution of a display test, simultaneously triggering an audio playback test during the execution of a wireless communication test, or simultaneously triggering a temperature rise monitoring test during the execution of a high-load computing test, in order to identify coupled faults that are difficult to detect by a single test.

[0011] A further improvement to the above scheme is that the result determination module further includes a fault location submodule. The fault location submodule is used to output the fault attribution category based on the time sequence of the anomaly occurrence, the interface call chain, the log context, and the trend of resource usage changes. The fault attribution category includes at least hardware anomaly, driver anomaly, system configuration anomaly, application anomaly, and environmental interference anomaly.

[0012] A further improvement to the above scheme is that the report traceability module includes a result reporting unit, a version backtracking unit, and a trend analysis unit; The result reporting unit is used to upload the test results to the server; The version backtracking unit is used to look up the corresponding test script version, system version, and judgment threshold version based on the unique identifier of the tablet computer under test. The trend analysis unit is used to perform statistical analysis on the anomaly types and frequencies of devices in the same batch, model, or version.

[0013] A testing method based on a tablet computer automated testing system includes the following steps: Obtain the device model, system version, and hardware configuration information of the tablet computer under test; Based on the device model information, system version information, and hardware configuration information, a corresponding test template is matched, and a test task sequence is generated; Call the system interface, driver interface, or application interface of the tablet computer under test to execute a preset test scenario; Log data, status parameters, event response data, and performance data are collected during the execution of the preset test scenario; Analyze the collected data and output the test results; The test results are associated with the unique identifier of the tablet computer under test, and a test report is generated.

[0014] A further improvement to the above scheme is that the step of generating the test task sequence includes: establishing a dependency graph between each test item; determining the prerequisite test items, parallel test items, and mutually exclusive test items based on the dependency graph; and dynamically adjusting the test order based on the remaining battery power of the tablet computer under test, the current system load, and the interface availability status, so as to shorten the overall test time and reduce resource conflicts.

[0015] A further improvement to the above scheme is that, in the step of analyzing the collected data, a normalized score is calculated for each individual test result, and a comprehensive judgment value is calculated according to the following formula:

[0016] in, This is a comprehensive judgment value. For the first The normalized score of the test item For the first The weighting coefficients of the test items, For the first The environmental compensation coefficient corresponding to the test item, and it satisfies... ; when If the value is greater than or equal to the first preset threshold, the tablet computer under test is deemed qualified. when If the value is less than the second preset threshold, the tablet computer under test is determined to be unqualified. when When the value is between the first preset threshold and the second preset threshold, the tablet computer under test is determined to be a re-inspection object.

[0017] The beneficial effects of this invention are: This invention, by setting up a test management module, a device access module, a scenario-driven module, a data acquisition module, a result judgment module, and a report traceability module, can automatically generate corresponding test task sets and test execution sequences based on the model information, system version information, and hardware configuration information of the tablet computer under test. It can also automatically call system interfaces, driver interfaces, or application layer interfaces to complete the execution of each test scenario, thereby reducing the time consumption caused by manually configuring the test process item by item, and improving the efficiency of whole-machine testing and batch testing capabilities.

[0018] The test management module in this invention includes a test template submodule, a task orchestration submodule, and a version adaptation submodule. It can automatically match the corresponding test template for different models, hardware configurations, and system versions, and dynamically adjust the test scripts, test parameters, and judgment thresholds. Therefore, it can adapt to different tablet computer models and different software version environments, avoid the problem of poor adaptability of traditional fixed test scripts, and improve the universality and scalability of the automatic testing system.

[0019] This invention not only automates and standardizes the tablet computer testing process, but also improves test coverage, result accuracy, environmental adaptability, and fault traceability, thus possessing high practical value and promotional significance. Attached Figure Description

[0020] Figure 1 This is a connection diagram of the tablet computer automatic testing system of the present invention; Figure 2 for Figure 1 A connection diagram of another embodiment of the automatic testing system for tablet computers; Figure 3 This is a flowchart illustrating the testing method of the present invention.

[0021] Figure labeling: Test Management Module 1, Test Template Sub-module 11, Task Orchestration Sub-module 12, Version Adaptation Sub-module 13, Device Access Module 2, Scenario-Driven Module 3, Interface Call Unit 31, Event Injection Unit 32, State Switching Unit 33, Data Acquisition Module 4, Log Acquisition Unit 41, Parameter Acquisition Unit 42, Timing Monitoring Unit 43, Result Judgment Module 5, Rule Judgment Unit 51, Learning Judgment Unit 52, Fault Location Sub-module 53, Environment Compensation Module 6, Report Traceability Module 7, Result Reporting Unit 71, Version Backtracking Unit 72, Trend Analysis Unit 73, Self-Update Module 8. Detailed Implementation

[0022] To facilitate understanding of the present invention, a more complete description will be given below with reference to the accompanying drawings. Preferred embodiments of the invention are shown in the drawings. However, the invention can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided to provide a thorough and complete understanding of the disclosure of the invention.

[0023] It should be noted that when a component is said to be "fixed to" another component, it can be directly attached to the other component or there may be an intervening component. When a component is said to be "connected to" another component, it can be directly connected to the other component or there may be an intervening component.

[0024] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used herein in the description of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

[0025] like Figures 1-2 As shown, in one embodiment of the present invention, an automatic testing system for tablet computers is provided. This system is mainly applied to scenarios such as factory testing after the tablet computer is manufactured, regression testing after software upgrades, and re-inspection testing after repairs.

[0026] The tablet computer automatic testing system includes a test management module 1, a device access module 2, a scenario-driven module 3, a data acquisition module 4, a result judgment module 5, an environmental compensation module 6, a report traceability module 7, and a self-updating module 8.

[0027] The device access module 2 is used to establish a communication connection with the tablet computer under test. In this embodiment, the device access module 2 can connect to the tablet computer under test via one or more of the following interfaces: USB interface, LAN interface, wireless debugging interface, or serial debugging interface. After establishing a connection, the device access module 2 reads the model identifier, hardware configuration information, system version information, and interface status information of the tablet computer under test. For example, the device access module 2 can read the processor model, memory capacity, screen resolution, wireless communication module configuration, sensor configuration, and current system firmware version.

[0028] Test management module 1 is used to generate a set of test tasks and a test execution order corresponding to the tablet computer under test based on the information obtained by device access module 2. Specifically, test management module 1 includes test template submodule 11, task orchestration submodule 12, and version adaptation submodule 13.

[0029] Test template submodule 11 pre-stores test templates for multiple models. Different test templates can correspond to different hardware configurations and different system versions.

[0030] The task orchestration submodule 12 organizes multiple test items into an ordered task chain based on preset dependencies. For example, before conducting camera testing, basic power-on testing and system startup testing are completed first; before conducting high-load stability testing, battery status testing and heat dissipation status checks are completed first.

[0031] Version adaptation submodule 13 automatically adjusts test parameters based on the current system version. For example, when a certain version of the system modifies the log output fields, version adaptation submodule 13 can automatically switch the corresponding log parsing rules.

[0032] Scene-driven module 3 is used to call the system interface, driver interface or application layer interface of the tablet computer under test to trigger different types of test scenarios.

[0033] In this embodiment, the scene-driven module 3 includes an interface calling unit 31, an event injection unit 32, and a state switching unit 33.

[0034] The interface calling unit 31 can call the display interface, touch driver interface, audio driver interface, wireless communication interface, camera interface and storage read / write interface of the tablet computer under test to execute preset test instructions.

[0035] The event injection unit 32 is used to inject simulated touch events, button events, rotation events, network events, and abnormal interruption events. For example, during touch testing, preset coordinate click events and swipe events are generated by software to verify whether the touch function is normal; during abnormal scenario testing, network disconnection events, application abnormal exit events, or background high usage events can be injected.

[0036] The state switching unit 33 is used to control the tablet computer under test to switch between normal mode, power saving mode, high performance mode, airplane mode and sleep wake-up mode in order to test the stability and recovery capability of the system function under different working states.

[0037] Data acquisition module 4 is used to collect multi-dimensional operational data of the tablet computer under test during the testing process.

[0038] Specifically, the data acquisition module 4 includes a log acquisition unit 41, a parameter acquisition unit 42, and a time series monitoring unit 43.

[0039] The log acquisition unit 41 is used to collect system logs, driver logs and application logs; the parameter acquisition unit 42 is used to collect operating parameters such as CPU utilization, memory utilization, battery current, battery temperature, wireless signal strength, screen frame rate and storage read / write speed; the timing monitoring unit 43 is used to record the test command issuance time, event response time, test completion time and abnormal occurrence time to form complete test timing data.

[0040] With the help of the aforementioned multi-source data, the system can accurately reconstruct the execution process of the test scenario.

[0041] The result determination module 5 is used to analyze the data obtained by the data acquisition module 4 and output the final test results.

[0042] In this embodiment, the result determination module 5 includes a rule determination unit 51, a learning determination unit 52, and a fault location submodule 53.

[0043] The rule determination unit 51 makes a determination based on preset thresholds, rule templates and fault feature databases. For example, when the touch response delay exceeds the set threshold, the touch is determined to be abnormal; when the wireless signal strength is lower than the set threshold and the number of connection retries exceeds the limit, the communication is determined to be abnormal.

[0044] The learning and decision unit 52 establishes an anomaly recognition model based on historical test samples to identify boundary state anomalies and multi-factor coupled anomalies. For example, some tablet computers only experience short-term lag when high-load computing and wireless communication are performed simultaneously. Traditional single-item rules are difficult to accurately identify such anomalies, but the learning and decision unit 52 can identify such anomaly patterns through sample training.

[0045] The fault location submodule 53 classifies the exception type based on the time sequence of the exception occurrence, the interface call chain, the log context, and the trend of resource usage changes, and determines whether it belongs to hardware exception, driver exception, system configuration exception, application exception, or environmental interference exception.

[0046] The environmental compensation module 6 is used to acquire network environment parameters, system load parameters, battery power parameters, and ambient temperature parameters during testing, and to normalize and correct the test data. For example, when the network environment fluctuates significantly, the environmental compensation module 6 will compensate for the wireless communication test results to avoid misjudging normal devices as unqualified due to external network fluctuations; when the battery power of the tablet under test is low, the environmental compensation module 6 will correct the power consumption test and performance test results.

[0047] The report traceability module 7 is used to generate a test report after the test is completed and to associate the test results with the unique identifier of the tablet computer under test. This module includes a result reporting unit 71, a version backtracking unit 72, and a trend analysis unit 73. The result reporting unit 71 uploads the test results to the server; the version backtracking unit 72 uses the unique identifier to look up the test script version, system version, and judgment threshold version; and the trend analysis unit 73 performs statistical analysis on the anomaly types and frequencies of devices in the same batch, model, or version to facilitate subsequent process optimization and software version iteration.

[0048] The self-updating module 8 is used to update the test template, fault feature library, judgment threshold, and anomaly identification model based on historical test results, re-inspection results, and manual review results. For example, when a batch of equipment frequently makes misjudgments during re-inspection, the self-updating module 8 can adjust relevant thresholds and model parameters based on the review results to improve the accuracy of subsequent automatic tests.

[0049] See Figures 1-3 As shown, based on the above system, this embodiment provides an automatic testing method for a tablet computer, including the following steps: Step S1: Obtain basic information about the tablet computer under test.

[0050] The device access module establishes a communication connection with the tablet computer under test and reads the model information, system version information, and hardware configuration information.

[0051] Step S2: Generate a test task sequence.

[0052] The test management module matches the corresponding test template from the test template submodule based on the obtained device model information, system version information, and hardware configuration information, and generates a test task sequence in conjunction with the task orchestration submodule.

[0053] When generating a test task sequence, a dependency graph between test items can also be established. Based on the dependency graph, pre-test items, parallel test items, and mutually exclusive test items can be distinguished. The test order can be dynamically adjusted according to the current remaining power, system load, and interface availability to reduce resource conflicts and shorten the overall test time.

[0054] Step S3: Execute the preset test scenario.

[0055] The scenario-driven module executes preset test scenarios by calling the system interface, driver interface, or application interface of the tablet computer under test according to the test task sequence.

[0056] Preset test scenarios include, but are not limited to, display testing, touch testing, audio testing, camera testing, sensor testing, communication testing, storage testing, and power consumption testing.

[0057] In addition, it can perform anomaly injection test scenarios, such as injecting network outage events, low battery events, abnormal application exit events, storage space full events, permission restriction events, and high background usage events into the tablet under test, in order to test its stability and recovery capabilities under abnormal conditions.

[0058] Step S4: Collect test data.

[0059] During the test, the data acquisition module synchronously collects log data, status parameters, event response data, and performance data.

[0060] For example, in display tests, record the screen refresh rate and display driver logs; in communication tests, record the wireless signal strength, connection establishment delay, and number of retries; in exception injection tests, record the exception occurrence time, system recovery time, and error log information.

[0061] Step S5: Perform environmental compensation and result analysis.

[0062] The environmental compensation module normalizes and corrects the collected test data based on network environment parameters, system load parameters, battery power parameters, and ambient temperature parameters during the test.

[0063] The result determination module performs rule determination and learning determination on the corrected data.

[0064] In one example, a normalized score is calculated for each individual test result, and the overall judgment value is calculated using the following formula:

[0065] in, This is a comprehensive judgment value. For the first The normalized score of the test item For the first The weighting coefficients of the test items, For the first The environmental compensation coefficient corresponding to the test item, and it satisfies... ; when If the value is greater than or equal to the first preset threshold, the tablet computer under test is deemed qualified. when If the value is less than the second preset threshold, the tablet computer under test is determined to be unqualified. when When the value is between the first preset threshold and the second preset threshold, the tablet computer under test is determined to be a re-inspection object.

[0066] Step S6: Output the test results and generate a test report.

[0067] The result determination module outputs a pass / fail or re-inspection result; the report traceability module associates the test results with the unique identifier of the tablet computer under test and generates a test report which is uploaded to the server for subsequent quality analysis and problem tracking.

[0068] Step S7: Perform self-learning optimization.

[0069] The system regularly collects automatic test results, re-inspection results, and manual review results to identify misjudged samples, missed samples, and boundary samples. Based on these samples, it adjusts the test weight coefficients, judgment thresholds, environmental compensation coefficients, and anomaly identification model parameters, thereby continuously improving the system's automatic test accuracy and robustness.

[0070] To further illustrate the technical effects of the present invention, an example of a combined test is given below.

[0071] In this example, the scenario-driven module first triggers a high-load computing test to keep the processor and graphics processing unit of the tablet under test running continuously. During the execution of the high-load computing test, a wireless communication test and an audio playback test are triggered simultaneously, and the data acquisition module collects CPU utilization, memory utilization, battery temperature, wireless signal strength, audio output status, and system logs.

[0072] If audio stuttering, wireless disconnection, or increased system interface response delay occurs during the combined test, the result determination module will analyze and locate the fault by combining log context, resource usage change trends, and the timing of the anomaly.

[0073] For example, when the logs show that the audio service thread is blocked and the wireless communication reconnection operation occurs at the same time, and the system resource usage increases significantly in the short period before the anomaly, the anomaly can be classified as a system scheduling anomaly under multi-task concurrency conditions.

[0074] Through this type of combined testing, the present invention can effectively identify coupled faults that are difficult to detect by traditional single-item testing, thereby improving the authenticity and effectiveness of the testing system.

[0075] The above embodiments merely illustrate several implementation methods of the present invention, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the present invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention. Therefore, the protection scope of this patent should be determined by the appended claims.

Claims

1. An automatic testing system for tablet computers, characterized in that, It includes a test management module, a device access module, a scenario-driven module, a data acquisition module, a result judgment module, and a report traceability module; The device access module is used to establish a communication connection with the tablet computer under test and to obtain the model identifier, hardware configuration information, system version information and interface status information of the tablet computer under test. The test management module is used to generate a set of test tasks and a test execution order corresponding to the tablet computer under test based on the model identifier, hardware configuration information and system version information; The scenario driving module is used to call the system interface, driver interface or application layer interface of the tablet computer under test to trigger at least one test scenario among display test, touch test, audio test, camera test, sensor test, communication test, storage test and power consumption test; The data acquisition module is used to collect the operating logs, status parameters, event response data and performance data of the tablet computer under test during the testing process; The result determination module is used to analyze the execution results of each test scenario based on the data collected by the data acquisition module, and output the determination results of qualified, unqualified or re-inspection. The report traceability module is used to generate test reports and associate the test results with the unique identifier of the tablet computer under test.

2. The automatic testing system for tablet computers according to claim 1, characterized in that, The test management module includes a test template submodule, a task orchestration submodule, and a version adaptation submodule. The test template submodule is used to create configurable test templates according to different models; The task orchestration submodule is used to orchestrate multiple test items sequentially, in parallel, or under conditional triggering based on preset dependencies. The version adaptation submodule is used to dynamically adapt the test script, test parameters, and judgment thresholds according to the system version or firmware version of the tablet computer under test.

3. The automatic testing system for tablet computers according to claim 1, characterized in that, The scene-driven module includes an interface call unit, an event injection unit, and a state switching unit; The interface calling unit is used to call the underlying driver interface or upper-layer application interface of the tablet computer under test to execute preset test instructions; The event injection unit is used to inject simulated touch events, key events, rotation events, network events, or abnormal interruption events into the tablet computer under test. The state switching unit is used to control the tablet computer under test to switch between at least two modes among normal mode, power saving mode, high performance mode, airplane mode and sleep wake-up mode, so as to test the functional stability under different working states.

4. The automatic testing system for tablet computers according to claim 1, characterized in that, The data acquisition module includes a log acquisition unit, a parameter acquisition unit, and a time-series monitoring unit; The log collection unit is used to collect system logs, driver logs, and application logs; The parameter acquisition unit is used to acquire at least one of the following operating parameters: CPU utilization, memory utilization, battery current, battery temperature, wireless signal strength, frame rate, and storage read / write speed. The timing monitoring unit is used to record the test command issuance time, event response time, test completion time, and anomaly occurrence time to generate test timing data.

5. The automatic testing system for tablet computers according to claim 1, characterized in that, The scenario-driven module is configured to execute a combined test task, which includes at least one of the following: simultaneously triggering a touch test during the execution of a display test, simultaneously triggering an audio playback test during the execution of a wireless communication test, or simultaneously triggering a temperature rise monitoring test during the execution of a high-load computing test, in order to identify coupled faults that are difficult to detect in a single test.

6. The automatic testing system for tablet computers according to claim 1, characterized in that, The result determination module also includes a fault location submodule, which is used to output the fault category based on the time sequence of the anomaly occurrence, the interface call chain, the log context, and the trend of resource usage changes. The fault category includes at least hardware anomaly, driver anomaly, system configuration anomaly, application anomaly, and environmental interference anomaly.

7. The automatic testing system for tablet computers according to claim 1, characterized in that, The report traceability module includes a result reporting unit, a version traceability unit, and a trend analysis unit; The result reporting unit is used to upload the test results to the server; The version backtracking unit is used to look up the corresponding test script version, system version and judgment threshold version based on the unique identifier of the tablet computer under test. The trend analysis unit is used to perform statistical analysis on the anomaly types and frequencies of devices in the same batch, model, or version.

8. A testing method based on the automatic testing system for tablet computers according to any one of claims 1 to 7, characterized in that, Includes the following steps: Obtain the device model, system version, and hardware configuration information of the tablet computer under test; Based on the device model information, system version information, and hardware configuration information, a corresponding test template is matched, and a test task sequence is generated; Call the system interface, driver interface, or application interface of the tablet computer under test to execute a preset test scenario; Log data, status parameters, event response data, and performance data are collected during the execution of the preset test scenario; Analyze the collected data and output the test results; The test results are associated with the unique identifier of the tablet computer under test, and a test report is generated.

9. The test method according to claim 8, characterized in that, The steps for generating the test task sequence include: Establish a dependency graph between the various test items; Based on the dependency graph, determine the pre-test items, parallel test items, and mutually exclusive test items; The test order is dynamically adjusted based on the remaining battery power of the tablet computer under test, the current system load, and the availability of interfaces, in order to shorten the overall test time and reduce resource conflicts.

10. The test method according to claim 8, characterized in that, In the step of analyzing the collected data, a normalized score is calculated for each individual test result, and a comprehensive judgment value is calculated according to the following formula: ； in, This is a comprehensive judgment value. For the first The normalized score of the test item, For the first The weighting coefficients of the test items. For the first The environmental compensation coefficient corresponding to the test item, and satisfies... ; when If the value is greater than or equal to the first preset threshold, the tablet computer under test is determined to be qualified. when If the value is less than the second preset threshold, the tablet computer under test is determined to be unqualified; when When the value is between the first preset threshold and the second preset threshold, the tablet computer under test is determined to be a re-inspection object.

Images