A multi-model remote controller automatic test method and system

Abstract

The application provides a multi-model remote controller automatic test method and system, and relates to the technical field of intelligent television remote controller testing, and comprises obtaining a logical key library, a pressing coordinate mapping corresponding to a to-be-tested remote controller model, and response judgment data corresponding to a television software version; the logical key library comprises a logical key identifier, an expected code value associated with the logical key identifier, and a test sequence; based on a default key layout or a layout adjustment operation of the to-be-tested remote controller model, a current key layout mapping is generated; the application hierarchically manages universal key logic, model physical coordinates, and software version response data. When a new remote controller model is added, mainly coordinate mapping is supplemented; when a new television software version is added, mainly response data is supplemented; keys with the same function can share the same logical key library, thereby significantly reducing script maintenance cost and avoiding mismatching between coordinates, code values, and response pictures.

Description

Technical Field

[0001] This invention relates to the field of smart TV remote control testing technology, and in particular to an automated testing method and system for multiple remote control models. Background Technology

[0002] Remote control functionality verification typically requires confirming two interrelated results simultaneously: first, whether the remote control issued the correct key code value; and second, whether the television terminal responded correctly to that key code value. Only when both are true can the button be considered to be functioning correctly throughout the entire process.

[0003] Existing manual testing methods require testers to press each button individually and observe changes in the TV screen, resulting in low testing efficiency and difficulty in ensuring coverage and consistency when dealing with a large number of remote control models and button combinations. Some automated testing solutions bind mechanical press coordinates, remote control models, button codes, and test scripts together. These solutions often require copying and modifying numerous test scripts after remote control model changes, button replacements, or TV software upgrades, leading to high maintenance costs and a tendency for mismatches between press coordinates, button codes, and expected response images, resulting in misjudgments. For example, if the layout of individual buttons on a remote control model is adjusted, and the coordinates in the script are not updated synchronously, the pressing device will press the wrong physical location. Similarly, if a TV software upgrade changes the interface screenshot, and the expected response image is not updated synchronously, the image comparison will fail. Furthermore, simply listening to button codes is insufficient to prove that the TV terminal has responded correctly, as correct codes do not guarantee that the terminal interface or state has changed as expected; and simply comparing the TV screen is insufficient to prove that the remote control's output codes are correct, as the same interface change could be caused by other reasons. Therefore, a single verification method is insufficient in terms of accuracy. In summary, there is a need for an automated testing solution for multiple remote control models that can dynamically parse press coordinates based on the current layout, decouple test logic from physical coordinates and software version response data, and jointly execute code value verification and terminal response verification. This would reduce maintenance costs, adapt to layout changes, and improve the reliability of test results. Summary of the Invention

[0004] To address the problems in existing technologies, such as the coupling of coordinates and test logic for multiple remote controller models, mismatch of response data between different software versions, and insufficient accuracy of a single verification method, this invention provides an automated testing method and system for multiple remote controller models.

[0005] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: An automated testing method for multiple remote control models includes: Acquire the logic button library, the press coordinate mapping corresponding to the model of the remote control under test, and the response judgment data corresponding to the TV software version. The logic button library includes logic button identifiers, expected code values ​​associated with the logic button identifiers, and test sequences. Based on the default button layout or layout adjustment operation of the remote control model under test, generate the current button layout mapping. The current button layout mapping records the correspondence between logical button identifiers and press coordinates. For the logic keys under test, the pressing coordinates of each logic key in the test sequence are parsed according to the current key layout mapping. The three-axis pressing device is controlled to execute the test sequence based on the pressed coordinates obtained from the analysis, and the button events output by the TV terminal are acquired. Match the key events with the expected code values ​​associated with the logical keys in the test sequence to obtain the code value matching results; Based on the response judgment data corresponding to the TV software version, the TV terminal response after the test sequence is executed is judged, and the response judgment result is obtained. When both the code value matching result and the response judgment result are passed, the logic key under test is determined to have passed the test.

[0006] Preferably, the pressing coordinate mapping corresponding to the remote control model under test includes the X-axis offset, Y-axis offset and Z-axis pressing depth of each logical button relative to the fixed reference point of the remote control; Different remote control models have their own press coordinate mappings, and buttons with the same function share the same logical button identifier in the logical button library.

[0007] Preferably, the layout adjustment operation includes at least one of the following: Swap the button information between the two layout positions; Replace existing buttons with available buttons; Add available buttons to the blank layout space; Remove the button from the layout.

