Cabin test method and related device

Abstract

The invention discloses a cockpit test method and a related device, relates to the field of vehicle test, and can convert test specification description content into a test script in a target format based on a test script conversion rule. And performing test case conversion on the test script in the target format by calling test case writing software to obtain a test case table. And finally, calling case test software to inject the test case in the test case table into a lower computer connected with the control equipment, so that the lower computer controls the control equipment to control an interactive interface of the cabin according to a control action indicated by the test case. And controlling the sound control equipment to generate a corresponding voice instruction to test the sound control function of the cabin. According to the method, the test personnel can automatically complete the whole process from the generation of the test case to the execution of the test case for cabin test only by inputting the corresponding test content, and the manual intervention degree can be remarkably reduced, so that the test efficiency is improved, the research and development cycle is shortened, and the test efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle testing technology, and in particular to a cockpit testing method and related apparatus. Background Technology

[0002] The design of a vehicle's cockpit is crucial to its driving comfort and safety. Compared to traditional cockpits, smart cockpits integrate various information technologies and artificial intelligence to form an integrated digital platform within the vehicle, providing drivers with an intelligent experience and promoting driving safety. The control components of a smart cockpit mainly include cockpit domain control, various LCD screens, a head-up display (HUD), and a streaming rearview mirror. Currently, with the accelerating pace of in-vehicle software iteration, manual testing methods are no longer sufficient to meet testing requirements, severely hindering the development speed and functional iteration of in-vehicle systems. Summary of the Invention

[0003] In view of the above problems, this application provides a cockpit testing method and related apparatus to improve testing efficiency and reduce testing costs. The specific solution is as follows:

[0004] The first aspect of this application provides a cockpit testing method, including:

[0005] Based on test script conversion rules, the test specification description is converted into a test script in the target format;

[0006] The test case writing software is invoked to convert the test script in the target format into test cases, thereby obtaining a test case table;

[0007] The test case testing software is invoked to inject the test cases from the test case table into the lower-level machine connected to the control device, so that the lower-level machine controls the control device to operate the interactive interface of the cockpit according to the control actions indicated by the test cases; and controls the voice control device to generate corresponding voice commands to test the voice control function of the cockpit.

[0008] In one possible implementation, the step of converting the test specification description into a test script in the target format based on test script conversion rules includes:

[0009] The test specification description is broken down into independent operation instructions;

[0010] The operation instructions are identified by function group to obtain test cases for each function group, and test case identifiers are generated for the test cases.

[0011] Based on the expression of the operation instruction and the bus database file, the bus signal path of the test case is generated;

[0012] After combining and naming the test cases of each functional group according to the preset structure, they are converted into test scripts in a format compatible with the test case writing software.

[0013] In one possible implementation, after combining and naming the test cases of each functional group according to a preset structure, and before converting them into test scripts in a format compatible with the software written from the test cases, the method further includes:

[0014] The operation instructions are formatted according to their categories, and the formatted operation instructions are then replaced in the corresponding test cases.

[0015] In one possible implementation, the format of each of the operation instructions is converted according to its category, including:

[0016] The setting instructions are converted into amplitude node instructions that are adapted to the preset structure, and the check signals are converted into instructions with timeout detection logic.

[0017] In one possible implementation, the cockpit testing method further includes:

[0018] An industrial camera is used to monitor the response status of the interactive interface, and the cockpit is evaluated by combining the monitoring results with the test results obtained from the test software.

[0019] In one possible implementation, the cockpit testing method further includes:

[0020] The test case testing software is invoked to compare and analyze the execution result data returned by the cockpit and the test cases based on the assertion mechanism, and a test report is generated.

[0021] A second aspect of this application provides a cockpit testing apparatus, comprising:

[0022] The test script generation module is used to convert the test specification description into a test script in the target format based on test script conversion rules.

[0023] The test case generation module is used to call test case writing software to convert the target format test script into test cases, thereby obtaining a test case table; and,

[0024] The test case execution module is used to call the test case testing software to inject the test cases in the test case table into the lower-level machine connected to the control device, so that the lower-level machine controls the control device to operate the interactive interface of the cockpit according to the control actions indicated by the test cases; and controls the voice control device to generate corresponding voice commands to test the voice control function of the cockpit.

