Vehicle data closed-loop automated testing method, device, equipment and medium

Abstract

The present application relates to the field of vehicle technology, and more particularly to a method, apparatus, device, and medium for automated data closed-loop testing of a vehicle. The method comprises: setting a test target within the collection range of the vehicle to be tested; obtaining the number of events of the vehicle to be tested collecting the test target and the number of commands of the server pulling events; and determining that the data closed-loop test of the vehicle to be tested is qualified when the number of events is equal to the number of commands; otherwise, determining that the data closed-loop test of the vehicle to be tested is unqualified. This solves the problem of conventional manual testing of data closed-loops in the related art, which results in reduced accuracy and efficiency, and a reduced testing experience.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a method, device, equipment and medium for automatic closed-loop data testing of a vehicle. Background Art

[0002] Data loops are crucial for autonomous driving, so efficient and accurate testing is crucial. Manual testing is often used in related technologies. However, due to the vast scope and volume of data involved in SDA projects, manual testing of hardware links is not only difficult but also highly inefficient, potentially failing to identify problems. Summary of the Invention

[0003] The present application provides a vehicle data closed-loop automated testing method, device, testing equipment and storage medium to solve the problems in the related art of usually testing data closed-loop through manual testing methods, resulting in reduced test accuracy and efficiency, and reduced testing experience.

[0004] The first aspect of the present application provides a method for automated closed-loop data testing of a vehicle, comprising the following steps: setting a test target within the collection range of the vehicle to be tested; obtaining the number of events of the vehicle to be tested collecting the test target and the number of commands of the server pulling events; when the number of events is equal to the number of commands, determining that the data closed-loop test of the vehicle to be tested is qualified; otherwise, determining that the data closed-loop test of the vehicle to be tested is unqualified.

[0005] Based on the above technical means, the embodiments of the present application can realize automated closed-loop data testing of vehicles, reduce the difficulty of testing, avoid the low efficiency and inaccuracy of manual testing, effectively improve the accuracy and efficiency of data closed-loop testing, and enhance the user's testing experience.

[0006] Furthermore, the determination that the data closed-loop test of the vehicle to be tested is unqualified includes: when the number of events is greater than the number of commands, determining that the event upload channel has lost event information; when the number of events is less than the number of commands, determining that the vehicle to be tested has abnormally sent event information.

[0007] According to the above technical means, the embodiment of the present application can detect the specific reasons for the failure of the data closed-loop test, provide a reference direction for the optimization of the closed-loop test, and improve the user experience.

[0008] Furthermore, before placing the test target within the collection range of the vehicle to be tested, it includes: identifying whether the target model file is compiled successfully; if the target model file is compiled successfully, determining that the data closed-loop test environment meets the test conditions, and placing the test target within the collection range of the vehicle to be tested; if the target model file fails to compile, calling the compilation module to compile the target model file until the target model file is compiled successfully.

[0009] According to the above technical means, the embodiment of the present application can automatically build a test environment before testing, that is, it has the ability to build a test environment, thereby improving the degree of automation of data closed-loop testing.

[0010] Furthermore, the calling compilation module compiles the target model file until the target model file is compiled successfully, including: obtaining the statistical number of times the target model file fails to compile; when the statistical number is greater than a preset number, controlling the compilation module to stop compiling and generating a prompt for the integrity check of the target model file.

[0011] According to the above technical means, the embodiment of the present application can provide a prompt for model file integrity check when multiple compilation fails, promptly remind the user of the reasons for the failure, assist the user in setting up the environment, and improve the user's usage experience.

[0012] Furthermore, before identifying whether the target model file is compiled successfully, it includes: judging whether all target devices participating in the data closed-loop test in the vehicle to be tested are in the same subnet; if all target devices are in the same subnet, obtaining the target model file according to the model file address input by the user; if all target devices are not in the same subnet, reconfiguring all target devices until all target devices are in the same subnet.