[0008] Preferably, each layout position in the current button layout mapping is associated with at least a logical button identifier, expected code value, response determination type, version response data, and press coordinates; Based on the current key layout mapping, the press coordinates of each logical key in the test sequence of the logical keys under test are analyzed, including: For each logical key in the test sequence, the current key layout mapping is queried in real time to obtain the pressing coordinates of the logical key under the current layout.

[0009] Preferably, the desired code value includes a desired infrared code value and a desired Bluetooth code value; Match key events with expected code values, including: According to the preset monitoring mode, the button events are matched with the expected infrared code value in infrared monitoring mode, and the button events are matched with the expected Bluetooth code value in Bluetooth monitoring mode.

[0010] Preferably, the response determination data includes standard response images and a similarity threshold; For image-responsive key presses, the TV terminal's response after the test sequence is executed is judged, including: After the test sequence is executed, a screenshot of the TV terminal is obtained. The similarity of the TV terminal screenshot with the standard response image corresponding to the TV software version is compared. When the similarity is not lower than the similarity threshold, the TV terminal response is deemed to have passed.

[0011] Preferably, for status response type buttons, the television terminal response after the test sequence is executed is judged, including: Read the TV terminal status before and after the test sequence is executed, and determine whether the TV terminal response passes according to the preset status change rules; Status response buttons include at least one of the following: volume up button, volume down button, and mute button.

[0012] Preferably, for the power button, the response of the TV terminal after the test sequence is executed is determined, including: After the code value matching is completed, the power status of the TV terminal before and after the power button is pressed is read, and it is determined whether the power status of the TV terminal has changed. The TV terminal screenshot is not used as the basis for determining the response of the power button. The power button is executed at the end of the batch test sequence.

[0013] Preferred options also include: Multiple numeric keys are grouped into numeric key groups, a unified test sequence is executed on the numeric key groups, and the expected response data corresponding to the numeric key groups is used to determine the response, while retaining the code value matching results of each numeric key in the numeric key group. Additionally, when the test of the logic button under test fails, the system saves the button name, remote control model, TV software version, press coordinates, expected code value, actual code value, TV terminal screenshot, standard response image path, and reason for failure for the logic button under test, and performs selective retesting based on the set of failed buttons.

[0014] An automated testing system for multiple remote control models includes: The model configuration module is used to provide the press coordinate mapping corresponding to the model of the remote control under test. The press coordinate mapping includes the X-axis offset, Y-axis offset and Z-axis press depth of each logical button relative to the fixed reference point of the remote control. The logic key library module provides logic key identifiers, expected code values ​​associated with the logic key identifiers, and test sequences. The version response module is used to provide response determination data corresponding to the TV software version; The current layout mapping module is used to generate the current button layout mapping based on the default button layout or layout adjustment operation of the remote control model under test. The current button layout mapping records the correspondence between logical button identifiers and press coordinates. The three-axis pressing control module is used to analyze the pressing coordinates of each logical key in the test sequence according to the current key layout mapping for the logic key under test, and control the three-axis pressing device to execute the test sequence according to the analyzed pressing coordinates. The code value monitoring module is used to acquire the key events output by the TV terminal and match the key events with the expected code values ​​to obtain the code value matching results; The response determination module is used to determine the response of the TV terminal based on the response determination data to obtain the response determination result. Specifically, it performs screenshot similarity comparison for image response buttons, reads the terminal status for status response buttons, and determines the power status switching for the power button. The reporting module is used to generate a test pass conclusion when both the code value matching result and the response judgment result are pass, and to save evidence of failure when the test fails.

[0015] The beneficial effects of this invention are: 1. This invention manages general button logic, model physical coordinates, and software version response data in a hierarchical manner. When a new remote control model is added, the main focus is on supplementing coordinate mapping; when a new TV software version is added, the main focus is on supplementing response data. Buttons with the same function can share the same logical button library, thereby significantly reducing script maintenance costs and avoiding mismatches between coordinates, code values, and response images.

[0016] 2. This invention uses the current button layout to map and query the press coordinates in real time. Even if button replacements or layout adjustments occur before testing, the test sequence can still execute correctly based on the updated current layout, without needing to rewrite the script for each layout change.

[0017] 3. This invention derives test conclusions through a dual determination of code value matching and terminal response. Code value matching is used to confirm that the code value output by the remote control and received by the TV terminal is correct, while terminal response determination is used to confirm that the TV terminal has indeed produced the expected change. The combination of the two improves the reliability of the test conclusions.

