A cockpit test method and device, vehicle-mounted equipment and vehicle

Abstract

The application relates to a cockpit test method and device, a vehicle-mounted equipment and a vehicle. The method comprises the following steps: acquiring a current configuration condition of a cockpit, an execution action required by cockpit testing, and configuration information of the execution action; comparing the current configuration condition with a preset execution condition; if the current configuration condition is consistent with the preset execution condition, starting to control the execution action to be executed; recording an execution process of the execution action; recording an interaction signal in the execution process of the execution action; determining an actual execution result of the execution action according to a recording picture; and determining a test result of the cockpit by combining the interaction signal, a preset execution result and the actual execution result. The application realizes automatic testing of cockpit functions, reduces the probability of errors during testing, improves test efficiency and test accuracy, and saves manpower and resources.

Description

Technical Field

[0001] This application relates to the field of automated testing technology, and in particular to a cockpit testing method, apparatus, vehicle-mounted equipment, and vehicle. Background Technology

[0002] New energy vehicles refer to automobiles that use unconventional vehicle fuels as their power source (or use conventional vehicle fuels and adopt new on-board power devices), and integrate advanced technologies in vehicle power control and drive, resulting in vehicles with advanced technical principles, new technologies, and new structures.

[0003] New energy vehicles have more and more complex functions than traditional fuel vehicles. Currently, the human-machine interaction test of the cockpit of new energy vehicles is usually completed manually by testers. However, due to factors such as the complexity of some test cases, the need to monitor a large number of signals during the test, and the time and manpower wasted on stress testing, traditional manual testing is increasingly unable to meet the testing needs of new energy vehicles.

[0004] In summary, the manual testing methods for new energy vehicles have the following problems: 1. Some new energy vehicle cockpit test cases involve complex steps, making manual testing cumbersome and prone to errors; 2. Some new energy vehicle cockpit test cases require monitoring numerous signals, making it inconvenient for manual signal verification, and manual signal verification may result in errors; 3. Some new energy vehicle cockpit test cases involve dynamic scenarios, requiring at least two people to participate in the testing, which leads to unnecessary waste of manpower; 4. The testing process for new energy vehicle cockpits is highly repetitive, resulting in a large amount of repetitive work for testers, low testing efficiency, and low testing accuracy.

[0005] Therefore, current cockpit testing methods need to be improved. Summary of the Invention

[0006] In view of the shortcomings of the prior art described above, this application provides a cockpit testing method, apparatus, vehicle-mounted equipment, and vehicle to solve the above-mentioned technical problems.

[0007] This application provides a cockpit testing method, the method comprising: acquiring the current configuration conditions of the cockpit, the execution actions required for cockpit testing, and configuration information of the execution actions; the configuration information including preset execution results and preset execution conditions; comparing the current configuration conditions with the preset execution conditions; if the current configuration conditions match the preset execution conditions, controlling the execution action to begin execution, recording the execution process of the execution action, and recording the interaction signals during the execution process of the execution action; determining the actual execution result of the execution action based on the recorded screen, and determining the test result of the cockpit by combining the interaction signals, the preset execution result, and the actual execution result.

[0008] In one embodiment of this application, after comparing the current configuration conditions with the preset execution conditions, the method further includes: if the current configuration conditions do not match the preset execution conditions, then correcting the current configuration conditions; if the corrected settings do not match the preset execution conditions, then ending the test process; if the corrected settings match the preset execution conditions, then controlling the execution action to enter the execution process, and determining the test result of the cockpit by combining the preset execution result, the interaction signals during the execution of the execution action, and the actual execution result obtained during the execution of the execution action.

[0009] In one embodiment of this application, the process of correcting the current configuration conditions includes: if the current configuration conditions include current gear information, the preset execution conditions include preset gear information, and the current gear information is inconsistent with the preset gear information, then the gear shifting device is controlled by a preset control device to change the current gear information until the changed gear information is consistent with the preset gear information; if the current configuration conditions include current pedal state, the preset execution conditions include preset pedal state, and the current pedal state is inconsistent with the preset pedal state, then the pedal is controlled by a preset control device to change the current pedal state until the changed pedal state is consistent with the preset pedal state; the pedal includes a brake pedal.

[0010] In one embodiment of this application, the process of determining the actual execution result of the action based on the recorded screen includes: capturing a state image of the target subject at the start of the action from the recorded screen, denoted as the initial image; capturing a state image of the target subject during the execution of the action from the recorded screen, denoted as the process image; and capturing a state image of the target subject at the end of the action from the recorded screen, denoted as the end image; the target subject is the object of the action; and the actual execution result is determined based on the pixel values ​​of the initial image, the process image, and the end image.

[0011] In one embodiment of this application, the process of determining the test result of the cockpit by combining the interaction signal, the preset execution result, and the actual execution result includes: verifying the interaction signal to obtain a verification result; if the preset execution result is consistent with the actual execution result, and the verification result indicates that the interaction signal is correct, then the test is considered successful as the test result of the cockpit; if the preset execution result is inconsistent with the actual execution result, and / or the verification result indicates that the interaction signal is incorrect, then the test is considered unsuccessful as the test result of the cockpit.

