Automotive domain controller automated testing method and apparatus, electronic device, and medium

Abstract

The application provides an automobile domain controller automatic test method, device, electronic equipment and medium, the method obtains a pre-built domain controller test system, a pre-defined domain controller test action, a pre-defined domain controller test parameter, controls a test action execution device to execute the pre-defined domain controller test action, and monitors the data parameter in the pre-defined domain controller test action execution process through a test parameter monitoring device, compares the pre-defined domain controller test parameter with the data parameter monitored by the test parameter monitoring device, obtains a parameter comparison result, and judges whether the domain controller test passes according to the parameter comparison result; the application can reduce the test time and improve the test efficiency by not needing to spend a lot of learning time to train a mechanical arm to simulate user actions.

Description

Technical Field

[0001] This application relates to the field of automotive automation testing technology, specifically to automotive domain controller automation testing methods, devices, electronic equipment, and media. Background Technology

[0002] With the continuous development of new energy vehicle technology and its ever-increasing functionality, coupled with the growing demand for personalized solutions, more and more vehicle models are emerging with evolving hardware and software architectures and platforms, further enhancing the capabilities of new energy vehicles. To cope with the current abundance and rapid development of automotive technology, automakers must find more targeted R&D methods. As vehicle functions become increasingly complex, so too do the data and structures related to vehicle functions, leading to higher time and manpower costs for R&D. Automated testing technology is thus becoming increasingly important.

[0003] While the automated testing technologies currently used by major companies can cover many aspects of functional and performance testing, they also generally have some shortcomings that affect the effectiveness of the testing.

[0004] For example, Chinese invention patent application number CN202110958777.9, entitled "An Automated Testing Method and Apparatus for In-Vehicle Multimedia Functions," discloses an automated testing method for in-vehicle multimedia functions. This method first generates image information representing the user input interface image of a qualified multimedia screen; trains a robotic arm to learn the image information recognition algorithm and the user selection of characters and / or icons; and calibrates the robotic arm's movements. It then presets image template information, and the robotic arm simulates the multimedia test according to the calibrated movements, capturing real-time image information of the user input interface of the tested multimedia screen. The real-time image information is compared with the image template information to determine whether the multimedia is qualified. However, due to the wide variety of multimedia functions, a significant amount of learning time is required to train the robotic arm to simulate user movements, resulting in low testing efficiency.

[0005] For example, Chinese invention patent application CN201811418477.6, entitled "A Portable Automated Testing System for Vehicle Bus," discloses a portable automated testing system for vehicle bus. This system consists of a control board and various testing devices. The control board connects to the testing devices via an interface, and the testing devices connect to an industrial control computer via a communication bus. The control board is a vehicle bus simulation board used to aggregate the testing devices. The control board connects to the ECU under test via test lines, and the ECU has five wiring harnesses connected to the control board: CANH, CANL, KL31, KL30, and KL15. However, because this testing system can only test a single ECU, it cannot meet the testing requirements for environments with multiple ECUs.

[0006] Therefore, optimization is needed to improve testing efficiency and meet various testing conditions. Summary of the Invention

[0007] In view of the shortcomings of the prior art described above, the present invention provides an automated testing method, apparatus, electronic device and medium for automotive domain controllers to solve the above-mentioned technical problems.

[0008] This invention provides an automated testing method for automotive domain controllers. The automated testing of the automotive domain controller includes: acquiring a pre-built domain controller testing system, predefined domain controller test actions, and predefined domain controller test parameters. The predefined domain controller test actions correspond to the predefined domain controller test parameters. The domain controller testing system includes a test action execution device and a test parameter monitoring device; controlling the test action execution device to execute the predefined domain controller test actions, and monitoring the data parameters during the execution of the predefined domain controller test actions through the test parameter monitoring device; comparing the predefined domain controller test parameters with the data parameters monitored by the test parameter monitoring device to obtain a parameter comparison result, and determining whether the domain controller test passes based on the parameter comparison result.

[0009] In one embodiment of the present invention, the process of controlling the test action execution device to execute the predefined domain controller test action includes: obtaining the number of predefined domain controller test actions; if the number of predefined domain controller test actions is greater than a first quantity threshold, obtaining the timing sequence between the multiple predefined domain controller test actions; and controlling the test action execution device to perform actions according to the timing sequence between the multiple predefined domain controller test actions.

[0010] In one embodiment of the present invention, after obtaining the timing sequence between multiple predefined domain controller test actions, the method includes: obtaining a display screen, the display screen being obtained by the test action execution device executing the predefined domain controller test actions; determining whether the executed actions in the display screen are consistent with the corresponding predefined domain controller test actions, and obtaining a test action comparison result.

[0011] In one embodiment of the present invention, the process of comparing the predefined domain controller test parameters with the data parameters monitored by the test parameter monitoring device to obtain a parameter comparison result, and determining whether the domain controller test passes based on the parameter comparison result, includes: obtaining the test action comparison result, wherein the test action comparison result includes: test action matching and test action mismatch; and the parameter comparison result includes: parameter matching and parameter mismatch. If the test action comparison result is test action matching and the parameter comparison result is parameter matching, the domain controller test is determined to pass; otherwise, the domain controller test is determined to fail.

