Vehicle testing system and method, vehicle and storage medium

Abstract

The invention relates to the technical field of vehicle testing, and discloses a vehicle testing system and method, a vehicle and a storage medium, and the vehicle testing system comprises a testing terminal, a plurality of tested vehicles and a cloud server. The cloud server is used for storing a plurality of test requirements; the test terminal is used for determining and installing target test software matched with the type of each tested vehicle based on the test installation package; the target test software is configured with a first test requirement; and each tested vehicle is used for obtaining the second test demand from the cloud server through the target test software, determining a target test demand according to a comparison result of the first test demand and the second test demand, and testing based on the target test demand. The test terminal automatically installs the target test software into the tested vehicle based on the test installation package, manual intervention and configuration errors are avoided, each tested vehicle is allowed to obtain the latest test requirements from the cloud server, and the test requirements are freely and flexibly adjusted.

Description

Technical Field

[0001] This application relates to the field of vehicle testing technology, and more particularly to a vehicle testing system, method, vehicle, and storage medium. Background Technology

[0002] In the vehicle manufacturing industry, End-of-Line (EOL) testing is a crucial step before a vehicle rolls off the production line, used to verify the functional integrity of the entire vehicle's electronic systems. The industry commonly employs a configuration file-driven approach, importing configuration data from external sources to manage test content differently, adapting to the functional combinations and communication logic of various vehicle models. However, existing technologies still face several challenges: test programs are highly dependent on specialized equipment and technicians, resulting in high deployment costs and complex operations; test logic is often embedded in software code, requiring recompilation and re-release for changes, leading to long response cycles and hindering rapid iteration. Summary of the Invention

[0003] In view of this, embodiments of this application provide a vehicle testing system, method, vehicle, and storage medium, which can effectively solve the problems of vehicle testing being highly dependent on technical personnel and having high deployment costs.

[0004] In a first aspect, embodiments of this application provide a vehicle testing system, including: a testing terminal, multiple vehicles under test, and a cloud server; Each of the vehicles under test is communicatively connected to the test terminal and the cloud server, respectively. The cloud server is used to store multiple test requirements, each of which corresponds to a different model of the vehicle under test. The test terminal is used to determine the target test software that is compatible with the model of each of the vehicles under test based on the test installation package, and to install the target test software into the corresponding vehicle under test. The test installation package includes test software for different vehicle models, and the target test software is configured with a first test requirement. Each of the vehicles under test is used to obtain a second test requirement that is compatible with the current vehicle model from multiple test requirements on the cloud server through the target test software; Each of the vehicles under test is also used to compare the first test requirement with the second test requirement using the target test software, determine the target test requirement based on the comparison result, and perform testing based on the target test requirement.

[0005] In a first possible embodiment of the first aspect, each of the vehicles under test includes an on-board host, and the test installation package further includes an automatic identification installation script; The test terminal is used to read the vehicle model information of the vehicle under test based on the automatic identification and installation script, select the target test software that is compatible with the vehicle model under test according to the vehicle model information, and install the target test software into the vehicle host.

[0006] In a second possible embodiment of the first aspect, the target testing software in the vehicle host is used to obtain the vehicle identification code of the vehicle under test when receiving the first test instruction, and send the vehicle identification code as a request parameter to the cloud server, so as to receive the second test requirement returned by the cloud server based on the vehicle identification code.

[0007] In a third possible embodiment of the first aspect, the target test software in the vehicle host is used to take the first test requirement as the target test requirement when the first test requirement and the second test requirement are the same. When the first test requirement differs from the second test requirement, the second test requirement shall be taken as the target test requirement.

[0008] In a fourth possible embodiment of the first aspect, each of the vehicles under test further includes multiple electronic control units; The target test software in the vehicle host is used to generate a corresponding second test instruction based on the target test requirements, and send the second test instruction to each of the electronic control units so that each electronic control unit performs a test action.