[0018] 4. When a test fails, this invention saves evidence of failure, such as button name, model, software version, press coordinates, expected code value, actual code value, terminal screenshot, standard image path, and reason for failure. It can also perform selective retesting based on the set of failed buttons, thereby improving the efficiency of problem tracing and retesting. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating the automated testing method for multiple remote controller models provided in an embodiment of the present invention. Detailed Implementation

[0020] 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.

[0021] 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.

[0022] Specific embodiments of the present invention are described below with reference to the accompanying drawings.

[0023] Example 1 Please see Figure 1 This embodiment provides an automated testing method for multiple remote control models. The testing steps are as follows: S101, The system obtains the logic key library, the press coordinate mapping corresponding to the model of the remote control under test, and the response judgment data corresponding to the current TV software version.

[0024] To further explain, the logic key library, model press coordinate mapping, and software version response determination data are composed as follows: The logical buttons in the logical button library can be, for example, KEY_HOME (home button), KEY_INPUT (input source button), and KEY_VOLUME_UP (volume up button). Each logical button is associated with a desired infrared code value, a desired Bluetooth code value, and a test sequence.

[0025] For example, the logic key library can be recorded using the structure shown in Table 1.

[0026] Table 1: Logical Key Library The expected infrared code value and the expected Bluetooth code value are used for subsequent code value matching; the test sequence is used to specify the pressing actions that need to be performed sequentially to verify the logical button.

[0027] The model-specific press coordinates use a pre-selected remote control reference button as a fixed reference point, recording the X-axis plane offset, Y-axis plane offset, and Z-axis press depth of each physical button relative to this reference button. For example, if a corner button is selected as the reference button, the coordinate mapping of this model can be recorded as the horizontal and vertical offset of each logical button relative to the reference button in the horizontal plane, as well as the vertical depth required for the press head to be pressed down to effectively trigger the button.

[0028] Different models can have different coordinate mappings, but buttons with the same function can share the same logical button identifier in the logical button library. For example, both Model A and Model B have a home button, but their physical positions and pressing depths may be different. Therefore, they are registered with their own three-axis coordinates in their respective coordinate mappings, but they both correspond to the same logical button identifier KEY_HOME in the logical button library.

[0029] The TV software version response data corresponds to the specific TV software version and records the data required for response determination, including image response data, status response rules, or thresholds.

[0030] For example, the image response data can be a standard image directory organized by software version, containing standard response images for each image response type button under that version; the state response rules can be the changes that the volume, mute, and other states should meet before and after being pressed; the threshold can be the similarity threshold used for image similarity comparison. When the TV software version is upgraded, only the corresponding standard images and rules need to be added to the new version, without modifying the logical button library and coordinate mapping.

[0031] S102. The system loads the default layout of the model under test and generates the current button layout mapping. If the button layout of the actual remote control is inconsistent with the default layout, the current button layout mapping is updated through layout adjustment operations such as swapping, replacing, adding or removing to make it consistent with the actual remote control.

[0032] To further explain, the system allows updating the current button layout mapping based on the actual remote control layout, i.e., performing a layout adjustment operation. The layout adjustment operation can include at least one of the following: First, swap the button information in two positions, that is, exchange the button information registered in two layout positions; second, replace the existing button in a position with a usable button, that is, replace the original button in a layout position with a usable button; third, add a button to an empty position, that is, add a usable button to a layout position that originally had no button registered; fourth, remove a button, that is, remove the button registered in a layout position.

[0033] In the updated current key layout mapping, each layout position is associated with at least a logical key identifier, expected code value, response determination type, version response data, and press coordinates. In other words, the current key layout mapping not only records the correspondence between logical key identifiers and press coordinates, but also carries the expected code value required for subsequent code value matching, as well as the response determination type and version response data required for subsequent response determination, along with the layout position.

[0034] For example, when the volume up and volume down buttons of a certain model's actual remote control are swapped, the tester can perform an operation to swap the button information of the two positions in the current button layout mapping; or, when a button in a certain position is replaced with a button for another function, the tester can perform an operation to replace the existing button with the available button.

[0035] After the above adjustments, the current button layout mapping reflects the actual button arrangement of the remote control. Since the subsequent analysis of press coordinates is based on the current button layout mapping, even if button replacements or layout adjustments occur before testing, the test sequence can still be executed correctly according to the updated current layout without having to rewrite the coordinates in the test script one by one.