[0012] In one embodiment of the present invention, before obtaining a pre-built domain controller test system, the method includes: connecting the test action execution device to a first domain controller; connecting the first domain controller to multiple second domain controllers to obtain multiple connection links; connecting the test parameter monitoring device in series to the multiple connection links and connecting the test parameter monitoring device to a host computer to obtain the pre-built domain controller test system, so as to perform domain controller testing according to the pre-built domain controller test system.

[0013] In one embodiment of the present invention, the process of monitoring data parameters during the execution of a predefined domain controller test action by the test parameter monitoring device includes: when the test action execution device executes the predefined domain controller test action, the test action execution device sends signal data corresponding to the predefined domain controller test action to the first domain controller; when the first domain controller and the second domain controller interact based on the signal data, the test parameter monitoring device monitors the interaction data between the first domain controller and the second domain controller, and sends the interaction data to the host computer, the host computer including a test management module; and the test management module obtains the data parameters in the interaction data.

[0014] In one embodiment of the present invention, the process of monitoring the interaction data between the first domain controller and the second domain controller through the test parameter monitoring device and sending the interaction data to the host computer includes: receiving the interaction data between the first domain controller and the second domain controller through the test parameter monitoring device, converting the interaction data into software interface adaptation layer data, and then sending it to the test management module.

[0015] According to one aspect of the present invention, an automated testing device for automotive domain controllers is provided. The automated testing device includes: a system acquisition module, configured to acquire a pre-built domain controller testing system, predefined domain controller test actions, and predefined domain controller test parameters, wherein the predefined domain controller test actions correspond to the predefined domain controller test parameters, and the domain controller testing system includes a test action execution device and a test parameter monitoring device; an execution control module, configured to control the test action execution device to execute the predefined domain controller test actions and monitor the data parameters during the execution of the predefined domain controller test actions through the test parameter monitoring device; and a result judgment module, configured to compare the predefined domain controller test parameters with the data parameters monitored by the test parameter monitoring device to obtain a parameter comparison result, and to determine whether the domain controller test has passed based on the parameter comparison result.

[0016] According to one aspect of the present invention, an electronic device is provided, the electronic device comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device enables the automated testing method for automotive domain controllers as described above.

[0017] According to one aspect of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a computer's processor, causes the computer to perform the aforementioned automated testing method for automotive domain controllers.

[0018] The beneficial effects of this invention are as follows: This invention acquires a pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters. It controls the test action execution device to execute the predefined domain controller test actions and monitors the data parameters during the execution of the corresponding test actions through a test parameter monitoring device. The predefined domain controller test parameters are compared with the data parameters during the execution of the corresponding test actions to obtain the parameter comparison results. The domain controller test results are then determined based on the parameter comparison results. This testing process does not require a large amount of learning time to train the robotic arm to simulate user actions, thereby reducing testing time and improving testing efficiency. In addition, the first domain controller is connected to multiple second domain controllers simultaneously, and the test parameter monitoring device is connected in series to multiple connection links, allowing for simultaneous testing of multiple domain controllers and meeting various testing conditions.

[0019] 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

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

[0021] Figure 1 This is a schematic diagram illustrating an implementation environment for testing an automotive domain controller, as shown in an exemplary embodiment of this application.

[0022] Figure 2 This is a flowchart illustrating an automated testing method for an automotive domain controller, as shown in an exemplary embodiment of this application.

[0023] Figure 3 This is a block diagram illustrating an automated testing architecture for an automotive domain controller, as shown in an exemplary embodiment of this application.

[0024] Figure 4 This is a block diagram illustrating the connection of a first domain controller, a second domain controller, and a test parameter monitoring device, as shown in an exemplary embodiment of this application.

[0025] Figure 5 This is a block diagram illustrating an automated testing apparatus for an automotive domain controller, as shown in an exemplary embodiment of this application.

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

[0027] The embodiments of the present invention 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 the present invention from the content disclosed in this specification. The present invention 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 the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0028] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention 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 invention. However, it will be apparent to those skilled in the art that embodiments of the invention 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 invention.

[0030] First, it should be noted that Data Distribution Service (DDS) is a new generation of distributed real-time communication middleware protocol. Its high real-time performance, high reliability, open architecture, and decoupled publish / subscribe performance greatly accelerate and simplify the development of distributed systems, making it very suitable for the automotive field. It can not only meet the needs of big data transmission in the intelligent driving domain of automobiles, but also meet the requirements of Service-Oriented Architecture (SOA).

[0031] Figure 1 An exemplary embodiment of this application illustrates a schematic diagram of an implementation environment for testing an automotive domain controller, with reference to... Figure 1As shown, the system architecture may include a system setup device 101 and a computer device 102. The computer device 102 may be at least one of a desktop graphics processing unit (GPU) computer, a GPU computing cluster, or a neural network computer. Technical personnel can use the computer device 102 to obtain a pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters. They can control the test action execution device to execute the predefined domain controller test actions and monitor the data parameters during the execution of the corresponding test actions through a test parameter monitoring device. The predefined domain controller test parameters are compared with the data parameters during the execution of the corresponding test actions to obtain the parameter comparison results, and the domain controller test results are determined based on the parameter comparison results. The system setup device 101 is used to obtain the built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters. In this embodiment, the system setup device 101 builds the domain controller test system according to the actual interface definitions, network topology diagram, and electrical schematic diagram, and provides it to the computer device 102 for processing.