[0012] In one embodiment of this application, if the configuration information includes an action type and an action description, then after obtaining the test results of the cockpit, the method includes: displaying the recorded screen to obtain a display screen; and adding the verification result, the preset execution result, the actual execution result, the action type, and the action description to the display screen according to a preset display method.

[0013] In one embodiment of this application, the process of verifying the interaction signal includes: determining whether the configuration information includes key-value pairs, wherein the key-value pairs are used to indicate the mapping relationship between the execution action and the target signal type; the target signal type is the signal type that the execution action needs to verify; if the configuration information does not include the key-value pairs, then all interaction signals are verified; if the configuration information includes the key-value pairs, then the interaction signals corresponding to the target signal type are verified.

[0014] According to one aspect of the embodiments of this application, a cockpit testing apparatus is provided. The apparatus includes: a condition acquisition module, configured to acquire the current configuration conditions of the cockpit, the execution actions required for cockpit testing, and configuration information of the execution actions; the configuration information includes preset execution results and preset execution conditions; a condition comparison module, configured to compare the current configuration conditions with the preset execution conditions; an action execution module, configured to control the execution action to start execution if the current configuration conditions match the preset execution conditions, and to record the execution process of the execution action, and to record the interaction signals during the execution process of the execution action; and a result determination module, configured to determine the actual execution result of the execution action based on the recorded screen, and to determine the test result of the cockpit by combining the interaction signals, the preset execution result, and the actual execution result.

[0015] According to one aspect of the embodiments of this application, an in-vehicle device is provided, including: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the in-vehicle device to implement the cockpit testing method as described above.

[0016] According to one aspect of the embodiments of this application, a vehicle is provided, the vehicle including the cockpit testing apparatus as described above or the vehicle-mounted equipment as described above.

[0017] The beneficial effects of this application are as follows: This application obtains the current configuration conditions of the cockpit, the execution actions required for cockpit testing, and the configuration information of the execution actions. It compares the current configuration conditions with preset execution conditions. If the current configuration conditions match the preset execution conditions, it controls the execution actions to begin, records the execution process of the execution actions, and records the interaction signals during the execution process. Based on the recorded screen, it determines the actual execution result of the execution actions. Combining the interaction signals, preset execution results, and actual execution results, it determines the test result of the cockpit. The above process automatically determines whether the current configuration conditions match the preset execution conditions. When the current configuration conditions match the preset execution conditions, it controls the execution actions to execute automatically, automatically records the execution process of the execution actions, automatically records the interaction signals during the execution process, and automatically determines the test result of the cockpit by combining the interaction signals, preset execution results, and actual execution results. This achieves automated testing of cockpit functions, reduces the probability of errors during testing, improves testing efficiency and accuracy, and saves manpower and resources.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0020] Figure 1 This is a schematic diagram illustrating an exemplary system architecture as shown in an exemplary embodiment of this application;

[0021] Figure 2 This is a flowchart illustrating a cockpit testing method in an exemplary embodiment of this application;

[0022] Figure 3 This is a flowchart illustrating an automated click control as shown in an exemplary embodiment of this application;

[0023] Figure 4 This is a flowchart illustrating an exemplary embodiment of the present application of an automated test;

[0024] Figure 5 This is a schematic diagram illustrating a user interface in an exemplary embodiment of this application;

[0025] Figure 6 This is a block diagram illustrating a cockpit testing apparatus according to an exemplary embodiment of this application;

[0026] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing the vehicle-mounted device of the present application is shown. Detailed Implementation

[0027] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0028] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0029] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the present application. However, it will be apparent to those skilled in the art that embodiments of the present application may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the present application.

[0030] Figure 1 This is a schematic diagram illustrating an exemplary system architecture as shown in an exemplary embodiment of this application.

[0031] Reference Figure 1 As shown, the system architecture may include a storage device 101 and an in-vehicle controller 102. The in-vehicle controller 102 can be at least one of a desktop graphics processing unit (GPU) computer, a GPU computing cluster, or a neural network computer. Those skilled in the art can use the in-vehicle controller 102 to acquire the current configuration conditions of the cockpit, the actions required for cockpit testing, and the configuration information of the actions. The current configuration conditions are compared with preset execution conditions. If the current configuration conditions match the preset execution conditions, the execution actions are initiated, and the execution process is recorded. Interaction signals during the execution process are also recorded. The actual execution result of the actions is determined based on the recorded footage. The cockpit test result is determined by combining the interaction signals, the preset execution result, and the actual execution result. The storage device 101 stores the current configuration conditions of the cockpit, the actions required for cockpit testing, and the configuration information of the actions. After acquiring these conditions, it provides them to the in-vehicle controller 102 for processing.

