Vehicle body controller test method and test system, equipment and medium thereof

By automatically testing the body controller based on the communication architecture, the inconvenience and inaccuracy of manual hard-wire control in the prior art are solved, and efficient and accurate body controller testing is achieved.

CN119087955APending Publication Date: 2024-12-06VOYAH AUTOMOBILE TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411039586.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-31
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing body controller testing equipment requires manual hardwire control, which leads to inconvenience and low accuracy, making it impossible to achieve efficient automated testing.

Method used

Using a communication architecture-based method, a test execution file is generated by obtaining test case configuration information and communication architecture information, and automated testing is performed in combination with interface variables, simulating the functional operations of the vehicle body controller, generating test results and comparing the expected results.

Benefits of technology

The automated testing of the body controller is realized, which improves the convenience and accuracy of the test, reduces the uncertainty of manual testing, reduces the manual investment in system development and test execution, and improves the testing efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119087955A_ABST
    Figure CN119087955A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of vehicle testing, and discloses a testing method of a vehicle body controller, a testing system of the vehicle body controller, equipment and a medium. The method comprises the following steps: acquiring an interface configuration file of test case configuration information of a to-be-tested vehicle body controller, wherein the interface configuration file comprises a plurality of interface variables; according to the test case configuration information and the communication architecture information of the to-be-tested vehicle body controller, generating a corresponding test execution file; carrying out binding association on the test execution subfile and the interface variable; and obtaining a target test case, calling the corresponding first interface variable and the target test execution sub-file according to the target test case, and running the target test execution sub-file to obtain a test result of the target test case. According to the method provided by the invention, the vehicle body controller can be automatically tested on the basis of the communication architecture, and the problems of inconvenience and relatively low accuracy caused by manual hardwired control of the vehicle body controller in the prior art are solved.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0002] The main functions of the body control module (BCM) include: external light control, internal light control, door lock control, wiper control, window and sunroof control, etc. The scope involved is the most common scenarios in the use of the vehicle. The correctness of the function of BCM during use is very important for the normal use of the vehicle.

[0003] In existing vehicles, high requirements are placed on BCM test equipment during controller development, and it is often necessary to develop a corresponding load box for manual testing, which brings great inconvenience and a high risk of inaccuracy due to manual testing. Summary of the invention

[0004] The present application provides a testing method for a vehicle body controller and its testing system, equipment, and medium, which can perform automated testing on the vehicle body controller based on a communication architecture, solving the problems of inconvenience and low accuracy caused by the need for manual hard-wired control of the vehicle body controller in the prior art.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to one aspect of an embodiment of the present application, a method for testing a vehicle body controller is provided, the method comprising:

[0007] Obtaining an interface configuration file of test case configuration information of the vehicle body controller to be tested, wherein the interface configuration file includes a plurality of interface variables;

[0008] Generate a corresponding test execution file according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested, wherein the test execution file includes a plurality of test execution sub-files;

[0009] Binding and associating the test execution subfile with the interface variable;

[0010] A target test case is obtained, a corresponding first interface variable and a target test execution subfile are called according to the target test case, and the target test execution subfile is run to obtain a test result of the target test case.

[0011] In one embodiment of the present application, based on the above solution, before obtaining the interface configuration file of the test case configuration information of the vehicle body controller to be tested, it also includes:

[0012] Acquire test case configuration information of the vehicle body controller to be tested, wherein the test case configuration information includes a plurality of predefined message information and execution action information;

[0013] The message information and the execution action information are defined as corresponding interface variables according to preset configuration rules to generate the interface configuration file.

[0014] In one embodiment of the present application, based on the above solution, generating a corresponding test execution file according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested includes:

[0015] Based on the communication architecture information, each of the message information and each of the execution action information in the test case configuration information is used to generate corresponding test codes in a preset format;

[0016] Generate the test execution file according to each of the test codes;

[0017] Wherein, the test execution sub-file is the test code.