[0032] In a schematic manner, after acquiring the domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters built by the system building equipment 101, the computer device 102 controls the test action execution device to execute the predefined domain controller test actions and monitors the data parameters during the execution of the corresponding test actions through the test parameter monitoring device. The predefined domain controller test parameters are compared with the data parameters during the execution of the corresponding test actions to obtain the parameter comparison results. Based on the parameter comparison results, the domain controller test results are determined. The above test process does not require a large amount of learning time to train the robotic arm to simulate user actions, thereby reducing test time and improving test efficiency. In addition, the first domain controller is connected to multiple second domain controllers simultaneously, and the test parameter monitoring device is connected in series to multiple connection links, which can test multiple domain controllers simultaneously and meet various test conditions.

[0033] It should be noted that the automated testing method for automotive domain controllers provided in this application embodiment is generally executed by computer device 102, and correspondingly, the automated testing device for automotive domain controllers is generally set in computer device 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 automated testing method for an automotive domain controller, as shown in an exemplary embodiment of this application. This automated testing method for an automotive domain controller can be executed by a computing processing device, which may be... Figure 1The computer device 102 shown is illustrated. (Refer to...) Figure 2 As shown, this automated testing method for automotive domain controllers includes at least steps S210 to S230, which are detailed below:

[0036] In step S210, the pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters are obtained.

[0037] In one embodiment of this application, predefined domain controller test actions correspond to predefined domain controller test parameters, and the domain controller test system includes test action execution equipment and test parameter monitoring equipment.

[0038] In this embodiment, the device executing the test action can be a robotic arm or other execution device. The predefined domain controller test action is to simulate user actions by using the robotic arm to operate related functions of the central control screen. The predefined domain controller test parameters are parameter values ​​set for the predefined domain controller test action.

[0039] In step S220, the control test action execution device executes the predefined domain controller test action, and the test parameter monitoring device monitors the data parameters during the execution of the predefined domain controller test action.

[0040] In this embodiment, the test parameter monitoring device is connected to the domain controller, and the central control screen is connected to the domain controller. When the robot clicks the function button on the central control screen, the test parameter monitoring device will monitor the data parameters sent by the central control screen to the domain controller based on the predefined domain controller test actions, as well as the data parameters fed back by the domain controller to the central control screen based on the data parameters of the central control screen.

[0041] In step S230, the predefined domain controller test parameters are compared with the data parameters monitored by the test parameter monitoring device to obtain the parameter comparison result, so as to determine whether the domain controller test passes based on the parameter comparison result.

[0042] In this embodiment, if the predefined domain controller test parameters are consistent with the data parameters monitored by the test parameter monitoring device, the parameter comparison results are consistent, and the domain controller test is determined to be passed; if the predefined domain controller test parameters are inconsistent with the data parameters monitored by the test parameter monitoring device, the parameter comparison results are inconsistent, and the domain controller test is determined to be failed.

[0043] In this embodiment, by acquiring a pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters, the test action execution device is controlled to execute the predefined domain controller test actions, and the data parameters during the execution of the corresponding test actions are monitored by the test parameter monitoring device. The predefined domain controller test parameters are compared with the data parameters during the execution of the corresponding test actions to obtain the parameter comparison results. The domain controller test results are then determined based on the parameter comparison results. This testing process does not require a large amount of learning time to train the robotic arm to simulate user actions, thereby reducing testing time and improving testing efficiency.

[0044] In one embodiment of this application, the process of controlling the test action execution device to execute predefined domain controller test actions includes:

[0045] Get the number of test actions for the predefined domain controller.

[0046] In this embodiment, there can be one or more predefined domain controller test actions. The number of predefined domain controller test actions can be determined according to the functions that the domain controller needs to test.

[0047] If the number of predefined domain controller test actions is greater than the first quantity threshold, obtain the timing sequence between multiple predefined domain controller test actions.

[0048] In this embodiment, the first quantity threshold can be 1 or other values. When there are multiple predefined domain controller test actions, the timing of multiple predefined domain controller test actions needs to be preset.

[0049] The control test execution device performs actions according to the timing sequence between multiple predefined domain controller test actions.

[0050] In this embodiment, when the test action execution device performs actions according to the timing sequence between multiple predefined domain controller test actions, the test parameter monitoring device can monitor multiple data parameters sent by the central control screen to the domain controller based on the timing sequence of multiple predefined controller test actions, as well as multiple data parameters fed back by the domain controller to the central control screen based on the data parameters of the central control screen.

[0051] In this embodiment, the predefined domain controller test parameters include multiple test parameters sent by the central control screen to the domain controller based on the timing of multiple predefined controller test actions, and multiple test parameters fed back by the domain controller to the central control screen based on the test parameters of the central control screen.

[0052] In one embodiment of this application, after obtaining the timing sequence between multiple predefined domain controller test actions, the process includes:

[0053] Get the displayed screen.