[0009] In a fifth possible embodiment of the first aspect, the cloud server is further configured to update the corresponding stored test requirements to the latest configured test requirements in real time upon obtaining the latest configured test requirements; The test requirements in the cloud server are stored in the form of a configuration table on the cloud server. In a sixth possible embodiment of the first aspect, the target testing software in the vehicle host is used to generate a test report based on the test results, and upload the test report and the vehicle identification number of the vehicle under test to the cloud server for storage.

[0010] Secondly, embodiments of this application provide a vehicle testing method, including: When the test terminal determines the target test software that is compatible with the model of each of the vehicles under test based on the test installation package, and installs the target test software on the corresponding vehicle under test, the second test requirement that is compatible with the current model is obtained from multiple test requirements on the cloud server through the target test software. The test installation package includes test software for different vehicle models, and the target test software is configured with a first test requirement; the cloud server is used to store multiple test requirements, each of which corresponds to a different model of the vehicle under test.

[0011] The first test requirement is compared with the second test requirement using the target test software; The target test requirements are determined based on the comparison results, and tests are conducted based on the target test requirements.

[0012] Thirdly, embodiments of this application provide a vehicle, including a memory and a processor, wherein the memory stores a computer program, and the computer program executes the above-described vehicle testing method when it runs on the processor.

[0013] Fourthly, embodiments of this application provide a readable storage medium storing a computer program that executes the vehicle testing method described above when run on a processor.

[0014] The embodiments of this application have the following beneficial effects: This embodiment of a vehicle testing system includes: a test terminal, multiple vehicles under test, and a cloud server; each vehicle under test is communicatively connected to both the test terminal and the cloud server; the cloud server stores multiple test requirements, each corresponding to a different model of vehicle under test; the test terminal determines and installs target test software compatible with the vehicle model of each vehicle under test based on a test installation package; the test installation package includes test software for different vehicle models, and the target test software is configured with first test requirements; each vehicle under test obtains a second test requirement compatible with its current vehicle model from the multiple test requirements on the cloud server through the target test software; each vehicle under test also compares the first test requirement with the second test requirement through the target test software, determines the target test requirement based on the comparison result, and performs testing based on the target test requirement. Based on the above scheme, this application uses a test installation package, where the test terminal automatically selects and installs the matching target test software according to the vehicle model, avoiding manual intervention and configuration errors, and improving vehicle testing efficiency. Moreover, a single test terminal can test multiple vehicles, saving testing costs. It allows each vehicle to obtain the test requirements adapted to its current model from the cloud server and execute the latest test requirements from the cloud server, enabling flexible adjustment of test requirements. Attached Figure Description

[0015] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 A schematic diagram of a first structure of the vehicle testing system according to an embodiment of this application is shown; Figure 2 A second structural schematic diagram of the vehicle testing system according to an embodiment of this application is shown; Figure 3 A third structural schematic diagram of the vehicle testing system according to an embodiment of this application is shown; Figure 4 A schematic flowchart of a vehicle testing method according to an embodiment of this application is shown.

[0017] Explanation of key component symbols: 100 - Vehicle testing system; 110 - Test terminal; 120 - Vehicle under test; 121 - Vehicle host; 130 - Cloud server. Detailed Implementation

[0018] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0019] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0020] In the following text, the terms "comprising," "having," and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as primarily excluding the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more combinations thereof. Furthermore, the terms "first," "second," "third," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0021] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0022] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0023] In the industry, to address the diverse testing needs of EOL (End-of-Life) tests across multiple vehicle models and controllers, a common approach is to write test configuration files, import them into testing software, and then read these files for testing. Current industry practices include two main methods: First, installing diagnostic software on a laptop connected to the vehicle's OBD (On-Board Diagnostics) interface. Before testing, the EOL test script and information are configured on the diagnostic software's test function interface. At the start of the test, the path to the test item configuration file for the tested vehicle model is entered in a pop-up window, and then automated EOL testing begins. Second, using testing software on the cockpit system. The configuration table only records the configuration names for different vehicle models to distinguish test items. This configuration table needs to be pre-installed in the vehicle's infotainment system's storage location. The vehicle's intermediate control layer reads the configuration table and passes it to the interaction layer for display. The interaction layer then initiates the test.