[0025] A third aspect of this application provides a computer program product including computer-readable instructions that, when executed on an electronic device, cause the electronic device to implement the cockpit testing method of the first aspect or any implementation thereof.

[0026] A fourth aspect of this application provides an electronic device, including at least one processor and a memory connected to the processor, wherein:

[0027] The memory is used to store computer programs;

[0028] The processor is used to execute the computer program to enable the electronic device to implement the cockpit testing method of the first aspect or any implementation thereof.

[0029] The fifth aspect of this application provides a computer storage medium carrying one or more computer programs, which, when executed by an electronic device, enable the electronic device to implement the cockpit testing method described in the first aspect or any implementation thereof.

[0030] By employing the above technical solution, the cockpit testing method provided in this application can convert the test specification description into a test script in the target format based on test script conversion rules. By calling test case writing software to convert the target format test script into test cases, a test case table is obtained. Finally, the test case testing software is called to inject the test cases from the test case table into the lower-level machine connected to the control device. This allows the lower-level machine to control the control device to operate the cockpit's interactive interface according to the control actions indicated by the test cases; and to control the voice control device to generate corresponding voice commands to test the cockpit's voice control function. This allows testers to automate the entire process from test case generation to test case execution for cockpit testing simply by inputting the corresponding test content. This significantly reduces the degree of manual intervention, thereby improving testing efficiency and shortening the development cycle. It also reduces the need for human intervention, thus effectively reducing testing costs. Attached Figure Description

[0031] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0032] Figure 1 An architecture diagram of a cockpit testing system provided in this application;

[0033] Figure 2 A flowchart of a cockpit testing method provided in this application;

[0034] Figure 3 A software architecture diagram for cockpit testing provided in this application;

[0035] Figure 4 A hardware architecture diagram for cockpit testing provided in this application;

[0036] Figure 5 A structural diagram of a cockpit testing device provided in this application;

[0037] Figure 6 This is a structural diagram of an electronic device provided in this application. Detailed Implementation

[0038] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.

[0039] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0040] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0041] See Figure 1 , Figure 1 A schematic diagram of the architecture of a cockpit testing system is shown. The system may include a terminal 100 and a server 200. The server 200 can provide the cockpit testing method provided in the embodiments of this application to one or more terminals.

[0042] The terminal 100 may be equipped with a cockpit testing application. The application and webpage can provide an interface. The terminal 100 can receive the test specification description entered by the user on the cockpit testing interface and send the test specification description to the server 200. The server 200 can control the testing system to obtain the processing result based on the received parameters and return the processing result to the terminal 100.

[0043] It should be understood that in some optional implementations, the terminal 100 can also complete the connection control with the test system and obtain the processing results on its own, without the need for the server to cooperate. This application embodiment is not limited to this.

[0044] The following description Figure 1 The product form of the mid-terminal 100;

[0045] The terminal 100 in this application embodiment can be a tablet computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., and this application embodiment does not impose any restrictions on it.

[0046] Terminal 100 may include a radio frequency unit, memory, input unit, display unit, camera (optional), audio circuitry (optional), speaker (optional), microphone (optional), headphone jack (optional), processor, external interface, power supply, and other components. Those skilled in the art will understand that the above-mentioned components are merely examples and do not constitute a limitation on the terminal or multifunctional device; it may include more or fewer components, or a combination of certain components, or different components.

[0047] The input unit can be used to receive input numeric or character information, and to generate key signal inputs related to user settings and function control of the portable multi-functional device. Specifically, the input unit may include a touchscreen (optional) and / or other input devices. Other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0048] Among them, the input device can receive input data, etc.

[0049] The display unit can be used to display information input by the user or information provided to the user, various menus of the terminal, interactive interfaces, file display, and / or playback of any multimedia file. In the embodiments of this application, the display unit can be used to display the cockpit test interface, processing results, etc.

[0050] The memory can be used to store software code related to the cockpit testing method, the processor can execute the steps of the cockpit testing method, and can also schedule other units (such as the above-mentioned input unit and display unit) to achieve the corresponding functions.

[0051] This radio frequency unit (optional) can be used to receive and send signals during information transmission or calls.

[0052] In this embodiment of the application, the radio frequency unit can send data to the server 200 and receive the processing results sent by the server 200.