[0054] In this embodiment, the displayed screen is obtained from the feedback of the test action execution device executing the predefined domain controller test action. The displayed screen includes the predefined domain controller test action executed by the test action execution device and the execution result obtained by the test action execution device executing the predefined domain controller test action. For example, when the robot clicks the central control screen according to the predefined controller test action, the image acquisition device such as the camera acquires and stores the robot's action of clicking the central control screen display interface and the execution result obtained after the robot clicks the central control screen display interface.

[0055] In this embodiment, when there are multiple predefined domain controller test actions, the display screen includes multiple execution actions and execution results corresponding to each of the multiple execution actions.

[0056] Determine whether the actions executed on the displayed screen are consistent with the test actions of the corresponding predefined domain controller, and obtain the test action comparison results.

[0057] In this embodiment, if the execution action in the display screen is consistent with the predefined domain controller test action, and the execution result corresponding to the execution action in the display screen is consistent with the result corresponding to the predefined domain controller test action, then the test action comparison is consistent; otherwise, the test action comparison is inconsistent.

[0058] In this embodiment, when there are multiple predefined domain controller test actions, the execution actions in the display screen are compared with the predefined domain controller test actions according to the timing sequence between the multiple predefined domain controller test actions. If the execution actions in the display screen are consistent with the predefined domain controller test actions, and the execution result corresponding to the execution action in the display screen is consistent with the result corresponding to the predefined domain controller test action, then the test actions are consistent; otherwise, the test actions are inconsistent.

[0059] In one embodiment of this application, the process of comparing predefined domain controller test parameters with data parameters monitored by a test parameter monitoring device to obtain a parameter comparison result, and determining whether the domain controller test passes based on the parameter comparison result, includes:

[0060] Obtain the test action comparison results, which include: test actions match and test actions do not match. Parameter comparison results include: parameter matches and parameter does not match.

[0061] In this embodiment, during or after the test, the multiple data parameters sent by the central control screen to the domain controller based on the timing of multiple predefined controller test actions are compared with the multiple test parameters sent by the central control screen to the domain controller based on the timing of multiple predefined controller test actions. Additionally, the multiple data parameters fed back to the central control screen by the domain controller based on the central control screen's test parameters are compared with the multiple test parameters fed back to the central control screen by the domain controller based on the central control screen's test parameters. If all data parameters match all test parameters, the parameter comparison is determined to be consistent; otherwise, the parameter comparison is determined to be inconsistent.

[0062] If the test action comparison results show that the test actions match and the parameter comparison results show that the parameters match, the domain controller test is considered passed; otherwise, the domain controller test is considered failed.

[0063] In this embodiment, the test action comparison results and parameter comparison results are combined. When the test action comparison results show that the test actions match and the parameter comparison results show that the parameters match, the domain controller test is determined to be passed, thus improving the accuracy of the domain controller test.

[0064] In one embodiment of this application, before obtaining the pre-built domain controller test system, the following steps are included:

[0065] The test action execution device is connected to the first domain controller. By connecting the first domain controller to multiple second domain controllers, multiple connection links are obtained. The test parameter monitoring device is connected in series to multiple connection links and connected to the host computer to obtain a pre-built domain controller test system. Domain controller testing is then performed based on the pre-built domain controller test system.

[0066] In this embodiment, the first domain controller can be a diesel injection electronic control system, etc., and the second domain controller can be a vehicle interface unit, etc. The first domain controller is connected to the host computer, and the second domain controller is connected to the host computer.

[0067] In this embodiment, by connecting the first domain controller with multiple second domain controllers to obtain multiple connection links, and connecting the test parameter monitoring device in series with multiple connection links, multiple domain controllers can be tested simultaneously, which can meet a variety of test conditions.

[0068] In this embodiment, when the test action execution device executes a predefined domain controller test action, the first domain controller detects the execution action of the test action execution device, calls the DDS in the second domain controller and sends the DDS to the second domain controller. After receiving the DDS, the second domain controller returns a data parameter to the first domain controller. During the data interaction between the first and second domain controllers, the test parameter monitoring device monitors the data parameters sent by the first domain controller to the second domain controller and the data parameters fed back by the second domain controller to the first domain controller. The test parameter monitoring device connects to the host computer through a vehicle Ethernet to industrial Ethernet converter box, and then through a switch. The host computer compares the data parameters with the predefined domain controller test parameters to obtain the parameter comparison result.

[0069] In this embodiment, when the test action execution device executes a predefined domain controller test action, after the first domain controller detects the execution action of the test action execution device, the first domain controller sends the data parameters of the test action execution device to the host computer, thereby monitoring the data parameters between the first domain controller and the test action execution device, and comparing the data parameters with the predefined domain controller test parameters through the host computer to obtain the parameter comparison result.

[0070] In this embodiment, after receiving the DDS, the second domain controller converts the received DDS into a corresponding Controller Area Network (CAN) signal and sends it to its downstream corresponding controller. Upon receiving this CAN signal, the corresponding controller executes the corresponding operation to drive the load. After completing this series of signal transfers, the downstream corresponding controller sends a CAN signal back to the second domain controller via the same path. At this time, the second domain controller performs the CAN signal to DDS conversion operation and notifies the downstream controller of the DDS conversion. This enables the monitoring of data parameters between the second domain controller and its downstream corresponding controller. The host computer then compares the data parameters with predefined domain controller test parameters to obtain the parameter comparison results.