[0013] According to the above technical means, the embodiment of the present application can automatically configure all target devices participating in the data closed-loop test to be in the same subnet, provide conditions for setting up an automated test environment, and improve the feasibility of setting up the test environment.

[0014] Furthermore, the reconfiguration of all target devices until all target devices are in the same subnet includes: sequentially executing configuration operations of mounting a driver, adding a network port, configuring a network port, adding a default route, and changing a configuration file on all target devices; when all configuration operations are successful, if it is detected that all target devices are in the same subnet, the reconfiguration is successful; if all target devices are not in the same subnet, a fault prompt is generated; when any operation in the configuration operation is unsuccessful, all target devices are reconfigured.

[0015] According to the above technical means, the embodiment of the present application can automatically reconfigure when the configuration fails, without the need for manual operation by the user, and after the configuration is successful, when it is detected that all target devices are still not in the same subnet, a fault prompt will be issued, so that the user can obtain fault information in time and perform troubleshooting in time.

[0016] The second aspect of the present application provides a data closed-loop automated testing device for a vehicle, including: a setting module for setting a test target within the collection range of the vehicle to be tested; an acquisition module for acquiring the number of events of the vehicle to be tested collecting the test target and the number of commands of the server pulling events; a judgment module for judging that the data closed-loop test of the vehicle to be tested is qualified when the number of events is equal to the number of commands, otherwise, judging that the data closed-loop test of the vehicle to be tested is unqualified.

[0017] Furthermore, the determination module is further configured to: determine that the event upload channel has lost event information when the number of events is greater than the number of commands; and determine that the vehicle to be tested has abnormally sent event information when the number of events is less than the number of commands.

[0018] Furthermore, it also includes: an identification module, which is used to identify whether the target model file is compiled successfully before the test target is placed within the collection range of the vehicle to be tested; if the target model file is compiled successfully, it is determined that the data closed-loop test environment meets the test conditions, and the test target is placed within the collection range of the vehicle to be tested; if the target model file fails to compile, the compilation module is called to compile the target model file until the target model file is compiled successfully.

[0019] Furthermore, the identification module is further used to: obtain the statistical number of compilation failures of the target model file; when the statistical number is greater than a preset number, control the compilation module to stop compiling and generate a prompt for integrity detection of the target model file.

[0020] Furthermore, it also includes: a judgment module, which is used to judge whether all target devices participating in the data closed-loop test in the vehicle to be tested are in the same subnet before identifying whether the target model file is compiled successfully; if all target devices are in the same subnet, the target model file is obtained according to the model file address input by the user; if all target devices are not in the same subnet, all target devices are reconfigured until all target devices are in the same subnet.

[0021] Furthermore, the judgment module is further used to: perform configuration operations of mounting drivers, adding network ports, configuring network ports, adding default routes and changing configuration files on all target devices in sequence; when all configuration operations are successful, if it is detected that all target devices are in the same subnet, the reconfiguration is successful; if all target devices are not in the same subnet, a fault prompt is generated; when any operation in the configuration operation is unsuccessful, all target devices are reconfigured.

[0022] The third aspect of the present application provides a vehicle, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the data closed-loop automated testing method for the vehicle as described in the above embodiment.

[0023] The fourth aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement the data closed-loop automated testing method for a vehicle as described in the above embodiment.

[0024] Therefore, this application has at least the following beneficial effects:

[0025] (1) The embodiments of the present application can realize automated closed-loop data testing of vehicles, reduce the difficulty of testing, avoid the low efficiency and inaccuracy of manual testing, effectively improve the accuracy and efficiency of data closed-loop testing, and enhance the user's testing experience;

[0026] (2) The embodiments of the present application can detect the specific reasons why the data closed-loop test fails, and can provide a reference direction for optimizing the closed-loop test, thereby improving the user experience;

[0027] (3) The embodiment of the present application can automatically build a test environment before testing, that is, it has the ability to build a test environment, which improves the automation level of data closed-loop testing;