[0053] It should be understood that this radio frequency unit is optional and can be replaced with other communication interfaces, such as a network port.

[0054] Terminal 100 also includes a power source (such as a battery) for supplying power to the various components.

[0055] Terminal 100 also includes an external interface, which can be a standard Micro USB interface or a multi-pin connector, which can be used to connect terminal 100 to other devices for communication or to connect a charger to charge terminal 100.

[0056] Server 200 includes a bus, a processor, a communication interface, and memory. The processor, memory, and communication interface communicate with each other via the bus.

[0057] The memory can be used to store software code related to the cockpit testing method, the processor can execute the steps of the chip's cockpit testing method, and can also schedule other units to achieve corresponding functions.

[0058] In the current model, having a single individual undertake the coding of thousands of test case scripts greatly increases the risk of human error. Large-scale script development lacks effective automated verification mechanisms, leading to deviations in functional implementation and potential system stability risks. Furthermore, the process of converting natural language-described test specifications into automatically executable scripts is inefficient, significantly extending the development cycle and lagging far behind the rapid iteration requirements of in-vehicle infotainment software, thus hindering agile development and functional iteration of in-vehicle infotainment systems. In addition, to meet development cycle requirements, a significant amount of additional manpower and time is required for each project, leading not only to concentrated consumption and inefficient allocation of human resources but also to increased project development costs.

[0059] To address the aforementioned problems, this application provides a cockpit testing method. The cockpit testing method of this application embodiment will be described in detail below with reference to the accompanying drawings.

[0060] Reference Figure 2 , Figure 2 A flowchart illustrating a cockpit testing method provided in this application embodiment is shown below. Figure 2 As shown in the embodiment of this application, a cockpit testing method may include steps 201 to 203, which are described in detail below.

[0061] 201. Based on the test script conversion rules, convert the test specification description into a test script in the target format.

[0062] Specifically, the test specification can be recorded in tabular form. Each row in the table represents a test step or process, and each column represents the components of the corresponding instruction, such as step identifier, operation type, and element value. Users can fill in the required test content in batches in this table, then save it to generate a test content table. This test content table can then be input into script generation software, which will convert the content in the test content table into a corresponding test script that is compatible with the processing format of the subsequent test case writing software, according to the predicted test script conversion rules.

[0063] 202. Use test case writing software to convert the target format test script into test cases to obtain a test case table.

[0064] Based on the test scripts obtained above, test case writing software can be called, such as vTESTstudio, which provides a unified, model-based environment for efficiently designing, developing, managing, executing, and automating functional, integration, and system testing for embedded systems, especially automotive ECUs (Electronic Control Units). The test scripts are then converted into corresponding test cases compatible with the test case testing software.

[0065] 203. Call the test case testing software to inject the test cases in the test case table into the lower-level machine connected to the control device, so that the lower-level machine controls the control device to operate the cockpit's interactive interface according to the control actions indicated by the test cases; and controls the voice control device to generate corresponding voice commands to test the cockpit's voice control function.

[0066] Specifically, the test case software can use CANoe, which connects to the cockpit's electronic control unit (ECU) via the CAN bus. It can acquire feedback from the ECU when the control devices and voice control devices test the cockpit's interactive interface or interface. It provides a complete intelligent cockpit system simulation testing environment, realizing a closed-loop testing system covering test management, execution, monitoring, automated result evaluation, and report generation. It also supports real-time monitoring of the in-vehicle infotainment system's operating status.

[0067] This cockpit testing method automates the entire process of generating test scripts, test cases, and executing tests based solely on a pre-prepared table containing test content. This significantly reduces human intervention, thereby improving testing efficiency and shortening the development cycle. Furthermore, compared to traditional semi-automatic testing, it significantly reduces the need for human intervention, effectively cutting testing costs.

[0068] In another embodiment, the process of converting the test specification description into a test script in the target format based on test script conversion rules may specifically include:

[0069] Step 2011: Decompose the test specification description into independent operation instructions.

[0070] Step 2012: Identify the functional groups of each operation instruction, obtain the test cases for each functional group, and generate the test case identifiers for the test cases.

[0071] Step 2013: Based on the expression of the operation instruction and the bus database file, generate the bus signal path for the test cases.