[0071] In one embodiment of this application, the process of monitoring data parameters during the execution of a predefined domain controller test action using a test parameter monitoring device includes:

[0072] When the test action execution device performs a predefined domain controller test action, it sends the signal data corresponding to the predefined domain controller test action to the first domain controller.

[0073] In this embodiment, when the test action execution device performs a predefined domain controller test action, the test action execution device sends signal data corresponding to the predefined domain controller test action to the first domain controller, so that the first domain controller can detect the execution action of the test action execution device. The signal data includes data parameters.

[0074] When the first domain controller and the second domain controller interact with each other based on signal data, the interaction data between the first domain controller and the second domain controller is monitored by the test parameter monitoring device, and the interaction data is sent to the host computer, which includes a test management module.

[0075] In this embodiment, the information interaction process between the first domain controller and the second domain controller based on signal data includes: after the first domain controller detects the execution action of the test action execution device, it calls the Data Distribution Service (DDS) in the second domain controller and sends the DDS to the second domain controller. After receiving the DDS, the second domain controller returns a data parameter to the first domain controller. During the data interaction between the first and second domain controllers, the test parameter monitoring device monitors the data parameters sent by the first domain controller to the second domain controller and the data parameters fed back by the second domain controller to the first domain controller. The test parameter monitoring device connects to the host computer through a vehicle Ethernet to industrial Ethernet converter box and then through a switch and sends the data parameters to the host computer. In this process, the interactive data includes all data parameters in the interaction process, and the host computer compares the data parameters with the predefined domain controller test parameters to obtain the parameter comparison result.

[0076] Data parameters are obtained from the interactive data through the test management module.

[0077] In this embodiment, the test management module is used to receive data parameters sent by the test parameter monitoring device, or to actively request the test parameter monitoring device to send data parameters. The data parameters are contained in the CAN database file (DBC) and the interface definition language (IDL) file, where CAN is short for Controller Area Network.

[0078] In one embodiment of this application, the process of monitoring the interaction data between the first domain controller and the second domain controller through a test parameter monitoring device and sending the interaction data to the host computer includes:

[0079] The test parameter monitoring device receives the interaction data between the first domain controller and the second domain controller, converts the interaction data into software interface adaptation layer data, and then sends it to the test management module.

[0080] In this embodiment, the software interface adaptation layer serves as a bridge between the test parameter monitoring device and the test management module. It enables data interaction between the test parameter monitoring device and the test management module by converting interactive data into data from the software interface adaptation layer.

[0081] In this embodiment, the test parameter monitoring device is an application developed based on the DDS protocol stack. Here, the implementation method, version or code of the application are not specifically limited.

[0082] This application acquires a pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters. It controls a test action execution device to execute the predefined domain controller test actions and monitors the data parameters during the execution of the corresponding test actions using a test parameter monitoring device. The predefined domain controller test parameters are compared with the data parameters during the execution of the corresponding test actions to obtain the parameter comparison results. Based on the parameter comparison results, the domain controller test results are determined. This testing process eliminates the need for extensive training of a robotic arm to simulate user actions, thereby reducing testing time and improving testing efficiency. Furthermore, the first domain controller can be connected to multiple second domain controllers simultaneously, and the test parameter monitoring device can be connected in series to multiple links, allowing for simultaneous testing of multiple domain controllers and meeting various testing conditions.

[0083] Figure 3 This is a block diagram illustrating an automated testing architecture for an automotive domain controller, as shown in an exemplary embodiment of this application. Please refer to [link / reference]. Figure 3As shown, the automated testing architecture for automotive domain controllers includes: a host computer, an automated equipment cabinet, a test bench, and a hardware-in-the-loop (HIL) cabinet. The HIL cabinet houses various boards to simulate and acquire various signals from the domain controller. The automated equipment cabinet includes a central control screen, test action execution devices (actuators), and a high-definition camera. The test action execution devices simulate user actions to operate relevant functions on the central control screen, and the high-definition camera captures the displayed images on the central control screen. The test bench includes domain controller A and its downstream loads, domain controller B and its downstream loads, and domain controller C and its downstream loads. Domain controller A is connected to domain controller B, and domain controller B is connected to domain controller C. Domain controllers A, B, and C are all connected to a switch via an industrial Ethernet to vehicle Ethernet converter box. The switch is then connected to a host computer. The host computer is pre-configured with a test management module (i.e., test management software) and automated testing software. The automated testing software is used to write test procedure scripts based on the test functions of the domain controllers. The test scripts predefine the domain controller test actions, predefine the domain controller test parameters, and predefine the domain controller test... The timing of actions, etc., and control the test action execution equipment to simulate user actions to operate the relevant functions of the central control screen. The test management software is used to obtain the interaction data of domain controller A and its downstream load, domain controller B and its downstream load, and domain controller C and its downstream load monitored by the test parameter monitoring equipment when the test action execution equipment simulates user actions to operate the relevant functions of the central control screen. The software sends the data parameters in the interaction data to the automated test software. The automated test software compares the data parameters with the predefined domain controller test parameters according to the timing of the predefined domain controller test actions to obtain the parameter comparison results.

