Testing system and smoking testing method of vehicle-mounted controller

Abstract

The invention provides a test system and a smoking test method of a vehicle-mounted controller, and the method can be applied to a test management system, and comprises the steps: judging whether the vehicle-mounted controller completes the development and release of a new software version or not; if yes, creating a software flashing task of the vehicle-mounted controller, and performing software flashing on the vehicle-mounted controller according to the software flashing task; after the vehicle-mounted controller finishes software flashing, the smoking test task of the vehicle-mounted controller is determined, and the smoking test is performed on the vehicle-mounted controller according to the smoking test task, so that the smoking test can be automatically performed on the vehicle-mounted controller by utilizing the test management system, and the problem that the existing smoking test needs to be performed on software on a real vehicle or a traditional HiL rack, and the test efficiency is high is solved. The problems that in the prior art, a special person needs to be arranged to deploy a smoking test environment and make a smoking test plan, more testers need to be invested, and meanwhile frequent test environment switching also brings increase of time cost and disordered test plans are solved.

Description

Technical Field

[0001] The present invention relates to the technical field of test management, and particularly relates to a test system and a smoke test method for a vehicle-mounted controller. Background Art

[0002] With the development of new energy vehicles, vehicles are becoming more and more electronic and intelligent. To meet people's intelligent driving needs, new energy vehicles need to be equipped with intelligent driving software.

[0003] Currently, after the intelligent driving software is released, developers do not have an environment for verifying the basic functions of the software, and need to release the software to a real vehicle or a traditional HiL bench for verification. When performing a smoke test on the software on a real vehicle or a traditional HiL bench, it is necessary to arrange special personnel to deploy the smoke test environment and formulate a smoke test plan, which not only requires more test personnel, but also the frequent switching of the test environment brings an increase in time cost and the problem of chaotic test plans. Summary of the Invention

[0004] In view of this, the present application provides a test system and a smoke test method for a vehicle-mounted controller to solve the problems that the existing smoke test needs to be performed on a real vehicle or a traditional HiL bench, requires special personnel to deploy the smoke test environment and formulate a smoke test plan, which not only requires more test personnel, but also the frequent switching of the test environment brings an increase in time cost and the problem of chaotic test plans.

[0005] To achieve the above object, the embodiments of the present invention provide the following technical solutions:

[0006] The first aspect of the present application discloses a smoke test method for a vehicle-mounted controller, which is applied to a test management system. The test management system at least includes a test cabinet, and the test cabinet is connected to the vehicle-mounted controller. The method includes:

[0007] Determine whether the vehicle-mounted controller has completed the development and release of a new software version;

[0008] If it is determined that the vehicle-mounted controller has completed the development and release of the new software version, create a software flashing task for the vehicle-mounted controller, and perform software flashing on the vehicle-mounted controller according to the software flashing task. The software flashing task is a flashing task for the new version software of the vehicle-mounted controller;

[0009] After the vehicle-mounted controller completes the software flashing, determine the smoke test task for the vehicle-mounted controller, and perform a smoke test on the vehicle-mounted controller according to the smoke test task. The smoke test task includes at least one of a communication function test, a high-voltage power-on / off operation test, a gear shifting operation test, a sensor operation test, an intelligent driving function activation test, and a state switching test.

[0010] Optionally, in the above smoke test method for the vehicle-mounted controller, determining whether the vehicle-mounted controller has completed the development and release of a new software version includes:

[0011] Obtain the software version of the vehicle-mounted controller and the software version of the CI server respectively;

[0012] Compare the software version of the vehicle-mounted controller with the software version of the CI server;

[0013] If the software version of the vehicle-mounted controller is different from the software version of the CI server, it is determined that the vehicle-mounted controller has completed the development and release of a new software version;

[0014] If the software version of the vehicle-mounted controller is the same as the software version of the CI server, it is determined that the vehicle-mounted controller has not completed the development and release of a new software version.

[0015] Optionally, in the above smoke test method for the vehicle-mounted controller, creating the software flashing task for the vehicle-mounted controller includes:

[0016] Determine the software information of the vehicle-mounted controller, where the software information is the information of the new version software of the vehicle-mounted controller;

[0017] Determine the configuration project information, configuration case information, and configuration flashing method corresponding to the software information;

[0018] Create according to the configuration project information, the configuration case information, and the configuration flashing method to obtain the software flashing task for the vehicle-mounted controller.

[0019] Optionally, in the above smoke test method for the vehicle-mounted controller, after creating the software flashing task for the vehicle-mounted controller and performing software flashing on the vehicle-mounted controller according to the software flashing task, it further includes:

[0020] If the vehicle-mounted controller cannot complete the software flashing, generate a flashing error message and / or control the software of the vehicle-mounted controller to roll back to the previous version, where the flashing error message includes a flashing error code.

[0021] Optionally, in the above smoke test method for the vehicle-mounted controller, performing a smoke test on the vehicle-mounted controller according to the smoke test task includes:

[0022] Configure the test environment required to execute the smoke test task;

[0023] Perform a smoke test on the vehicle-mounted controller using the test environment.

[0024] Optionally, in the above-mentioned smoke test method for vehicle-mounted controllers, configuring the test environment required for performing the smoke test task includes:

[0025] Determining the hardware configuration information and software configuration information required for performing the smoke test task;

[0026] Invoking the hardware devices corresponding to the hardware configuration information and the software code corresponding to the software configuration information to obtain the test environment required for the smoke test task;

[0027] Among them, the hardware configuration information required for the smoke test task includes at least one of a CAN communication board, an ETH communication board, an IO resource board, and a video injection board, and the software configuration information required for the smoke test task includes at least one of bus simulation software and test management software.

[0028] Optionally, in the above-mentioned smoke test method for vehicle-mounted controllers, after performing the smoke test on the vehicle-mounted controller according to the smoke test task, it further includes:

[0029] Generating a smoke test report;

[0030] Uploading the smoke test report to the cloud.

[0031] A second aspect of the present application discloses a test system, including: a CI server, a task manager, an invoker, and a test management system, and the test management system at least includes a test cabinet;

[0032] The test management system is respectively connected to the CI server, the task manager, and the invoker, and is used to execute the smoke test method for vehicle-mounted controllers according to any one of the first aspect.

[0033] Optionally, in the above-mentioned test system, the connection between the test cabinet and the vehicle-mounted controller to be tested includes at least one of an Ethernet communication connection, a LIN communication connection, and a CAN communication connection.

[0034] Optionally, in the above-mentioned test system, it further includes: a programmable power supply, and the programmable power supply is at least used to supply power to the vehicle-mounted controller to be tested, and / or supply power to at least one of the test cabinet, the CI server, the task manager, and the invoker.

[0035] The present invention provides a method for smoke testing an in-vehicle controller, which is applied to a test management system. The test management system includes at least a test cabinet, and the test cabinet is connected to the in-vehicle controller. The method includes: determining whether the in-vehicle controller has completed the development and release of a new software version; if it is determined that the in-vehicle controller has completed the development and release of the new software version, creating a software flashing task for the in-vehicle controller, and flashing the software of the in-vehicle controller according to the software flashing task, where the software flashing task is a flashing task for the new version software of the in-vehicle controller; after the in-vehicle controller completes the software flashing, determining a smoke testing task for the in-vehicle controller, and performing a smoke test on the in-vehicle controller according to the smoke testing task, where the smoke testing task includes at least one of a communication function test, a high-voltage power-on / off operation test, a gear shifting operation test, a sensor operation test, an intelligent driving function activation test, and a state switching test. It can automatically perform smoke testing on the in-vehicle controller using the test management system, solving the problem that existing smoke testing needs to be carried out on a real vehicle or a traditional HiL bench for software, requiring special personnel to deploy the smoke testing environment and formulate a smoke testing plan, which not only requires more test personnel, but also the frequent switching of the testing environment brings an increase in time cost and confusion in the testing plan. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0037] Figure 1 It is a flowchart of a method for smoke testing an in-vehicle controller provided by an embodiment of the present application;