[0032] Indicatively, after obtaining the current configuration conditions of the cockpit, the execution actions required for cockpit testing, and the configuration information of the execution actions from the storage device 101, the vehicle controller 102 compares the current configuration conditions with the preset execution conditions. If the current configuration conditions match the preset execution conditions, the controller starts executing the action, records the execution process, and records the interaction signals during the execution process. Based on the recorded screen, the controller determines the actual execution result of the action. Combining the interaction signals, the preset execution result, and the actual execution result, the controller determines the cockpit test result. This process automatically determines whether the current configuration conditions match the preset execution conditions. When the current configuration conditions match the preset execution conditions, the controller automatically executes the action, automatically records the execution process, automatically records the interaction signals during the execution process, and automatically determines the cockpit test result by combining the interaction signals, the preset execution result, and the actual execution result. This achieves automated testing of cockpit functions, reduces the probability of errors during testing, improves testing efficiency and accuracy, and saves manpower and resources.

[0033] It should be noted that the cockpit testing method provided in this application embodiment is generally executed by the vehicle controller 102, and correspondingly, the cockpit testing device is generally installed in the vehicle controller 102.

[0034] The implementation details of the technical solutions in the embodiments of this application are described in detail below:

[0035] Figure 2 This is a flowchart illustrating an exemplary embodiment of the present application of a cockpit testing method, which can be executed by a computing processing device, the computing processing device being... Figure 1 The vehicle controller 102 shown is illustrated. (Refer to...) Figure 2 As shown, the cockpit testing method includes at least steps S210 to S240, which are described in detail below:

[0036] In step S210, the current configuration conditions of the cockpit, the actions required for cockpit testing, and the configuration information of the actions are obtained.

[0037] In one embodiment of this application, the current configuration conditions include current gear information, current accelerator pedal state, current brake pedal state, and current temperature information. The configuration information includes preset execution results and preset execution conditions. The preset execution conditions include preset gear information, preset brake pedal state, and preset temperature range. The preset execution results include successful action execution, failed action execution, grayed-out action function button, action function incompatible with the test vehicle model, and missing action button display.

[0038] In step S220, the current configuration conditions are compared with the preset execution conditions.

[0039] In this embodiment, if the current configuration conditions match the preset execution conditions, it is determined that the current configuration conditions meet the preset execution conditions; if the current configuration conditions do not match the preset execution conditions, it is determined that the current configuration conditions do not meet the preset execution conditions.

[0040] In step S230, if the current configuration conditions match the preset execution conditions, the execution action is started, the execution process of the execution action is recorded, and the interaction signals during the execution process are recorded.

[0041] In this embodiment, when the current configuration conditions meet the preset execution conditions, the execution action is automatically controlled to start, and the execution process of the execution action is automatically recorded. In addition, the interaction signals during the execution process of the execution action are automatically recorded, which reduces the workload of testers and improves the automation of the testing process.

[0042] In this embodiment, the execution process of the action is automatically recorded using a CANalyzer device.

[0043] In step S240, the actual execution result of the action is determined based on the recorded screen, and the test result of the cockpit is determined by combining the interactive signal, the preset execution result and the actual execution result.

[0044] In this embodiment, by automatically determining whether the current configuration conditions are consistent with the preset execution conditions, and when the current configuration conditions are consistent with the preset execution conditions, the system controls the automatic execution of the action, automatically records the execution process of the action, automatically records the interaction signals during the execution process, and combines the interaction signals, preset execution results, and actual execution results to automatically determine the test results of the cockpit. This achieves automated testing of the cockpit functions, reduces the probability of errors during testing, improves testing efficiency and accuracy, and saves manpower and resources.

[0045] In one embodiment of this application, after comparing the current configuration conditions with preset execution conditions, the cockpit testing method further includes:

[0046] If the current configuration conditions do not match the preset execution conditions, the current configuration conditions will be corrected.

[0047] In this embodiment, by setting up a process to correct the current configuration conditions, the intelligence and automation of the testing process are improved.

[0048] If the corrected settings do not match the preset execution conditions, the test process ends.

[0049] In this embodiment, the test process is terminated only when the corrected settings do not meet the preset execution conditions, thus avoiding the waste of resources caused by repeated testing when the preset execution conditions are not met.

[0050] If the corrected settings match the preset execution conditions, the control action will enter the execution process. The test results of the cockpit will be determined by combining the preset execution results, the interactive signals during the execution process, and the actual execution results obtained during the execution process.

[0051] In this embodiment, when the corrected settings meet the preset execution conditions, the execution action can be automatically controlled to enter the execution process, reducing the need for manual correction of the current configuration conditions and saving manpower and resources.

[0052] In one embodiment of this application, the process of correcting the current configuration conditions includes:

[0053] If the current configuration conditions include the current gear information, the preset execution conditions include the preset gear information, and the current gear information is inconsistent with the preset gear information, then the preset control device controls the shifting device to change the current gear information until the changed gear information is consistent with the preset gear information.

[0054] In this embodiment, the preset control device can be a robotic arm. When the current gear information is inconsistent with the preset gear information, the robotic arm starts to control the gear shifting device to perform actions, such as switching the current gear from parking gear to reverse gear, thereby realizing the gear shifting simulation function of the gear shifting device.

[0055] If the current configuration conditions include the current pedal state, the preset execution conditions include the preset pedal state, and the current pedal state is inconsistent with the preset pedal state, then the pedal is controlled to move through the preset control device to change the current pedal state until the changed pedal state is consistent with the preset pedal state.

