Automatic test method, device and equipment for automobile controller interface and storage medium

Abstract

The invention relates to an automatic test method and device for an automobile controller interface, equipment and a storage medium. The method comprises the following steps: in response to a received automobile controller interface test request, obtaining various types of interface test cases according to the request; according to each type of interface test case, generating each type of interface test script to obtain a plurality of types of interface test scripts; and calling the configured test software to run various types of interface test scripts to obtain an interface test result of the automobile controller. According to the scheme provided by the invention, the full-link interface automatic test of the automobile controller can be realized, the automatic test requirements of various types of interfaces of the automobile controller are met, and the test coverage, the test accuracy and the test efficiency of various types of interface tests in the automobile controller can be improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to an automatic testing method, device, equipment and storage medium for an automobile controller interface. Background Art

[0002] In the related art, testers can usually perform interface testing on the interface of the controller on a corresponding desktop test bench.

[0003] If the interface test of a large number of software and hardware interfaces is involved, it is necessary to rebuild the targeted test bench to implement the interface test of a large number of software and hardware interfaces. In addition, in the process of testing software interfaces or software and hardware interfaces, testers usually use manual testing. Summary of the invention

[0004] In order to solve or partially solve the problems existing in the related technology, the present application provides a method, device, equipment and storage medium for automatic testing of the interface of an automobile controller, which can realize automatic testing of the full-link interface of the automobile controller, meet the needs of automatic testing of various types of interfaces of the automobile controller, and is conducive to improving the test coverage, test accuracy and test efficiency of various types of interface tests in the automobile controller.

[0005] The first aspect of the present application provides an automated testing method for an automobile controller interface, comprising: in response to receiving an automobile controller interface test request, obtaining multiple types of interface test cases according to the request; generating each type of interface test script according to each type of interface test case to obtain multiple types of interface test scripts; calling configured test software to run multiple types of interface test scripts to obtain automobile controller interface test results.

[0006] In some embodiments, each type of interface test case includes multiple pairs of input interface signals and output interface signals; each type of interface test script is generated according to each type of interface test case, including: traversing each type of interface test case to obtain multiple pairs of input interface signals and output interface signals; generating an interface test script corresponding to any pair of input interface signals and output interface signals according to any pair of input interface signals and output interface signals; generating each type of interface test script according to the interface test script corresponding to each pair of input interface signals and output interface signals.

[0007] In some embodiments, the method further includes: obtaining a signal matrix file according to a request; generating each type of interface test script according to each type of interface test case, so as to obtain multiple types of interface test scripts, including: generating each type of interface test script according to each type of interface test case and the signal matrix file, so as to obtain multiple types of interface test scripts; wherein the signal matrix file is used to determine whether the interface signal in any pair of input interface signal and output interface signal is correct.

[0008] In some implementations, the multiple types of interface test cases include at least two types of interface test cases of a basic software layer, interface test cases of an application software layer, and interface test cases of a runtime environment.

[0009] In some embodiments, the configured test software is called to run various types of interface test scripts to obtain the interface test results of the automobile controller, including at least one of the following: for the interface test cases of the basic software layer, the test software runs the interface test script of the basic software layer, controls the electrical signal IO board to output the first electrical signal to the controller by sending a CAN signal, and parses the second electrical signal received from the controller to obtain the interface test results of the basic software layer of the controller; for the interface test cases of the application software layer, the test software runs the interface test script of the application software layer, calibrates the internal variable interface value of the output interface, parses the internal variable interface value received from the input interface of the controller, and obtains the interface test results of the application software layer of the controller; for the interface test cases of the runtime environment, the test software runs the interface test script of the runtime environment, calibrates the internal variable value of the application software layer, parses the CAN signal value received from the basic software layer, and obtains the interface test results of the runtime environment of the controller.

[0010] In some implementations, the interface test case is obtained by matching a preset signal set according to a preset interface architecture table.