[0038] Figure 2 It is a flowchart for determining the development and release of a new software version provided by an embodiment of the present application;

[0039] Figure 3 It is a flowchart for creating a software flashing task for an in-vehicle controller provided by an embodiment of the present application;

[0040] Figure 4 It is a flow chart of a smoke test for an in-vehicle controller provided by an embodiment of the present application;

[0041] Figure 5 It is a schematic diagram for building a communication function test environment provided by an embodiment of the present application;

[0042] Figure 6 It is a schematic diagram for building a vision function test environment provided by an embodiment of the present application;

[0043] Figure 7 It is a flowchart of another method for smoke testing an in-vehicle controller provided by an embodiment of this application;

[0044] Figure 8 It is a schematic structural diagram of a test system provided by this application. Specific implementation manners

[0045] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0046] This application provides a test system and a method for smoke testing an in-vehicle controller to solve the problem that the existing smoke testing needs to be performed on a real vehicle or a traditional HiL bench for software, which requires arranging special personnel to deploy the smoke testing environment and formulate a smoke testing plan. This not only requires more testing personnel, but also the frequent switching of the testing environment brings an increase in time cost and confusion in the testing plan.

[0047] The method for smoke testing the in-vehicle controller can be applied to a test management system. The test management system at least includes a test cabinet, and the test cabinet is connected to the in-vehicle controller. Please refer to Figure 1 ., and the method mainly includes the following steps:

[0048] S101. Determine whether the development and release of a new software version of the in-vehicle controller are completed.

[0049] In some embodiments, the specific execution process of step S101, determining whether the development and release of a new software version of the in-vehicle controller are completed, is as Figure 2 shown, and mainly includes steps S201 to S204:

[0050] S201. Obtain the software version of the in-vehicle controller and the software version of the CI server respectively.

[0051] In practical applications, the test management system can obtain the software version of the in-vehicle controller by communicating with the in-vehicle controller.

[0052] In specific applications, the software version of the in-vehicle controller can also be obtained through a diagnostic tool such as using OBD-II (On-Board Diagnostic Generation 2); of course, the software version of the in-vehicle controller can also be obtained through a remote update service. It can be determined according to the application environment and user requirements, and all are within the protection scope of this application.

[0053] A CI (Continuous Integration) server is a tool used to automatically execute build, test, and deployment processes during software development. The CI server is mainly used to store software versions of in-vehicle controllers. When developers complete the development of a new version of the in-vehicle controller software and release it on the CI server, the CI server will update the software version information of the in-vehicle controller it stores.

[0054] S202. Compare the software version of the in-vehicle controller with the software version of the CI server.

[0055] In practical applications, after obtaining the software version of the in-vehicle controller and the software version of the CI server, the software version of the in-vehicle controller can be compared with the software version of the CI server. For example, compare the software version number of the in-vehicle controller with the software version number of the CI server.

[0056] S203. If the software version of the in-vehicle controller is different from the software version of the CI server, it can be determined that the in-vehicle controller has completed the development and release of the new software version.

[0057] In practical applications, if the software version of the in-vehicle controller is different from the software version of the CI server, it means that the software version number in the CI server is higher than the software version number of the in-vehicle controller, and it can be determined that the in-vehicle controller has completed the development and release of the new software version.

[0058] S204. If the software version of the in-vehicle controller is the same as the software version of the CI server, it can be determined that the in-vehicle controller has not completed the development and release of the new software version.

[0059] In practical applications, if the software version of the in-vehicle controller is the same as the software version of the CI server, it means that the software version number in the CI service is the same as the software version number of the in-vehicle controller, and it can be determined that the in-vehicle controller has not completed the development and release of the new software version.

[0060] If it is determined that the in-vehicle controller has completed the development and release of the new software version, step S102 can be executed.

[0061] S102. Create a software flashing task for the in-vehicle controller and perform software flashing on the in-vehicle controller according to the software flashing task.