[0056] In this embodiment, the pedal includes a brake pedal. The preset control device can be a relay, which is connected to a brake switch. When the current pedal state is inconsistent with the preset pedal state, the brake switch is opened by controlling the relay to switch the pedal from the release state to the pressing state. Alternatively, the brake switch is disconnected by controlling the relay to switch the pedal from the pressing state to the release state.

[0057] In this embodiment, the preset control device can be a robotic arm. When the current pedal state is inconsistent with the preset pedal state, the robotic arm starts to control the pedal to perform an action to change the current pedal state until the changed pedal state is consistent with the preset pedal state.

[0058] In one embodiment of this application, the process of determining the actual execution result of an action based on the recorded screen includes:

[0059] Capture the state image of the target subject at the start of the action from the recorded footage, and record it as the initial image.

[0060] In this embodiment, a state image of the target subject at the start of the execution of the action is captured using video screenshot software, including Snagit, Camtasia, Movavi ScreenRecorder, Bandicam, etc.

[0061] Capture the state image of the target subject during the execution of the action from the recorded footage, and record it as the process image.

[0062] In this embodiment, the state image of the target subject during the execution of the action is captured by video screenshot software. The number of process images can be one or more, and no specific limitation is made here.

[0063] Additionally, capture the state image of the target subject at the end of the execution of the action from the recorded screen, and record it as the end image.

[0064] In this embodiment, a state image of the target subject is captured by video screenshot software when the execution of the action ends. The target subject is the object that performs the action.

[0065] In this embodiment, when the action is to open the trailer mode, the executing entity is the robotic arm, and the target entity is the trailer mode button on the vehicle screen. When the action is to open the energy-saving mode, the executing entity is the robotic arm, and the target entity is the energy-saving mode button on the vehicle screen, etc.

[0066] The actual execution result is determined based on the pixel values ​​of the initial image, the process image, and the final image.

[0067] In this embodiment, the method for determining the actual execution result based on the pixel values ​​of the initial image, the pixel values ​​of the process image, and the pixel values ​​of the final image can be implemented with reference to the methods for determining the actual execution result of the execution action in relevant technical documents, and no specific limitation is made here.

[0068] In one embodiment of this application, the process of determining the test results of the cockpit by combining interactive signals, preset execution results, and actual execution results includes:

[0069] The interaction signal is verified to obtain the verification result.

[0070] In this embodiment, the interaction signal is a CAN (Controller Area Network) test signal. The method for verifying and analyzing the CAN test signal to obtain the verification result can be implemented by referring to relevant technical documents on the method for verifying and analyzing the CAN test signal. Here, no specific limitation is made.

[0071] In this embodiment, the interactive signals are verified using a CANalyzer device, a VBA (Visual Basic for Applications) device, etc., to obtain the verification results.

[0072] If the preset execution result is consistent with the actual execution result, and the verification result shows that the interaction signal is correct, then the test success will be taken as the test result of the cockpit.

[0073] In this embodiment, if the preset execution result is consistent with the actual execution result, it means that the execution action was successfully executed, and if the verification result is that the interaction signal is correct, it means that the execution action test was successful.

[0074] If the preset execution result is inconsistent with the actual execution result, and / or the verification result is an interaction signal error, then the test failure will be taken as the test result for the cockpit.

[0075] In this embodiment, if the preset execution result is inconsistent with the actual execution result, it indicates that the execution action has failed. In the case of execution action failure, regardless of whether the verification result is an interaction signal error, it indicates that the execution action test is unsuccessful.

[0076] In one embodiment of this application, if the configuration information includes action type and action description, then after obtaining the cockpit test results, the cockpit testing method includes:

[0077] The recorded screen is then displayed to obtain the displayed image.

[0078] In this embodiment, the recorded footage is displayed using a display device, which can be a vehicle infotainment screen or a separate display screen located inside or outside the cabin.

[0079] According to the preset display method, the verification result, preset execution result, actual execution result, action type and action description are added to the display screen.

[0080] In this embodiment, the preset display mode can be a preset display time and a preset display position. Through the display screen, not only can the execution process of the action be restored, but also the actual execution result, action type, action description, and verification result of the action can be displayed simultaneously, making it convenient for testers to view the execution process of historical actions.

[0081] In this implementation, after obtaining the test results of the cockpit, the displayed screen, actual execution results, action type, action description, verification results, etc. can be recorded to form log information, which makes it convenient for testers to analyze the log information of historical execution actions.

[0082] In one embodiment of this application, the process of verifying the interaction signal includes:

[0083] Determine whether the configuration information includes key-value pairs.

[0084] In this embodiment, key-value pairs are used to indicate the mapping relationship between the action to be performed and the target signal type. The target signal type is the signal type that needs to be verified by the action to be performed. Key-value pairs can be marked by key-value pair flags, etc. If the key-value pair flag is 1, the configuration information contains key-value pairs; if the key-value pair flag is 0, the configuration information does not contain key-value pairs.

[0085] If the configuration information does not include key-value pairs, then all interaction signals are validated.

[0086] In this embodiment, if the configuration information does not include key-value pairs, it means that the interaction signals have not been customized, and all interaction signals need to be verified.