[0018] In one embodiment of the present application, based on the above solution, the target test case includes multiple test elements, and calling the corresponding first interface variable and the target test execution subfile according to the target test case includes:

[0019] For each of the test elements, the interface variable corresponding to the test element and the target test code corresponding to the test element are called to run the target test code to obtain the test result of the test element.

[0020] In one embodiment of the present application, based on the above solution, after running the target test execution subfile to obtain the test result of the target test case, it also includes:

[0021] Calling a corresponding second interface variable according to the target test case, where the second interface variable is an expected result variable corresponding to the test result;

[0022] The expected result variables are compared with the test result variables to generate a test report.

[0023] In one embodiment of the present application, based on the above solution, before obtaining the target test case, it also includes:

[0024] In response to a user's interface variable definition request, a corresponding control interface is generated according to the interface variable definition request, so that when the control interface is called, a target interface variable corresponding to the interface variable definition request is assigned or retrieved.

[0025] In one embodiment of the present application, based on the aforementioned solution, the method is applied to a vehicle adopting a service-oriented architecture.

[0026] According to one aspect of an embodiment of the present application, a vehicle body controller test system is further provided, the system being used to execute the method described in the above embodiment, the system comprising:

[0027] A configuration unit, wherein the configuration unit is configured to: obtain an interface configuration file of test case configuration information of the vehicle body controller to be tested, wherein the interface configuration file includes a plurality of interface variables;

[0028] A file generating unit, wherein the test executing unit is configured to: generate a corresponding test executing file according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested, wherein the test executing file includes a plurality of test executing sub-files;

[0029] A binding association unit, wherein the binding association unit is configured to: bind and associate the test execution sub-file with the interface variable;

[0030] The test execution unit, the interface calling unit is configured to: obtain a target test case, call the corresponding first interface variable and a target test execution subfile according to the target test case, and run the target test execution subfile to obtain a test result of the target test case.

[0031] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. The computer program includes executable instructions. When the executable instructions are executed by a processor, the test method of the vehicle body controller as described in the above embodiment is implemented.

[0032] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; and a memory for storing executable instructions of the processors, wherein when the executable instructions are executed by the one or more processors, the one or more processors implement the testing method of the vehicle body controller as described in the above embodiments.

[0033] In the technical solution of the embodiment of the present application, the interface configuration file of the test case configuration information of the body controller to be tested is obtained, and then the interface variables in the interface configuration file can be called. According to the test case configuration information and the communication architecture information of the body controller to be tested, a corresponding test execution file is generated. Since the test execution file is generated based on the communication architecture information, the test of the body controller proposed in the embodiment of the present application can be implemented by combining network communication with software, without the need for manual testing through a load box in the prior art.

[0034] Furthermore, each test execution sub-file of the test execution file is bound and associated with each interface variable in the interface configuration file in a one-to-one correspondence, so that when obtaining the target test case, the corresponding first interface variable can be called to run the target test execution sub-file accordingly to obtain the test result of the target test case. The testing method provided in the embodiment of the present application has a high degree of automation and does not require manual testing of each function of the body controller one by one, which greatly improves the convenience of testing the body controller and avoids the problem of low accuracy caused by manual testing.

[0035] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0037] Figure 1 It is a flow chart of a method for testing a vehicle body controller according to an embodiment of the present application;

[0038] Figure 2 It is a specific execution flow chart of each module in the test system of the vehicle body controller according to the embodiment of the present application;

[0039] Figure 3 is a block diagram of a vehicle body controller test system according to an embodiment of the present application;

[0040] Figure 4 It is a schematic diagram of the system structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0041] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0042] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0043] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or micro-control node devices.

[0044] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0045] It should be noted that the "multiple" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0046] The implementation details of the technical solution of the embodiment of the present application are described in detail below:

[0047] First of all, it should be noted that the test scheme of the body controller proposed in the embodiment of the present application can be applied to the relevant technical fields of vehicle testing. In the embodiment of the present application, the entire test method is applied to the service-oriented architecture, namely SOA (Service Oriented Architecture), that is, the vehicle mentioned in the present application follows the SOA architecture, then the SOA architecture does not require the body controller to interact with the body parts through hard-wired connection, but communicates and interacts through message signals, that is, it removes the restrictions of hard-wired control and manual testing.

[0048] In existing vehicles, BCMs are arranged in a distributed manner in the vehicle architecture, and the BCM itself is required to perform direct hard-wired control of various parts, such as the lock motor, wiper motor, etc., while the test method proposed in the embodiment of the present application is based on a simulation system, that is, a series of functions of the body controller are simulated through a simulation system, and corresponding actions are performed or corresponding message signals are sent and received to simulate a series of actions that the body controller needs to perform in actual application scenarios, and then the actions performed by the simulation system are tested to obtain the test results corresponding to the body controller. Therefore, the test method proposed in the present application is executed by a computer or some upper computer equipment, and the body controller can be isolated from the hardware driver. Therefore, it is more efficient in the design of the test system, and can realize automated testing earlier, greatly reducing the manual input of system development and test execution, effectively improving the test efficiency, and achieving the purpose of reducing costs and increasing efficiency.

[0049] According to one aspect of the present application, a method for testing a vehicle body controller is provided. Figure 1 Flow chart of a vehicle body controller testing method according to an embodiment of the present application, the vehicle body controller testing method at least includes steps 110-140:

[0050] In step 110, an interface configuration file of the test case configuration information of the vehicle body controller to be tested is obtained, wherein the interface configuration file includes a plurality of interface variables.

[0051] Specifically, the test case configuration information of the body controller to be tested is manually written, and the test case configuration information can be reflected in the form of a table. More specifically, the test case configuration information can be a test case element table, which defines the actions that need to be performed by the body controller to be tested, and the message information received and sent, including message signals in the form of CAN messages, SOME / IP messages, etc.

[0052] In one embodiment of the present application, before obtaining the interface configuration file of the test case configuration information of the vehicle body controller to be tested, it also includes:

[0053] Acquire test case configuration information of the vehicle body controller to be tested, wherein the test case configuration information includes a plurality of predefined message information and execution action information;

[0054] The message information and the execution action information are defined as corresponding interface variables according to preset configuration rules to generate the interface configuration file.

[0055] Specifically, the embodiment of the present application provides an automated test simulation system variable generation module, which can automatically generate a system variable file (interface configuration file) that can be imported by the automated test simulation system according to the test case element table, and import the interface configuration file into the automated test simulation system. By calling the corresponding interface variables, the automated test simulation system can perform a series of operations related to the vehicle body controller in the actual scenario, such as assigning values ​​to messages and taking values. In other words, a single interface variable can map the actions that the corresponding vehicle body controller needs to perform.

[0056] Among them, the test case configuration information, that is, the test case element table is pre-defined by the developer, and defines the actions that the body controller to be tested needs to perform, and the message information to be received and sent, that is, the message information and execution action information mentioned above.

[0057] In step 120, a corresponding test execution file is generated according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested, and the test execution file includes a plurality of test execution sub-files.

[0058] In one embodiment of the present application, before obtaining the interface configuration file of the test case configuration information of the vehicle body controller to be tested, it also includes:

[0059] Acquire test case configuration information of the vehicle body controller to be tested, wherein the test case configuration information includes a plurality of predefined message information and execution action information;

[0060] The message information and the execution action information are defined as corresponding interface variables according to preset configuration rules to generate the interface configuration file.

[0061] Specifically, the communication architecture information of the body controller to be tested is the communication matrix. The body controller proposed in the present application achieves data interaction by transmitting messages with the vehicle components and various controllers through the communication matrix. Therefore, based on the communication architecture information, each of the message information and each of the execution action information in the test case configuration information is generated into corresponding test codes according to a preset format. That is, each of the message information and each of the execution action information is generated into corresponding test codes in a format that can be recognized and run by the automated test simulation system. Then, when a certain interface variable is called, the automated test simulation system can execute the test code corresponding to the interface variable, and then execute the message information or execution action information corresponding to the test code.