[0062] Among them, the software flashing task is the flashing task of the new version software of the in-vehicle controller.

[0063] In some embodiments, the specific process of creating a software flashing task for the in-vehicle controller in step S102 is as Figure 3 shown, mainly including steps S301 to S303:

[0064] S301. Determine the software information of the vehicle-mounted controller.

[0065] Among them, the software information is the information of the new version software of the vehicle-mounted controller.

[0066] In practical applications, after obtaining the new version software of the vehicle-mounted controller, the relevant information of the new version software can be used as the information of the new version software of the vehicle-mounted controller. The information of the new version software of the vehicle-mounted controller includes at least the version number, build number, etc. of the new version software.

[0067] S302. Determine the configuration project information, configuration case information, and configuration flashing method corresponding to the software information.

[0068] Among them, the configuration project information is the tools, environment, and resources required for software flashing, the configuration case information is the operation method under the corresponding configuration for software flashing, and the configuration flashing method is the configuration data required for software flashing.

[0069] In practical applications, configuration information for implementing smoke testing can be pre-configured for the software information of the vehicle-mounted controller. This configuration information can include configuration project information, configuration case information, configuration flashing method, etc. After obtaining the software information of the vehicle-mounted controller, the corresponding configuration project information, configuration case information, and configuration flashing method can be determined according to the software information of the vehicle-mounted controller.

[0070] Specifically, the corresponding configuration project information can be determined first according to the software information, then the configuration case information, and finally the configuration flashing method.

[0071] S303. Create according to the configuration project information, configuration case information, and configuration flashing method to obtain the software flashing task of the vehicle-mounted controller.

[0072] In practical applications, creation can be carried out according to the configuration project information, configuration case information, and configuration flashing method to obtain the software flashing task of the vehicle-mounted controller.

[0073] S103. After the vehicle-mounted controller completes software flashing, determine the smoke testing task of the vehicle-mounted controller, and perform smoke testing on the vehicle-mounted controller according to the smoke testing task.

[0074] The smoke testing task includes at least one of communication function testing, high-voltage power-on and power-off operation testing, gear shifting operation testing, sensor working testing, intelligent driving function activation testing, and state switching testing.

[0075] In actual applications, the test management system can call different tools to complete the software flashing of the vehicle controller according to the software flashing task of the vehicle controller. Each time the flashing is performed, the software will be downloaded to obtain the latest version of the software. After the flashing is completed, the vehicle controller will restart, re-enter the vehicle controller to execute the Linux command to obtain the current vehicle controller version and compare it with the latest version. If they are consistent, the flashing is completed. Specifically, the latest version of the software can be obtained through the identifier provided by the user, or a mutually agreed acquisition method, such as providing a version record file, naming the file with the version, etc.

[0076] It should be noted that after the vehicle controller completes the software flashing, that is, after the vehicle controller software is successfully flashed, a smoke test task can be automatically generated according to the smoke test requirements. The smoke test task includes at least one of a communication function test, a high-voltage power on and off operation test, a gear shifting operation test, a sensor operation test, an intelligent driving function activation test, and a state switching test.

[0077] In some embodiments, the specific process of performing a smoke test on the vehicle controller according to the smoke test task in step S103 is as follows: Figure 4 As shown, it mainly includes steps S401 and S402:

[0078] S401. Configure the test environment required to perform the smoke test task.

[0079] In practical applications, the hardware configuration information and software configuration information required for executing the smoke test task can be determined; the hardware device corresponding to the hardware configuration information and the software code corresponding to the software configuration information are called to obtain the test environment required for the smoke test task; wherein, the hardware configuration information required for the smoke test task includes: at least one of a CAN communication board, an ETH communication board, an IO resource board and a video injection board, and the software configuration information required for the smoke test task includes: at least one of a bus simulation software and a test management software.

[0080] It should be noted that the smoke test of the vehicle controller requires a complex test environment. In order to quickly execute the smoke test task, the smoke test system can be initialized by calling software and hardware resources and automatically delegating software and hardware configuration parameters.