[0028] (4) The embodiment of the present application can prompt the user to check the integrity of the model file when multiple compilations fail, promptly remind the user of the reasons for the failure, assist the user in setting up the environment, and improve the user's experience;

[0029] (5) The embodiment of the present application can automatically configure all target devices participating in the data closed-loop test to be in the same subnet, providing conditions for setting up an automated test environment and improving the feasibility of setting up the test environment;

[0030] (6) The embodiment of the present application can automatically reconfigure when configuration fails, without the need for manual operation by the user, and after successful configuration, when it is detected that all target devices are still not in the same subnet, a fault prompt is given, so that the user can obtain fault information in time and perform troubleshooting in time.

[0031] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0033] Figure 1 Flowchart of a closed-loop automated data testing method for a vehicle according to an embodiment of the present application;

[0034] Figure 2 This is a flow chart of a data closed-loop automated testing method for a vehicle according to one embodiment of the present application;

[0035] Figure 3 This is an example diagram of a data closed-loop automated testing device for a vehicle provided according to an embodiment of the present application;

[0036] Figure 4 This is a schematic diagram of the structure of the test equipment provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following describes in detail embodiments of the present application, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0038] Due to the vast scope and volume of data involved in closed-loop SDA projects, manually testing changes in data closed-loop hardware links is not only difficult but also likely to miss problems due to low efficiency. Therefore, an automated testing tool capable of automating the testing of data closed-loop hardware links is essential. Furthermore, since configuring a test environment is a complex process, this automated testing tool should also be able to build a test environment.

[0039] Based on the above-mentioned existing problems and needs, an embodiment of the present application provides a tool for automatically setting up a data closed-loop hardware test environment and monitoring data flow, which realizes the automated construction of the test environment for the data closed-loop hardware part and the automated testing of the hardware link.

[0040] The following describes the data closed-loop automated testing method, device, testing equipment and storage medium for vehicles according to the embodiments of the present application with reference to the accompanying drawings. Specifically, Figure 1A flow chart of a closed-loop automated vehicle data testing method provided in an embodiment of the present application.

[0041] like Figure 1 As shown, the vehicle data closed-loop automated testing method includes the following steps:

[0042] In step S101 , a test target is set within the collection range of the vehicle to be tested.

[0043] The test objectives can be selected based on actual test requirements and are not specifically limited.

[0044] It is understandable that the embodiment of the present application can use Shell scripts to monitor data streams. When monitoring data streams, the program will automatically turn on the camera and prompt the user to aim at the image to be identified. When the user is ready, the data stream monitoring program will start to execute.

[0045] In step S102, the number of events of the vehicle to be tested collecting the test target and the number of commands of the server to pull the event are obtained.

[0046] As you can understand, the data closed-loop rig primarily calls three programs: the data acquisition module, the abstraction module, and the forward-facing camera main program. These three modules are executed sequentially, first monitoring their successful launch. If not, the system checks the integrity of the relevant files, notifying the user of a specific incomplete file and closing the program. If all three modules are successfully launched, the system matches their associated results, capturing the number of events and commands.

[0047] Specifically, once the camera is focused on the target image, the program sequentially launches the data acquisition module, the abstraction module, and the main forward-view camera program. If an error occurs while calling the main forward-view camera program, the user will be prompted to check the integrity of the files in the model directory. The program also monitors changes in the output of the data acquisition module, redirects it to a text file, and extracts keywords related to the number of events from the output.

[0048] After the program completes calling the three modules, it will continue to count the commands received from the cloud to determine the connectivity of the upload link channel for event information. The program will continuously record the number of commands received from the cloud and then match the size with the keywords extracted by the data collection module.

[0049] In step S103 , when the number of events is equal to the number of commands, it is determined that the data closed-loop test of the vehicle to be tested is qualified; otherwise, it is determined that the data closed-loop test of the vehicle to be tested is unqualified.