[0062] In step 130, the test execution subfile is bound and associated with the interface variable.

[0063] Specifically, the test execution subfile is the test code mentioned above. By binding the test code to the interface variable, when a certain interface variable is called, the automated test simulation system can automatically execute the test code associated with the interface variable, and then execute the action corresponding to the test code.

[0064] In step 140, a target test case is obtained, a corresponding first interface variable and a target test execution subfile are called according to the target test case, and the target test execution subfile is run to obtain a test result of the target test case.

[0065] In one embodiment of the present application, the target test case includes a plurality of test elements, and calling the corresponding first interface variable and the target test execution subfile according to the target test case includes:

[0066] For each of the test elements, the interface variable corresponding to the test element and the target test code corresponding to the test element are called to run the target test code to obtain the test result of the test element.

[0067] Specifically, the target test case includes multiple test elements, each of which can represent a functional category of the body controller. Therefore, each test element in the target test case can be read to know which functions of the body controller need to be tested, and each test element corresponds to one or more interface variables. At this time, it is necessary to call the corresponding interface variable according to the pre-set execution steps, so that the automated test simulation system can run the corresponding target test code according to the called interface variable, and then obtain the test results of the test element. After the test results of all test elements are obtained, a test report will be automatically generated for users to review.

[0068] In one embodiment of the present application, after running the target test execution subfile to obtain the test result of the target test case, it also includes:

[0069] Calling a corresponding second interface variable according to the target test case, where the second interface variable is an expected result variable corresponding to the test result;

[0070] The expected result variables are compared with the test result variables to generate a test report.

[0071] Specifically, the target test case can also be written manually in a table-like file. When reading the target test case, the expected result variable in the target test case can be read, and the expected result variable can be compared with the test result after the test to generate a test report. For example, a test element in a target test case is "controlling the door to be unable to unlock when the vehicle speed signal is greater than 10 kilometers per hour". At this time, the first interface variable corresponding to the test element is first read, so that the automated test simulation system performs the action of the vehicle speed being greater than 10 kilometers per hour and reads the lock state signal of the door at this speed. Then, the lock state signal of the door at this speed is read as the test result, and the expected result variable is the corresponding second interface variable called by the target test case, so that the lock state signal read is locked. By comparing the test result with the expected result variable, a test report is generated to reflect the effectiveness of the function that the door cannot be unlocked when the vehicle speed is greater than 10 kilometers per hour.

[0072] In one embodiment of the present application, before obtaining the target test case, the method further includes:

[0073] In response to a user's interface variable definition request, a corresponding control interface is generated according to the interface variable definition request, so that when the control interface is called, a target interface variable corresponding to the interface variable definition request is assigned or retrieved.

[0074] Specifically, the user can make the value of the interface variable reach the value required by the user by sending an interface variable definition request. For example, the user needs to define a certain interface variable as "read the real-time speed of the motor". At this time, the target interface variable corresponding to the interface variable definition request can be assigned or taken. When the interface variable is called, the automated test simulation system executes the action corresponding to reading the real-time speed of the motor to complete the automated test.

[0075] Furthermore, Figure 2 As shown, the execution steps of the embodiment of the present application are further described:

[0076] First, the present application also proposes an automated test simulation system code automatic generation module, an automated test simulation system control module and a test execution control module.

[0077] Among them, the automatic test simulation system code automatic generation module is used to generate the code of the simulation node that performs the simulation function in the automated test simulation system, mainly covering the sending and receiving of CAN message signals and SOME / IP message signals, the execution of operation actions, etc. The main input of the automatic test simulation system code automatic generation module is the test case element table and the communication matrix document. The automatic test simulation system code automatic generation module reads the element table and the communication matrix, identifies the message information and operation actions that need to be simulated, and generates the corresponding code according to the format defined by the automated test simulation system. The generated code will be associated with the system variables generated in S1.2. When the relevant system variables are called, the simulation code corresponding to the system variables is executed. For example, assign a value to a CAN message signal.