[0081] Assuming that the smoke test task is a communication function test, the communication function test environment can be automatically built by calling the bus simulation software and test management software, as well as the ETH communication board and IO resource board. Figure 5 As shown; assuming that the smoke test task is a visual function test, the visual function test environment can be automatically built by calling the bus simulation software and the video injection board, such as Figure 6 shown.

[0082] S402. Conduct a smoke test on the vehicle-mounted controller using the test environment.

[0083] In practical applications, after configuring the test environment required for performing the smoke test task, the vehicle-mounted controller can be smoke-tested using the test environment.

[0084] In some embodiments, after performing the smoke test on the vehicle-mounted controller according to the smoke test task in step S103, as Figure 7 shown, the smoke test method for the vehicle-mounted controller may further include:

[0085] S501. Generate a smoke test report.

[0086] In practical applications, the test management system can quickly execute the smoke test task, complete the test for the underlying logic and basic functions of the software, and generate a smoke test report.

[0087] S502. Upload the smoke test report to the cloud.

[0088] In practical applications, after generating the smoke test report, the smoke test report can be uploaded to the cloud through the notification server and sent to the testers in multiple ways such as email and message prompts. The testers can evaluate the new version of the software through the smoke test report to formulate subsequent test plans.

[0089] It should be noted that the vehicle-mounted controller in this application can be a controller equipped with intelligent driving software. Through the above method, the smoke test of the intelligent driving software can be realized.

[0090] It should also be noted that taking the intelligent driving software as an example, through the above, the smoke test of the iterative intelligent driving software can be quickly performed, reducing the loopholes in the function test when the intelligent driving software is finalized. The test management system automatically adjusts the software and hardware configuration environment and automatically generates test cases. It can effectively improve the test efficiency of verifying the new version of the intelligent driving software, shorten the time for test environment deployment and test execution. That is, by executing the smoke test method of the vehicle-mounted controller through the test management system, it is convenient to upgrade and iterate the software, and accelerate the rapid implementation and test verification of the software.

[0091] The smoke test method for the vehicle-mounted controller provided in this embodiment is applied to a test management system. The test management system at least includes a test cabinet, and the test cabinet is connected to the vehicle-mounted controller. The method includes: determining whether the development and release of a new software version of the vehicle-mounted controller are completed; if it is determined that the development and release of the new software version of the vehicle-mounted controller are completed, creating a software flashing task for the vehicle-mounted controller, and flashing the software of the vehicle-mounted controller according to the software flashing task, where the software flashing task is the flashing task of the new version software of the vehicle-mounted controller; after the software flashing of the vehicle-mounted controller is completed, determining the smoke test task of the vehicle-mounted controller, and performing a smoke test on the vehicle-mounted controller according to the smoke test task, where the smoke test task includes at least one of a communication function test, a high-voltage power-on and power-off operation test, a gear shifting operation test, a sensor operation test, an intelligent driving function activation test, and a state switching test. It can automatically perform a smoke test on the vehicle-mounted controller using the test management system, solving the problem that the existing smoke test needs to be carried out on a real vehicle or a traditional HiL bench for software, requiring special personnel to deploy the smoke test environment and formulate a smoke test plan, which not only requires more test personnel, but also increases the time cost and causes confusion in the test plan due to frequent test environment switching.

[0092] Optionally, in another embodiment of the present application, after performing step S102, creating a software flashing task for the vehicle-mounted controller and flashing the software of the vehicle-mounted controller according to the software flashing task, if the vehicle-mounted controller cannot complete the software flashing, it is also possible to generate a flashing error message and / or control the software of the vehicle-mounted controller to roll back to the previous version, and the flashing error message includes a flashing error code.

[0093] In practical applications, if the vehicle-mounted controller cannot complete the software flashing, the test system can feedback the flashing error code and roll back to the previous software version, and send the flashing result to the developers and testers through the notification server.

[0094] It should be noted that the failure of software flashing does not affect the current test tasks of the testers, and can also enable the developers to repair the vulnerabilities as soon as possible, reduce the overall development time, and improve the development efficiency.