[0050] It can be understood that the embodiment of the present application can realize the qualified judgment of the data closed-loop test based on the number of commands received by the cloud and the number of keywords extracted by the data acquisition module, thereby realizing the automated data closed-loop testing of the vehicle, reducing the difficulty of testing, avoiding the low efficiency and inaccuracy of manual testing, effectively improving the accuracy and efficiency of the data closed-loop test, and enhancing the user's testing experience.

[0051] In an embodiment of the present application, determining that the data closed-loop test of the vehicle to be tested is unqualified includes: when the number of events is greater than the number of commands, determining that the event upload channel has lost event information; when the number of events is less than the number of commands, determining that the vehicle to be tested has abnormally sent event information.

[0052] It can be understood that the embodiments of the present application can detect the specific reasons why the data closed-loop test fails, and can provide a reference direction for optimizing the closed-loop test, thereby improving the user experience.

[0053] Specifically, if the number of commands received from the cloud exceeds the number of keywords extracted by the data acquisition module, the data acquisition module will be prompted to send event information abnormally and the abnormal behavior will be recorded. If the number of keywords extracted by the data acquisition module exceeds the number of commands received from the cloud, the event upload channel will be prompted to lose information and the abnormal behavior will be recorded.

[0054] In the above embodiment, the embodiment of the present application uses Shell scripts to monitor data streams. Before monitoring the data streams, the embodiment of the present application can also use Shell scripts to apply all the commands required for building a data closed-loop test bench to form an automated test environment. The following will be specifically explained:

[0055] In an embodiment of the present application, before placing the test target within the collection range of the vehicle to be tested, the process includes: identifying whether the target model file is successfully compiled; if the target model file is successfully compiled, determining that the data closed-loop test environment meets the test conditions, and placing the test target within the collection range of the vehicle to be tested;

[0056] If the target model file fails to compile, the compilation module is called to compile the target model file until the target model file is compiled successfully.

[0057] It can be understood that the embodiment of the present application can first identify whether the system has the test environment required for bench testing. If the test environment exists, it will skip the step of data flow monitoring. Otherwise, it will start to automatically build the environment, so that the test environment can be automatically built before the test, that is, it has the ability to build a test environment, thereby improving the degree of automation of data closed-loop testing.

[0058] In an embodiment of the present application, the compilation module is called to compile the target model file until the target model file is compiled successfully, including: obtaining the statistical number of target model file compilation failures; when the statistical number is greater than the preset number, controlling the compilation module to stop compiling and generating a prompt for target model file integrity detection.

[0059] The preset number of times can be set according to actual conditions, such as 2 times or 3 times, etc., without specific limitation.

[0060] It is understandable that when multiple compilation failures occur, a prompt for model file integrity check can be provided to promptly inform the user of the reasons for the failure, assist the user in setting up the environment, and improve the user experience.

[0061] In an embodiment of the present application, before identifying whether the target model file is compiled successfully, it includes: determining whether all target devices participating in the data closed-loop test in the vehicle to be tested are in the same subnet; if all target devices are in the same subnet, obtaining the target model file according to the model file address input by the user; if all target devices are not in the same subnet, reconfiguring all target devices until all target devices are in the same subnet.

[0062] It can be understood that the embodiment of the present application can automatically configure all target devices participating in the data closed-loop test to be in the same subnet, provide conditions for setting up an automated test environment, and improve the feasibility of setting up the test environment.

[0063] In an embodiment of the present application, all target devices are reconfigured until all target devices are in the same subnet, including: performing configuration operations of mounting a driver, adding a network port, configuring a network port, adding a default route, and changing a configuration file on all target devices in sequence; when all configuration operations are successful, if it is detected that all target devices are in the same subnet, the reconfiguration is successful; if all target devices are not in the same subnet, a fault prompt is generated; when any operation in the configuration operation is unsuccessful, all target devices are reconfigured.