[0072] Step 2014: After combining the test cases of each functional group according to the preset structure and adding names, convert them into a format and test case to write test scripts that are compatible with the software.

[0073] Specifically, taking a test specification description recorded in tabular form as an example, the table can be broken down into independent operation instructions (Set / Check, etc.) by row. Set can represent setting operation instructions, and Check can represent checking operation instructions.

[0074] Then, by differentiating the various functions within the IHU (In-Vehicle Infotainment Unit) of the in-vehicle cockpit system, different function groups are generated, and corresponding identifiers are added.

[0075] By parsing the Set / Check signal expressions above, the complete bus signal path can be obtained by querying the DBC table. The DBC table is a standard file format widely used in CAN (Controller Area Network) communication. It defines the transmission rules and formats for messages and signals, and the corresponding path can be determined by referring to this table.

[0076] Finally, the data is assembled into an XML tree structure, namespaces are added, and the output is formatted as a .vtt file, which can be called and edited by vTESTstudio.

[0077] In some embodiments, to further improve the compatibility of instructions and test case testing software, after combining and naming the test cases of each functional group according to a preset structure, and before converting them into test scripts that are compatible with the software format and test cases, the following steps are also included:

[0078] The operation instructions are formatted according to their categories, and the formatted operation instructions are then replaced in the corresponding test cases.

[0079] Specifically, setting instructions are converted into amplitude node instructions adapted to the preset structure, and check signals are converted into instructions with timeout detection logic. For example, the Set signal is converted into a signal amplitude XML node, and verification logic with timeout detection is built for the Check signal.

[0080] In other embodiments, to verify the test results data, an industrial camera can be used to monitor the response status of the interactive interface, and the cockpit can be evaluated by combining the monitoring results with the test results obtained from the test software.

[0081] In test case testing software, assertion mechanisms can be used to compare and analyze the execution result data returned by the cockpit and the test cases to generate test reports.

[0082] As a specific application of the above-mentioned cockpit testing methods, refer to Figure 3 The software architecture for implementing this cockpit testing method is shown below:

[0083] TTS, or Script Transformation Software, automatically converts test specifications described in text form into executable test scripts.

[0084] vTESTstudio: Provides a unified, model-based environment for efficiently designing, developing, and managing automated test scripts.

[0085] The CANoe project provides a complete intelligent cockpit system simulation testing environment, realizing a closed-loop testing system covering the entire process of test management, execution, monitoring, automated result evaluation, and report generation. Specifically, it includes:

[0086] a. Create a virtual testing environment: Through multi-source virtual environment modeling and automated testing closed loop, realize the full-stack simulation verification of intelligent cockpit functions, and support multi-level collaborative testing and defect diagnosis from signal interaction to human-machine interface.

[0087] b. Real-time feedback on vehicle system operating status: Based on the Trace / Graphics / Data module, the underlying signal interaction mechanism of the vehicle host is captured in real time, enabling multi-dimensional monitoring and diagnostic analysis of the system operating status during the manual debugging phase.

[0088] c. Test Case Management and Organization: Implement structured storage, attribute definition and version control of test cases, support requirement association and scenario classification, and ensure the traceability and multi-dimensional reuse of test activities.

[0089] d. Automated test execution: Based on the CAPL / Python API, the test sequence is automatically scheduled and executed, realizing multi-node collaborative stimulation, precise timing control and exception injection, and supporting unmanned verification of the entire HIL process.

[0090] e. Test monitoring and result determination: Through a dynamic assertion multi-source real-time signal mechanism, the test process achieves full-domain state perception and automated result determination, and simultaneously generates quantifiable deviation reports and fault root cause localization.

[0091] f. Test Record and Report Generation: Enables automatic generation of traceable verification reports that meet standards, supporting defect root cause localization.

[0092] HMI software: Through multimodal interaction channels such as graphical user interface (GUI), voice recognition, and touch / gesture, it enables bidirectional information transmission and logic control with the vehicle host.

[0093] The test engineering used is a collaborative control system centered on an in-vehicle computing platform, integrating HMI (Human-Machine Interface), IVI (In-Vehicle Infotainment), ADAS (Advanced Driver Assistance Systems), and cloud services. It reconstructs the driving experience through multimodal interaction and AI decision-making, and its design must meet the triple paradigms of functional safety (ISO 26262), cybersecurity (ISO / SAE 21434), and scene intelligence.