[0095] On the above basis, optionally, another embodiment of the present application also provides a test system, as Figure 8 shown, including: a CI server, a task manager, a caller, and a test management system, where the test management system at least includes a test cabinet;

[0096] The test management system is respectively connected to the CI server, the task manager, and the caller, and is used to execute the smoke test method for the vehicle-mounted controller described in any of the above embodiments.

[0097] In practical applications, the connection between the test cabinet and the vehicle-mounted controller under test may include at least one of the following: Ethernet communication connection, LIN communication connection, and CAN communication connection. It can be determined according to the application environment and user requirements, and all are within the protection scope of this application.

[0098] In some embodiments, the test management system mainly consists of a test cabinet. The test cabinet provides a rich external working environment and signals, as well as virtual working condition simulation capabilities for the vehicle-mounted controller under test, and can effectively implement the smoke test method for the vehicle-mounted controller described in any of the above embodiments, that is Figure 8 The various processes shown.

[0099] Among them, in order to enable the test management system to read the version of the vehicle-mounted controller under test and flash the software version of the vehicle-mounted controller, the test management system can provide a vehicle Ethernet communication box to implement vehicle Ethernet communication with the vehicle-mounted controller under test. Through the vehicle Ethernet communication device, the system can support accessing the vehicle-mounted controller system using traditional industrial Ethernet, modifying files, overwriting files, etc., to modify the software version and underlying logic of the vehicle-mounted controller under test, and accessing virtual addresses, etc.

[0100] At the same time, the Ethernet communication device provides the communication ability of virtual Ethernet nodes. By simulating the Ethernet virtual nodes of the vehicle-mounted controller under test, it is possible to simulate other opponent virtual nodes of the vehicle-mounted controller under test, and meet the requirements of vehicle-mounted large screen controller and domain control Ethernet message simulation in intelligent driving vehicles.

[0101] In some embodiments, the test system may further include: a programmable power supply, which is at least used to supply power to the vehicle-mounted controller under test and / or at least one of the test cabinet, CI server, task manager, and invoker.

[0102] It should be noted that by using this programmable power supply to supply power to the vehicle-mounted controller under test and / or at least one of the test cabinet, CI server, task manager, and invoker, it can not only ensure the smooth progress of the smoke test of the vehicle-mounted controller under test and related equipment, but also reduce the power supply cost and achieve safe and reliable power supply for the test system.

[0103] It should also be noted that in order to ensure the correct execution of test cases, the test management system needs to provide a vehicle simulation editable programmable power supply for the controller under test, such as providing KL15 and KL30 power, so as to meet the power supply requirements of the vehicle-mounted controller under test and other components. Among them, the test management system can provide a power control board card, and through the loading of the upper computer driver program, control the power control board to realize the remote control of the programmable power supply and the manual and automatic power on / off requirements of the vehicle-mounted controller of the vehicle under test.

[0104] In order to provide a complete peripheral environment for the vehicle-mounted controller under test, the test management system can also provide the controller under test with hardware such as CAN / CANFD communication boards, Ethernet communication boards, LIN communication boxes, analog quantity simulation boards, and digital quantity PWM simulation boards. Different hardware boards are powered by a programmable power supply in the system. To ensure the synchronization of output signals between different hardware, a synchronization box and synchronization wires are used to make a hardware synchronization connection for the entire smoke test system.

[0105] The features described in the respective embodiments of this specification can be replaced or combined with each other. For the same or similar parts among the various embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for a system or system embodiment, since it is basically similar to a method embodiment, the description is relatively simple. For the relevant parts, reference can be made to the partial description of the method embodiment. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative efforts.

[0106] Those skilled in the art can further realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0107] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be obvious to those skilled in the art. The general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.

[0108] It should also be noted that in this text, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising said element.

Claims

