Human-machine interaction automatic testing method for HMI (Human Machine Interface) software
By receiving the operation data input by users in real-time in the human-computer interactive interface software automation test, the initial operation chain and operation results covering the user's operating habits and timing are generated, and the problem of inability to fully simulate user operations and timing laws in the prior art is solved, achieving more accurate and comprehensive test coverage.
Patent Information
- Application Number
- CN202510216483.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-26
- Publication Date
- 2025-06-27
AI Technical Summary
In the automated testing of human-computer interactive interface software, the prior art cannot fully simulate the user's operations and corresponding operation results, and the test results have certain errors in the judgment of the test results, and the operation chain and timing rules cannot be fully covered.
The automated testing software receives the operation data input by the user in real time, records and stores the input sequence and input time of the operation data, and generates an initial operation chain and operation results covering the user's operating habits and timing. Use enumeration to derive new operation chains and operation results, configure parameters to adjust the operation chains and operation results, and perform corresponding operations on the human-computer interactive interface to generate actual operation results, and determine whether the operation is successfully executed.
In the interface human-computer interaction automation test, the operation habits and timing rules of real users are fully simulated, covering most real test cases, improving the accuracy and coverage of the test, and accurately identifying the test results through background interaction information monitoring.
Smart Images
Figure CN120216358A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of automated testing of human-computer interaction interface software, and particularly relates to a method for automated human-computer interaction testing of HMI software. Background Art
[0002] An important part of the testing process for human-computer interaction interface software is to conduct human-computer interaction testing, that is, to perform user operations on the interface to detect whether the established operation goals can be achieved, such as whether content such as screen jumps and state changes meets the established requirements. At the same time, this kind of testing can also detect whether various operation chains will affect the software itself and cause unexpected problems. Finally, it can also be jointly tested with background processing programs, etc., and the normality of the background program can be judged through the results. Interface testing usually requires users to operate on the software and optimize it based on the feedback of user operations. However, the time cost of this kind of testing for users is relatively high, and at the same time, the testing cannot fully cover all operations. Therefore, automated interface testing tools provide a low-cost and fast testing method.
[0003] An automated interface testing method is disclosed in the prior art. This existing automated testing method generates operation chains according to interface design principles and generates test standard cases through the results of the operation chains. According to these standard test cases, relevant test programs are automatically executed, and the test results are judged by means of machine vision, etc. If there are differences from the standard result screen, it indicates that the purpose of discovering problems has been achieved in the testing.
[0004] Although the existing technology has great advantages in the automation of test case execution and discrimination, there are also some defects. The main defects include the following points: First, the generation of test cases determines the operation chains through the state parameters of the human-computer interaction interface (including interface design, screen jump rules, execution results). This method obtains all operation chains by enumeration. However, this method does not consider the operation timing (including not only sequence but also time difference) that the human-computer interaction interface facing interaction with the background program, and cannot fully simulate user operations and corresponding operation results. Second, the execution of test cases can completely judge whether the interface meets the requirements through methods such as machine vision, but the actual interaction information with the background has not been tested, and there is a certain error in the judgment of the test results, and this error will not be displayed in the current interface. Summary of the Invention
[0005] The present invention provides a method for automated human-computer interaction testing of HMI software, which can solve the technical problems in the prior art.
[0006] The present invention provides a method for automated human-computer interaction testing of HMI software, wherein the method includes:
[0007] After the automated testing software is started, it receives the operation data input by the user in real time. The operation data is input in sequence according to the interaction results with the background data of the automated testing software and the user's habits.
[0008] Record and store the input sequence and input time of the operation data in real time to obtain a test case set.
[0009] According to the input sequence and input time of the operation data in the test case set, supplement the status information involved in the screen development of the human-computer interaction software to obtain an initial operation chain and an initial operation result that cover the user's operation habits and consider the time sequence.
[0010] Derive new operation chains and new operation results by enumerating the preset operation processes in the operation process database, and use the new operation chains and new operation results to update the initial operation chain and the initial operation result to obtain an updated operation chain and an updated operation result.
[0011] Configure the updated operation chain and the updated operation result according to the preset configuration parameters to obtain a configured operation chain and a configured operation result.
[0012] Execute corresponding operations on the human-computer interaction interface according to the configured operation chain and generate corresponding actual operation results.
[0013] Judge whether the corresponding operation is executed successfully according to the actual operation result.
[0014] Mark the operation chain that fails to be executed as a failure case, and iteratively optimize the automated testing software by recording the failure cases.
[0015] Preferably, obtain status parameters according to the relevant data of the initial operation chain. The status parameters include the sequence information between operations and the time between each step of operation.
[0016] Preferably, the status information involved in the screen development of the human-computer interaction software includes the human-computer interaction interface, the screen switching and jumping rules, and the execution results.
[0017] Preferably, the configuration parameters include the time information and step information of the test cases.
[0018] Preferably, judging whether the corresponding operation is executed successfully according to the actual operation result includes:
[0019] Judge whether the corresponding operation is executed successfully through the human-computer interaction interface according to the actual operation result;
[0020] Judge whether the corresponding operation is executed successfully according to the information of the interaction between the human-computer interaction interface and the background according to the actual operation result.
[0021] Preferably, the information interacting with the background through the human-machine interaction interface determines whether the corresponding operation is successfully executed according to the actual operation result, including:
[0022] Compare the actual operation result with the preset operation result in the background. If the comparison results are consistent, it is determined that the corresponding operation is successfully executed; otherwise, it is determined that the corresponding operation is not successfully executed.
[0023] Through the above technical solutions, in the automated testing of the human-machine interface, several deficiencies of the traditional methods can be solved (for example, completely automated machine operations lose consideration of user habits and the timing rules of certain operations). By incorporating the teaching mode, the process of user operations is recorded, the user operation cases are accurately restored, and more test status information can be obtained at the same time. Through the supplement of these status information, more test cases can be obtained, and each test can be flexibly adjusted by configuring parameters to achieve a wider test coverage. Finally, by monitoring the information interacting with the background, the discrimination of changes in control instructions and status information is achieved, and the test results can be better determined. These methods make rich supplements to the automated testing of the human-machine interface and promote the improvement of the testing quality in this field. Description of the Drawings
[0024] The included drawings are used to provide a further understanding of the embodiments of the present invention, which form a part of the specification, are used to illustrate the embodiments of the present invention, and are used to explain the principles of the present invention together with the text description. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.
[0025] Figure 1 It shows a flowchart of an automated testing method for the human-machine interaction of an HMI software according to an embodiment of the present invention. Detailed Embodiments
[0026] It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, rather than all embodiments. The following description of at least one exemplary embodiment is actually only illustrative and in no way limits the present invention and its application or use. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.
[0027] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular forms are also intended to include the plural forms. In addition, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they specify the presence of features, steps, operations, devices, components, and / or combinations thereof.
[0028] Unless otherwise specifically stated, the relative arrangements of components and steps, numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present invention. At the same time, it should be understood that for the convenience of description, the dimensions of the various parts shown in the drawings are not drawn in actual proportional relationships. Technologies, methods, and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, the said technologies, methods, and devices should be regarded as part of the authorized specification. In all the examples shown and discussed herein, any specific values should be construed as merely exemplary and not as a limitation. Therefore, other examples of the exemplary embodiments may have different values. It should be noted that like reference numerals and letters denote like items in the following drawings, and thus, once an item is defined in one drawing, it does not require further discussion in subsequent drawings.
[0029] Figure 1 The flowchart of a method for automated testing of human-computer interaction of HMI software according to an embodiment of the present invention is shown.
[0030] As Figure 1 shown, an embodiment of the present invention provides a method for automated testing of human-computer interaction of HMI software, wherein the method includes:
[0031] After the automated testing software is started, it receives the operation data input by the user in real time, and the operation data is input in sequence according to the interaction results with the background data of the automated testing software and the user's habits.
[0032] Record and store the input order and input time of the operation data in real time to obtain a test case set.
[0033] According to the input order and input time of the operation data in the test case set, supplement the state information involved in the screen development of the human-computer interaction software to obtain an initial operation chain and an initial operation result that cover the user's operation habits and consider the time sequence.
[0034] Derive new operation chains and new operation results by enumerating the preset operation processes in the operation process database, and use the new operation chains and new operation results to update the initial operation chain and the initial operation result to obtain an updated operation chain and an updated operation result.
[0035] Configure the updated operation chain and the updated operation result according to preset configuration parameters to obtain the configured operation chain and the configured operation result;
[0036] Execute corresponding operations on the human-machine interaction interface according to the configured operation chain, and generate corresponding actual operation results;
[0037] That is, it is possible to perform actual operations according to relatively comprehensive operation use cases, and then judge the subsequent operation results.
[0038] Judge whether the corresponding operation is executed successfully according to the actual operation result;
[0039] Mark the operation chain that fails to be executed as a failure use case, and iteratively optimize the automated test software by recording the failure use cases.
[0040] That is, according to the discrimination result, it is possible to determine the failure use cases of the interface human-machine interaction. By recording these failure use cases, the purpose of iteratively optimizing the software can be achieved. At the same time, the interaction information in the background can also be used as a detection of the background program application.
[0041] Through the above technical solutions, in the automated test of the interface human-machine interaction, several deficiencies of the traditional method can be solved (such as completely automated machine operations losing consideration of user habits and the timing rules of certain operations). By incorporating the teaching mode, the operation process of the user is recorded, the operation use cases of the user are accurately restored, and more test status information can be obtained. Through the supplement of these status information, more test cases can be obtained, and each test can be flexibly adjusted by configuring parameters to obtain a wider test coverage. Finally, by monitoring the background interaction information, the discrimination of the changes in control instructions and status information can be achieved, and the test results can be better determined. These methods have made rich supplements to the automated test of the human-machine interaction interface and promoted the improvement of the test quality in this field.
[0042] That is, the present invention solves the generation of test cases, comprehensively simulates the operation habits of real users, and covers most real test cases.
[0043] According to an embodiment of the present invention, state parameters are obtained according to the relevant data of the initial operation chain. The state parameters include the sequence information between operations (that is, there is a sequence between operations or there is no sequence between operations) and the time between each step of operations.
[0044] That is, after the user operation teaching is completed, the test software learns the user's operation process and operation timing rules, and obtains several state parameters according to the detailed data of the operation chain, such as which operations have a sequence, the time between each step of operations (intermediate time difference), and other information.
[0045] The normal operation process and operation status information can be obtained according to the test case set. The operation chain and operation result obtained by the enumeration method correspond to the abnormal operation process (for example, the error process).
[0046] Among them, the updated operation chain and the updated operation result include the operation chain and operation result corresponding to the normal operation process and the operation chain and operation result corresponding to the abnormal operation process.
[0047] According to an embodiment of the present invention, the status information involved in the screen development of the human-computer interaction software includes the human-computer interaction interface, the screen switching and jumping rules, and the execution result.
[0048] According to an embodiment of the present invention, the configuration parameters include the time information and step information of the test case.
[0049] That is, more actual possible operation cases can be obtained by configuring the time information and step information of the test case, etc.
[0050] According to an embodiment of the present invention, judging whether the corresponding operation is successfully executed according to the actual operation result includes:
[0051] Judging whether the corresponding operation is successfully executed according to the actual operation result through the human-computer interaction interface;
[0052] Judging whether the corresponding operation is successfully executed according to the actual operation result through the information of the interaction between the human-computer interaction interface and the background.
[0053] For example, for information that cannot be displayed on the interface, such as whether the correct command is sent to the background and whether the status is updated normally, the judgment operation can be performed through the information of the interaction between the human-computer interaction interface and the background.
[0054] That is, the present invention not only judges the test execution result through the interface display, but also can judge through the change of the information of the interaction between the human-computer interaction interface and the background. This method can judge the operation result that will not be displayed on the interface after the operation, making the result discrimination more reliable.
[0055] According to an embodiment of the present invention, judging whether the corresponding operation is successfully executed according to the actual operation result through the information of the interaction between the human-computer interaction interface and the background includes:
[0056] Comparing the actual operation result with the preset operation result in the background. If the comparison result is consistent, it is judged that the corresponding operation is successfully executed, otherwise it is judged that the corresponding operation is not successfully executed.
[0057] In the description of the present invention, it should be understood that the orientation or positional relationship indicated by orientation words such as "front, rear, upper, lower, left, right", "lateral, vertical, perpendicular, horizontal" and "top, bottom", etc. is usually based on the orientation or positional relationship shown in the drawings. It is only for the convenience of describing the present invention and simplifying the description. Without contrary explanation, these orientation words do not indicate and imply that the device or element referred to must have a specific orientation or be constructed and operated in a specific orientation. Therefore, it should not be construed as a limitation on the protection scope of the present invention; the orientation words "inside, outside" refer to the inside and outside relative to the contour of each component itself.
[0058] For the convenience of description, spatial relative terms such as "above...", "over...", "on the upper surface of...", "above" etc. can be used here to describe the spatial positional relationship between a device or feature shown in the drawings and other devices or features. It should be understood that the spatial relative terms are intended to include different orientations in use or operation other than the orientation described in the drawings for the device. For example, if the device in the drawings is inverted, the device described as "above other devices or structures" or "over other devices or structures" will then be positioned as "below other devices or structures" or "under other devices or structures". Thus, the exemplary term "above..." can include both the orientations of "above..." and "below...". The device can also be positioned in other different ways (rotated 90 degrees or in other orientations), and corresponding interpretations should be made for the spatial relative descriptions used here.
[0059] In addition, it should be noted that the use of words such as "first", "second" etc. to limit components is only for the convenience of distinguishing the corresponding components. Without otherwise stating, the above words have no special meaning. Therefore, it should not be construed as a limitation on the protection scope of the present invention.
[0060] The above are only the preferred embodiments of the present invention and are not used to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.
Claims
1. A method for automated testing of human-computer interaction of HMI software, characterized in that: The method includes: After the automated testing software is started, it receives the operation data input by the user in real time. The operation data is input in a time sequence according to the interaction results with the automated testing software background data and the user's habits; Record and store the input sequence and input time of operation data in real time to obtain a test case set; According to the input sequence and input time of the operation data in the test case set, the state information involved in the screen development of the human-computer interaction software is supplemented to obtain the initial operation chain and initial operation results that cover the user's operation habits and consider the timing; Deriving a new operation chain and a new operation result by enumerating the operation process preset in the operation process database, and updating the initial operation chain and the initial operation result by using the new operation chain and the new operation result to obtain an updated operation chain and an updated operation result; The updated operation chain and the updated operation result are configured according to preset configuration parameters to obtain the configured operation chain and the configured operation result; Execute corresponding operations on the human-computer interaction interface according to the configured operation chain and generate corresponding actual operation results; Determine whether the corresponding operation is successfully executed based on the actual operation results; Mark unsuccessful operation chains as failed cases, and iteratively optimize the automated testing software by recording failed cases.
2. The method according to claim 1, characterized in that The state parameters are obtained according to the relevant data of the initial operation chain, and the state parameters include the sequential connection information between the operations and the time between each operation step.
3. The method according to claim 2, characterized in that The status information involved in the screen development of human-computer interaction software includes the human-computer interaction interface, screen switching rules and execution results.
4. The method according to claim 3, characterized in that Configuration parameters include the time information and step information of the test case.
5. The method according to claim 1, characterized in that Judging whether the corresponding operation is successful based on the actual operation results includes: Determine whether the corresponding operation is successfully executed based on the actual operation results through the human-computer interaction interface; The information exchanged between the human-computer interaction interface and the background is used to determine whether the corresponding operation is successful based on the actual operation results.
6. The method according to claim 5, characterized in that The information exchanged between the human-computer interaction interface and the background is used to determine whether the corresponding operation is successful based on the actual operation results, including: The actual operation result is compared with the background preset operation result. If the comparison results are consistent, it is judged that the corresponding operation is executed successfully, otherwise it is judged that the corresponding operation is not executed successfully.