[0078] The automated test simulation system control module is used to associate the automated test simulation system with the test execution control module, and provide a corresponding interface for the test execution control module to call, thereby controlling the automated test simulation system to perform corresponding actions.

[0079] The automated test simulation system control module provides an automated test simulation system control startup and shutdown interface for starting and shutting down the automated test simulation system.

[0080] The automated test simulation system control module provides an automated test simulation system control start and stop interface, which is used to control the automated test simulation system to start simulation or stop.

[0081] The automated test simulation system control module provides a system variable control interface for controlling the assignment or retrieval of system variables in the automated test simulation system.

[0082] The test execution control module is used to complete the entire test execution, test report generation and other tasks. The main input of the test execution control module is the test case. The test execution control module will execute the test steps according to the elements used in the test steps in the test case by calling the interface variables of the automated test simulation system. The test execution control module will perform result confirmation by calling the interface variables of the automated test simulation system according to the elements used in the expected results in the test case.

[0083] Figure 2 Step S1 is executed by the automatic test simulation system variable generation module, step S2 is executed by the automatic test simulation system code automatic generation module, step S3 is executed by the automatic test simulation system control module, step S4 is executed by the test execution control module, and running the test code to perform the corresponding action is executed by the automatic simulation system.

[0084] In summary, the embodiment of the present application proposes a SOA architecture body controller software automation test system and method with a higher degree of automation and short development time, and has cross-project and cross-model portability to meet the requirements of different test tasks. The present application adopts a fully automated solution for the entire test process, which can greatly reduce the time investment of testers, effectively reduce manpower and time costs, and avoid the risk of manual testing errors.

[0085] Figure 3 This is a block diagram of a test system 300 for a vehicle body controller according to an embodiment of the present application. According to a test system 300 for a vehicle body controller according to an embodiment of the present application, the system 300 includes: a configuration unit 301, a file generation unit 302, a binding association unit 303, and a test execution unit 304.

[0086] A configuration unit 301, wherein the configuration unit is configured to: obtain an interface configuration file of test case configuration information of a vehicle body controller to be tested, wherein the interface configuration file includes a plurality of interface variables;

[0087] A file generating unit 302, wherein the test executing unit is configured to: generate a corresponding test executing file according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested, wherein the test executing file includes a plurality of test executing sub-files;

[0088] A binding association unit 303, wherein the binding association unit is configured to: bind and associate the test execution sub-file with the interface variable;

[0089] The test execution unit 304, the interface calling unit is configured to: obtain a target test case, call the corresponding first interface variable and a target test execution subfile according to the target test case, and run the target test execution subfile to obtain a test result of the target test case.

[0090] As another aspect, the present application further provides a computer-readable storage medium on which a program product capable of implementing the method provided above in this specification is stored. In some possible implementations, various aspects of the present application may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary implementations of the present application described in the above "Embodiment Method" section of this specification.

[0091] According to the program product for implementing the above method in the embodiment of the present application, it can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present application is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0092] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0093] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0094] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0095] Program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0096] As another aspect, the present application also provides an electronic device capable of implementing the above method.

[0097] Those skilled in the art will appreciate that various aspects of the present application may be implemented as a system, method or program product. Therefore, various aspects of the present application may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to as "circuit", "module" or "system" herein.

[0098] Refer to the following Figure 4 The electronic device 400 according to this embodiment of the present application is described. Figure 4 The electronic device 400 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0099] like Figure 4 As shown, the electronic device 400 is in the form of a general computing device. The components of the electronic device 400 may include but are not limited to: at least one processing unit 410, at least one storage unit 420, and a bus 430 connecting different system components (including the storage unit 420 and the processing unit 410).

[0100] The storage unit stores program codes, which can be executed by the processing unit 410, so that the processing unit 410 executes the steps described in the above “Example Method” section of this specification according to various exemplary implementations of the present application.

