A vehicle electronic automation testing method, device, system and medium
Through the automated integrated test system, monitor the version database, download and edit the new version project, compile and generate target files, and conduct vehicle electronic control unit testing, solve the problem that traditional test systems cannot meet the needs of rapid iteration, and achieve efficient and sustainable automated testing.
Patent Information
- Application Number
- CN202111198778.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-10-14
- Publication Date
- 2025-06-27
- Estimated Expiration
- 2041-10-14
AI Technical Summary
With the development of the software-defined automobile trend, the iteration cycle of software modules is getting shorter and shorter, resulting in a significant increase in the number of integrated test versions and test tasks. Traditional automated integrated test systems and methods can no longer meet the growing test needs, with high manual participation and low testing efficiency.
By monitoring the release of new versions in the version database, downloading new version projects, editing the computer test code, compiling and generating target files, and burning them into the vehicle electronic control unit for testing, and integrating these processes into a system using automation means.
It reduces manual participation, improves the versatility, sustainability and testing efficiency of vehicle electronic automation testing, and can adapt to the needs of software updates and iterations more quickly.
Smart Images

Figure CN113849412B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to automated testing technologies, and particularly to a vehicle electronic automated testing method, apparatus, system, and medium. Background Art
[0002] Currently, automotive electronic automated integration testing systems are widely used in automotive electronic integration testing activities. With the development of the trend of software-defined vehicles, the iteration cycle of software modules is getting shorter and shorter. The number of integrated test versions and the amount of test tasks have increased significantly. Traditional automated integration testing systems and methods can no longer meet the growing test requirements.
[0003] Therefore, with the accelerating speed of software update and iteration, it is necessary to reduce the manual participation and improve the test efficiency of automated integration testing. Summary of the Invention
[0004] Embodiments of the present invention provide a vehicle electronic automated testing method, apparatus, system, and medium to reduce manual participation and improve the versatility, sustainability, and test efficiency of automated testing.
[0005] In a first aspect, embodiments of the present invention provide a vehicle electronic automated testing method, which includes:
[0006] If it is monitored that a new version is released in the version database, download the new version project from the version database and determine the version number information of the new version project;
[0007] Copy the lower computer test code from the test database, and edit the lower computer test code according to the version number information of the new version project to obtain a lower computer editing result;
[0008] Compile according to the new version project and the lower computer editing result to obtain a target file;
[0009] Burn the target file into the vehicle's electronic control unit, and test the electronic control unit using the target file.
[0010] In a second aspect, embodiments of the present invention further provide a vehicle electronic automated testing apparatus, which includes:
[0011] A version monitoring and downloading module, configured to download a new version project from the version database and determine the version number information of the new version project if it is monitored that a new version is released in the version database;
[0012] A test code editing module, configured to copy the lower computer test code from the test database, and edit the lower computer test code according to the version number information of the new version project to obtain a lower computer editing result;
[0013] A target file acquisition module, configured to compile a target file according to a new version project and the editing result of the lower computer.
[0014] A testing module, configured to burn the target file into an electronic control unit in a vehicle and test the electronic control unit by using the target file.
[0015] Thirdly, an embodiment of the present invention further provides a vehicle electronic automation testing system, and the system includes:
[0016] One or more processors;
[0017] A storage device, configured to store one or more programs.
[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the vehicle electronic automation testing method as described in any embodiment of the present invention.
[0019] Fourthly, an embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, and when the program is executed by a processor, the vehicle electronic automation testing method as described in any embodiment of the present invention is implemented.
[0020] In the embodiments of the present invention, by adjusting the working modes and triggering mechanisms of four processes including new version project monitoring and downloading, lower computer test code editing, target file acquisition and burning, and electronic control unit testing, and integrating these four processes into a system by using an automated means, the manual participation degree is reduced, and the generality, sustainability, and testing efficiency of vehicle electronic automation testing are improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1 FIG. is a flowchart of a vehicle electronic automation testing method provided in Embodiment 1 of the present invention;
[0022] Figure 2 FIG. is a flowchart of a vehicle electronic automation testing method provided in Embodiment 2 of the present invention;
[0023] Figure 3 FIG. is a structural block diagram of a vehicle electronic automation testing device provided in Embodiment 3 of the present invention;
[0024] Figure 4 FIG. is a structural block diagram of a vehicle electronic automation testing system provided in Embodiment 4 of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0025] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present invention, rather than limiting the present invention. In addition, it should be noted that for the convenience of description, only the parts related to the present invention are shown in the drawings, rather than all the structures.
[0026] Embodiment 1
[0027] Figure 1 FIG. is a flowchart of a vehicle electronic automation test method provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of vehicle electronic automation testing. This method can be executed by a vehicle electronic automation test device, and this device can be implemented in a software and / or hardware manner. This device can be configured in a server and / or a vehicle-mounted controller. Specifically, this method includes:
[0028] S110. If it is monitored that a new version is released in the version database, download the new version project from the version database and determine the version number information of the new version project.
[0029] Among them, the version database is used to store version projects that have been developed and can implement different vehicle electronic functions. The version project can also be called a development program. The version project is divided into a macro version project and a sub-version project. One or more sub-version projects can correspond to each macro version project. Each macro version project implements different functions, and its corresponding sub-version project is an optimization or bug fix of the macro version project. The version number is used as the identifier of the version project, and each version project has its corresponding version number. Through the version number, users can quickly and accurately obtain whether the version project is the latest version, and at the same time, they can also obtain the corresponding version number information. The version number information can include information such as the name, function, and parameters of the version project. The version number is also divided into a macro version number and a sub-version number, which correspond to the macro version project and the sub-version project. When a new version project is developed, the staff will upload the new version project to the version database and generate a corresponding version number. The new version project can also be called a project to be tested.
[0030] It should be noted that if it is monitored that a new version is released in the version database, downloading the new version project from the version database and determining the version number information of the new version project means that if a new version is released, the version release management module will start the target program management module, and the target program management module will download the new version project and determine the version number information of the new version project. Among them, the version release management module is used to monitor whether a new version is released in the version database. The target program management module is used to complete tasks such as target file compilation and burning. The target file refers to a file that can test the new version project.
[0031] S120. Copy the lower computer test code from the test database, and edit the lower computer test code according to the version number information of the new version project to obtain the lower computer editing result.
[0032] Among them, the test database is used to store a series of lower computer test codes. The lower computer test code is used to test whether the version project can run accurately and smoothly and implement the corresponding functions, and one lower computer test code can only test one function. The lower computer test code has a certain degree of generality. For example, the parameters of the lower computer test code are different from the parameter names of the new version project but have the same purpose. Therefore, if the lower computer test code is applied to the test of the new version project, the parameter names need to be unified. Copying the lower computer test code from the test database and editing the lower computer test code according to the version number information of the new version project to obtain the lower computer editing result means that after the target program management module is started, while downloading the new version project and determining the version number information of the new version project, copy the lower computer test code from the test database, and perform corresponding editing on the lower computer test code according to the version number information of the new version project, so as to obtain the lower computer editing result applicable to the new version project.
[0033] In an optional implementation manner, before editing the lower computer test code according to the version number information of the new version project, it further includes:
[0034] Control the start of the lower computer test code associated with the target macro version information according to the target macro version information to which the version number information of the new version project belongs, and control the closing of other lower computer test codes.
[0035] Among them, the target macro version information refers to the version number information corresponding to the macro version project corresponding to the new version project. Since the lower computer test code in this embodiment is selected according to the macro version number, when the monitored new version project is a sub-version project, its corresponding macro version project will be searched for and its version number information will be obtained. Since the test result has reference value only when the function of the version project is consistent with the function tested by the lower computer test code, in order to improve the test efficiency, only the lower computer test code related to the target macro version information will be started. Controlling the start of the lower computer test code associated with the target macro version information according to the target macro version information to which the version number information of the new version project belongs, and controlling the closing of other lower computer test codes means that the target program management module obtains the corresponding target macro version information according to the version number information of the new version project, and only enables the lower computer test code associated with the target macro version information to test the new version project.
[0036] By only enabling the lower computer test code associated with the target macro version information to test the new version project, it effectively avoids the operation of invalid test programs, saves a large amount of test time, and improves the test efficiency.
[0037] S130. Compile according to the new version project and the lower computer editing result to obtain a target file.
[0038] Among them, compilation refers to translating a high-level language into a binary language that a computer can recognize. Here, the high-level language can also be called the source program, and the binary language can also be called the target program. The compilation process can be divided into five stages: lexical analysis, syntax analysis, semantic checking and intermediate code generation, code optimization, and target code generation. The generated target code is the target program obtained by compilation. Compiling according to the new version project and the lower computer editing result to obtain a target file means that the target program management module uses a compiler to compile the new version project and the lower computer editing result, and the compilation result is the target file.
[0039] S140. Burn the target file into the electronic control unit in the vehicle, and use the target file to test the electronic control unit.
[0040] Among them, the electronic control unit can include a program update interface, a power supply, a drive interface, and a communication interface. The program update interface burns the target file into the electronic control unit through a modulator, providing a software environment for the test process. The power supply is used to supply power to the electronic control unit. The drive interface is used to collect sensor information. By combining the sensor information and the running situation of the target file, it can be judged whether the new version project can run accurately and smoothly. The communication interface is used for communication between various parts of the electronic control unit and can communicate in a bus manner. Burning the target file into the electronic control unit in the vehicle and using the target file to test the electronic control unit means that after the target program management module burns the target file into the electronic control unit in the vehicle, it starts the automated integration test module, and uses the drive interface and communication interface, etc. to realize the automated test of the electronic control unit in the vehicle.
[0041] The technical solution of this embodiment, through the cooperation of the version release management module, the target program management module, and the automated integration test module, completes the entire process from monitoring the new version release to generating the target file and testing the signature control unit, solves the problems of high manual participation and low test efficiency in the vehicle electronic automation test process, reduces the manual participation, and improves the versatility, sustainability, and test efficiency of the vehicle electronic automation test.
[0042] On the basis of the above technical solution, the compiling according to the new version project and the lower computer editing result to obtain a target file preferably can include:
[0043] Introduce the editing result of the slave computer into the new version project, and call the function in the editing result of the slave computer through the new version project to obtain an integration result;
[0044] Compile the integration result to obtain an object file.
[0045] Among them, the editing result of the slave computer consists of one or more functions and is used to reflect the result of detecting the new version project. Introducing the editing result of the slave computer into the new version project means storing the editing result of the slave computer in the new version project. Calling the function in the editing result of the slave computer through the new version project means that in the new version project where the editing result of the slave computer is stored, it is necessary to call the function in the editing result of the slave computer to obtain the test result. Introducing the editing result of the slave computer into the new version project and calling the function in the editing result of the slave computer through the new version project to obtain an integration result means that the obtained integration result is the new version project storing the editing result of the slave computer, and the function in the editing result of the slave computer can be called in the new version project. Compiling the integration result to obtain an object file means using a compiler to compile the integration result, and the obtained object file is the result of the compilation.
[0046] Introducing the editing result of the slave computer into the new version project and calling the function in the editing result of the slave computer through the new version project realizes the integration of the editing result of the slave computer and the new version project, which not only ensures the smooth operation of the test program but also improves the operation efficiency of the program and saves the test time.
[0047] Embodiment 2
[0048] Figure 2 The flowchart of a vehicle electronic automation test method provided by Embodiment 2 of the present invention. Based on the above embodiments, preferably, if it is monitored that there is a new version release in the version database, download the new version project from the version database, including: if it is monitored that there is a new version release in the version database, set the version monitoring flag to the first value and read the value of the test idle flag; if the value of the test idle flag is the third value, start the target program management module, and when the target program management module starts up, set the version monitoring flag to the second value; download the new version project from the version database through the target program management module, and when the new version project is downloaded, set the value of the test idle flag to the fourth value. Among them, the specific method is as follows:
[0049] S210. If it is monitored that there is a new version release in the version database, set the version monitoring flag to the first value and read the value of the test idle flag.
[0050] Among them, the version monitoring flag is used to indicate whether a new version is released. For example, in this embodiment, B_Released can be used to represent the version monitoring flag. B_Released = 1 indicates that a new version is released, and B_Released = 0 indicates that no new version is released. The test idle flag is used to indicate whether a new test task is supported. In this embodiment, B_Testldle can be used to represent the test idle flag. If it is monitored that a new version is released in the version database, the version monitoring flag is set to the first value, and reading the value of the test idle flag means that in this embodiment, if it is monitored that a new version is released in the version database, the version monitoring flag is set to 1, that is, the first value, and it is judged whether the current process can continue to the next step according to the value of the test idle flag. It can be understood that if B_Testldle = 1, it means that a new test task can be supported, that is, step S220 can be executed. If B_Testldle = 0, it means that a new test task cannot be supported, and step S220 cannot be executed.
[0051] S220. If the value of the test idle flag is the third value, start the target program management module, and when the target program management module starts up, set the version monitoring flag to the second value.
[0052] Among them, if the value of the test idle flag is the third value, starting the target program management module means that when B_Testldle is 1, that is, the third value, it means that a new test task can be supported and the target program management module can be started. When the target program management module starts up, setting the version monitoring flag to the second value means that after the target program management module starts, B_Released is set to 0, that is, the second value, indicating that there is no new version released currently.
[0053] S230. Download the new version project from the version database through the target program management module, and when the new version project is downloaded, set the value of the test idle flag to the fourth value.
[0054] Among them, when the new version project is downloaded, setting the value of the test idle flag to the fourth value means that after the new version project is downloaded, B_Testldle is set to 0, that is, the fourth value, indicating that there is currently a test task being executed and a new test task cannot be supported.
[0055] S240. Copy the lower computer test code from the test database, and edit the lower computer test code according to the version number information of the new version project to obtain the lower computer editing result.
[0056] S250. Compile according to the new version project and the lower computer editing result to obtain the target file.
[0057] S260. Burn the target file into the electronic control unit in the vehicle and test the electronic control unit using the target file.
[0058] In an alternative embodiment, after testing the electronic control unit using the target file, it further includes: after the electronic control unit test is completed, generating a test report and setting the value of the test idle flag to a third value.
[0059] Among them, the test report refers to a file formed by describing the test results after the new version project test is completed. Its content can include whether the new version project can run smoothly and whether the operation results are accurate. After the electronic control unit test is completed, generating a test report and setting the value of the test idle flag to a third value means that after the test is completed and the test report is formed, set B_Testldle to 1, indicating that there is no current test task and new test tasks can be supported.
[0060] By setting the value of the test idle flag to a third value after the electronic control unit test is completed, it is ensured that when a new version is monitored next time, new test tasks can be continued to be executed, ensuring the sustainability of the test.
[0061] The technical solution of this embodiment enables each step in the vehicle electronic automation test process to achieve automatic cyclic operation by setting the version monitoring flag and the test idle flag, solves the problems of high manual participation and low test efficiency in the vehicle electronic automation test process, reduces the manual participation, and improves the versatility, sustainability and test efficiency of the vehicle electronic automation test.
[0062] Embodiment III
[0063] Figure 3 FIG. 3 is a schematic structural diagram of a vehicle electronic automation test device provided in Embodiment III of the present invention. The device can execute the vehicle electronic automation test method provided in the above embodiment. The device may include: a version monitoring and downloading module 310, a test code editing module 320, a target file obtaining module 330, and a test module 340.
[0064] Among them, the version monitoring and downloading module 310 is configured to, if a new version is released in the version database, download the new version project from the version database and determine the version number information of the new version project;
[0065] The test code editing module 320 is configured to copy the lower computer test code from the test database and edit the lower computer test code according to the version number information of the new version project to obtain a lower computer editing result;
[0066] A target file acquisition module 330, configured to compile according to a new version project and the editing result of the lower computer to obtain a target file;
[0067] A test module 340, configured to burn the target file into an electronic control unit in a vehicle, and test the electronic control unit by using the target file.
[0068] Through the cooperation of a version monitoring and downloading module, a test code editing module, a target file acquisition module, and a test module, the technical solution provided by the embodiments of the present invention completes the entire process from monitoring a new version release to generating a target file and testing a signature control unit, solves the problems of high manual participation and low test efficiency in the vehicle electronic automation test process, reduces the manual participation, and improves the versatility, sustainability, and test efficiency of the vehicle electronic automation test.
[0069] In the above device, optionally, the target file acquisition module 330 includes:
[0070] An editing result integration unit, configured to introduce the editing result of the lower computer into the new version project, and call a function in the editing result of the lower computer through the new version project to obtain an integration result;
[0071] An integration result compilation unit, configured to compile the integration result to obtain a target file.
[0072] Optionally, the above device further includes:
[0073] A test code control module, configured to control the start of a lower computer test code associated with the target macro version information according to the target macro version information to which the version number information of the new version project belongs, and control the closing of other lower computer test codes.
[0074] In the above device, optionally, the version monitoring and downloading module 310 includes:
[0075] A version monitoring unit, configured to, if a new version is released in the version database, set a version monitoring flag to a first value, and read a value of a test idle flag;
[0076] A program management startup unit, configured to, if the value of the test idle flag is a third value, start a target program management module, and when the target program management module is started successfully, set the version monitoring flag to a second value;
[0077] A version downloading unit, configured to download a new version project from the version database through the target program management module, and when the new version project is downloaded successfully, set the value of the test idle flag to a fourth value.
[0078] Optionally, the above device further includes:
[0079] A test report generation unit, configured to generate a test report after the electronic control unit test is completed, and set the value of the test idle flag to a third value.
[0080] The device provided in this embodiment constructs modules that can implement each step in the vehicle electronic automation test device. Using the editing result integration module, the new version project and the lower computer editing result are integrated. Using the test code control module, the irrelevant lower computer test code is closed, reducing the running time of the test program and improving the test efficiency.
[0081] Embodiment 4
[0082] Figure 4 is a schematic structural diagram of a vehicle electronic automation test system provided in Embodiment 4 of the present invention. As Figure 4 shown, the system includes a processor 40, a memory 41, an input device 42, and an output device 43; the number of processors 40 in the system can be one or more, Figure 4 here, one processor 40 is taken as an example; the processor 40, the memory 41, the input device 42, and the output device 43 in the device / terminal / server can be connected through a bus or other means, Figure 4 here, connection through a bus is taken as an example.
[0083] The memory 41, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions and modules corresponding to the vehicle electronic automation test method in the embodiments of the present invention (for example, the version monitoring and downloading module 310, the test code editing module 320, the target file acquisition module 330, and the test module 340). The processor 40 executes various functional applications and data processing of the system by running the software programs, instructions, and modules stored in the memory 41, that is, implements the above-mentioned vehicle electronic automation test.
[0084] The memory 41 may mainly include a program storage area and a data storage area. Among them, the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory 41 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some instances, the memory 41 may further include a memory remotely set relative to the processor 40, and these remote memories may be connected to the system through a network. Examples of the above network include but are not limited to the Internet, an enterprise internal network, a local area network, a mobile communication network, and combinations thereof.
[0085] The input device 42 can be used to receive input digital or character information and generate key signal inputs related to the user settings and function controls of the system. The output device 43 can include display devices such as a display screen.
[0086] Embodiment 5
[0087] Embodiment 5 of the present invention also provides a storage medium storing computer-executable instructions, which are used to execute a vehicle electronic automation testing method when executed by a computer processor. The method includes:
[0088] If it is monitored that a new version is released in the version database, download the new version project from the version database and determine the version number information of the new version project;
[0089] Copy the lower computer test code from the test database, and edit the lower computer test code according to the version number information of the new version project to obtain a lower computer editing result;
[0090] Compile according to the new version project and the lower computer editing result to obtain a target file;
[0091] Burn the target file into the electronic control unit in the vehicle, and test the electronic control unit with the target file.
[0092] Certainly, for a storage medium storing computer-executable instructions provided by an embodiment of the present invention, the computer-executable instructions are not limited to the method operations as described above, and can also execute relevant operations in the vehicle electronic automation testing method provided by any embodiment of the present invention.
[0093] Through the above description of the embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software and necessary general hardware. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as a floppy disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (FLASH), a hard disk, or an optical disc of a computer, etc., including several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present invention.
[0094] It should be noted that in the embodiments of the above-mentioned vehicle electronic automation test device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of mutual distinction and do not limit the protection scope of the present invention.
[0095] Note that the above is only the preferred embodiment of the present invention and the technical principles applied. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, re-adjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments. Without departing from the concept of the present invention, more other equivalent embodiments can be included, and the scope of the present invention is determined by the scope of the appended claims.
Claims
1. A vehicle electronic automation test method, characterized in that, Including: If it is monitored that a new version is released in the version database, download the new version project from the version database and determine the version number information of the new version project; wherein, the version number information includes the name, function and parameters of the version project; Copy the lower computer test code from the test database, and edit the lower computer test code according to the version number information of the new version project to obtain the lower computer editing result; wherein, the lower computer test code has a certain generality and is used to test whether the version project can run accurately and smoothly and implement the corresponding functions. One lower computer test code can only test one function; the editing includes unifying the parameter names; Compile according to the new version project and the lower computer editing result to obtain the target file; Burn the target file into the electronic control unit in the vehicle, and use the target file to test the electronic control unit; Among them, the step of "if it is monitored that a new version is released in the version database, download the new version project from the version database" includes: If it is monitored that a new version is released in the version database, set the version monitoring flag to the first value and read the value of the test idle flag; If the value of the test idle flag is the third value, start the target program management module, and when the target program management module starts successfully, set the version monitoring flag to the second value; Download the new version project from the version database through the target program management module, and when the new version project is downloaded successfully, set the value of the test idle flag to the fourth value.
2. The method according to claim 1, wherein The step of "compile according to the new version project and the lower computer editing result to obtain the target file" includes: Introduce the lower computer editing result into the new version project, and call the function in the lower computer editing result through the new version project to obtain the integration result; Compile the integration result to obtain the target file.
3. The method according to claim 1, wherein Before editing the lower computer test code according to the version number information of the new version project, it further includes: According to the target macro version information to which the version number information of the new version project belongs, control the start of the lower computer test code associated with the target macro version information, and control the shutdown of other lower computer test codes.
4. The method according to claim 1, characterized in that After testing the electronic control unit with the target file, it further includes: After the electronic control unit test is completed, generate a test report and set the value of the test idle flag to the third value.
5. A vehicle electronic automation test device, characterized in that, Including: A version monitoring and downloading module, which is used to download a new version project from the version database if it is monitored that a new version is released in the version database, and determine the version number information of the new version project; wherein, the version number information includes the name, function and parameters of the version project; A test code editing module, which is used to copy the lower computer test code from the test database, edit the lower computer test code according to the version number information of the new version project to obtain the lower computer editing result; wherein, the lower computer test code has a certain generality and is used to test whether the version project can run accurately and smoothly and implement the corresponding functions, and one lower computer test code can only test one function; the editing includes unifying parameter names. A target file acquisition module, which is used to compile the new version project and the lower computer editing result to obtain a target file. A test module, which is used to burn the target file into the electronic control unit in the vehicle and test the electronic control unit with the target file. The version monitoring and downloading module includes: A version monitoring unit, which is used to set the version monitoring flag to the first value if a new version is released in the version database, and read the value of the test idle flag. A program management startup unit, which is used to start the target program management module if the value of the test idle flag is the third value, and set the version monitoring flag to the second value when the target program management module starts successfully. A version downloading unit, which is used to download the new version project from the version database through the target program management module, and set the value of the test idle flag to the fourth value when the new version project is downloaded successfully.
6. The device according to claim 5, characterized in that The target file acquisition module includes: An editing result integration unit, which is used to introduce the lower computer editing result into the new version project, and call the functions in the lower computer editing result through the new version project to obtain an integration result. An integration result compilation unit, which is used to compile the integration result to obtain a target file.
7. The device according to claim 5, characterized in that The device further includes: A test code control module, which is used to control the startup of the lower computer test code associated with the target macro version information according to the target macro version information to which the version number information of the new version project belongs, and control the shutdown of other lower computer test codes.
8. A vehicle electronic automation test system, characterized in that, including: One or more processors; A storage device, which is used to store one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the vehicle electronic automation test method according to any one of claims 1-4.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the vehicle electronic automation test method according to any one of claims 1-4.
Citation Information
Patent Citations
A method and system for realizing automatic software testing based on a vehicle body electronic module
CN109446106A
Long -range renewal device of vehicle ECU
CN205899529U