[0064] It can be understood that the embodiment of the present application can execute the environment building commands in sequence according to the program settings, and check whether the command is executed successfully by matching the results of the commands. At the same time, a retry mechanism is used to re-execute the currently failed command when the command execution fails; and after the command execution fails multiple times, the relevant failure reasons are prompted to assist the user in building the environment, so that when the configuration fails, it can be automatically reconfigured without manual operation by the user, and after the configuration is successful, when it is detected that all target devices are still not in the same subnet, a fault prompt is issued, so that the user can obtain fault information in time and perform troubleshooting in time.

[0065] Therefore, the embodiment of the present application can realize the testing work of the data closed loop module in the SDA architecture, which supports the construction of the test environment on the hardware and the changes of various indicators and data flows during the data closed loop operation. The following will describe the data closed loop automated testing method of the vehicle through a specific embodiment. Figure 2 As shown, the following steps are included:

[0066] 1. Before using this tool, you must first set up the hardware environment, then log in to the C2 controller system and open the automated tool. The tool will first determine whether all hardware devices are in the same subnet. If the devices are not in the same subnet, it will execute the subnet configuration program. The program will sequentially execute commands to mount the 8021 driver, add VLAN network ports, configure VLAN network ports, add default routes, modify configuration files, and check whether the devices are in the same subnet. If the command execution fails, it will prompt the specific information of the failed step and then close the tool. If the execution is successful, the results of the successful step will be listed.

[0067] 2. After confirming that all devices are on the same subnet, the program prompts the user to enter the model file address. After entering the model file address, the program searches for a folder named "build" in the current directory to determine whether the model file has been compiled. This folder is generated after the model is compiled. If the model file has not been compiled, the program executes the compilation command in the current directory. If the compilation fails after multiple attempts, the user is prompted to check the integrity of the model file.

[0068] 3. After the model file is compiled, the automated test environment of the tool is set up. The following tools will begin to monitor the data flow of the data closed-loop hardware:

[0069] 3.1. First, the program will open the camera and prompt the user to align it with the target image. Once the camera is aligned with the target image, the program will sequentially launch the data acquisition module, the abstraction module, and the front view camera main program. If an error occurs while calling the front view camera main program, the user will be prompted to check the integrity of the files in the model directory.

[0070] 3.2. At the same time, the program will monitor the changes in the output information of the data acquisition module. The program will redirect the output information of the data acquisition module to a text file and extract the keywords about the number of events in the results.

[0071] 3.3. After the program completes calling the three modules, it will continuously count the commands for pulling data from the cloud to determine the connectivity of the event information upload link channel. The program will continuously record the number of commands received from the cloud and match the size with the keywords extracted by the data acquisition module. If the number of commands received from the cloud exceeds the keywords extracted by the data acquisition module, the data acquisition module will be prompted to abnormally send event information and the abnormal behavior will be recorded. If the keywords extracted by the data acquisition module are greater than the number of commands received from the cloud, the event upload channel will be prompted to lose information and the abnormal behavior will be recorded.

[0072] 3.4. While the program is running, it monitors keyboard input. When the user enters q+enter, the program stops monitoring the data closed-loop hardware. It then outputs a test report to the console and saves it in the model directory. The test report includes the running time of the automation tool, the number of frames extracted by the abstract module, the number of events identified, the number of commands received from the cloud, and abnormal behavior.

[0073] The vehicle data closed-loop automated testing method proposed in the embodiment of the present application can realize the vehicle data closed-loop automated testing, reduce the testing difficulty, avoid the low efficiency and inaccuracy of manual testing, and effectively improve the accuracy and efficiency of data closed-loop testing; and can detect the specific reasons for the failure of the data closed-loop test, and provide a reference direction for the optimization of the closed-loop test; at the same time, it can automatically build a test environment before the test, that is, it has the ability to build a test environment, which improves the degree of automation of data closed-loop testing, and can perform model file integrity detection prompts when multiple compilations fail, and promptly remind users of the reasons for the relevant failures to assist users in building the environment, thereby improving the user experience.

[0074] Next, the data closed-loop automatic testing device for a vehicle proposed in an embodiment of the present application will be described with reference to the accompanying drawings.