[0101] The storage unit 420 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 421 and / or a cache memory unit 422 , and may further include a read-only memory unit (ROM) 423 .

[0102] The storage unit 420 may also include a program / utility 424 having a set (at least one) of program modules 425, such program modules 425 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0103] Bus 430 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller node, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0104] The electronic device 400 may also communicate with one or more external devices 1200 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 400, and / or communicate with any device that enables the electronic device 400 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 450. In addition, the electronic device 400 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 460. As shown, the network adapter 460 communicates with other modules of the electronic device 400 via a bus 430. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0105] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0106] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present application, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0107] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be performed without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for testing a vehicle body controller, characterized in that: The method comprises: Obtaining an interface configuration file of test case configuration information of the vehicle body controller to be tested, wherein the interface configuration file includes a plurality of interface variables; Generate a corresponding test execution file according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested, wherein the test execution file includes a plurality of test execution sub-files; Binding and associating the test execution subfile with the interface variable; A target test case is obtained, a corresponding first interface variable and a target test execution subfile are called according to the target test case, and the target test execution subfile is run to obtain a test result of the target test case.

2. The method according to claim 1, characterized in that Before obtaining the interface configuration file of the test case configuration information of the body controller to be tested, it also includes: Acquire test case configuration information of the vehicle body controller to be tested, wherein the test case configuration information includes a plurality of predefined message information and execution action information; The message information and the execution action information are defined as corresponding interface variables according to preset configuration rules to generate the interface configuration file.

3. The method according to claim 2, characterized in that The generating a corresponding test execution file according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested includes: Based on the communication architecture information, each of the message information and each of the execution action information in the test case configuration information is used to generate corresponding test codes in a preset format; Generate the test execution file according to each of the test codes; Wherein, the test execution sub-file is the test code.

4. The method according to claim 1, characterized in that: The target test case includes a plurality of test elements, and the calling of the corresponding first interface variable and the target test execution subfile according to the target test case includes: For each of the test elements, the interface variable corresponding to the test element and the target test code corresponding to the test element are called to run the target test code to obtain the test result of the test element.

5. The method according to claim 4, characterized in that After running the target test execution subfile to obtain the test result of the target test case, the method further includes: Calling a corresponding second interface variable according to the target test case, where the second interface variable is an expected result variable corresponding to the test result; The expected result variables are compared with the test result variables to generate a test report.

6. The method according to claim 1, characterized in that Before obtaining the target test case, it also includes: In response to a user's interface variable definition request, a corresponding control interface is generated according to the interface variable definition request, so that when the control interface is called, a target interface variable corresponding to the interface variable definition request is assigned or retrieved.

7. The method according to claim 1, characterized in that The method is applied to a vehicle adopting a service-oriented architecture.

8. A vehicle body controller test system, characterized in that: The system is used to execute the method according to any one of claims 1 to 7, and the system comprises: A configuration unit, wherein the configuration unit is configured to: obtain an interface configuration file of test case configuration information of the vehicle body controller to be tested, wherein the interface configuration file includes a plurality of interface variables; A file generating unit, wherein the test executing unit is configured to: generate a corresponding test executing file according to the test case configuration information and the communication architecture information of the vehicle body controller to be tested, wherein the test executing file includes a plurality of test executing sub-files; A binding association unit, wherein the binding association unit is configured to: bind and associate the test execution sub-file with the interface variable; The test execution unit, the interface calling unit is configured to: obtain a target test case, call the corresponding first interface variable and a target test execution subfile according to the target test case, and run the target test execution subfile to obtain a test result of the target test case.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program code, and the at least one program code is loaded and executed by a processor to implement the operations performed by the method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: The electronic device includes one or more processors and one or more memories, wherein at least one program code is stored in the one or more memories, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by the method according to claim 7.

Citation Information

Cited By

  • Automated testing system for in-vehicle software

    WO2026195029A1