[0084] In this embodiment, the automated testing process of the automotive domain controller includes: (1) building an automated testing architecture for the automotive domain controller by referring to the actual interface definition, network topology diagram and electrical schematic diagram; (2) connecting the test parameter monitoring device in series with the first connection link (CAN bus) formed by the connection between domain controller A and domain controller B and the second connection link (CAN bus) formed by the connection between domain controller B and domain controller C through a VN5650 switch, and connecting the test parameter monitoring device to the switch through an industrial Ethernet to vehicle Ethernet converter box, and then connecting the switch to the host computer; (3) the first domain controller (diesel injection electronic controller system) downloads the corresponding service code list, IDL file and DBC file in the automated testing software, and tests it in the test management module (Automotive Bus Development Environment (CANoe, CAN open)). In the environment settings, set the corresponding baud rate, sampling points, and other parameters. The CAN bus channels correspond one-to-one with the test parameter monitoring device channels. Finally, import the corresponding DBC files into the test parameter monitoring device and the test management module. When a test node sends a message to the bus, the test parameter monitoring device can collect the message and send it to the host computer test management software. The test management software can then obtain the data parameters in the CAN message. In addition, virtual nodes can also be added to the bus, and CAN messages can be simulated to be sent to the bus through these nodes. This makes it very convenient to perform online monitoring of CAN messages.

[0085] In this embodiment, the test parameter monitoring device is an application developed based on the DDS protocol stack. The test parameter monitoring device acts as a bridge between CANoe and the system under test. After the test parameter monitoring device and CANoe are started, they will submit registration to the registration machine. The registration information mainly includes Internet Protocol Address (IP address) and port number. The data communication and interaction between the test parameter monitoring device, CANoe and the system under test are realized through the registration information.

[0086] Figure 4 An exemplary embodiment of this application illustrates a block diagram showing the connection of a first domain controller, a second domain controller, and a test parameter monitoring device. Please refer to [link to relevant documentation]. Figure 4 As shown, the test parameter monitoring device is connected to the link between the first domain controller and the second domain controller via a VN5650 switch, and then connected to the switch via an industrial Ethernet to vehicle Ethernet converter box. The switch is then connected to the host computer, so that the test parameter monitoring device can participate in the communication of the node under test.

[0087] In this embodiment, the test parameter monitoring device can participate in the system's communication like a regular DDS node, subscribing to all interactive topics in the system. When domain controllers interact within the system, it can listen to these topics. For example, when the first domain controller sends topic 1 to the second domain controller, the test parameter monitoring device can receive topic 1; when the second domain controller sends topic 2 to the first domain controller, the test parameter monitoring device can also receive topic 2; and when the test parameter monitoring device sends topic 3, both the first and second domain controllers can receive topic 3. Simultaneously, it can also publish subscribed topics by simulating a non-existent area controller in the system (automation equipment cabinet). The DDS service data parameters required by the test parameter monitoring device are stored in these topics. The test parameter monitoring device then converts the received topic data into software interface adaptation layer data before forwarding it to CANoe.

[0088] In this embodiment, the process of the automated equipment cabinet automatically executing the predefined domain controller's actions includes: (1) writing a script on the automated test software to execute the test steps, and using the script to control the actuator (robotic arm) in the equipment cabinet to simulate user actions to operate the relevant functions of the central control screen. After the first domain controller detects the user operation, it will call the corresponding DDS service in the second domain controller (domain controller A, domain controller B, or domain controller C) and send the DDS service to the second domain controller. After receiving the DDS service, the second domain controller will return a service value to the first domain controller. During this process, the DDS service will also pass through a vehicle Ethernet to industrial Ethernet conversion box, and then through a switch to reach the test management software in the host computer to realize the monitoring of data parameters. (2) The second domain controller will convert the received DDS service into a corresponding CAN signal and send it to the corresponding controller connected to it. Similarly, when the CAN signal flows through the test parameter monitoring equipment, it will also be monitored by the test management software. After receiving the CAN signal, the controller will execute the corresponding operation to drive the load. After completing this series of signal flows, the downstream controller will send another CAN signal back to the second domain controller. At this time, the second domain controller will perform the CAN signal to DDS service conversion operation and notify the first domain controller of the converted DDS service. Similarly, the signal flow in this process will also be monitored. After the test management software monitors all data parameters generated during the user operation, the automated test software will read these DDS service and CAN signal data parameters through the serial communication interface. At the same time, it will compare and verify with the test parameters defined in the service list. If all monitored data parameters are consistent with the predefined domain controller test parameters, and the high-definition camera in the automated equipment cabinet recognizes the correct changes on the central control screen display interface, and the load device performs the correct action, then the test can be judged as passed. If the monitored data parameters are inconsistent with the predefined domain controller test parameters in the service list, or if relevant user data is not sent according to the actual logic, or if the load does not perform the corresponding action according to the actual logic, or if the camera does not recognize the corresponding changes on the central control screen display interface, then the test is judged as failed.

[0089] In this embodiment, since receiving DDS service is more difficult than receiving CAN signal, traditional hardware-in-the-loop testing schemes cannot currently support the parsing of DDS service data. If Ethernet data cannot be captured during the test, and test conclusions are given only from the input or output signals, the integrity of the test link cannot be guaranteed, and the test process has significant defects.