[0011] The second aspect of the present application provides an automatic testing device for an automobile controller interface, which includes: a first acquisition module, used to respond to receiving an automobile controller interface test request and obtain multiple types of interface test cases according to the request; a second acquisition module, used to generate each type of interface test script according to each type of interface test case, so as to obtain multiple types of interface test scripts; a third acquisition module, used to call the configured test software to run multiple types of interface test scripts to obtain the automobile controller interface test result.

[0012] A third aspect of the present application provides an electronic device, including:

[0013] Processor; and

[0014] The memory stores executable codes thereon, and when the executable codes are executed by the processor, the processor is caused to execute the method as described above.

[0015] A fourth aspect of the present application provides a computer-readable storage medium having executable code stored thereon. When the executable code is executed by a processor of an electronic device, the processor is caused to execute the method as described above.

[0016] The technical solution provided in the present application may include the following beneficial effects: it can realize the automated testing of the full-link interfaces of the automobile controller, meet the automated testing requirements of various types of interfaces of the automobile controller, and is conducive to improving the test coverage, test accuracy and test efficiency of various types of interface tests in the automobile controller.

[0017] The technical solution of the present application can also: continuously reuse and improve the reusability of the interface test equipment.

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

[0019] The above and other objects, features and advantages of the present application will become more apparent by describing in more detail the exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0020] Figure 1 It is a flow chart of an automatic testing method for an automobile controller interface shown in an embodiment of the present application;

[0021] Figure 2 is a schematic diagram of executing the method for automatic testing of the automobile controller interface according to an embodiment of the present application;

[0022] Figure 3 It is a structural schematic diagram of an automatic test device for an automobile controller interface shown in an embodiment of the present application;

[0023] Figure 4 It is a schematic diagram of the structure of an electronic device shown in an embodiment of the present application. DETAILED DESCRIPTION

[0024] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0025] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0026] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0027] The automobile controller can be abstracted to include a three-layer architecture, namely BSW (Basic Software), ASW (Application Software Layer) and RTE (Run-Time Environment). Therefore, when performing interface testing of the automobile controller, it is necessary to meet the requirements of various types of interface automation testing.

[0028] Although testers can complete interface testing through manual testing, they cannot achieve full-link automated testing of interface testing. They also have problems such as low efficiency, incomplete coverage, high error rate, and poor reusability.

[0029] In response to the above problems, an embodiment of the present application provides an automated testing method for an automobile controller interface, which can realize automated testing of the full-link interface of the automobile controller, meet the automated testing requirements of various types of interfaces of the automobile controller, and is conducive to improving the test coverage, test accuracy and test efficiency of various types of interface tests in the automobile controller.

[0030] The technical solution of the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0031] Figure 1 It is a flow chart of an automatic testing method for an automobile controller interface shown in an embodiment of the present application.

[0032] See also Figure 1 , an automatic testing method for an automobile controller interface, the method comprising:

[0033] Step 101 , in response to receiving a vehicle controller interface test request, obtain multiple types of interface test cases according to the request.

[0034] In some embodiments, various types of interface test cases can be written separately according to the automobile controller interface test request.

[0035] For example, such as interface test cases of the basic software layer (BSW interface test cases), interface test cases of the application software layer (ASW interface test cases) and interface test cases of the runtime environment (RTE interface test cases).

[0036] Step 102, generating each type of interface test script according to each type of interface test case, so as to obtain multiple types of interface test scripts.

[0037] In some embodiments, interface test cases of respective types may be converted into interface test scripts through a test case to test script tool.

[0038] For example, according to any type of interface test case, any type of interface test case is converted into a corresponding interface test script through a test case to test script tool, thereby generating each type of interface test script.

[0039] Step 103, calling the configured test software to run various types of interface test scripts to obtain the vehicle controller interface test results.

[0040] In some embodiments, the configured test software is called to run the interface test script to perform the test, thereby obtaining the vehicle controller interface test result.

[0041] Furthermore, a corresponding test report can be output according to the test results of the automobile controller interface.