[0075] Figure 3 It is a block diagram of a data closed-loop automated testing device for a vehicle according to an embodiment of the present application.

[0076] like Figure 3 As shown, the vehicle data closed-loop automatic testing device 10 includes: a setting module 100 , an acquisition module 200 and a determination module 300 .

[0077] Among them, the setting module 100 is used to set the test target within the collection range of the vehicle to be tested; the acquisition module 200 is used to obtain the number of events of the vehicle to be tested collecting the test target and the number of commands of the server pulling events; the judgment module 300 is used to judge that the data closed-loop test of the vehicle to be tested is qualified when the number of events is equal to the number of commands, otherwise, it is judged that the data closed-loop test of the vehicle to be tested is unqualified.

[0078] In the embodiment of the present application, the determination module 300 is further used to: when the number of events is greater than the number of commands, determine that the event upload channel has lost event information; when the number of events is less than the number of commands, determine that the vehicle to be tested has abnormally sent event information.

[0079] In the embodiment of the present application, the apparatus 10 of the embodiment of the present application further includes an identification module. The identification module is configured to identify whether a target model file has been successfully compiled before placing the test target within the acquisition range of the vehicle to be tested. If the target model file has been successfully compiled, the data closed-loop test environment is determined to meet the test conditions, and the test target is placed within the acquisition range of the vehicle to be tested. If the target model file fails to be compiled, the compilation module is invoked to compile the target model file until the target model file is successfully compiled.

[0080] In an embodiment of the present application, the identification module is further used to: obtain the statistical number of target model file compilation failures; when the statistical number is greater than a preset number, control the compilation module to stop compilation and generate a prompt for target model file integrity detection.

[0081] In the embodiment of the present application, the apparatus 10 of the embodiment of the present application further includes a judgment module. The judgment module is configured to determine whether all target devices in the vehicle under test that participate in the data closed-loop test are in the same subnet before determining whether the target model file has been successfully compiled; if all target devices are in the same subnet, the target model file is obtained based on the model file address input by the user; if all target devices are not in the same subnet, all target devices are reconfigured until all target devices are in the same subnet.

[0082] In an embodiment of the present application, the judgment module is further used to: execute configuration operations of mounting a driver, adding a network port, configuring a network port, adding a default route, and changing a configuration file on all target devices in sequence; when all configuration operations are successful, if it is detected that all target devices are in the same subnet, the reconfiguration is successful; if all target devices are not in the same subnet, a fault prompt is generated; if any operation in the configuration operation is unsuccessful, all target devices are reconfigured.

[0083] It should be noted that the above explanation of the embodiment of the vehicle data closed-loop automatic testing method is also applicable to the vehicle data closed-loop automatic testing device of this embodiment, and will not be repeated here.

[0084] The data closed-loop automated testing device for a vehicle proposed in the embodiment of the present application can realize data closed-loop automated testing of the vehicle, reduce the difficulty of testing, avoid the low efficiency and inaccuracy of manual testing, and effectively improve the accuracy and efficiency of data closed-loop testing; and can detect the specific reasons for failure of the data closed-loop test, and provide a reference direction for the optimization of the closed-loop test; at the same time, it can automatically build a test environment before testing, that is, it has the ability to build a test environment, which improves the degree of automation of data closed-loop testing, and can perform model file integrity detection prompts when multiple compilations fail, and promptly remind users of the reasons for the relevant failures to assist users in building the environment, thereby improving the user's usage experience.

[0085] Figure 4 A schematic diagram of the structure of the test equipment provided in an embodiment of the present application. The vehicle may include:

[0086] Memory 401 , processor 402 , and computer programs stored in the memory 401 and executable on the processor 402 .

[0087] When the processor 402 executes the program, the vehicle data closed-loop automated testing method provided in the above embodiment is implemented.

[0088] Furthermore, the test equipment also includes:

[0089] The communication interface 403 is used for communication between the memory 401 and the processor 402 .

[0090] The memory 401 is used to store computer programs that can be run on the processor 402 .