[0024] However, the first approach has drawbacks: it requires specialized testers to be familiar with the scripts and configuration table paths, resulting in high labor costs during actual production line EOL testing. Furthermore, each computer can only run one diagnostic software program, and one computer corresponds to one vehicle under test. If multiple vehicles need to run the test simultaneously, multiple computers are required, leading to higher equipment costs. The second approach suffers from the disadvantage that the testing methods for each function are already fixed in the test software's logic code. Quality control personnel cannot flexibly adjust the testing methods for each item. Modifying the testing methods requires modifying the code and recompiling, releasing, and integrating the software—a series of processes. The configuration tables need to be pre-loaded into the vehicle's system storage location, requiring manual differentiation and loading for different vehicle models.

[0025] To address the aforementioned issues, this application provides a vehicle testing system, method, vehicle, and storage medium, offering a vehicle testing method with low labor costs, low equipment costs, flexibility, dynamic configuration, and one-click, user-friendly installation to save costs and improve the efficiency of vehicle off-line testing, thereby reducing costs and increasing efficiency.

[0026] The vehicle testing system will be described below with reference to some specific embodiments.

[0027] Figure 1 A schematic diagram of a vehicle testing system 100 according to an embodiment of this application is shown. Exemplarily, the vehicle testing system 100 includes: a test terminal 110, a plurality of vehicles under test 120, and a cloud server 130, wherein each vehicle under test 120 is communicatively connected to the test terminal 110 and the cloud server 130 respectively.

[0028] In this embodiment, the cloud server 130 stores multiple test requirements, each corresponding to a different model of the vehicle under test 120. Exemplarily, a test requirement refers to a series of test items set during the final factory inspection stage after vehicle assembly to verify whether the vehicle's various functions are normal, the configuration is correct, and the hardware and software are compatible. All test requirements are centrally hosted on the cloud server 130, supporting remote updates and releases, thus achieving dynamic configurability of the test requirements. Test requirements include, but are not limited to, Electronic Control Unit (ECU) communication testing, vehicle network communication testing, and lighting system function testing. Each test requirement includes multiple test strategy parameters, including, but not limited to, the number of tests, test frequency, verification value comparison method, and pass rate threshold setting.

[0029] Test terminal 110 is used to determine the target test software compatible with the vehicle models of each vehicle under test 120 based on the test installation package, and to install the target test software onto the corresponding vehicle under test 120. The test installation package includes test software for different vehicle models, and the target test software is configured with the first test requirements. When one or more vehicles under test 120 enter the test station, test terminal 110 can call the test installation package to filter out the target test software compatible with the current vehicle model, and automatically download and install it into the vehicle under test 120. This eliminates the need for manual configuration of the corresponding test program, reduces errors, and improves testing efficiency. Test terminals include, but are not limited to, laptops, tablets, and host computers.

[0030] Exemplary, the test software utilizes a vehicle-specific test requirement configuration table, system security signature, and authentication password, which are statically embedded into the source code during the software build phase. Through a single compilation process, multiple customized EOL test applications suitable for different vehicle models, possessing authentication and tamper-proof capabilities, are output. The test requirement configuration table includes all test requirements corresponding to the vehicle model; the system security signature is a vehicle-specific identity identifier or integrity verification credential, ensuring that the generated test software can be trusted by the vehicle; and the authentication password is the key or password for accessing the vehicle model's system, allowing the test software to enter the vehicle's EOL test mode. The vehicle-specific test requirement configuration table, system security signature, and authentication password are hard-coded into the program segment, generating dedicated test software for different brands and models of vehicles.