[0036] S103. The system determines the logic keys to be tested in this round and places the power key at the end of the batch test sequence; for numeric keys, they can be grouped into numeric key groups for unified processing.

[0037] S104. For each logic key to be tested, the system parses its test sequence and queries the current key layout mapping for each logic key in the sequence in real time to obtain the pressing coordinates; then controls the three-axis pressing device to move to a safe height first, and then performs planar movement, pressing trigger and lifting, to complete the pressing of each key in the sequence in sequence.

[0038] To further explain, for the input source button KEY_INPUT, its test sequence can include the home button KEY_HOME and the input source button KEY_INPUT. That is, first press the home button to make the TV terminal enter the known interface, and then press the input source button to trigger the input source related interface.

[0039] For each logical key in the test sequence, the system queries the current key layout mapping in real time to obtain the corresponding press coordinates of that logical key under the current layout. Since the coordinates are derived from the current key layout mapping rather than a fixed script, any layout adjustments will be reflected in the analysis results immediately.

[0040] After obtaining the press coordinates, the system controls the three-axis pressing device to execute the pressing action. For example, for each logical key in the sequence, the pressing head first moves to a safe height, then moves along the X and Y axes from that safe height to above the target key, subsequently pressing down along the Z axis to the corresponding pressing depth to trigger the key, and finally lifting and returning to the safe height to move to the next key in the sequence. This method of moving to a safe height first and then moving along the plane avoids the pressing head scraping against other keys or the remote control surface during the plane movement.

[0041] S105. Before or during the pressing, the system listens to the key events output by the TV terminal and matches the actual code value with the expected code value according to the preset listening mode to obtain the code value matching result.

[0042] To further clarify, the expected code value includes the expected infrared code value and the expected Bluetooth code value. The system performs code value matching on the button events output by the TV terminal according to a preset monitoring mode: In infrared monitoring mode, the system matches the actual infrared code value corresponding to the key event with the expected infrared code value of the logical key. In Bluetooth monitoring mode, the system matches the actual Bluetooth code value corresponding to the button event with the expected Bluetooth code value of the logical button. When the actual code value matches the expected code value, the logical button is considered to have successfully matched the code value.

[0043] S106. Based on the response judgment data of the current TV software version, the system performs screenshot similarity comparison for image response buttons, reads the terminal status before and after pressing for status response buttons, and determines the power status switching for power buttons, thus obtaining the response judgment result.

[0044] To further explain, for image-based response buttons, the system retrieves the expected response image from the standard image directory corresponding to the current TV software version. After the test sequence is completed, the system acquires a screenshot of the TV terminal and compares this screenshot with the expected response image for similarity. If the similarity is not lower than a preset similarity threshold, the TV terminal response is considered successful. Because the expected response images are organized by software version, when the TV software version upgrades and the interface changes, only the corresponding standard response image needs to be provided for the new version to continue the image comparison, without mismatch due to interface changes.

[0045] For status-responsive buttons such as volume up, volume down, and mute, the system reads the TV terminal state before and after the test sequence is executed and makes a judgment based on preset state change rules. For example, for the volume up button, the system reads the volume values ​​before and after pressing; if the volume value after pressing increases according to the rules, the response is considered successful. For the mute button, the system reads the mute state before and after pressing; if the mute state switches according to the rules, the response is considered successful. For status-responsive buttons, the system can use changes in the terminal state as the basis for response judgment without relying on screenshots.

[0046] For the power button, after completing the code value verification, the system reads the power state of the TV terminal before and after the power button is pressed, and determines whether the power state of the TV terminal has changed. Since pressing the power button causes the TV terminal to turn on and off, screenshots are not suitable as a basis for response judgment in this case. Therefore, for the power button, the response judgment is based on whether the power state has changed, not on screenshots. In addition, the system schedules the power button test at the end of the batch test sequence to avoid the power on / off triggered by the power button affecting the testing of other buttons in the batch test.

[0047] It should be noted that multiple numeric keys can be grouped into numeric key groups. The system performs a unified test sequence on the numeric key groups and uses the expected response data corresponding to the numeric key groups for response determination. At the same time, the system retains the individual code value matching result of each numeric key in the numeric key group. In other words, at the response determination level, the numeric key group is used as a whole for determination using unified expected response data, thereby simplifying configuration; while at the code value matching level, the matching results of each numeric key are still retained individually, thereby ensuring the individual confirmation of the correctness of the code value of each numeric key.