[0042] The automobile controller interface automation testing method of the embodiment of the present application can realize the full-link interface automation testing of the automobile controller, meet the various types of interface automation testing requirements of the automobile controller, and is beneficial to improving the test coverage, test accuracy and test efficiency of various types of interface tests in the automobile controller; the automobile controller interface automation testing method can also be continuously reused to improve the reusability of the interface testing equipment.

[0043] In some embodiments, each type of interface test case includes multiple pairs of input interface signals and output interface signals; each type of interface test script is generated according to each type of interface test case, including: traversing each type of interface test case to obtain multiple pairs of input interface signals and output interface signals; according to any pair of input interface signals and output interface signals, generating an interface test script corresponding to any pair of input interface signals and output interface signals; generating each type of interface test script according to the interface test script corresponding to each pair of input interface signals and output interface signals.

[0044] In some embodiments, the interface test case is obtained by matching a preset signal set according to a preset interface architecture table.

[0045] It can be understood that the interface test case can be an interface test case table, and each type of interface test case table can include multiple pairs of input interface signals (Input interface signals) and output interface signals (Output interface signals).

[0046] Generate corresponding interface test scripts for the traversed Input interface signals and Output interface signals. After traversing all rows in a single interface test case table, save all corresponding interface test scripts for Input interface signals and Output interface signals according to the type of the current interface test case table and use them as the interface test scripts for the current interface test case table.

[0047] For example, there are three types of interface test cases, such as interface test cases of the basic software layer, interface test cases of the application software layer, and interface test cases of the runtime environment. After traversing the three interface test case tables, the three generated interface test scripts are saved in a target file, such as a file of an automated test device.

[0048] In some embodiments, a signal matrix file may also be obtained upon request.

[0049] The signal matrix file is a design version of the signal matrix provided when developing the controller software, which clarifies the specific send and receive messages and corresponding signals.

[0050] In some embodiments, each type of interface test script is generated according to each type of interface test case respectively to obtain multiple types of interface test scripts, which may include: generating each type of interface test script according to each type of interface test case and signal matrix file respectively to obtain multiple types of interface test scripts; wherein the signal matrix file is used to determine whether the interface signal in any pair of input interface signal and output interface signal is correct.

[0051] For example, by traversing the Input interface signals and Output interface signals of three types of interface test case tables and checking whether the above signals exist in the signal matrix file, it is possible to verify whether the interface signals in the interface test case are written correctly.

[0052] The automated testing method for the automobile controller interface of the embodiment of the present application generates each type of interface test script according to each type of interface test case and signal matrix file, so as to obtain multiple types of interface test scripts, thereby improving test accuracy and reducing error rate.

[0053] In some embodiments, the configured test software is called to run various types of interface test scripts to obtain vehicle controller interface test results, including at least one of the following.

[0054] For example, 1. For the interface test case of the basic software layer, the test software runs the interface test script of the basic software layer, controls the electrical signal IO board to output the first electrical signal to the controller by sending a CAN signal, parses the second electrical signal received from the controller, and obtains the interface test result of the basic software layer of the controller.

[0055] For example, the interface test case of the basic software layer is loaded into the interface test device, and the interface test case is converted into the corresponding interface test script through the test case to test script tool, and loaded into the test software. The test software controls the electric signal IO board to output the first electric signal to the controller by sending a CAN signal. After the controller receives the first electric signal, it observes the change of the corresponding signal of the controller through the internal variables and makes a judgment; the controller internal variables are calibrated through the test software, and the controller outputs the corresponding second electric signal to the electric signal IO board through the wiring harness according to the calibrated internal variable value, and the electric signal IO board sends it to the test software in the form of a CAN message to obtain the interface test result of the basic software layer of the controller.

[0056] Electrical signals may include analog signals, digital signals, and pulse signals.

[0057] For example, 2. For the interface test case of the application software layer, the test software runs the interface test script of the application software layer, calibrates the internal variable interface value of the output interface, parses the internal variable interface value received from the input interface of the controller, and obtains the interface test result of the application software layer of the controller.