[0031] Each vehicle under test 120 is used to obtain a second test requirement adapted to the current vehicle model from multiple test requirements of the cloud server 130 through the target test software. Each vehicle under test 120 is also used to compare the first test requirement with the second test requirement through the target test software, determine the target test requirement based on the comparison result, and perform testing based on the target test requirement. The vehicle testing system 100 constructs a collaborative testing architecture of cloud server 130, test terminal 110, and vehicle under test 120. After installing the target test software, the vehicle under test 120 can autonomously select the latest configured target test requirement to execute the test without modifying the code when the test requirement is updated, realizing fully automated operation of the vehicle off-line testing.

[0032] In one embodiment, such as Figure 2 As shown, each vehicle under test 120 includes an on-board host 121, and the test installation package also includes an automatic identification installation script; the test terminal 110 is used to read the vehicle model information of the vehicle under test 120 based on the automatic identification installation script, so as to select from various vehicle model test software (such as...) according to the vehicle model information. Figure 2 Select the target test software that is compatible with the vehicle model 120 (APP1, APP2 and APP3 shown) and install the target test software into the vehicle host 121.

[0033] In this embodiment, the automatic identification installation script is a program written in a scripting language to automate the software deployment process. Developers can write the automatic identification installation script based on the pre-acquired vehicle information, including vehicle brand, model, etc. When the test vehicle 120 of different models goes online, the automatic identification installation script can intelligently identify the current vehicle model and select the matching target test software for installation without manual installation, saving labor costs.

[0034] In one embodiment, the test terminal 110 and each vehicle under test 120 are connected via a communication interface. The test terminal 110 can use the automatic identification and installation script of the test installation package to obtain the vehicle model information through the communication interface, select the target test software matching the current test model, and install the target test software into the on-board host 121 of each vehicle under test 120 through the communication interface. The on-board host 121 can be the cockpit domain controller of the vehicle under test 120, and the target test software can run on the SOC (System on Chip) of the cockpit domain controller. The communication interface includes, but is not limited to, a Universal Serial Bus (USB) interface, an Ethernet interface, a controller area network, Bluetooth, etc.

[0035] In this embodiment, testers do not need to concern themselves with the specific supplier or model of the vehicle under test 120. They can simply use the test installation package on the test terminal 110 to perform a one-click installation and run of the target test software, saving manpower costs. After installing and running the target test software using the test installation package, testers can proceed with the installation and run of the target test software for the next vehicle under test 120. The testing process requires no monitoring, allowing multiple vehicles under test 120 to be tested simultaneously, saving time costs.

[0036] In one embodiment, the target testing software in the vehicle host 121 is used to obtain the vehicle identification number (VIN) of the vehicle under test 120 when receiving the first test instruction, and send the vehicle identification number as a request parameter to the cloud server 130 to receive the second test requirement returned by the cloud server 130 based on the vehicle identification number.

[0037] In this embodiment, the first test command is the start test command entered by the tester when the target test software is installed on the vehicle under test 120. For example, the tester only needs to click the start test button to start the target test software for testing. The cloud server 130 is used to send the latest test requirements for the current vehicle model to the vehicle under test 120 when it receives a request carrying a vehicle identification code.

[0038] In one embodiment, the cloud server 130 is further configured to update the corresponding stored test requirements to the latest configured test requirements in real time when the latest configured test requirements are obtained; wherein the test requirements in the cloud server 130 are stored in the cloud server 130 in the form of a configuration table.

[0039] In this embodiment, the testing requirements for different vehicle models are configured in a table (such as...). Figure 2The vehicle models (A, B, configuration tables A, B, etc.) shown are stored on cloud server 130 and updated in real time upon receiving the latest configuration, enabling centralized management of test requirements. In fact, the configuration tables can be editable Excel files on a computer, and can be replaced with any file that can be recognized and read by the target test software executable. For example, the configuration tables can be replaced with XML (eXtensible Markup Language) or JSON (JavaScript Object Notation) format files.

[0040] Optionally, the configuration table contains detailed data that allows for dynamic adjustment of the testing methods. This detailed data includes, but is not limited to, the number of test executions, test intervals, test command sending frequency, expected response values, verification rules, timeout thresholds, and retry strategies. By modifying this detailed data, the testing methods can be dynamically adjusted without updating the target test software version, significantly improving the flexibility and maintainability of the testing system.