[0048] S107. When both the code value matching result and the response judgment result are passed, the system determines that the logic key under test has passed the test; otherwise, it determines that the test has failed and saves failure evidence such as key name, model, software version, press coordinates, expected code value, actual code value, terminal screenshot, standard diagram path and failure reason.

[0049] S108. After all the logic keys under test have been processed, the system generates test conclusions through the report module; if there are failed keys, the system can perform selective retesting based on the set of failed keys.

[0050] Example 2 This embodiment provides an automated testing system for multiple remote controller models. The system includes a model configuration module, a logic button library module, a version response module, a current layout mapping module, a three-axis press control module, a code value monitoring module, a response judgment module, and a reporting module.

[0051] The model configuration module is used to provide the press coordinate mapping corresponding to the model of the remote control under test. The press coordinate mapping includes the X-axis offset, Y-axis offset and Z-axis press depth of each logical button relative to the fixed reference point of the remote control. The logic key library module provides logic key identifiers, expected code values ​​associated with the logic key identifiers, and test sequences. The version response module is used to provide response determination data corresponding to the TV software version; The current layout mapping module is used to generate the current button layout mapping based on the default button layout or layout adjustment operation of the remote control model under test. The current button layout mapping records the correspondence between logical button identifiers and press coordinates. The three-axis pressing control module is used to analyze the pressing coordinates of each logical key in the test sequence according to the current key layout mapping for the logic key under test, and control the three-axis pressing device to execute the test sequence according to the analyzed pressing coordinates. The code value monitoring module is used to acquire the key events output by the TV terminal and match the key events with the expected code values ​​to obtain the code value matching results; The response determination module is used to determine the response of the TV terminal based on the response determination data to obtain the response determination result. Specifically, it performs screenshot similarity comparison for image response buttons, reads the terminal status for status response buttons, and determines the power status switching for the power button. The reporting module is used to generate a test pass conclusion when both the code value matching result and the response judgment result are pass, and to save evidence of failure when the test fails.

[0052] The three-axis pressing control module is connected to the three-axis pressing device and is used to drive the mechanical pressing head to press the remote control under test, which is fixed on the fixture. The code value monitoring module and the response judgment module are connected to the TV terminal under test and are used to obtain the button events output by the TV terminal and the screen, status or power information of the TV terminal.

[0053] In terms of data organization, this embodiment divides the data on which the test depends into three independent layers: The first layer is the general button logic layer, which is carried by the logic button library. It records the logic button identifier, the expected infrared code value and expected Bluetooth code value associated with that logic button, and the test sequence. The logic button library is independent of the physical form of a specific remote control model; buttons with the same function can reuse the same logic button identifier.

[0054] The second layer is the model physical coordinate layer, which is carried by the model-specific press coordinate mapping. It records the three-axis press coordinates of each logical button relative to the fixed reference point of the remote control for that model. Different models have their own coordinate mappings.

[0055] The third layer is the software version response layer, which is carried by the TV software version response data and records response judgment data such as standard response images, status change rules or thresholds corresponding to the current TV software version.

[0056] Because the three layers are independent of each other, when adding a new remote control model, the main task is to supplement the press coordinate mapping for that model; when adding a new TV software version, the main task is to supplement the response data for that version; and the logic button library can be reused across multiple models and versions. Therefore, the testing logic is no longer fixedly bound to physical coordinates and version response data, avoiding the need to copy and modify a large number of scripts when changing models or upgrading versions, and also avoiding mismatches between coordinates, code values, and response images.

[0057] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0058] The embodiments described above are merely illustrative of several implementations of the present invention, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. 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 invention patent should be determined by the appended claims.

Claims

1. An automated testing method for multiple remote control models, characterized in that, include: Acquire the logic button library, the press coordinate mapping corresponding to the model of the remote control under test, and the response judgment data corresponding to the TV software version. The logic button library includes logic button identifiers, expected code values ​​associated with the logic button identifiers, and test sequences. Based on the default button layout or layout adjustment operation of the remote control model under test, generate the current button layout mapping. The current button layout mapping records the correspondence between logical button identifiers and press coordinates. For the logic keys under test, the pressing coordinates of each logic key in the test sequence are parsed according to the current key layout mapping. The three-axis pressing device is controlled to execute the test sequence based on the pressed coordinates obtained from the analysis, and the button events output by the TV terminal are acquired. Match the key events with the expected code values ​​associated with the logical keys in the test sequence to obtain the code value matching results; Based on the response judgment data corresponding to the TV software version, the TV terminal response after the test sequence is executed is judged, and the response judgment result is obtained. When both the code value matching result and the response judgment result are passed, the logic key under test is determined to have passed the test.