[0087] If the configuration information includes key-value pairs, then the interaction signal corresponding to the target signal type is validated.

[0088] In this embodiment, the target signal type is customized by setting key-value pairs. During the verification of the interaction signal, only the interaction signal corresponding to the target signal type needs to be verified, which reduces the time spent on verification.

[0089] In this embodiment, if the action includes multiple sub-actions, the process of verifying the interaction signal includes: verifying the interaction signal in the execution process of each sub-action according to the execution order of the multiple sub-actions; if the interaction signal verification result of all sub-actions is that the interaction signal is correct, then the correct interaction signal is taken as the verification result; if the interaction signal verification result of at least one sub-action is that the interaction signal is incorrect, then the incorrect interaction signal is taken as the verification result.

[0090] In this embodiment, multiple sub-actions may include first-level sub-actions, second-level sub-actions, third-level sub-actions, etc. First-level sub-actions include the click action of entering the settings interface from the main interface of the vehicle screen; second-level sub-actions include entering a certain function interface (e.g., the energy interface) from the settings interface; and third-level sub-actions include the action of clicking the function button of a certain function interface.

[0091] Figure 3This is a flowchart illustrating an automated click control as shown in an exemplary embodiment of this application, such as... Figure 3 As shown, the process of automated click control includes: (1) inputting the preset execution result; (2) locating the first-level interface (such as the main interface of the vehicle screen) and locking the first-level interface; (3) entering the second-level interface (such as the settings interface) through the first-level sub-action and locking the second-level interface; (4) entering the function interface (such as the energy interface) through the second-level sub-action and locking the function interface; (5) locating the function button (or control) in the function interface; (6) judging the state of the function button before the third-level sub-action starts; (7) controlling the third-level sub-action to perform the action on the function button; (8) locating the function button and judging the state of the function button; (9) determining the test result based on the preset execution result, the state of the function button before the third-level sub-action starts, the state of the function button after the third-level sub-action performs the action on the function button, and the verification result of the interaction signal during the automated click control process.

[0092] In this embodiment, XPath (XML Path Language) is used to locate the function buttons (or controls) in the functional interface.

[0093] In this embodiment, XPath is a language for locating and selecting nodes in an XML document. Based on the tree structure of XML, it provides the ability to find nodes within a data structure tree. XPath's flexibility and powerful functionality make it an important tool for accurately locating and extracting data in XML or HTML documents, and it can recognize and locate complex actions other than clicking (such as dragging, long-pressing, etc.).

[0094] In this embodiment, the execution of sub-actions is achieved by the host computer sending HTTP commands to the robotic arm, which then performs the actions.

[0095] Figure 4 This is a flowchart illustrating an exemplary embodiment of the present application of an automated test, such as... Figure 4As shown, the automated testing process includes: (1) controlling the CANalyzer device to automatically start recording; (2) judging whether the current configuration conditions meet the preset execution conditions. If the current configuration conditions meet the preset execution conditions, the execution action is controlled to start; if the current configuration conditions do not meet the preset execution conditions, the first condition judgment is determined to be unsatisfactory, and the current configuration conditions are corrected; (3) if the corrected configuration conditions are inconsistent with the preset execution conditions, the second condition judgment is determined to be unsatisfactory, the CANalyzer device automatically stops recording, and the test result is returned as unsatisfactory; (4) if the corrected configuration conditions are consistent with the preset execution conditions, the second condition judgment is determined to be successful, and the execution action is controlled to start; (5) during the execution of the action, the interaction signals during the execution of the action are recorded and the execution process of the action is recorded; (6) when the execution action ends, the CANalyzer device automatically stops recording, and the actual execution result is determined according to the recording screen, and the interaction signals are verified; (7) the test result is determined according to the preset execution result, the actual execution result, and the verification result of the interaction signals; (8) the test result is displayed on the display interface.

[0096] Figure 5 This is a schematic diagram of a user interface shown in an exemplary embodiment of this application, such as... Figure 5 As shown, the User Interface (UI) has human-computer interaction functions. Testers can select the corresponding test vehicle model, test cases, filter static / dynamic test cases, and choose whether to perform prerequisite criteria (preset execution condition judgment) and result criteria (test result judgment) in the user interface. In addition, they need to fill in the vehicle serial number (SN) for connecting to the vehicle's infotainment system, and the vehicle identification number (VIN) for naming the binary data file (binarylogging format, blf). The user interface will display the test case execution status, detailed execution status of each step of a single test case, and also includes buttons for starting and stopping the test.

[0097] In this embodiment, the Python programming platform enables automatic data recording, automatic screen clicking, automatic signal judgment, and automatic brake pedal control, which can replace manual labor in completing the cockpit testing work of new energy vehicles.

[0098] This application includes software and hardware designs. The software includes a control module for automatically controlling a robotic arm to operate the vehicle's infotainment screen; a visual judgment module for automatically evaluating the operation results after the screen is operated; a control module for automatically controlling a CANalyzer device to record data; a control module for automatically controlling a CANalyzer device to verify signals; a control module for automatically controlling the brake pedal; a test case framework module; a test case module; and a user graphical interface module. The hardware includes a Vector CANalyzer device and a CH340 relay.