[0041] It is understandable that when testers want to temporarily adjust the test requirements for a certain vehicle model, they can update the configuration table and upload it to the cloud server 130. The target test software only needs to retrieve the latest configuration of the test requirements from the cloud server 130. There is no need to recompile the target test software to obtain and execute the latest configuration of the test requirements, which reflects the flexibility and variability of the test requirements.

[0042] In one embodiment, the target testing software in the vehicle-mounted host 121 is used to use the first test requirement as the target test requirement when the first test requirement and the second test requirement are the same. When the first test requirement and the second test requirement are different, the second test requirement is used as the target test requirement. If it fails to obtain the test requirement adapted to the current vehicle model, the test requirement configured by the target testing software is used as the target test requirement.

[0043] In this embodiment, the second test requirement obtained from the cloud server 130 is the latest configured test requirement. By comparing the first and second test requirements, the latest target test requirement is dynamically selected. When the two are the same, the first test requirement is used to ensure execution efficiency. When the two are different, the latest configured second test requirement is adopted first to ensure that the test content is the latest configured test requirement, thereby achieving adaptive adjustment of test requirements. When test requirements are updated, there is no need to go through the test software compilation, test, and release process again; the configuration table of test requirements on the cloud server 130 can be updated directly to achieve flexibility and adaptability.

[0044] In one embodiment, each vehicle under test 120 further includes multiple electronic control units (ECUs), such as a Body Control Module (BCM), a Battery Management System (BMS), an In-Vehicle Infotainment System (IVI), and an Advanced Driver Assistance System (ADAS). Exemplarily, the target test software in the onboard host 121 generates corresponding second test instructions based on target test requirements and sends these instructions to each ECU to enable each ECU to perform test actions. The second test instructions are a sequence of executable commands dynamically generated and distributed to each ECU by the target test software on the onboard host 121 based on the target test requirements adapted to the current vehicle model, for the actual execution of test actions.

[0045] In one implementation, such as Figure 3 As shown, the second test command can be sent to the vehicle signal service (Car Service) at the lower level of the vehicle system. The Car Service sends the second test command to the MCU (Microcontroller Unit) via a serial communication interface, and then to the CAN (Controller Area Network) bus. Various ECUs on the vehicle (such as...) Figure 3 After receiving the second test command, ECU1, ECU2, ECU3, etc., as shown, execute the test action.

[0046] In one embodiment, the target testing software in the vehicle-mounted host 121 is used to generate a test report based on the test results (e.g., Figure 3 Test reports A, B, etc. (as shown) are uploaded to cloud server 130 along with the vehicle identification number of the tested vehicle 120 for storage. The target testing software can upload test reports to cloud server 130 via a request carrying the vehicle identification number, enabling cloud server 130 to store test reports for the current vehicle model.

[0047] In this embodiment, the test report is a digital certificate of the vehicle's quality status before it leaves the factory. It is used to record data throughout the testing process and provide test results. The test results include whether the vehicle is qualified or unqualified. The test report includes, but is not limited to, the vehicle identification number, vehicle model, test results, test start time, and test result time.

[0048] Figure 4 A schematic flowchart of a vehicle testing method according to an embodiment of this application is shown. Exemplarily, the vehicle testing method includes: S210, when the test terminal 110 determines the target test software that is compatible with the model of each vehicle under test 120 based on the test installation package, and installs the target test software to the corresponding vehicle under test 120, the second test requirement that is compatible with the current model is obtained from multiple test requirements of the cloud server 130 through the target test software.

[0049] The test installation package includes test software for different vehicle models, and the target test software is configured with the primary test requirements.

[0050] S220 compares the first test requirement with the second test requirement using the target test software.

[0051] S230: Determine the target test requirements based on the comparison results, and conduct tests based on the target test requirements.

[0052] It is understood that the method in this embodiment corresponds to the vehicle testing system 100 in the above embodiment, and the options in the above embodiment are also applicable to this embodiment, so they will not be described again here.

[0053] This application also provides a vehicle, exemplary of which includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program to enable the vehicle to perform the vehicle testing method described above.

[0054] The processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including at least one of a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Network Processor (NP), Digital Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application.

[0055] The memory can be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory is used to store computer programs, and the processor can execute the computer programs accordingly after receiving execution instructions.

[0056] This application also provides a computer-readable storage medium for storing the computer program used in the aforementioned vehicle. For example, the computer-readable storage medium may include, but is not limited to, various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0057] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, in alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0058] In addition, the functional modules or units in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0059] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0060] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A vehicle testing system, characterized in that, include: Test terminal, multiple vehicles under test, and cloud server; Each of the vehicles under test is communicatively connected to the test terminal and the cloud server, respectively. The cloud server is used to store multiple test requirements, each of which corresponds to a different model of the vehicle under test. The test terminal is used to determine the target test software that is compatible with the model of each of the vehicles under test based on the test installation package, and to install the target test software into the corresponding vehicle under test. The test installation package includes test software for different vehicle models, and the target test software is configured with a first test requirement. Each of the vehicles under test is used to obtain a second test requirement that is compatible with the current vehicle model from multiple test requirements on the cloud server through the target test software; Each of the vehicles under test is also used to compare the first test requirement with the second test requirement using the target test software, determine the target test requirement based on the comparison result, and perform testing based on the target test requirement.