2. The method according to claim 1, characterized in that, The press coordinate mapping corresponding to the remote control model under test includes the X-axis offset, Y-axis offset and Z-axis press depth of each logical button relative to the fixed reference point of the remote control; Different remote control models have their own press coordinate mappings, and buttons with the same function share the same logical button identifier in the logical button library.

3. The method according to claim 1, characterized in that, Layout adjustment operations include at least one of the following: Swap the button information between the two layout positions; Replace existing buttons with available buttons; Add available buttons to the blank layout space; Remove the button from the layout.

4. The method according to claim 1, characterized in that, Each layout position in the current key layout mapping is associated with at least a logical key identifier, expected code value, response judgment type, version response data, and press coordinates; Based on the current key layout mapping, the press coordinates of each logical key in the test sequence of the logical keys under test are analyzed, including: For each logical key in the test sequence, the current key layout mapping is queried in real time to obtain the pressing coordinates of the logical key under the current layout.

5. The method according to claim 1, characterized in that, The expected code value includes the expected infrared code value and the expected Bluetooth code value; Match key events with expected code values, including: According to the preset monitoring mode, the button events are matched with the expected infrared code value in infrared monitoring mode, and the button events are matched with the expected Bluetooth code value in Bluetooth monitoring mode.

6. The method according to claim 1, characterized in that, The response determination data includes standard response images and a similarity threshold; For image-responsive key presses, the TV terminal's response after the test sequence is executed is judged, including: After the test sequence is executed, a screenshot of the TV terminal is obtained. The similarity of the TV terminal screenshot with the standard response image corresponding to the TV software version is compared. When the similarity is not lower than the similarity threshold, the TV terminal response is deemed to have passed.

7. The method according to claim 1, characterized in that, For status response type buttons, the response of the TV terminal after the test sequence is executed is judged, including: Read the TV terminal status before and after the test sequence is executed, and determine whether the TV terminal response passes according to the preset status change rules; Status response buttons include at least one of the following: volume up button, volume down button, and mute button.

8. The method according to claim 1, characterized in that, For the power button, the response of the TV terminal after the test sequence is executed is judged, including: After the code value matching is completed, the power status of the TV terminal before and after the power button is pressed is read, and it is determined whether the power status of the TV terminal has changed. The TV terminal screenshot is not used as the basis for determining the response of the power button. The power button is executed at the end of the batch test sequence.

9. The method according to claim 1, characterized in that, Also includes: Multiple numeric keys are grouped into numeric key groups, a unified test sequence is executed on the numeric key groups, and the expected response data corresponding to the numeric key groups is used to determine the response, while retaining the code value matching results of each numeric key in the numeric key group. Additionally, when the test of the logic button under test fails, the system saves the button name, remote control model, TV software version, press coordinates, expected code value, actual code value, TV terminal screenshot, standard response image path, and reason for failure for the logic button under test, and performs selective retesting based on the set of failed buttons.

10. An automated testing system for multiple remote controller models, characterized in that, include: The model configuration module is used to provide the press coordinate mapping corresponding to the model of the remote control under test. The press coordinate mapping includes the X-axis offset, Y-axis offset and Z-axis press depth of each logical button relative to the fixed reference point of the remote control. The logic key library module provides logic key identifiers, expected code values ​​associated with the logic key identifiers, and test sequences. The version response module is used to provide response determination data corresponding to the TV software version; The current layout mapping module is used to generate the current button layout mapping based on the default button layout or layout adjustment operation of the remote control model under test. The current button layout mapping records the correspondence between logical button identifiers and press coordinates. The three-axis pressing control module is used to analyze the pressing coordinates of each logical key in the test sequence according to the current key layout mapping for the logic key under test, and control the three-axis pressing device to execute the test sequence according to the analyzed pressing coordinates. The code value monitoring module is used to acquire the key events output by the TV terminal and match the key events with the expected code values ​​to obtain the code value matching results; The response determination module is used to determine the response of the TV terminal based on the response determination data to obtain the response determination result. Specifically, it performs screenshot similarity comparison for image response buttons, reads the terminal status for status response buttons, and determines the power status switching for the power button. The reporting module is used to generate a test pass conclusion when both the code value matching result and the response judgment result are pass, and to save evidence of failure when the test fails.

Images