[0058] For example, the interface test case of the application software layer is loaded into the interface test equipment, and the interface test case is converted into the corresponding interface test script through the test case to test script tool, and loaded into the test software. The test software calibrates the internal variable interface value of the output interface, and then observes the internal variable interface value of the corresponding output interface returned by the controller, makes a judgment and obtains the interface test result of the application software layer of the controller.

[0059] For example, 3. For the interface test case of the runtime environment, the test software runs the interface test script of the runtime environment, calibrates the internal variable values ​​of the application software layer, parses the CAN signal values ​​received from the basic software layer, and obtains the interface test results of the runtime environment of the controller.

[0060] For example, the interface test case of the runtime environment is loaded into the interface test equipment, and the interface test case is converted into the corresponding interface test script through the test case to test script tool, and loaded into the test software. The test software performs an interface test from the application software layer (ASW) to the basic software layer (BSW), and makes a judgment by calibrating the value of the internal variable of the application software layer (ASW) and then observing the CAN signal value; the interface test from the basic software layer (BSW) to the application software layer (ASW) is performed by changing the CAN signal value and then observing the calibrated value of the internal variable of the application software layer (ASW) to determine whether it is consistent, thereby obtaining the interface test result of the runtime environment of the controller.

[0061] The embodiment of the present application provides an automated testing method for an automobile controller interface, which can realize automated full-chain interface testing of a basic software layer, an application software layer, and a runtime environment.

[0062] In order to better understand the present application, the content of the present application is further explained below in conjunction with the embodiments, but the present application is not limited to the following embodiments.

[0063] Figure 2 It is a schematic diagram of the execution of the automobile controller interface automatic testing method shown in the embodiment of the present application.

[0064] See also Figure 2 In order to meet the requirements of multi-type interface testing, BSW, ASW and RTE interface test case tables are compiled according to the interface testing requirements; each interface test case table can traverse all signals for matching according to the interface architecture table to automatically generate interface test cases. Then load the test case table and signal matrix file into the interface automatic test equipment to obtain the test results. The following is an example of three interface tests.

[0065] For BSW interface testing, first configure the electrical signal harness according to the interface configuration requirements of the controller BSW, and then connect it to the device electrical signal connector. The specific test logic is as follows; after the BSW interface test case table is loaded into the device, the interface test case is converted into the corresponding interface test script through the test case to test script tool, and loaded into the test software. The main test object of BSW interface testing is the software and hardware interface.

[0066] Then, the test software controls the electrical signal IO board to output the first electrical signal to the controller by sending a CAN signal. After receiving the first electrical signal, the controller observes the change of the corresponding signal of the controller through the internal variables and makes a judgment. For example, the test software controls the IO board to output the electrical signal to the flying line point of the controller by changing the CAN_A signal. Assuming that the output is 5V, if CAN_A is an AI signal, the actual voltage value read by the controller corresponds to the ADC internal BSW_XCP_a sampling value of 4096±(4096*x%), and x% is the maximum allowable error ratio, assuming it is 0.5%. If the ADC internal BSW_XCP_a sampling value is between 4074.52 and 4116.48, the interface test result is passed, otherwise it is not passed.

[0067] After that, the controller internal variables are calibrated by the test software, and the controller outputs the corresponding second electrical signal to the electrical signal IO board through the wiring harness led out of the flying point according to the calibrated internal variable value, and the electrical signal IO board is sent to the test software in the form of a CAN message to obtain the interface test result of the basic software layer of the controller. For example, the test software controls the electrical signal output by the controller flying point by changing the BSW_XCP_b signal value inside the ADC, and outputs it to the IO board, and finally parses it through the test software. Assuming that the BSW_XCP_b sampling value inside the ADC is 4096, the flying point output is 5V. If the BSW_XCP_b inside the ADC is an AO signal, the value of the CAN_B signal read by the test software is 5000±(5000*x%), and x% is the maximum allowable error ratio, assuming it is 0.5%. If the value of the CAN_B signal is between 4975 and 5025mv, the interface test result is passed, otherwise it is not passed.