1. A method for smoke testing an in-vehicle controller, characterized in that, Applied to a test management system, the test management system at least includes a test cabinet, and the test cabinet is connected to the vehicle-mounted controller. The method includes: Determine whether the vehicle-mounted controller has completed the development and release of a new software version; If it is determined that the vehicle-mounted controller has completed the development and release of a new software version, create a software flashing task for the vehicle-mounted controller, and perform software flashing on the vehicle-mounted controller according to the software flashing task. The software flashing task is a flashing task for the new version software of the vehicle-mounted controller; After the vehicle-mounted controller completes software flashing, determine a smoke test task for the vehicle-mounted controller, and perform a smoke test on the vehicle-mounted controller according to the smoke test task. The smoke test task includes at least one of a communication function test, a high-voltage power-on / off operation test, a gear shifting operation test, a sensor operation test, an intelligent driving function activation test, and a state switching test.

2. The smoke test method for the vehicle-mounted controller according to claim 1, wherein, Determining whether the vehicle-mounted controller has completed the development and release of a new software version includes: Obtain the software version of the vehicle-mounted controller and the software version of the CI server respectively; Compare the software version of the vehicle-mounted controller with the software version of the CI server; If the software version of the vehicle-mounted controller is different from the software version of the CI server, it is determined that the vehicle-mounted controller has completed the development and release of a new software version; If the software version of the vehicle-mounted controller is the same as the software version of the CI server, it is determined that the vehicle-mounted controller has not completed the development and release of a new software version.

3. The smoke test method for the vehicle-mounted controller according to claim 1, characterized in that Creating a software flashing task for the vehicle-mounted controller includes: Determine the software information of the vehicle-mounted controller. The software information is the information of the new version software of the vehicle-mounted controller; Determine the configuration project information, configuration case information, and configuration flashing method corresponding to the software information; Create according to the configuration project information, the configuration case information, and the configuration flashing method to obtain the software flashing task of the vehicle-mounted controller.

4. The smoke test method for the vehicle-mounted controller according to claim 1, characterized in that After creating the software flashing task for the vehicle-mounted controller and performing software flashing on the vehicle-mounted controller according to the software flashing task, it further includes: If the vehicle-mounted controller cannot complete software flashing, generate a flashing error message and / or control the software of the vehicle-mounted controller to roll back to the previous version. The flashing error message includes a flashing error code.

5. The smoke test method for an in-vehicle controller according to claim 1, characterized in that Performing a smoke test on the vehicle-mounted controller according to the smoke test task includes: Configure the test environment required to execute the smoke test task; Use the test environment to perform a smoke test on the vehicle-mounted controller.

6. The smoking test method for the vehicle-mounted controller according to claim 5, wherein, Configuring the test environment required to execute the smoke test task includes: Determine the hardware configuration information and software configuration information required to execute the smoke test task; Call the hardware device corresponding to the hardware configuration information and the software code corresponding to the software configuration information to obtain the test environment required for the smoke test task. Among them, the hardware configuration information required for the smoke test task includes at least one of a CAN communication board, an ETH communication board, an IO resource board, and a video injection board, and the software configuration information required for the smoke test task includes at least one of bus simulation software and test management software.

7. The smoke test method for the vehicle-mounted controller according to claim 1, characterized in that, After performing the smoke test on the vehicle-mounted controller according to the smoke test task, it further includes: Generating a smoke test report; Uploading the smoke test report to the cloud.

8. A test system, characterized in that, It includes: A CI server, a task manager, an invoker, and a test management system, and the test management system at least includes a test cabinet; The test management system is respectively connected to the CI server, the task manager, and the invoker, and is used to execute the smoke test method for the vehicle-mounted controller according to any one of claims 1-7.

9. The test system according to claim 8, characterized in that The connection between the test cabinet and the vehicle-mounted controller to be tested includes at least one of an Ethernet communication connection, a LIN communication connection, and a CAN communication connection.

10. The test system according to claim 8, wherein It further includes: A programmable power supply, and the programmable power supply is at least used to supply power to the vehicle-mounted controller to be tested and / or at least one of the test cabinet, the CI server, the task manager, and the invoker.

Images