[0099] In this embodiment, the automated operation of the vehicle's infotainment screen is implemented using the uiautomator2 library in the Python programming platform. The screen is controlled by sending HTTP commands from the computer to the vehicle's infotainment system. The automated clicking process for screen functions includes: dividing the functions on the screen into different execution actions based on different operations. These actions include switching from driving mode to energy-saving mode, from driving mode to comfort mode, from driving mode to sport mode, and from driving mode to personalized mode. Each execution action is further divided into three levels of sub-actions: the first level sub-action controls the screen to switch to the settings interface; the second level sub-action controls the settings interface to switch to a specific function interface (such as the driving mode interface); and the third level sub-action controls the function itself (such as activating trailer mode in the driving mode interface).

[0100] In this embodiment, each sub-action has a corresponding preset execution result (i.e., expected result). When the preset execution result is that the sub-action is successful, the setting parameter corresponding to the preset execution result is 1. When the preset execution result is that the sub-action fails, the setting parameter corresponding to the preset execution result is 0. When the preset execution result is that the button for the sub-action function is grayed out, the setting parameter corresponding to the preset execution result is -1. When the preset execution result is that the sub-action function is not compatible with the test vehicle model, the setting parameter corresponding to the preset execution result is -2. When the preset execution result is that the sub-action button is missing, the setting parameter corresponding to the preset execution result is -3.

[0101] In this embodiment, taking enabling a certain function as an example, the process of this sub-action includes: first, visually judging the state of a function button; if the judgment result is 1, it is determined that the function has been enabled, and the function needs to be disabled before executing the enabling sub-action to complete the test process; if the judgment result is 0, it is determined that the function has not been enabled, and the enabling sub-action is executed to complete the test process. If the judgment result is a value other than 1 or 0, the function exits directly.

[0102] In this embodiment, the visual judgment module is implemented based on the OpenCV module of Python. Its principle is to simulate the human eye's perception of the feedback of the user interface function status display. That is, the human eye judges the function status by the color of the switch or the slider. This module takes screenshots of the function button before and after the action is executed, and then judges the change of the button based on the pixel value of the screenshot.

[0103] In this embodiment, the host computer calls the CANalyzer device through the win32com port to automate the recording of the execution process of the action.

[0104] In this embodiment, the host computer calls the CANalyzer device through the win32com port to verify the interaction signals. During the execution of the sub-action, it obtains the corresponding sub-action signal that meets the preset execution result according to the preset execution result of the sub-action, and forms a signal list of the sub-action signals. The interaction signals of each sub-action are concentrated in the CANalyzer device, which has high reusability.

[0105] In this embodiment, the preset control device controls a USB relay (such as a CH340 relay) via a serial port signal, and connects the relay in series with the brake switch. The computer sends serial port commands to control the opening and closing of the relay, thereby simulating the brake pedal.

[0106] In this embodiment, the use case framework module includes a single action execution framework method. This method passes in the sub-actions to be executed. This method uses a try-except statement to execute the sub-actions to prevent abnormal interruptions of the uiautomator2 test framework due to network fluctuations. The sub-actions have two execution opportunities. If the first execution is successful, the method will exit directly and return the result. If the first execution fails, the method will re-execute the sub-action.

[0107] In this embodiment, the use case framework module also includes execution action judgment, execution order judgment and actual execution result judgment. The parameters required by the method include the Chinese description of the execution action, the flag bit indicating whether the execution action needs to be signaled, the flag bit indicating whether the global use case needs to be result-based, the action tuple consisting of all sub-actions called by a single execution action, and the signal type for custom verification required by a single execution action.

[0108] In this embodiment, key-value pairs can be set in advance or not. If key-value pairs are set in advance, the signal list passed when the sub-action is executed is ignored. Signal verification is based on the signal type defined by the key-value pairs. Key-value pairs include the key-value pairs of each sub-action and the final key-value pairs. If the final key-value pairs are set, the signal type defined by the final key-value pairs will only be verified once after all actions are executed. The verified signal list is the signal list corresponding to the signal type defined by the final key-value pairs (denoted as the custom signal list).

[0109] In this embodiment, the use case step framework method first checks whether there is a final key-value pair. If there is a final key-value pair, all sub-action methods in the sub-action tuple are executed in a loop. Then, the signal list corresponding to the signal type defined by the final key-value pair is validated. If no final key-value pair is passed but a signal type defined by a sub-action key-value pair is passed, after the sub-action is executed, the signal list corresponding to the signal type defined by the sub-action key-value pair will overwrite the automatically passed sub-action signal list, and the signal list corresponding to the signal type defined by the sub-action key-value pair will be validated. If no key-value pair is passed, the signal list automatically passed after each sub-action is executed will be validated by default.

[0110] In this embodiment, the CANalyzer device's start recording function is inherited from the method that compares the current configuration conditions with the preset execution conditions. The test case number and name will be used for blf data naming. The test case step calls a single sub-step framework method, and the test case will return the test case execution result and test case name for display on the user interface.