2. The vehicle testing system according to claim 1, characterized in that, Each of the vehicles under test includes an on-board host, and the test installation package also includes an automatic identification installation script; The test terminal is used to read the vehicle model information of the vehicle under test based on the automatic identification and installation script, select the target test software that is compatible with the vehicle model under test according to the vehicle model information, and install the target test software into the vehicle host.

3. The vehicle testing system according to claim 2, characterized in that, The target testing software in the vehicle host is used to obtain the vehicle identification code of the vehicle under test when it receives the first test instruction, and send the vehicle identification code as a request parameter to the cloud server so as to receive the second test requirement returned by the cloud server based on the vehicle identification code.

4. The vehicle testing system according to claim 2, characterized in that, The target testing software in the vehicle host is used to take the first testing requirement as the target testing requirement when the first testing requirement and the second testing requirement are the same. When the first test requirement differs from the second test requirement, the second test requirement shall be taken as the target test requirement.

5. The vehicle testing system according to claim 2, characterized in that, Each of the vehicles under test also includes multiple electronic control units; The target test software in the vehicle host is used to generate a corresponding second test instruction based on the target test requirements, and send the second test instruction to each of the electronic control units so that each electronic control unit performs a test action.

6. The vehicle testing system according to claim 1, characterized in that, The cloud server is also used to update the stored test requirements in real time with the latest configured test requirements upon receiving the latest configuration test requirements. The test requirements in the cloud server are stored in the form of a configuration table on the cloud server.

7. The vehicle testing system according to claim 2, characterized in that, The target testing software in the vehicle-mounted host is used to generate a test report based on the test results, and upload the test report and the vehicle identification number of the vehicle under test to the cloud server for storage.

8. A vehicle testing method, characterized in that, include: When the test terminal determines the target test software that is compatible with the model of each of the vehicles under test based on the test installation package, and installs the target test software on the corresponding vehicle under test, the second test requirement that is compatible with the current model is obtained from multiple test requirements on the cloud server through the target test software. The test installation package includes test software for different vehicle models, and the target test software is configured with a first test requirement; the cloud server is used to store multiple test requirements, each of which corresponds to a different model of the vehicle under test. The first test requirement is compared with the second test requirement using the target test software; The target test requirements are determined based on the comparison results, and tests are conducted based on the target test requirements.

9. A vehicle, characterized in that, It includes a memory and a processor, the memory storing a computer program that, when run on the processor, executes the vehicle testing method of claim 8.

10. A readable storage medium, characterized in that, It stores a computer program that, when run on a processor, executes the vehicle testing method of claim 8.

Images