[0094] Accordingly, the hardware architecture used in the cockpit testing method refers to Figure 4 As shown, it can specifically include:

[0095] Host computer (equivalent to server): Deploys automated testing toolsets (such as the software mentioned above) to achieve dynamic loading of device parameters and control of the testing process.

[0096] Lower-level machine: By deploying the HMI on an independent terminal, the large-scale data generated during software operation is centrally stored, avoiding the problem of excessive load on the upper-level machine system due to too much test data.

[0097] Switch: Connects test hardware devices to the local area network to achieve interconnection and interoperability. It has the ability to automatically identify and network devices and supports parallel data transmission across multiple ports.

[0098] Three-axis robotic arm: Based on the spatial constraints of the driver's seat, a high-precision robotic arm system is deployed to perform automated continuous touch stimulation on the vehicle's IVI touch screen along a preset trajectory, simulating the driver's operating behavior.

[0099] Programmable power supply: Based on the TCP / IP protocol, it receives instructions and precisely regulates the output voltage / current to provide highly stable power supply for vehicle hardware.

[0100] Soundproof enclosure: Deploy acoustic equipment such as artificial mouthpieces, pickups, vehicle-mounted speakers, and microphones to create a noise-free testing environment and ensure accurate acquisition of acoustic characteristics.

[0101] As a specific application of the aforementioned cockpit testing method, it can be used for a series of intelligent cockpit automated tests, such as ADB automated testing, visual acquisition automation, digital key automated testing, functional diagnosis automation testing, and intelligent voice automation testing.

[0102] For example, the voice-controlled navigation and music test while driving verifies whether the system can accurately execute multimodal interactions and correctly handle task priority conflicts while ensuring driving safety when the navigation and entertainment systems are synchronously controlled via voice commands while the vehicle is in motion. In this test: First, TTS software is used to convert the preset natural language test cases into automated execution scripts; then, the scripts are imported into the vTESTstudio test development environment for compilation, generating a test list that can be run in the CANoe test software; the CANoe test software injects the preset test sequences into the lower-level machine for execution via the bus communication interface, synchronously calling the HMI simulation to generate standard human voice commands, thus achieving automated control of the in-vehicle infotainment system. System response status is captured by a high frame rate industrial camera (≥60fps).

[0103] The above describes a cockpit testing method provided by an embodiment of this application. The following describes the apparatus for performing the above cockpit testing method.

[0104] Please see Figure 5 , Figure 5 This is a schematic diagram of a cockpit testing device provided in an embodiment of this application. Figure 5 As shown, the cockpit testing device includes:

[0105] The test script generation module 501 is used to convert the test specification description content into a test script in the target format based on the test script conversion rules.

[0106] The test case generation module 502 is used to call the test case writing software to convert the target format test script into test cases, thereby obtaining a test case table; and,

[0107] The test case execution module 503 is used to call the test case testing software to inject the test cases in the test case table into the lower-level machine connected to the control device, so that the lower-level machine controls the control device to operate the cockpit's interactive interface according to the control actions indicated by the test cases; and controls the voice control device to generate corresponding voice commands to test the cockpit's voice control function.

[0108] In one possible implementation, the test script generation module 501, based on test script conversion rules, converts the test specification description into a test script in the target format, including:

[0109] The test specification description is broken down into independent operation instructions;

[0110] Each operation instruction is identified by its functional group to obtain test cases for each functional group, and test case identifiers are generated for each test case.

[0111] Based on the expressions of the operation instructions and the bus database file, the bus signal paths of the test cases are generated.

[0112] After combining and naming the test cases of each functional group according to the preset structure, the test cases are converted into a format that is compatible with the software and test scripts are written.

[0113] In one possible implementation, after combining and naming the test cases of each functional group according to a preset structure, and before converting them into test scripts that are compatible with the software format and test cases, the test script generation module 501 is further used for:

[0114] The operation instructions are formatted according to their categories, and the formatted operation instructions are then replaced in the corresponding test cases.

[0115] In one possible implementation, the process by which the test script generation module 501 performs format conversion on each operation instruction according to its category includes:

[0116] Convert setting instructions into amplitude node instructions that are compatible with the preset structure, and convert check signals into instructions with timeout detection logic.