[0111] In this embodiment, by automatically clicking on the vehicle's infotainment screen, the CANalyzer device is controlled to automatically load the cfg project file according to the selected vehicle model, avoiding the problem of cfg project file loading errors. The CANalyzer device is controlled to pre-name the blf files to be recorded according to the test case name of each test case, and automatically completes the verification of interactive signals and the comparison of preset execution results and actual execution results. This completely replaces the manual cockpit testing scheme and has higher testing efficiency, accuracy and reliability compared to manual testing methods.

[0112] In this embodiment, stress testing can be performed simply by setting up the test environment and running the automated test script. This does not require the time of testers and can automatically complete the test operations and signal verification. For dynamic test scenarios, testers only need to drive the system, and the rest of the test work can be completed automatically, which improves the safety, economy and efficiency of the test.

[0113] The following describes an embodiment of the apparatus described in this application, which can be used to perform the cockpit testing method described in the above embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the cockpit testing method described above.

[0114] Figure 6 This is a block diagram illustrating a cockpit testing apparatus according to an exemplary embodiment of this application. The apparatus can be applied to… Figure 1 The implementation environment shown is specifically configured in the vehicle controller 102. This device can also be applied to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the device is applicable.

[0115] like Figure 6 As shown, the exemplary cockpit testing apparatus includes:

[0116] The condition acquisition module 601 is used to acquire the current configuration conditions of the cockpit, the actions required for cockpit testing, and the configuration information of the actions.

[0117] The condition comparison module 602 is used to compare the current configuration conditions with the preset execution conditions.

[0118] The action execution module 603 is used to control the execution of an action to start if the current configuration conditions match the preset execution conditions, record the execution process of the action, and record the interactive signals during the execution process of the action.

[0119] The result determination module 604 is used to determine the actual execution result of the action based on the recorded screen, and to determine the test result of the cockpit by combining the interactive signal, the preset execution result and the actual execution result.

[0120] In this embodiment, specifically in one embodiment of this application, the current configuration conditions include current gear information, current accelerator pedal state, current brake pedal state, and current temperature information. The configuration information includes preset execution results and preset execution conditions. The preset execution conditions include preset gear information, preset brake pedal state, and preset temperature range. The preset execution results include successful action execution, failed action execution, grayed-out action function button, action function incompatible with this test vehicle model, and missing action button display.

[0121] In this embodiment, if the current configuration conditions match the preset execution conditions, it is determined that the current configuration conditions meet the preset execution conditions; if the current configuration conditions do not match the preset execution conditions, it is determined that the current configuration conditions do not meet the preset execution conditions.

[0122] In this embodiment, when the current configuration conditions meet the preset execution conditions, the execution action is automatically controlled to start, and the execution process of the execution action is automatically recorded, as well as the interaction signals during the execution process, thereby reducing the workload of testers and improving the automation level of the testing process.

[0123] In this embodiment, the execution process of the action is automatically recorded using a CANalyzer device.

[0124] In this embodiment, by automatically determining whether the current configuration conditions are consistent with the preset execution conditions, and when the current configuration conditions are consistent with the preset execution conditions, the system controls the automatic execution of the action, automatically records the execution process of the action, automatically records the interaction signals during the execution process, and combines the interaction signals, preset execution results, and actual execution results to automatically determine the test results of the cockpit. This achieves automated testing of the cockpit functions, reduces the probability of errors during testing, improves testing efficiency and accuracy, and saves manpower and resources.

[0125] It should be noted that the cockpit testing device and the cockpit testing method provided in the above embodiments belong to the same concept. The specific operation methods of each module and unit have been described in detail in the method embodiments and will not be repeated here. In practical applications, the cockpit testing device provided in the above embodiments can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. This is not a limitation here.

[0126] Embodiments of this application also provide an in-vehicle device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the in-vehicle device to implement the cockpit testing methods provided in the above embodiments.

[0127] Embodiments of this application also provide a vehicle that includes the cockpit testing apparatus or the vehicle-mounted equipment provided in the above embodiments.

[0128] Figure 7 A schematic diagram of a computer system suitable for implementing the vehicle-mounted device of the embodiments of this application is shown. It should be noted that... Figure 7 The computer system 700 of the vehicle-mounted device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0129] like Figure 7As shown, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 702 or programs loaded from storage portion 708 into Random Access Memory (RAM) 703. The RAM 703 also stores various programs and data required for system operation. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An Input / Output (I / O) interface 705 is also connected to the bus 704.

[0130] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0131] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs various functions defined in the system of this application.

[0132] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium, a computer-readable medium, or any combination of the two. For example, a computer-readable medium can be an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than a computer-readable medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program contained on a computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0133] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0134] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0135] Another aspect of this application provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer's processor, causes the computer to perform the aforementioned cockpit testing method. This computer-readable medium may be included in the vehicle-mounted equipment described in the above embodiments, or it may exist independently and not be installed in the vehicle-mounted equipment.

[0136] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable medium. A processor of a computer device reads the computer instructions from the computer-readable medium and executes the computer instructions, causing the computer device to perform the cockpit testing methods provided in the various embodiments described above.

[0137] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.

Claims