[0090] Therefore, this application employs a test parameter monitoring device (developing an application to subscribe to middleware services) to collect and parse service data, solving the problems of CAN signal and DDS service acquisition and simulation. It can capture all data parameters required during domain controller testing in real time, facilitating online analysis by testers. After real-time data parameter acquisition, the automated test software reads these parameters through a serial communication interface, compares and analyzes them with the test parameter values ​​defined in the corresponding version's software integration service list, and controls the test action execution device to simulate relevant user actions, thereby providing test conclusions. This method not only automates testing, improving efficiency, but also meets the testing conditions of multiple domain controllers, saving testing costs. Furthermore, the use of actuators and high-definition cameras for function wake-up better reflects actual user scenarios and ensures the integrity of the test chain.

[0091] The following describes an embodiment of the apparatus described in this application, which can be used to execute the automated testing method for automotive domain controllers 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 automated testing method for automotive domain controllers described above.

[0092] Figure 5 This is a block diagram illustrating an automated testing apparatus for an automotive domain controller, as shown in an exemplary embodiment of this application. The apparatus can be applied to… Figure 1 The implementation environment shown is specifically configured in computer device 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.

[0093] like Figure 5 As shown, this exemplary automated testing apparatus for automotive domain controllers includes:

[0094] The system acquisition module 501 is used to acquire the pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters. The predefined domain controller test actions correspond to the predefined domain controller test parameters. The domain controller test system includes test action execution equipment and test parameter monitoring equipment.

[0095] The execution control module 502 is used to control the test action execution device to execute the predefined domain controller test action and to monitor the data parameters during the execution of the predefined domain controller test action through the test parameter monitoring device.

[0096] The result judgment module 503 is used to compare the predefined test parameters of the domain controller with the data parameters monitored by the test parameter monitoring device to obtain the parameter comparison result, and to determine whether the domain controller test has passed based on the parameter comparison result.

[0097] In one embodiment of this application, predefined domain controller test actions correspond to predefined domain controller test parameters, and the domain controller test system includes test action execution equipment and test parameter monitoring equipment.

[0098] In this embodiment, the device executing the test action can be a robotic arm or other execution device. The predefined domain controller test action is to simulate user actions by using the robotic arm to operate related functions of the central control screen. The predefined domain controller test parameters are parameter values ​​set for the predefined domain controller test action.

[0099] In this embodiment, the test parameter monitoring device is connected to the domain controller, and the central control screen is connected to the domain controller. When the robot clicks the function button on the central control screen, the test parameter monitoring device will monitor the data parameters sent by the central control screen to the domain controller based on the predefined domain controller test actions, as well as the data parameters fed back by the domain controller to the central control screen based on the data parameters of the central control screen.

[0100] In this embodiment, if the predefined domain controller test parameters are consistent with the data parameters monitored by the test parameter monitoring device, the parameter comparison results are consistent, and the domain controller test is determined to be passed; if the predefined domain controller test parameters are inconsistent with the data parameters monitored by the test parameter monitoring device, the parameter comparison results are inconsistent, and the domain controller test is determined to be failed.

[0101] In this embodiment, by acquiring a pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters, the test action execution device is controlled to execute the predefined domain controller test actions, and the data parameters during the execution of the corresponding test actions are monitored by the test parameter monitoring device. The predefined domain controller test parameters are compared with the data parameters during the execution of the corresponding test actions to obtain the parameter comparison results. The domain controller test results are then determined based on the parameter comparison results. This testing process does not require a large amount of learning time to train the robotic arm to simulate user actions, thereby reducing testing time and improving testing efficiency.

[0102] It should be noted that the automated testing device for automotive domain controllers provided in the above embodiments and the automated testing method for automotive domain controllers provided in the above embodiments belong to the same concept. The specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here. In practical applications, the automated testing device for automotive domain controllers 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, and this is not a limitation here.

[0103] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the automated testing method for automotive domain controllers provided in the above embodiments.

[0104] Figure 6 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 6 The computer system 600 of the electronic 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.

[0105] like Figure 6 As shown, the computer system 600 includes a Central Processing Unit (CPU) 601, 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) 602 or programs loaded from Storage Unit 608 into Random Access Memory (RAM) 603. The RAM 603 also stores various programs and data required for system operation. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An Input / Output (I / O) interface 605 is also connected to the bus 604.

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

[0107] 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 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs various functions defined in the system of this application.

[0108] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage 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 computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

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

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

[0111] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a computer's processor, causes the computer to perform the aforementioned automated testing method for automotive domain controllers. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not incorporated into the electronic device.

[0112] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the automated testing method for automotive domain controllers provided in the various embodiments described above.

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

Claims