[0068] For ASW interface testing, after the ASW interface test case table is loaded into the device, the interface test case is converted into the corresponding interface test script through the test case to test script tool and loaded into the test software.

[0069] Then, the test software calibrates the internal variable interface value of the output interface of module 1 and parses the internal variable interface value received from the input interface of module 2 to obtain the interface test result of the controller's application software layer. For example, the ASW_Model1_XCP_c signal (calibration quantity, writable) and the internal ASW_Model2_XCP_c signal (observation quantity, readable), the value of ASW_Model1_XCP_c is modified by the test software, and the value of ASW_Model2_XCP_c is observed. If ASW_Model2_XCP_c = ASW_Model1_XCP_c, the interface test passes; otherwise, it fails.

[0070] For RTE interface testing, after the RTE interface test case table is loaded into the device, the interface test case is converted into the corresponding interface test script through the test case to test script tool and loaded into the test software.

[0071] Then, the test software performs an interface test from the application software layer (ASW) to the basic software layer (BSW), by calibrating the value of the internal variable of the application software layer (ASW), and then observing the CAN signal value to make a judgment; the interface test from the basic software layer (BSW) to the application software layer (ASW) is performed by changing the CAN signal value and then observing the value of the calibrated internal variable of the application software layer (ASW) to determine whether it is consistent, and obtain the interface test result of the running time environment of the controller. For example, ASW→BSW, the value of the ASW_XCP_d signal (calibrated quantity, writable) is modified by the test software, and the value of the CAN_D signal is observed. If CAN_D=ASW_XCP_d, the interface test passes, otherwise, it fails. BSW→ASW, the value of CAN_E is modified by the test software, and the value of the ASW_XCP_e signal (observable quantity, readable) is observed. If ASW_XCP_e=CAN_E, the interface test passes, otherwise, it fails.

[0072] Corresponding to the aforementioned application function realization method embodiment, the present application also provides an automobile controller interface automatic testing device, electronic equipment and corresponding embodiments.

[0073] Figure 3 It is a structural schematic diagram of an automobile controller interface automatic testing device shown in an embodiment of the present application.

[0074] See also Figure 3 The automobile controller interface automatic testing device 300 of this embodiment includes a first obtaining module 310 , a second obtaining module 320 and a third obtaining module 330 .

[0075] A first obtaining module 310 is used to obtain multiple types of interface test cases according to the request in response to receiving a vehicle controller interface test request;

[0076] The second obtaining module 320 is used to generate each type of interface test script according to each type of interface test case, so as to obtain multiple types of interface test scripts;

[0077] The third obtaining module 330 is used to call the configured test software to run various types of interface test scripts to obtain the vehicle controller interface test results.

[0078] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated again here.

[0079] According to an embodiment of the present application, any multiple modules in the first acquisition module 310, the second acquisition module 320 and the third acquisition module 330 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first acquisition module 310, the second acquisition module 320 and the third acquisition module 330 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, at least one of the first acquisition module 310, the second acquisition module 320 and the third acquisition module 330 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0080] Figure 4 It is a schematic diagram of the structure of an electronic device shown in an embodiment of the present application.

[0081] See also Figure 4 , the electronic device 400 includes a memory 410 and a processor 420.