[0091] The memory 401 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0092] If the memory 401, the processor 402, and the communication interface 403 are implemented independently, the communication interface 403, the memory 401, and the processor 402 can be connected to each other via a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0093] Optionally, in a specific implementation, if the memory 401, the processor 402 and the communication interface 403 are integrated on a chip, the memory 401, the processor 402 and the communication interface 403 can communicate with each other through an internal interface.

[0094] The processor 402 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0095] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-mentioned vehicle data closed-loop automated testing method.

[0096] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

[0097] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of technical features indicated. Thus, a feature specified as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of this application, "N" means at least two, for example, two, three, etc., unless otherwise specifically defined.

[0098] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present application belong.

[0099] It should be understood that various parts of the present application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiment, the N steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array, a field programmable gate array, etc.

[0100] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0101] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A data closed-loop automated testing method for a vehicle, characterized in that: The following steps are involved: Set the test target within the collection range of the vehicle to be tested; Obtaining the number of events of the vehicle to be tested collecting the test target and the number of commands of the server to pull events; When the number of events is equal to the number of commands, determining that the data closed-loop test of the vehicle to be tested is qualified; otherwise, determining that the data closed-loop test of the vehicle to be tested is unqualified; Before placing the test target within the acquisition range of the vehicle to be tested, including: Identify whether the target model file is compiled successfully; If the target model file is compiled successfully, it is determined that the data closed-loop test environment meets the test conditions, and the test target is placed within the collection range of the vehicle to be tested; If the target model file fails to be compiled, calling the compilation module to compile the target model file until the target model file is successfully compiled, calling the compilation module to compile the target model file until the target model file is successfully compiled, including: Obtaining a statistical count of the number of times the target model file fails to compile; When the statistical number of times is greater than a preset number of times, the compiling module is controlled to stop compiling and a prompt for integrity detection of the target model file is generated.

2. The method according to claim 1, characterized in that The determining that the data closed-loop test of the vehicle to be tested fails includes: When the number of events is greater than the number of commands, it is determined that the event upload channel has lost event information; When the number of events is less than the number of commands, it is determined that the vehicle to be tested sends event information abnormally.

3. The method according to claim 1, characterized in that Before identifying whether the target model file is compiled successfully, include: Determine whether all target devices participating in the data closed-loop test in the vehicle to be tested are in the same subnet; If all target devices are in the same subnet, the target model file is obtained according to the model file address input by the user; If all the target devices are not in the same subnet, all the target devices are reconfigured until all the target devices are in the same subnet.

4. The method according to claim 3, characterized in that The reconfiguring of all target devices until all target devices are in the same subnet includes: Perform the configuration operations of mounting drivers, adding network ports, configuring network ports, adding default routes, and changing configuration files on all target devices in sequence; When all configuration operations are successful, if it is detected that all target devices are in the same subnet, the reconfiguration is successful; if all target devices are not in the same subnet, a fault prompt is generated; When any operation in the configuration operation is unsuccessful, all the target devices are reconfigured.

5. A vehicle data closed-loop automated testing device, used to implement the vehicle data closed-loop automated testing method according to any one of claims 1 to 4, characterized in that: include: A setting module, used to set the test target within the collection range of the vehicle to be tested; An acquisition module, configured to acquire the number of events in which the vehicle to be tested collects the test target and the number of commands in which the server pulls events; The determination module is configured to determine that the data closed-loop test of the vehicle to be tested is qualified when the number of events is equal to the number of commands; otherwise, determine that the data closed-loop test of the vehicle to be tested is unqualified.

6. The device according to claim 5, characterized in that The determination module is further configured to: When the number of events is greater than the number of commands, it is determined that the event upload channel has lost event information; When the number of events is less than the number of commands, it is determined that the vehicle to be tested sends event information abnormally.

7. A testing device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the data closed-loop automated testing method for a vehicle as described in any one of claims 1 to 4.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the data closed-loop automated testing method for a vehicle as described in any one of claims 1 to 4.

Images