1. An automated testing method for automotive domain controllers, characterized in that, The automated testing method for the automotive domain controller includes: The system acquires a pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters. The predefined domain controller test actions correspond to the predefined domain controller test parameters. The domain controller test system includes test action execution equipment and test parameter monitoring equipment. The test action execution device is controlled to execute the predefined domain controller test action, and the test parameter monitoring device monitors the data parameters during the execution of the predefined domain controller test action; specifically, when the test action execution device executes the predefined domain controller test action, the test action execution device sends signal data corresponding to the predefined domain controller test action to the first domain controller; when the first domain controller and the second domain controller interact based on the signal data, the test parameter monitoring device monitors the interaction data between the first domain controller and the second domain controller; the test parameter monitoring device is developed based on the data distribution service protocol stack, and the interaction data includes data distribution service data corresponding to the signal data, and data distribution service data generated after responding to the signal data; the second domain controller is used to convert the data distribution service data corresponding to the signal data into the corresponding controller local area network signal and send it to the corresponding downstream controller, and is used to convert the controller local area network signal returned by the downstream controller based on the response to the signal data into the corresponding data distribution service data and send it to the first domain controller; The predefined domain controller test parameters are compared with the data parameters monitored by the test parameter monitoring device to obtain the parameter comparison result, and the domain controller test is judged based on the parameter comparison result. Before obtaining the pre-built domain controller test system, the process includes: connecting the test action execution device to the first domain controller; connecting the first domain controller to multiple second domain controllers to obtain multiple connection links; connecting the test parameter monitoring device in series to the multiple connection links and connecting the test parameter monitoring device to a host computer to obtain the pre-built domain controller test system, so as to perform domain controller testing based on the pre-built domain controller test system.

2. The automated testing method for automotive domain controllers according to claim 1, characterized in that, The process of controlling the test action execution device to execute the predefined domain controller test action includes: Obtain the number of test actions for the predefined domain controller; If the number of test actions of the predefined domain controller is greater than the first quantity threshold, obtain the timing sequence between the multiple test actions of the predefined domain controller; The device that controls the test action execution operates according to the timing sequence between the test actions of the multiple predefined domain controllers.

3. The automated testing method for automotive domain controllers according to claim 2, characterized in that, After obtaining the timing sequence between multiple predefined domain controller test actions, the process includes: The display screen is obtained by the test action execution device executing the predefined domain controller test action; Determine whether the action executed in the displayed screen is consistent with the test action of the corresponding predefined domain controller, and obtain the test action comparison result.

4. The automated testing method for automotive domain controllers according to claim 3, characterized in that, The process of comparing the predefined domain controller test parameters with the data parameters monitored by the test parameter monitoring device to obtain the parameter comparison result, and determining whether the domain controller test passes based on the parameter comparison result, includes: The test action comparison results are obtained, including: test actions match and test actions do not match; the parameter comparison results are including: parameter matches and parameter does not match. If the test action comparison result is consistent and the parameter comparison result is consistent, the domain controller test is deemed to have passed; otherwise, the domain controller test is deemed to have failed.

5. The automated testing method for automotive domain controllers according to any one of claims 1-4, characterized in that, The process of monitoring data parameters during the execution of test actions of the predefined domain controller using the test parameter monitoring device includes: The interactive data is sent to the host computer, which includes an experiment management module; The data parameters in the interactive data are obtained through the test management module.

6. The automated testing method for automotive domain controllers according to claim 5, characterized in that, The process of monitoring the interaction data between the first domain controller and the second domain controller through the test parameter monitoring device and sending the interaction data to the host computer includes: The test parameter monitoring device receives the interaction data between the first domain controller and the second domain controller, converts the interaction data into software interface adaptation layer data, and then sends it to the test management module.

7. An automated testing device for automotive domain controllers, characterized in that, The automated testing device for the automotive domain controller includes: The system acquisition module is used to acquire a pre-built domain controller test system, predefined domain controller test actions, and predefined domain controller test parameters. The predefined domain controller test actions correspond to the predefined domain controller test parameters. The domain controller test system includes test action execution equipment and test parameter monitoring equipment. An execution control module is used to control the test action execution device to execute the predefined domain controller test action and to monitor the data parameters during the execution of the predefined domain controller test action through the test parameter monitoring device. Specifically, this includes: when the test action execution device executes the predefined domain controller test action, sending signal data corresponding to the predefined domain controller test action to the first domain controller; when the first domain controller and the second domain controller interact based on the signal data, monitoring the interaction data between the first domain controller and the second domain controller through the test parameter monitoring device; the test parameter monitoring device is developed based on a data distribution service protocol stack, and the interaction data includes data distribution service data corresponding to the signal data and data distribution service data generated after responding to the signal data; the second domain controller is used to convert the data distribution service data corresponding to the signal data into a corresponding controller local area network (LAN) signal and send it to the corresponding downstream controller, and to convert the LAN signal returned by the downstream controller based on the response to the signal data into corresponding data distribution service data and send it to the first domain controller; The result judgment module is used to compare the predefined domain controller test parameters with the data parameters monitored by the test parameter monitoring device to obtain the parameter comparison result, and to determine whether the domain controller test passes based on the parameter comparison result; Before obtaining the pre-built domain controller test system, the process includes: connecting the test action execution device to the first domain controller; connecting the first domain controller to multiple second domain controllers to obtain multiple connection links; connecting the test parameter monitoring device in series to the multiple connection links and connecting the test parameter monitoring device to a host computer to obtain the pre-built domain controller test system, so as to perform domain controller testing based on the pre-built domain controller test system.

8. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the automotive domain controller automated testing method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by the computer's processor, causes the computer to perform the automated testing method for the automotive domain controller as described in any one of claims 1 to 6.

Images