Vehicle network test method, device and system, electronic equipment and storage medium
By receiving test configuration information and automatically calling unit and network segment test cases, the separation of component-level and system-level tests in vehicle network testing is solved, efficient automated testing is achieved, and labor costs and time consumption are reduced.
Patent Information
- Application Number
- CN202510834927.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-20
- Publication Date
- 2025-08-08
AI Technical Summary
There is a significant separation between component-level and system-level testing in existing vehicle network tests, resulting in low testing efficiency and high labor costs, and traditional testing modes require a lot of manual operation and repetitive work.
By receiving test configuration information related to the vehicle to be tested, automatically calling the unit and network segment test cases, the automatic collection and report generation of test data is realized, and manual intervention is reduced.
It improves the degree of test automation, reduces manual operations, saves time and labor costs, and improves test efficiency and accuracy.
Smart Images
Figure CN120455345A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle network testing technology, and in particular to a vehicle network testing method, device, system, electronic device, and storage medium. Background Art
[0002] In the field of vehicle network testing, there is a significant separation between the execution processes of component-level testing and system-level testing. The current industry generally adopts a phased testing strategy, which first conducts component-level functional verification on prototypes, and then integrates them for system-level integration testing. Taking vehicle model A as an example, during its R&D phase, the vehicle's electronic and electrical architecture includes 20 control units (ECUs). The component-level testing phase requires functional verification of these 20 ECUs one by one. After all units pass the test, physical connections and protocol configuration are performed based on the network topology of vehicle model A, and then system-level joint debugging testing is carried out.
[0003] The traditional testing model involves a large amount of manual operations throughout the entire process, such as replacing the unit under test, organizing and archiving test data, and switching the test environment, resulting in low testing efficiency and high labor costs. Summary of the Invention
[0004] The present application provides a vehicle network testing method, device, system, electronic device and storage medium, which can improve the existing vehicle network testing scheme.
[0005] In a first aspect, the present application provides a vehicle network testing method, comprising:
[0006] Receive test configuration information related to the vehicle to be tested, the test configuration information including unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested, each of the network segments to be tested including multiple units to be tested;
[0007] Calling corresponding unit test cases according to the unit configuration information of each unit to be tested, and running the unit test cases in sequence to obtain unit test data corresponding to each unit to be tested;
[0008] After detecting that each of the units to be tested has been tested in sequence, calling a corresponding network segment test case according to the network segment configuration information of each network segment to be tested, and sequentially running the network segment test case to obtain network segment test data corresponding to each network segment to be tested;
[0009] A test report for the vehicle to be tested is generated according to the unit test data and the network segment test data.
[0010] In a second aspect, the present application provides a vehicle network testing device, the device comprising:
[0011] A configuration information receiving module is used to receive test configuration information related to the vehicle to be tested, wherein the test configuration information includes unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested, each of the network segments to be tested includes multiple units to be tested;
[0012] A test case calling module is used to call the corresponding unit test case according to the unit configuration information of each unit to be tested, and run the unit test case in sequence to obtain the unit test data corresponding to each unit to be tested;
[0013] The test case calling module is further configured to, after detecting that each unit under test has been tested in sequence, call the corresponding network segment test case according to the network segment configuration information of each network segment under test, and sequentially run the network segment test case to obtain the network segment test data corresponding to each network segment under test;
[0014] A test report generating module is used to generate a test report of the vehicle to be tested based on the unit test data and the network segment test data.
[0015] In the third aspect, the present application provides a vehicle network testing system, which includes at least an industrial computer, a test device and an intelligent control board, and the intelligent control board is connected to the test device and the industrial computer respectively; the intelligent control board includes multiple network segments to be tested, and each network segment to be tested includes multiple units to be tested; the industrial computer is used to execute the vehicle network testing method as described in any one of claims 1-6.
[0016] In a fourth aspect, the present application further provides an electronic device, comprising:
[0017] at least one processor; and
[0018] a memory communicatively connected to the at least one processor; wherein,
[0019] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the vehicle network testing method described in any embodiment of the present application.
[0020] In a fifth aspect, the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the vehicle network testing method described in any embodiment of the present application when executed.
[0021] The vehicle network testing solution provided by the embodiment of the present application first receives test configuration information related to the vehicle to be tested, and the test configuration information includes unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested; then, the corresponding unit test case is called according to the unit configuration information of each unit to be tested, and the unit test case is run in sequence to obtain the unit test data corresponding to each unit to be tested; and after detecting that each unit to be tested has been tested in sequence, the corresponding network segment test case is called according to the network segment configuration information of each network segment to be tested, and the network segment test case is run in sequence to obtain the network segment test data corresponding to each network segment to be tested, thereby realizing automatic collection of test data. Compared with the step-by-step execution method of component-level and system-level testing in the traditional mode, the solution provided by this embodiment does not require manual replacement of the unit to be tested, and does not require repeated construction of the test environment for the network segment to be tested, thereby improving test automation; finally, by automatically integrating the unit test data and the network segment test data to generate a test report, the problem of data omission or format confusion that may be caused by manual archiving is avoided. The solution provided by this embodiment has the beneficial effect of improving test efficiency and saving labor costs.
[0022] It should be noted that the above-mentioned computer instructions may be stored in whole or in part on a computer-readable storage medium. The computer-readable storage medium may be packaged together with the processor of the vehicle network test device or separately from the processor of the vehicle network test device, and this application does not limit this.
[0023] The descriptions of the second, third, fourth and fifth aspects of this application can refer to the detailed description of the first aspect; and the beneficial effects of the descriptions of the second, fourth and fifth aspects can refer to the analysis of the beneficial effects of the first aspect, which will not be repeated here.
[0024] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description.
[0025] It is understandable that before using the technical solutions disclosed in the embodiments of this application, the type, scope of use, and usage scenarios of the personal information involved in this application should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.
[0027] Figure 1 This is a flow chart of a vehicle network testing method provided by an embodiment of the present application;
[0028] Figure 2 This is a structural diagram of a vehicle network testing system provided by an embodiment of the present application;
[0029] Figure 3 This is a structural diagram of a vehicle network testing device provided in an embodiment of the present application;
[0030] Figure 4 It is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0031] In order to enable those skilled in the art to better understand the present invention, the technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this embodiment. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.
[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0033] The present application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are intended only to illustrate the present application and are not intended to limit the present application. It should also be noted that, for ease of description, the accompanying drawings only illustrate portions of the present application, not all of the structures.
[0034] Figure 1 This is a flow chart of a vehicle network testing method provided in an embodiment of the present application. This embodiment is applicable to vehicle network testing. The method can be performed by a vehicle network testing device, which can be implemented in hardware and / or software and integrated into the electronic device that performs the method. Preferably, the electronic device in the embodiment of the present application can be a server, a computer, or the like.
[0035] refer to Figure 1 The vehicle network testing method of this embodiment includes but is not limited to the following steps:
[0036] S110: Receive test configuration information related to the vehicle to be tested.
[0037] Test configuration information is a set of parameters that guide the testing of the vehicle's electronic systems. This information clarifies the test object, communication protocol, and data collection rules, ensuring a standardized test process. In this embodiment, the test configuration information includes the configuration rules for the units under test and network segments, and is the fundamental data for test execution.
[0038] Specifically, the test configuration information of this example includes unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested, and each network segment to be tested includes multiple units to be tested.
[0039] The UUT is a functional module within a vehicle's electronic system that can be independently tested, such as an engine control unit (ECU), onboard sensors, and onboard communication modules. Unit configuration information is the parameter settings for a single UUT. These parameters may include functional parameters (such as control logic thresholds) and communication parameters (such as baud rate and data frame format). For example, testing the ECU's wake-up voltage threshold and sensor sampling frequency might be necessary.
[0040] The network segment to be tested is a communication network in the vehicle that connects multiple units to be tested, such as the Controller Area Network (CAN) bus, on-board Ethernet (Ethernet), and Local Interconnect Network (LIN) bus. Each network segment has independent physical layer and data link layer protocols to support concurrent communication among multiple control units.
[0041] Before receiving the test configuration information related to the vehicle to be tested, the test environment must be set up in advance. The tester must first connect the control units of the vehicle to be tested that require component-level and system-level network testing to the vehicle network test system according to the network topology. Figure 2 , Figure 2 It is a structural diagram of the vehicle network testing system provided in an embodiment of the present application.
[0042] Specifically, the vehicle network testing system provided in this embodiment includes at least an industrial computer, a test device and an intelligent control board, and the intelligent control board is connected to the test device and the industrial computer respectively; the intelligent control board includes multiple network segments to be tested, and each network segment to be tested includes multiple units to be tested; the industrial computer is used to execute the vehicle network testing method provided in this embodiment.
[0043] exist Figure 2 In this system, the industrial computer is used to store information such as test tool software, automated test programs, test cases, test host computers, and test data, and is used to control the relay resources of the intelligent control board of the automation controller. The intelligent controller board has a large number of hard-wired resources such as input / output interfaces and relays, and is controlled by the industrial computer to access different control units under test and test equipment. Test equipment is a hardware instrument or device that accesses the control unit under test, executes test instructions, and collects and analyzes data. Its function is to work in conjunction with the intelligent controller board (including hard-wired resources such as input / output interfaces and relays) and the industrial computer to perform functional verification, performance testing, or fault diagnosis of the test object (such as an in-vehicle ECU or industrial controller).
[0044] Specifically, the test equipment may include at least a data acquisition tool, a data interference tool, a programmable power supply, a signal generator, an oscilloscope, and a network analyzer. The data acquisition tool is used to collect vehicle network signals; the data interference tool is used to interfere with the network bus signal value for fault injection testing; the programmable power supply is used to connect to the intelligent control board and mainly provides voltage to the control unit under test; the signal generator is used to emit different waveforms or interference signals; the oscilloscope is used to collect and capture analog signals from the controller local area network; and the network analyzer measures network parameters and is used for Ethernet physical layer testing and wiring harness testing.
[0045] Then, the method for receiving test configuration information related to the vehicle under test in this embodiment can be: configuring the units under test and the network segments under test involved in a test in the visual interface of the industrial computer. For example, the configured unit configuration information may include the unit identifier (such as the controller name), part number, software version number, hardware version number, network segment, test database, parameters to be tested, and test sequence, etc.; the network segment configuration information may include the network segment identifier (network segment name), parameters to be tested, and test sequence, etc. After the test configuration information is completed, the "Done" control button in the visual interface can be clicked, so that the host computer receives the test configuration information related to the vehicle under test.
[0046] It should be noted that, in this embodiment, component-level testing can be understood as testing of each unit to be tested, and system-level testing can be understood as testing of each network segment to be tested.
[0047] S120 , calling corresponding unit test cases according to the unit configuration information of each unit to be tested, and running the unit test cases in sequence to obtain unit test data corresponding to each unit to be tested.
[0048] A unit test case is a set of test steps designed for a unit under test and stored in advance on an industrial computer. These test steps include input stimulus, execution conditions, expected results, and the software code used to execute the test. The corresponding unit test case can be called based on the unit configuration information for each unit under test. The unit configuration information can include at least a unit identifier corresponding to the unit under test. The industrial computer can then determine the unit test case to call based on the unit identifier and further execute the unit test case based on the test parameters contained in the configuration information.
[0049] In this embodiment, after completing the filling of the unit configuration information of each unit to be tested, you can further select the component-level test case sequence in the visual interface, such as testing controller A first, and then testing controllers B, C, and D in turn, and then select the component-level test cases of controllers A, B, C, and D respectively. The component-level test settings can be completed to achieve automated testing of each test unit at the component level.
[0050] In a preferred implementation, in this embodiment, the unit configuration information includes at least a unit identifier corresponding to each unit under test, a test parameter corresponding to each unit under test, and a test sequence corresponding to each unit under test.
[0051] The above-mentioned step S120 can be specifically implemented as follows: for the current unit under test, the corresponding unit test case is retrieved based on the unit identifier corresponding to the current unit under test, and the control unit test case is run to generate test data for the parameters to be tested corresponding to the current unit under test; after completing the test of the corresponding unit under test in sequence according to the test sequence corresponding to each unit under test, the unit test data corresponding to each unit under test is obtained. The method provided by this embodiment does not require manual configuration of the test sequence and parameters. The configuration file drives the execution of the entire process, thereby improving test efficiency. When adding a new unit under test, only the configuration information needs to be modified, without modifying the code. The same test case can be adapted to multiple units through different parameter configurations. For example, the "voltage test case" can be used to test the power modules of different ECUs, reducing development pressure.
[0052] Specifically, the current unit under test is a control unit that needs to be tested. The industrial computer reads the unit configuration information, extracts the unit identifier (such as "ECU-001"), the parameters to be tested (such as "voltage threshold"), and the test sequence (such as "[UC-01]", indicating the first one to be tested). Then, a task queue is generated according to the test sequence in the configuration. For example, the unit under test with the sequence identifier "[UC-01]" is executed first, followed by the unit under test with the sequence identifier "[UC-02]". After each unit test case is executed, the callback function notifies the scheduler to load the next unit test case.
[0053] The intelligent controller board's relay switches the connection between the unit under test (UUT). For example, when performing a voltage test on "ECU-001," the board's relay connects the DC power supply to the ECU's power interface. A control signal is output via the GPIO interface, triggering the UUT to enter test mode. To obtain test data for the UUT's corresponding parameters, for example, the ECU's supply voltage is read via the board's ADC channel at a sampling rate of 1kHz. For example, to obtain CAN communication parameters, the CAN card is used to capture messages in real time, parsing the speed values within the data frames to generate the corresponding unit test data.
[0054] Optionally, the unit configuration information of each unit under test may be configured based on Table 1:
[0055] Table 1
[0056]
[0057]
[0058] Among the parameters to be measured, a can represent the current ECU's communication voltage range; b can represent the current ECU's message transmission and reception status; c can represent the current ECU's physical waveform; d can represent the current ECU's initialization time; e can represent the current ECU's sampling point; and f can represent the current ECU's communication short circuit status. The specific meaning of each letter is not limited here.
[0059] In another preferred implementation, the unit configuration information further includes an association identifier corresponding to at least one associated unit associated with the unit under test. The solution provided in this embodiment further includes: performing a communication test based on the communication relationship between the unit under test and the associated unit to obtain communication data; and generating a test report based on the fault type of the fault data when the communication data is detected as fault data.
[0060] Specifically, the communication protocol rules between the unit under test and the associated units can be established in the system in advance (to define the format, frequency, verification method, etc. of data interaction). Therefore, after completing the basic functional test of the unit under test, the corresponding associated units are automatically located and activated according to the association identifier in the configuration information to establish a communication link. If the associated units of the unit under test ECU-001 include ECU-005, the system sends a communication request through the address of ECU-005 to establish a data interaction channel; and captures the communication data between the unit under test and the associated units in real time (such as the data packets sent / received, signal level and response time, etc.), so that the preset communication protocol standards can be compared to determine whether the communication data meets the specifications (such as data frame format, check code correctness, response delay threshold, etc.); if the communication If data anomalies occur, they are classified according to preset fault type rules, and the time, location (identification of the unit under test and associated units), fault type, and specific error data (such as error frame content and response delay value) of the fault are recorded in real time, thereby outputting a test report containing the fault type. For example, the test report may at least include: test object information: identification and configuration parameters of the unit under test and associated units; communication test results: normal / faulty status, detailed description of the fault data; fault analysis: automatic generation of possible causes based on the fault type (such as "CAN bus short circuit, possibly caused by poor cable contact"); recommended measures: such as "check the physical connection of associated unit ECU-005" and "reconfigure communication protocol parameters." The specific content included in the test report is not limited here.
[0061] The solution provided in this embodiment is that traditional testing only focuses on the function of the unit itself. This solution verifies the stability of data interaction when multiple devices work together through communication testing of associated units, thereby avoiding system-level problems caused by communication failures. In addition, in the process of traditional component-level testing, virtual units are often simulated to interact with real test samples, which has a certain interference with the reliability of the test results. However, this embodiment uses real communication units for test verification, which greatly improves the authenticity and reliability of the test and effectively guarantees product quality.
[0062] In another preferred implementation, in this embodiment, the unit configuration information also includes fault interference information.
[0063] Specifically, the solution provided in this embodiment includes running a test case of the control unit according to the test parameters corresponding to the current unit under test and the fault interference information, and generating test data of the test parameters corresponding to the current unit under test.
[0064] This fault interference information can be injected as voltage or current interference, using a signal generator to inject abnormal voltage or current signals to simulate power failures (such as voltage sags and surges), ground faults, and line shorts or opens. Alternatively, it can be waveform interference, using an oscilloscope and a signal conditioner to superimpose noise or distorted waveforms on network signals to simulate signal distortion caused by cable aging or poor contact. By using this fault interference information, test data corresponding to the parameters to be measured can be obtained to test the response logic of the ECU, network protocol, and entire vehicle system under abnormal operating conditions, ensuring that the system can perform error reporting, degradation, or safety redundancy operations as designed when a fault occurs.
[0065] S130 , after detecting that each unit to be tested has been tested in sequence, calling a corresponding network segment test case according to the network segment configuration information of each network segment to be tested, and running the network segment test case in sequence to obtain network segment test data corresponding to each network segment to be tested.
[0066] A network segment identifier can be the identifier corresponding to a test system. A network segment under test can contain multiple units under test. Currently, test systems can be divided into systems based on the vehicle's function under test, such as the powertrain, chassis, comfort, and intelligent driving systems. The units under test contained in each network segment under test may overlap, depending on the actual circuit topology.
[0067] The method for calling the corresponding network segment test case based on the network segment configuration information of each network segment to be tested can be that the network segment configuration information at least includes the network segment identifier corresponding to the network segment to be tested, so that the industrial computer can determine the network segment test case to be called based on the network segment identifier and further run the network segment test case based on the test parameters included in the network segment configuration information. The test parameters of each network segment to be tested can be set based on actual test requirements, such as testing transmission rate, response rate, voltage threshold, etc.
[0068] The network segment test cases corresponding to each network segment to be tested can be run in sequence in a serial manner, thereby recording the corresponding test results after each network segment test case is completed, so that after all the network segment test cases corresponding to each network segment to be tested are executed, the network segment test data corresponding to each network segment to be tested can be obtained.
[0069] In another preferred implementation, in this embodiment, the network segment configuration information includes at least the network segment identifiers corresponding to each network segment to be tested, the parameters to be tested corresponding to each network segment to be tested, and the test sequence corresponding to each network segment to be tested.
[0070] Specifically, the above step S130 can be implemented as follows:
[0071] For the current network segment to be tested, the corresponding network segment test case is called based on the network segment identifier corresponding to the current network segment to be tested, and the network segment test case is controlled to run to generate test data corresponding to the current network segment to be tested; after completing the test of each network segment to be tested according to the test sequence corresponding to each network segment to be tested, the network segment test data corresponding to each network segment to be tested is obtained.
[0072] A network segment ID-test case mapping table is pre-stored in the system's database or configuration file. The network segment ID (such as the network segment name) is used as the primary key to associate the corresponding test case set (such as test scripts, test commands, and network test tool instructions). By obtaining the network segment ID of the current network segment to be tested, the mapping table is searched based on the network segment ID to obtain the corresponding test case list and execution parameters, and finally the network segment test case is loaded into the execution engine.
[0073] In order to achieve test automation of the test system and reduce human participation in the testing process, the network segment test priority is specified through the test sequence (such as testing network segment A first and then testing network segment B), or sorted by network topology dependencies (such as testing the upper network segment first and then testing the lower network segment), etc. The specific method of defining the test sequence is not restricted here.
[0074] The solution provided in this embodiment can perform system-level testing on each network segment to be tested according to the network segment configuration information after completing the test of each unit to be tested in sequence. Specifically, the network segment configuration information of each network segment to be tested can be configured based on Table 2:
[0075] Table 2
[0076] Test sequence Network segment identifier System-level parameters to be tested 1 Power network segment a / b 2 Chassis network segment a / b / c / d / e 3 Comfortable network segment a / b / c 4 Information network segment a …… …… ……
[0077] The system-level test parameters in Table 1 and the component-level test parameters in Table 2 may contain the same content. When the test systems or test topologies are different, the test results obtained may be different even if the test parameters are the same.
[0078] In another preferred implementation, the solution provided in this embodiment further comprises a target storage path for the test configuration information. The target storage path is used to store test data generated during the test process in a fixed location. Specifically, the solution provided in this embodiment further comprises controlling the storage of unit test data corresponding to each unit under test and network segment test data corresponding to each network segment under test in the target storage path.
[0079] After selecting component-level and system-level test cases, click Run Device. The test system will automatically perform component-level tests on controllers A, B, C, and D in sequence. After completing a component test, the test results are automatically stored in the specified path (e.g., network test results for vehicle D / model A). After all component-level tests are complete, system-level testing will automatically begin, requiring no operator intervention. Similarly, the powertrain, chassis, comfort, and information network segments will be tested in sequence. Upon completion, the test results are stored in the specified path.
[0080] A specific application scenario description, specifically, in this embodiment, combined with Figure 2 The following test descriptions are given using the component-level test "communication end low voltage test" and the system-level test "power CAN physical waveform test case" as examples:
[0081] 1.1 Select the component-level test "Communication End Low Voltage Test" on the host computer, and then select the system-level test as "Power CAN Physical Waveform Test Case";
[0082] 1.2 The industrial computer calls the intelligent control board;
[0083] 1.3 The intelligent control board connects the data acquisition tools, programmable power supply, and relays required for the test case. The intelligent control board connects the relays of ECU_A and other interacting ECUs.
[0084] 1.4 The industrial computer sends a control command to power on the programmable power supply; the industrial computer controls the intelligent control board to supply power to each ECU, the relay closes, and the ECU starts working;
[0085] 1.5 The industrial computer controls the data acquisition tool to detect whether ECU_A interacts correctly with other ECUs.
[0086] 1.6 The industrial computer controls the programmable power supply to gradually reduce the ECU supply voltage. During this process, the system checks whether ECU_A interacts correctly with other ECUs until the interaction becomes abnormal. The programmable power supply value of ECU_A when the interaction becomes abnormal is recorded to obtain the test data for the "communication end low voltage test."
[0087] 1.7 The industrial computer controls the intelligent control board to turn off the relays of each test equipment and ECU;
[0088] 1.8 After completing the component-level "communication end low voltage test", store the test results in the specified path;
[0089] 2.0 The industrial computer calls the intelligent control board;
[0090] 2.1 The intelligent control board connects the data acquisition tools, programmable power supply, and relays required for the test case; the intelligent control board connects the relay of the power CAN ECU;
[0091] 2.2 The industrial computer sends a control command to power on the programmable power supply; the industrial computer controls the intelligent control board to supply power to each ECU, the relay closes, and the ECU starts working;
[0092] 2.3 The industrial computer controls the data acquisition tool to monitor whether the power CAN is sending and receiving messages to each ECU normally;
[0093] 2.4 The industrial computer controls the oscilloscope to collect and analyze the messages sent by each ECU on the power CAN to obtain the test data of the "power CAN physical waveform test case"
[0094] 2.5 The industrial computer controls the intelligent control board to turn off the relays of each test equipment and ECU;
[0095] 2.6 After completing the system-level power CAN physical waveform test case, store the test results in the specified path.
[0096] Through the test solution provided in this embodiment, the test system simulates real nodes and real loads in component-level testing, improves test credibility and reliability, and maximizes the restoration of the actual situation of the vehicle network; the test system component-level testing and system-level testing are automatically called, and the industrial computer controls the smart board to call different test tools, which greatly saves hardware resources and test system costs; in addition, the automatic calling of component-level and system-level test cases eliminates the need for testers to replace the control unit to be tested midway, improves test continuity, saves manual operations, multiple rounds of configuration and other operations, greatly improves the test pass capability, and saves time and costs.
[0097] S140: Generate a test report for the vehicle to be tested based on the unit test data and the network segment test data.
[0098] The method for generating a test report for a vehicle under test based on unit test data and network segment test data can be as follows: first, determine the core fields of the test field, such as the test object identifier (unit under test identifier / network segment under test identifier), test type (unit / network segment), test time, status (pass / fail / warning), indicator data (such as response time and error rate), test content, and fault type (if any). Furthermore, the functional test results from each unit under test (such as ECU power supply test and sensor sampling test) and the communication test results from each network under test segment (such as packet loss rate and protocol compatibility) are statistically analyzed to generate a test report.
[0099] Furthermore, when fault types are included, fault classification can be determined based on the fault type to clarify the severity of the current fault. For example, faults that affect driving safety (such as CAN bus communication interruption and brake ECU response timeout) are high risk; faults that affect functional performance (such as sensor data deviation and insufficient Ethernet throughput) are medium risk; and anomalies that do not affect core functions (such as log errors in non-critical units) are low risk.
[0100] The vehicle network testing method provided in the embodiment of the present application first receives test configuration information related to the vehicle to be tested, and the test configuration information includes unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested; then, the corresponding unit test case is called according to the unit configuration information of each unit to be tested, and the unit test case is run in sequence to obtain the unit test data corresponding to each unit to be tested; and after detecting that each unit to be tested has been tested in sequence, the corresponding network segment test case is called according to the network segment configuration information of each network segment to be tested, and the network segment test case is run in sequence to obtain the network segment test data corresponding to each network segment to be tested, thereby realizing automatic collection of test data. Compared with the step-by-step execution method of component-level and system-level testing in the traditional mode, the solution provided by this embodiment does not require manual replacement of the unit to be tested, and does not require repeated construction of the test environment for the network segment to be tested, thereby improving test automation; finally, by automatically integrating the unit test data and the network segment test data to generate a test report, the problem of data omission or format confusion that may be caused by manual archiving is avoided. The solution provided by this embodiment has the beneficial effect of improving test efficiency and saving labor costs.
[0101] Figure 3 This is a structural diagram of a vehicle network testing device provided in an embodiment of the present application, which is suitable for executing the vehicle network testing method provided in an embodiment of the present application. Figure 3 As shown, the device may specifically include: a configuration information receiving module 310, a test case calling module 320 and a test report generating module 330, wherein:
[0102] Configuration information receiving module 310, configured to receive test configuration information related to the vehicle to be tested, the test configuration information including unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested, each of the network segments to be tested including multiple units to be tested;
[0103] The test case calling module 320 is used to call the corresponding unit test case according to the unit configuration information of each unit under test, and sequentially run the unit test case to obtain the unit test data corresponding to each unit under test;
[0104] The test case calling module 320 is further configured to, after detecting that each unit under test has been tested in sequence, call a corresponding network segment test case according to the network segment configuration information of each network segment under test, and sequentially run the network segment test case to obtain network segment test data corresponding to each network segment under test;
[0105] The test report generating module 330 is configured to generate a test report for the vehicle to be tested based on the unit test data and the network segment test data.
[0106] The vehicle network testing device provided in the embodiment of the present application first receives test configuration information related to the vehicle to be tested, and the test configuration information includes unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested; then, the corresponding unit test case is called according to the unit configuration information of each unit to be tested, and the unit test case is run in sequence to obtain the unit test data corresponding to each unit to be tested; and after detecting that each unit to be tested has been tested in sequence, the corresponding network segment test case is called according to the network segment configuration information of each network segment to be tested, and the network segment test case is run in sequence to obtain the network segment test data corresponding to each network segment to be tested, thereby realizing automatic collection of test data. Compared with the step-by-step execution method of component-level and system-level testing in the traditional mode, the solution provided by this embodiment does not require manual replacement of the unit to be tested, and does not require repeated construction of the test environment for the network segment to be tested, thereby improving test automation; finally, by automatically integrating the unit test data and the network segment test data to generate a test report, the problem of data omission or format confusion that may be caused by manual archiving is avoided. The solution provided by this embodiment has the beneficial effect of improving test efficiency and saving labor costs.
[0107] In one embodiment, the unit configuration information includes at least a unit identifier corresponding to each unit under test, a test parameter corresponding to each unit under test, and a test sequence corresponding to each unit under test;
[0108] The test case calling module 320 is specifically used to call the corresponding unit test case for the current unit to be tested based on the unit identifier corresponding to the current unit to be tested, control the operation of the unit test case to generate test data for the test parameters corresponding to the current unit to be tested; after completing the test of the corresponding units to be tested in sequence according to the test sequence corresponding to each unit to be tested, obtain the unit test data corresponding to each unit to be tested.
[0109] In one embodiment, the unit configuration information further includes an association identifier corresponding to at least one association unit associated with the unit under test; and the apparatus further includes a communication test module, wherein:
[0110] A communication test module, configured to perform a communication test based on the communication relationship between the unit under test and the associated unit to obtain communication data;
[0111] The test report generating module 330 is further configured to generate the test report according to the fault type of the fault data when it is detected that the communication data is fault data.
[0112] In one embodiment, the unit configuration information further includes fault interference information;
[0113] The test case calling module 320 is further configured to control the execution of the unit test case according to the test parameters corresponding to the current unit under test and the fault interference information, and generate test data for the test parameters corresponding to the current unit under test.
[0114] In one embodiment, the network segment configuration information includes at least a network segment identifier corresponding to each network segment to be tested, a parameter to be tested corresponding to each network segment to be tested, and a test sequence corresponding to each network segment to be tested;
[0115] The test case calling module 320 is specifically used to call the corresponding network segment test case for the current network segment to be tested based on the network segment identifier corresponding to the current network segment to be tested, control the operation of the network segment test case to generate test data corresponding to the current network segment to be tested; after completing the test of each network segment to be tested according to the test sequence corresponding to each network segment to be tested, obtain the network segment test data corresponding to each network segment to be tested.
[0116] In one embodiment, the test configuration information further includes a target storage path; and the apparatus further includes a test data storage module, wherein:
[0117] The test data storage module is used to control the storage of the unit test data corresponding to each unit to be tested and the network segment test data corresponding to each network segment to be tested to the target storage path.
[0118] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the functional modules described above can refer to the corresponding process in the aforementioned method embodiment and will not be repeated here.
[0119] An embodiment of the present application also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the vehicle network testing method described in any embodiment of the present application.
[0120] An embodiment of the present application further provides a computer-readable medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the vehicle network testing method described in any embodiment of the present application when executed.
[0121] Reference below Figure 4 , Figure 4 FIG1 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application, which shows a schematic diagram of the structure of a computer system 500 suitable for implementing the electronic device in an embodiment of the present application. Figure 4 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.
[0122] like Figure 4 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage unit 508 into a random access memory (RAM) 503. Various programs and data required for the operation of the system 500 are also stored in the RAM 503. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.
[0123] The following components are connected to the I / O interface 505: an input section 506 including a keyboard, a mouse, and the like; an output section 507 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 508 including a hard disk; and a communication section 509 including a network interface card such as a LAN card or a modem. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 510 as needed, so that computer programs read therefrom can be installed into the storage section 508 as needed.
[0124] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 509, and / or installed from a removable medium 511. When the computer program is executed by the central processing unit (CPU) 501, the above-mentioned functions defined in the system of the present application are executed.
[0125] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this application, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. This propagated data signal can take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, and optical cables, or any suitable combination thereof.
[0126] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the above-mentioned module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of the boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0127] The modules and / or units described in the embodiments of the present application may be implemented in software or hardware. The modules and / or units described may also be provided in a processor. For example, the processor may be described as comprising a configuration information receiving module, a test case calling module, and a test case calling module. The names of these modules do not, in certain circumstances, limit the modules themselves.
[0128] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently and not be assembled into the device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by a device, the device includes: receiving test configuration information related to a vehicle to be tested, the test configuration information including unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested, each of the network segments to be tested including multiple units to be tested; calling a corresponding unit test case according to the unit configuration information of each unit to be tested, and sequentially running the unit test case to obtain unit test data corresponding to each unit to be tested; after detecting that each unit to be tested has been tested in sequence, calling a corresponding network segment test case according to the network segment configuration information of each network segment to be tested, and sequentially running the network segment test case to obtain network segment test data corresponding to each network segment to be tested; and generating a test report for the vehicle to be tested based on the unit test data and the network segment test data.
[0129] The technical solution of this embodiment eliminates the need to manually replace the unit under test and eliminates the need to repeatedly set up the test environment for the network segment under test, thereby improving test automation. By automatically integrating unit test data with network segment test data to generate a test report, this avoids data omissions or formatting issues that may result from manual filing. The solution provided by this embodiment achieves the beneficial effects of improving test efficiency and saving labor costs.
[0130] The above specific embodiments do not constitute a limitation on the scope of protection of this application. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application shall be included within the scope of protection of this application.
Claims
1. A vehicle network testing method, characterized in that: include: Receive test configuration information related to the vehicle to be tested, the test configuration information including unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested, each of the network segments to be tested including multiple units to be tested; Calling corresponding unit test cases according to the unit configuration information of each unit to be tested, and running the unit test cases in sequence to obtain unit test data corresponding to each unit to be tested; After detecting that each of the units to be tested has been tested in sequence, calling a corresponding network segment test case according to the network segment configuration information of each network segment to be tested, and sequentially running the network segment test case to obtain network segment test data corresponding to each network segment to be tested; A test report for the vehicle to be tested is generated according to the unit test data and the network segment test data.
2. The vehicle network testing method according to claim 1, characterized in that: The unit configuration information at least includes a unit identifier corresponding to each unit under test, a test parameter corresponding to each unit under test, and a test sequence corresponding to each unit under test; The calling of corresponding unit test cases according to the unit configuration information of each unit to be tested, and sequentially running the unit test cases to obtain unit test data corresponding to each unit to be tested, includes: For the current unit under test, based on the unit identifier corresponding to the current unit under test, the corresponding unit test case is retrieved, and the unit test case is controlled to run to generate test data for the parameters to be tested corresponding to the current unit under test; After completing the tests on the corresponding units to be tested in sequence according to the test sequence corresponding to each unit to be tested, unit test data corresponding to each unit to be tested is obtained.
3. The vehicle network testing method according to claim 2, characterized in that: The unit configuration information further includes an association identifier corresponding to at least one association unit associated with the unit to be tested; The method further comprises: Performing a communication test based on the communication relationship between the unit under test and the associated unit to obtain communication data; When it is detected that the communication data is fault data, the test report is generated according to the fault type of the fault data.
4. The vehicle network testing method according to claim 2, characterized in that: The unit configuration information also includes fault interference information; After controlling the unit test case to run and generate test data corresponding to the parameters to be tested of the current unit to be tested, the method further includes: The unit test case is controlled to run according to the parameters to be tested corresponding to the current unit to be tested and the fault interference information, and test data of the parameters to be tested corresponding to the current unit to be tested is generated.
5. The vehicle network testing method according to claim 1, characterized in that: The network segment configuration information at least includes the network segment identifiers corresponding to the network segments to be tested, the test parameters corresponding to each network segment to be tested, and the test sequence corresponding to each network segment to be tested; The calling of a corresponding network segment test case according to the network segment configuration information of each network segment to be tested, and sequentially running the network segment test case to obtain network segment test data corresponding to each network segment to be tested, includes: For the current network segment to be tested, based on the network segment identifier corresponding to the current network segment to be tested, a corresponding network segment test case is retrieved, and the network segment test case is controlled to run to generate test data corresponding to the current network segment to be tested; After completing the test of each network segment to be tested according to the test sequence corresponding to each network segment to be tested, network segment test data corresponding to each network segment to be tested is obtained.
6. The vehicle network testing method according to claim 1, characterized in that: The test configuration information also includes a target storage path; The method further comprises: The unit test data corresponding to each unit to be tested and the network segment test data corresponding to each network segment to be tested are controlled to be stored in the target storage path.
7. A vehicle network testing device, characterized in that: include: A configuration information receiving module is used to receive test configuration information related to the vehicle to be tested, wherein the test configuration information includes unit configuration information of multiple units to be tested and network segment configuration information of multiple network segments to be tested, each of the network segments to be tested includes multiple units to be tested; A test case calling module is used to call the corresponding unit test case according to the unit configuration information of each unit to be tested, and run the unit test case in sequence to obtain the unit test data corresponding to each unit to be tested; The test case calling module is further configured to, after detecting that each unit under test has been tested in sequence, call the corresponding network segment test case according to the network segment configuration information of each network segment under test, and sequentially run the network segment test case to obtain the network segment test data corresponding to each network segment under test; A test report generating module is used to generate a test report of the vehicle to be tested based on the unit test data and the network segment test data.
8. A vehicle network testing system, characterized in that: The vehicle testing system comprises at least an industrial computer, a test device and an intelligent control board, wherein the intelligent control board is connected to the test device and the industrial computer respectively; the intelligent control board comprises a plurality of network segments to be tested, and each network segment to be tested comprises a plurality of units to be tested; The industrial computer is used to execute the vehicle network testing method according to any one of claims 1 to 6.
9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor. The computer program is executed by the at least one processor to enable the at least one processor to perform the vehicle network testing method according to any one of claims 1 to 6.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the vehicle network testing method according to any one of claims 1 to 6 is implemented.