1. A cockpit testing method, characterized in that, The method includes: The system obtains the current configuration conditions of the cockpit, the actions required for the cockpit test, and the configuration information of the actions; the configuration information includes preset execution results and preset execution conditions. The current configuration conditions are compared with the preset execution conditions; If the current configuration conditions match the preset execution conditions, the execution action is controlled to start, the execution process of the execution action is recorded, and the interaction signals during the execution process of the execution action are recorded. The actual execution result of the action is determined based on the recorded footage, and the test result of the cockpit is determined by combining the interaction signal, the preset execution result, and the actual execution result. The process of determining the test result of the cockpit by combining the interaction signal, the preset execution result, and the actual execution result includes: verifying the interaction signal to obtain a verification result; if the preset execution result is consistent with the actual execution result, and the verification result indicates that the interaction signal is correct, then the test is considered successful as the test result of the cockpit; if the preset execution result is inconsistent with the actual execution result, and / or the verification result indicates that the interaction signal is incorrect, then the test is considered unsuccessful as the test result of the cockpit. The process of verifying the interaction signal includes: determining whether the configuration information includes key-value pairs, wherein the key-value pairs are used to indicate the mapping relationship between the execution action and the target signal type; the target signal type is the signal type that the execution action needs to verify; if the configuration information does not include the key-value pairs, then all interaction signals are verified; if the configuration information includes the key-value pairs, then the interaction signals corresponding to the target signal type are verified.

2. The cockpit testing method according to claim 1, characterized in that, After comparing the current configuration conditions with the preset execution conditions, the method further includes: If the current configuration conditions do not match the preset execution conditions, the current configuration conditions are corrected. If the corrected settings do not match the preset execution conditions, the test process ends. If the corrected settings match the preset execution conditions, the execution action is controlled to enter the execution process. The test result of the cockpit is determined by combining the preset execution result, the interaction signals during the execution process, and the actual execution result obtained during the execution process.

3. The cockpit testing method according to claim 2, characterized in that, The process of correcting the current configuration conditions includes: If the current configuration conditions include current gear information, the preset execution conditions include preset gear information, and the current gear information is inconsistent with the preset gear information, then the preset control device controls the shifting device to perform an action to change the current gear information until the changed gear information is consistent with the preset gear information. If the current configuration conditions include the current pedal state, the preset execution conditions include the preset pedal state, and the current pedal state is inconsistent with the preset pedal state, then the pedal is controlled to move by the preset control device to change the current pedal state until the changed pedal state is consistent with the preset pedal state; the pedal includes the brake pedal.

4. The cockpit testing method according to any one of claims 1-3, characterized in that, The process of determining the actual execution result of the action based on the recorded footage includes: Capture the state image of the target subject at the start of the execution of the action from the recorded screen, and record it as the initial image; Capture the state image of the target subject during the execution of the action from the recorded screen, and record it as a process image; Additionally, a state image of the target subject is captured from the recorded screen when the execution of the action ends, and is denoted as the end image; the target subject is the object to which the action is performed. The actual execution result is determined based on the pixel values ​​of the initial image, the pixel values ​​of the process image, and the pixel values ​​of the final image.

5. The cockpit testing method according to any one of claims 1-3, characterized in that, If the configuration information includes action type and action description, then after obtaining the test results of the cockpit, the method includes: The recorded screen is displayed to obtain a display screen; According to the preset display method, the verification result, the preset execution result, the actual execution result, the action type, and the action description are added to the display screen.

6. A cockpit testing device, characterized in that, The device includes: The condition acquisition module is used to acquire the current configuration conditions of the cockpit, the execution actions required for cockpit testing, and the configuration information of the execution actions; the configuration information includes preset execution results and preset execution conditions. The condition comparison module is used to compare the current configuration conditions with the preset execution conditions; An action execution module is used to control the execution action to start if the current configuration conditions match the preset execution conditions, record the execution process of the execution action, and record the interaction signals during the execution process of the execution action. The result determination module is used to determine the actual execution result of the action based on the recorded screen, and to determine the test result of the cockpit by combining the interaction signal, the preset execution result and the actual execution result. The result determination module is specifically used to verify the interaction signal and obtain a verification result; if the preset execution result is consistent with the actual execution result and the verification result indicates that the interaction signal is correct, then the test success is taken as the test result of the cockpit; if the preset execution result is inconsistent with the actual execution result, and / or the verification result indicates that the interaction signal is incorrect, then the test failure is taken as the test result of the cockpit. The result determination module is further configured to determine whether the configuration information includes key-value pairs, wherein the key-value pairs are used to indicate the mapping relationship between the execution action and the target signal type; the target signal type is the signal type that the execution action needs to verify; if the configuration information does not include the key-value pairs, then all interaction signals are verified; if the configuration information includes the key-value pairs, then the interaction signals corresponding to the target signal type are verified.

7. A vehicle-mounted device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, cause the vehicle-mounted device to implement the cockpit testing method as described in any one of claims 1 to 5.

8. A vehicle, characterized in that, The vehicle includes the cockpit testing apparatus as described in claim 6 or the on-board equipment as described in claim 7.

Images