[0082] The processor 420 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0083] The memory 410 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage. Among them, ROM can store static data or instructions required by the processor 420 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even after the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as a permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as a dynamic random access memory. The system memory may store some or all instructions and data required by the processor at run time. In addition, the memory 410 may include any combination of computer-readable storage media, including various types of semiconductor storage chips (such as DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks may also be used. In some embodiments, the memory 410 may include a readable and / or writable removable storage device, such as a laser disc (CD), a read-only digital versatile disc (such as a DVD-ROM, a double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (such as an SD card, a mini SD card, a Micro-SD card, etc.), a magnetic floppy disk, etc. The computer-readable storage medium does not include carrier waves and transient electronic signals transmitted wirelessly or wired.

[0084] The memory 410 stores executable codes, and when the executable codes are processed by the processor 420 , the processor 420 can execute part or all of the methods described above.

[0085] In addition, the method according to the present application may also be implemented as a computer program or a computer program product, which includes computer program code instructions for executing some or all of the steps in the above method of the present application.

[0086] Alternatively, the present application can also be implemented as a computer-readable storage medium (or non-transitory machine-readable storage medium or machine-readable storage medium) on which executable code (or computer program or computer instruction code) is stored. When the executable code (or computer program or computer instruction code) is executed by a processor of an electronic device (or server, etc.), the processor executes part or all of the steps of the above-mentioned method according to the present application.

[0087] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. An automatic testing method for an automobile controller interface, characterized in that: include: In response to receiving a vehicle controller interface test request, obtaining multiple types of interface test cases according to the request; Generate each type of interface test script according to each type of interface test case to obtain multiple types of interface test scripts; The configured test software is called to run the various types of interface test scripts to obtain the vehicle controller interface test results.

2. The method according to claim 1, characterized in that Each type of interface test case includes multiple pairs of input interface signals and output interface signals; Generate each type of interface test script based on each type of interface test case, including: Traversing each type of interface test case to obtain the multiple pairs of input interface signals and output interface signals; According to any pair of input interface signals and output interface signals, generate an interface test script corresponding to the pair of input interface signals and output interface signals; According to the interface test script corresponding to each pair of input interface signal and output interface signal, each type of interface test script is generated.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Obtaining a signal matrix file according to the request; The method generates each type of interface test script according to each type of interface test case to obtain multiple types of interface test scripts, including: Generate each type of interface test script according to each type of interface test case and the signal matrix file to obtain multiple types of interface test scripts; The signal matrix file is used to determine whether the interface signal in any pair of input interface signal and output interface signal is correct.

4. The method according to claim 1, characterized in that: The multiple types of interface test cases include at least two types of interface test cases of a basic software layer, an interface test case of an application software layer, and an interface test case of a runtime environment.

5. The method according to claim 4, characterized in that The calling of the configured test software to run the multiple types of interface test scripts to obtain the vehicle controller interface test results includes at least one of the following: For the interface test case of the basic software layer, the test software runs the interface test script of the basic software layer, controls the electrical signal IO board to output a first electrical signal to the controller by sending a CAN signal, parses the second electrical signal received from the controller, and obtains the interface test result of the basic software layer of the controller; For the interface test case of the application software layer, the test software runs the interface test script of the application software layer, calibrates the internal variable interface value of the output interface, parses the internal variable interface value received from the input interface of the controller, and obtains the interface test result of the application software layer of the controller; For the interface test case of the runtime environment, the test software runs the interface test script of the runtime environment, calibrates the internal variable values ​​of the application software layer, parses the CAN signal values ​​received from the basic software layer, and obtains the interface test results of the runtime environment of the controller.

6. The method according to claim 1, characterized in that The interface test case is obtained by matching the preset signal set according to the preset interface architecture table.

7. An automatic test device for automobile controller interface, characterized in that: include: A first obtaining module, configured to obtain, in response to receiving a vehicle controller interface test request, multiple types of interface test cases according to the request; The second acquisition module is used to generate each type of interface test script according to each type of interface test case, so as to obtain multiple types of interface test scripts; The third acquisition module is used to call the configured test software to run the multiple types of interface test scripts to obtain the vehicle controller interface test results.

8. The device according to claim 7, characterized in that Each type of interface test case includes multiple pairs of input interface signals and output interface signals; the second acquisition module is further used for: Traversing each type of interface test case to obtain the multiple pairs of input interface signals and output interface signals; According to any pair of input interface signals and output interface signals, generate an interface test script corresponding to the pair of input interface signals and output interface signals; According to the interface test script corresponding to each pair of input interface signal and output interface signal, each type of interface test script is generated.

9. An electronic device, characterized in that: include: processor; as well as A memory having executable codes stored thereon, which, when executed by the processor, causes the processor to execute the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having executable codes stored thereon, which, when executed by a processor of an electronic device, causes the processor to execute the method according to any one of claims 1 to 6.

Images