[0117] In one possible implementation, it also includes: a status monitoring module, which calls an industrial camera to monitor the response status of the interactive interface, and combines the monitoring results with test results obtained from test software to evaluate the cockpit.

[0118] In one possible implementation, it also includes: a test result verification module, which calls the test case testing software to compare and analyze the execution result data returned by the cockpit and the test cases based on the assertion mechanism, and generates a test report.

[0119] This application also provides an electronic device in its embodiments. (See reference...) Figure 6 The diagram illustrates a structural schematic suitable for implementing the electronic device in the embodiments of this application. The electronic device in the embodiments of this application may include, but is not limited to, fixed terminals such as laptops, desktop computers, etc. Figure 6 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0120] like Figure 6As shown, the electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. When the electronic device is powered on, the RAM 603 also stores various programs and data required for the operation of the electronic device. The processing unit 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0121] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, memory cards, hard drives, etc.; and communication devices 609. Communication device 609 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.

[0122] This application also provides a computer program product including computer-readable instructions, which, when executed on an electronic device, cause the electronic device to implement any of the cockpit testing methods provided in this application.

[0123] This application also provides a computer-readable storage medium that carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any of the cockpit testing methods provided in this application.

[0124] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0125] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0126] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0127] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

Claims

1. A cockpit testing method, characterized in that, include: Based on test script conversion rules, the test specification description is converted into a test script in the target format; The test case writing software is invoked to convert the test script in the target format into test cases, thereby obtaining a test case table; The test case testing software is invoked to inject the test cases from the test case table into the lower-level machine connected to the control device, so that the lower-level machine controls the control device to operate the interactive interface of the cockpit according to the control actions indicated by the test cases; and controls the voice control device to generate corresponding voice commands to test the voice control function of the cockpit.

2. The cockpit testing method according to claim 1, characterized in that, The process of converting the test specification description into a test script in the target format based on test script conversion rules includes: The test specification description is broken down into independent operation instructions; The operation instructions are identified by function group to obtain test cases for each function group, and test case identifiers are generated for the test cases. Based on the expression of the operation instruction and the bus database file, the bus signal path of the test case is generated; After combining and naming the test cases of each functional group according to the preset structure, they are converted into test scripts in a format compatible with the test case writing software.

3. The cockpit testing method according to claim 2, characterized in that, After combining and naming the test cases of each functional group according to the preset structure, and before converting them into test scripts in a format compatible with the software, the process further includes: The operation instructions are formatted according to their categories, and the formatted operation instructions are then replaced in the corresponding test cases.

4. The cockpit testing method according to claim 3, characterized in that, The format of each operation instruction is converted according to its category, including: The setting instructions are converted into amplitude node instructions that are adapted to the preset structure, and the check signals are converted into instructions with timeout detection logic.

5. The cockpit testing method according to any one of claims 1 to 4, characterized in that, Also includes: An industrial camera is used to monitor the response status of the interactive interface, and the cockpit is evaluated by combining the monitoring results with the test results obtained from the test software.

6. The cockpit testing method according to claim 1, characterized in that, Also includes: The test case testing software is invoked to compare and analyze the execution result data returned by the cockpit and the test cases based on the assertion mechanism, and a test report is generated.

7. A cockpit testing device, characterized in that, include: The test script generation module is used to convert the test specification description into a test script in the target format based on test script conversion rules. The test case generation module is used to call the test case writing software to convert the test script in the target format into test cases, and obtain a test case table. as well as, The test case execution module is used to call the test case testing software to inject the test cases in the test case table into the lower-level machine connected to the control device, so that the lower-level machine controls the control device to operate the interactive interface of the cockpit according to the control actions indicated by the test cases; and controls the voice control device to generate corresponding voice commands to test the voice control function of the cockpit.

8. A computer program product, characterized in that, Includes computer-readable instructions that, when executed on an electronic device, cause the electronic device to implement the cockpit testing method as described in any one of claims 1 to 6.

9. An electronic device, characterized in that, It includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program to enable the electronic device to implement the cockpit testing method as described in any one of claims 1 to 6.

10. A computer storage medium, characterized in that, The storage medium carries one or more computer programs that, when executed by an electronic device, enable the electronic device to implement the cockpit testing method as described in any one of claims 1 to 6.

Images