Software system testing method, device and equipment and readable storage medium

Abstract

This invention provides a software system testing method, apparatus, device, and readable storage medium. The software system testing method includes: acquiring test service options triggered by controls on the software system test interface, and performing corresponding tests based on the test service options; acquiring process data during the test based on CAN message trigger events or status trigger events; processing the process data to obtain data processing results; linking the software system test interface window environment variables to the data processing results; and displaying the functional test results and CAN interface test results of each piece of equipment software based on the data processing results. This invention ensures sufficient testing, displays the system test results of each piece of equipment software in real time on the software system test interface on a host computer, improves testing efficiency and quality, and thus enhances the reliability of the equipment software after testing.

Description

Technical Field

[0001] This invention relates to the field of equipment software system testing technology, and in particular to a software system testing method, apparatus, equipment, and readable storage medium. Background Technology

[0002] Software system testing is a system-level test of the compatibility between the software functions of various equipment within an aerospace system. It greatly helps ensure the software correctly fulfills the system's functional requirements and is a necessary step in verifying the software of each piece of equipment within the aerospace system. Current software system testing methods based on CAN bus communication require software testers to design test cases one by one using debugging tools and to execute these cases, resulting in low test analysis efficiency and a lack of intuitiveness. Furthermore, experience in testing CAN bus-based software systems is fragmented and exists only in various test reports, making it difficult to guarantee the adequacy of software system testing in actual testing work. Summary of the Invention

[0003] The main objective of this invention is to provide a software system testing method, apparatus, device, and readable storage medium, aiming to solve the technical problems of low testing efficiency and low testing quality in existing software system testing methods based on CAN bus communication.

[0004] In a first aspect, the present invention provides a software system testing method, the software system testing method comprising the following steps:

[0005] Obtain the test business options triggered by the software system test interface controls, and perform corresponding tests based on the test business options;

[0006] Acquire process data during the test based on CAN message-triggered events or status-triggered events;

[0007] The process data is processed to obtain the data processing result;

[0008] Link the environment variables of the software system test interface window to the data processing results, and display the functional test results and CAN interface test results of each equipment software based on the data processing results.

[0009] Optionally, before the step of obtaining the test business options triggered by the software system test interface control and performing the corresponding test based on the test business options, the following is included:

[0010] Determine whether each node running the software for each piece of equipment is a physical standalone machine;

[0011] If it is determined that the node machines running the software of each equipment are all physical single machines, then the test service option is to perform system testing on all software running on the physical single machines;

[0012] If it is determined that the node machines running the software of each equipment are not all physical single machines, then the test service option is to test the configuration items of the software running on the physical single machines.

[0013] Optionally, the step of performing corresponding tests based on the test service options includes:

[0014] If the test service option is to perform configuration item testing on software running on a physical standalone machine, then the corresponding service for the non-physical standalone machine will be simulated based on the type of non-physical standalone machine, and the configuration item testing will be performed on the software running on the physical standalone machine.

[0015] Optionally, the step of simulating the corresponding business of a non-physical standby machine based on the type of non-physical standby machine includes:

[0016] If the non-physical stand-alone device is an actively controlled stand-alone device, then the actively controlled stand-alone device is simulated to send a specific message in a specific time sequence or a specific state. The specific state includes the state of receiving control stimulus or the state of receiving preset variable value trigger.

[0017] If the non-physical stand-alone unit is a passive execution stand-alone unit, then the simulated passive execution stand-alone unit will perform the corresponding action after receiving the control message and transmit the feedback information to the CAN bus message monitoring channel.

[0018] If the non-physical stand-alone unit is a unidirectional output unit, then the simulated unidirectional output motor periodically outputs preset messages to the CAN bus.

[0019] Optionally, before the step of obtaining the test business options triggered by the software system test interface control and performing the corresponding test based on the test business options, the following is included:

[0020] Establish a message protocol family corresponding to software testing operations;

[0021] Configure the basic database corresponding to the software testing service based on the aforementioned message protocol family;

[0022] Configure controls for the software system test interface and set the display settings for the physical quantities corresponding to the software test business;

[0023] In the corresponding compilation environment, pre-compile the CAN message trigger event and status trigger event functions. The status trigger events include control trigger events and timer trigger events.

[0024] Secondly, the present invention also provides a software system testing apparatus, the software system testing apparatus comprising:

[0025] The test triggering module is used to obtain the test business options triggered by the test interface control of the software system, and to perform the corresponding test based on the test business options;

[0026] The acquisition module is used to acquire process data during the test based on CAN message-triggered events or status-triggered events.

[0027] The data processing module is used to process the process data and obtain the data processing results;

[0028] The display module is used to link the environment variables of the software system test interface window to the data processing results, and to display the functional test results and CAN interface test results of each piece of equipment software based on the data processing results.

[0029] Optionally, the software system testing apparatus further includes a determining module, used for:

[0030] Determine whether each node running the software for each piece of equipment is a physical standalone machine;

[0031] If it is determined that the node machines running the software of each equipment are all physical single machines, then the test service option is to perform system testing on all software running on the physical single machines;

[0032] If it is determined that the node machines running the software of each equipment are not all physical single machines, then the test service option is to test the configuration items of the software running on the physical single machines.

[0033] Optionally, the test triggering module is further specifically used for:

[0034] If the test service option is to perform configuration item testing on software running on a physical standalone machine, then the corresponding service for the non-physical standalone machine will be simulated based on the type of non-physical standalone machine, and the configuration item testing will be performed on the software running on the physical standalone machine.

[0035] Optionally, the test triggering module is further specifically used for:

[0036] If the non-physical stand-alone device is an actively controlled stand-alone device, then the actively controlled stand-alone device is simulated to send a specific message in a specific time sequence or a specific state. The specific state includes the state of receiving control stimulus or the state of receiving preset variable value trigger.

[0037] If the non-physical stand-alone unit is a passive execution stand-alone unit, then the simulated passive execution stand-alone unit will perform the corresponding action after receiving the control message and transmit the feedback information to the CAN bus message monitoring channel.

[0038] If the non-physical stand-alone unit is a unidirectional output unit, then the simulated unidirectional output motor periodically outputs preset messages to the CAN bus.

[0039] Optionally, the software system testing apparatus further includes a construction module for:

[0040] Establish a message protocol family corresponding to software testing operations;

[0041] Configure the basic database corresponding to the software testing service based on the aforementioned message protocol family;

[0042] Configure controls for the software system test interface and set the display settings for the physical quantities corresponding to the software test business;

[0043] In the corresponding compilation environment, pre-compile the CAN message trigger event and status trigger event functions. The status trigger events include control trigger events and timer trigger events.

[0044] Thirdly, the present invention also provides a software system testing device, the software system testing device including a processor, a memory, and a software system testing program stored in the memory and executable by the processor, wherein when the software system testing program is executed by the processor, it implements the steps of the software system testing method as described above.

[0045] Fourthly, the present invention also provides a readable storage medium storing a software system test program, wherein when the software system test program is executed by a processor, it implements the steps of the software system test method as described above.

[0046] This invention provides a software system testing method, apparatus, device, and readable storage medium. The software system testing method includes: acquiring test service options triggered by controls on the software system test interface, and performing corresponding tests based on the test service options; acquiring process data during the test based on CAN message trigger events or status trigger events; processing the process data to obtain data processing results; linking the software system test interface window environment variables to the data processing results; and displaying the functional test results and CAN interface test results of each piece of equipment software based on the data processing results. This invention ensures sufficient testing, displays the system test results of each piece of equipment software in real time on the software system test interface on a host computer, improves testing efficiency and quality, and thus enhances the reliability of the equipment software after testing. Attached Figure Description

[0047] Figure 1 This is a schematic diagram of the hardware structure of the software system testing equipment involved in the embodiments of the present invention;

[0048] Figure 2 This is a flowchart illustrating an embodiment of the software system testing method of the present invention;

[0049] Figure 3 This is a flowchart illustrating another embodiment of the software system testing method of the present invention;

[0050] Figure 4This is a schematic diagram of the functional modules of an embodiment of the software system testing device of the present invention.

[0051] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0052] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0053] In a first aspect, embodiments of the present invention provide a software system testing device.

[0054] Reference Figure 1 , Figure 1 This is a schematic diagram of the hardware structure of the software system testing equipment involved in the embodiments of the present invention. In this embodiment, the software system testing equipment may include a processor 1001 (e.g., a Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to realize communication between these components; the user interface 1003 may include a display screen or an input unit such as a keyboard; the network interface 1004 may optionally include a standard wired interface or a wireless interface (e.g., Wireless Fidelity, Wi-Fi interface); the memory 1005 may be high-speed random access memory (RAM) or stable memory (non-volatile memory), such as a disk storage device. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001. Those skilled in the art will understand that… Figure 1 The hardware structure shown does not constitute a limitation of the invention and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0055] Continue to refer to Figure 1 , Figure 1 The memory 1005, serving as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a software system testing program. The processor 1001 can call the software system testing program stored in the memory 1005 and execute the software system testing method provided in this embodiment of the invention.

[0056] Secondly, current software system testing methods based on CAN bus communication require software testers to design test cases one by one using debugging tools and to execute these test cases. This results in low test analysis efficiency, unintuitive test results, and fragmented testing experience across various test reports, making it difficult to guarantee the sufficiency of software system testing. Therefore, this invention uses a portable computer or PC as the host computer, employing pre-configured CANoe software. The host computer is then connected to the CAN bus of each node device via CANoe hardware. The CANoe hardware monitors and receives CAN data transmitted on the CAN bus, performs software system testing on the software of each device running on the node devices, and displays the test results. This enables visualized management of the reception, processing, result control curves, and feedback curves of messages received on the bus throughout the testing process. The node devices are connected via a CAN bus, and the software system test program runs on the host computer.

[0057] Based on the above, embodiments of the present invention provide a software system testing method.

[0058] Reference Figure 2 , Figure 2 This is a flowchart illustrating an embodiment of the software system testing method of the present invention.

[0059] In one embodiment of the software system testing method of the present invention, the software system testing method includes:

[0060] Step S10: Obtain the test service options triggered by the software system test interface controls, and perform corresponding tests based on the test service options;

[0061] In this embodiment, during software system testing, the test service options triggered by the tester clicking on interface controls in the software system testing interface are first obtained. These test service options include software configuration item testing and software system testing. The corresponding test is then performed after the test service option is selected.

[0062] Step S20: Obtain process data during the test based on CAN message trigger events or status trigger events;

[0063] In this embodiment, process data during the test is obtained based on CAN message trigger events or status trigger events. The process data includes control physical quantities and feedback physical quantities for functional testing and interface testing of software configuration items of a single node during the test.

[0064] Step S30: Perform data processing on the process data to obtain data processing results;

[0065] In this embodiment, the process data obtained from the testing process is processed to obtain the data processing results, which correspond to the test results of the functional items and interface items of the software on a single node.

[0066] Step S40: Link the environment variables of the software system test interface window to the data processing results, and display the functional test results and CAN interface test results of each equipment software based on the data processing results.

[0067] In this embodiment, the data processing results are obtained by linking the environment variables of the software system test interface window to the obtained data processing results, thereby displaying the test results of the compatibility between the functions and interfaces of each piece of equipment software in the software system test interface window. This method allows for real-time display of the system test results of each piece of equipment software on the host computer's software system test interface, effectively solving the problems of low testing efficiency and poor test quality in existing software system testing methods based on CAN bus communication, which lack system testing tools in the actual testing environment. This ensures test sufficiency and improves both testing efficiency and quality.

[0068] Furthermore, in one embodiment, reference is made to Figure 3 Before step S10, the following is included:

[0069] Step S01: Determine whether each node running the software of each piece of equipment is a physical standalone machine;

[0070] Step S02: If it is determined that the node machines running each piece of equipment software are all physical single machines, then the test service option is to perform system testing on all software running on the physical single machines.

[0071] Step S03: If it is determined that the node machines running each equipment software are not all physical single machines, then the test service option is to perform configuration item testing on the software running on the physical single machines.

[0072] In this embodiment, each piece of software participating in the test runs on a node device, which can be a real standalone device or a simulated standalone device. During the determination of test service options, it is necessary to ascertain whether all node devices running the equipment software are physical standalone devices. If all are physical standalone devices, the software system testing tool can act as a monitoring node during testing, receiving and processing messages on the bus throughout the entire testing process and displaying the results in real time through a graphical interface. This allows for system testing of the compatibility between the functions and interfaces of the equipment software running on the physical standalone devices. If it is determined that not all node devices running the equipment software are physical standalone devices, the test service option is to test the configuration items of the software running on the physical standalone devices, thus providing a very flexible application scenario.

[0073] The operation steps of the software system testing tool as a monitoring node are as follows: analyze the test cases, extract the physical quantities involved in the test process, extract the messages involved in the physical quantities in the CAN bus protocol and configure them in the database; process the data during the execution of system process testing, extract the required physical quantities after receiving specific messages, and display the data processing results after data processing; perform real-time interpretation of the data processing results, display the real-time results and theoretical results, and provide test data for the test cases.

[0074] Furthermore, in one embodiment, the step of performing corresponding tests based on the test service options includes:

[0075] If the test service option is to perform configuration item testing on software running on a physical standalone machine, then the corresponding service for the non-physical standalone machine will be simulated based on the type of non-physical standalone machine, and the configuration item testing will be performed on the software running on the physical standalone machine.

[0076] In this embodiment, if the test service option is determined to be to perform configuration item testing on software running on a physical standalone machine, then it is necessary to simulate the corresponding service of the non-physical standalone machine based on the type of non-physical standalone machine and perform configuration item testing on the software running on the physical standalone machine.

[0077] Furthermore, in one embodiment, the step of simulating the business corresponding to a non-physical standby machine based on the type of non-physical standby machine includes:

[0078] If the non-physical stand-alone device is an actively controlled stand-alone device, then the actively controlled stand-alone device is simulated to send a specific message in a specific time sequence or a specific state. The specific state includes the state of receiving control stimulus or the state of receiving preset variable value trigger.

[0079] If the non-physical stand-alone unit is a passive execution stand-alone unit, then the simulated passive execution stand-alone unit will perform the corresponding action after receiving the control message and transmit the feedback information to the CAN bus message monitoring channel.

[0080] If the non-physical stand-alone unit is a unidirectional output unit, then the simulated unidirectional output motor periodically outputs preset messages to the CAN bus.

[0081] In this embodiment, the simulated services for different types of non-physical stand-alone machines also differ. Generally, non-physical stand-alone machines are divided into three types: active control units, passive execution units, and unidirectional output motors. Common simulated services include: active control units needing to set specific timings and states to send specific messages; passive execution units needing to receive control messages, execute corresponding actions, and transmit feedback information to the bus monitoring channel; and unidirectional output units needing to periodically output predetermined messages to the CAN bus.

[0082] When simulating stand-alone business operations, if the non-physical stand-alone machine is an actively controlled stand-alone machine, then the simulated actively controlled stand-alone machine sends specific messages at specific times or under specific states. These specific states include states triggered by receiving control stimuli or states triggered by receiving preset variable values. For example, when simulating the business of a certain stand-alone machine 1, if it is necessary to simulate whether the state is normal after power-on, it is necessary to simulate the test execution reaching a specific time, or receiving control stimuli from the test interface, or sending preset messages after variable value triggering.

[0083] When simulating stand-alone service operation, if the non-physical stand-alone unit is a passively executing stand-alone unit, the simulated passively executing stand-alone unit will perform corresponding actions after receiving control messages and transmit feedback information to the CAN bus message monitoring channel. For example, simulating the service of a certain stand-alone unit 2 requires simulating whether its status is normal after power-on, simulating the execution of corresponding services after receiving control signals, and sending feedback signals back to the bus.

[0084] When simulating stand-alone operation, if the non-physical stand-alone unit is a unidirectional output unit, the simulated unidirectional output motor periodically outputs preset messages to the CAN bus. For example, simulating the operation of a certain stand-alone unit 3 requires simulating whether the stand-alone status is normal after power-on, and it is necessary to simulate the periodic message sending.

[0085] Furthermore, in one embodiment, the procedure prior to step S10 includes:

[0086] Establish a message protocol family corresponding to software testing operations;

[0087] Configure the basic database corresponding to the software testing service based on the aforementioned message protocol family;

[0088] Configure controls for the software system test interface and set the display settings for the physical quantities corresponding to the software test business;

[0089] In the corresponding compilation environment, pre-compile the CAN message trigger event and status trigger event functions. The status trigger events include control trigger events and timer trigger events.

[0090] In this embodiment, before performing system testing or configuration item testing on software running on a single node, a corresponding CAN message protocol family is established for each software testing service. Communication based on this CAN message protocol family enables functional and interface testing at the software system level, ensuring 100% coverage of all messages in the protocol. The CANoe software's CANdb++ is used to configure the corresponding basic database based on the CAN message protocol family for each software testing service. This database includes data related to the single node, CAN bus messages, CAN signals, and environment variables involved in the CANoe software system test interface window. The established basic database is stored as a file within the CANoe software, and the corresponding database file is retrieved during specific testing operations.

[0091] Furthermore, this embodiment utilizes the paneleditor on the CANoe software to construct the panel interface as the software system test interface for various equipment software within the aerospace system. The software system test interface allows for the setting of controls and the display of physical quantities corresponding to different test services. Finally, in the corresponding CAPL programming compilation environment, CAN message triggering event and status triggering event functions are pre-compiled. The status triggering events include control triggering events and timer triggering events. Testers can click on the corresponding controls on the software system test interface to input corresponding control physical quantities to various equipment software within the aerospace system based on the control triggering events. During the software system test, based on CAN message triggering events, corresponding control operations can be executed upon receiving control messages, or based on status triggering events, pre-set specific messages can be continuously and periodically output to the CAN bus.

[0092] This embodiment provides a software system testing method comprising: acquiring test service options triggered by controls on the software system test interface, and performing corresponding tests based on the test service options; acquiring process data during the test based on CAN message trigger events or status trigger events; processing the process data to obtain data processing results; linking the environment variables of the software system test interface window to the data processing results, and displaying the functional test results and CAN interface test results of each piece of equipment software based on the data processing results. This invention ensures sufficient testing, displays the system test results of each piece of equipment software in real time on the software system test interface on the host computer, improves testing efficiency and quality, and thus enhances the reliability of each piece of equipment software after testing.

[0093] Thirdly, embodiments of the present invention also provide a software system testing apparatus.

[0094] Reference Figure 4A schematic diagram of the functional modules of an embodiment of a software system testing device.

[0095] In this embodiment, the software system testing device includes:

[0096] The test triggering module 10 is used to obtain the test business options triggered by the test interface control of the software system, and to perform corresponding tests based on the test business options;

[0097] The acquisition module 20 is used to acquire process data during the test based on CAN message-triggered events or status-triggered events.

[0098] Data processing module 30 is used to process the process data to obtain data processing results;

[0099] Display module 40 is used to link the environment variables of the software system test interface window to the data processing results, and display the functional test results and CAN interface test results of each equipment software based on the data processing results.

[0100] Furthermore, in one embodiment, the software system testing apparatus further includes a determining module, used for:

[0101] Determine whether each node running the software for each piece of equipment is a physical standalone machine;

[0102] If it is determined that the node machines running the software of each equipment are all physical single machines, then the test service option is to perform system testing on all software running on the physical single machines;

[0103] If it is determined that the node machines running the software of each equipment are not all physical single machines, then the test service option is to test the configuration items of the software running on the physical single machines.

[0104] Furthermore, in one embodiment, the test triggering module 10 is also specifically used for:

[0105] If the test service option is to perform configuration item testing on software running on a physical standalone machine, then the corresponding service for the non-physical standalone machine will be simulated based on the type of non-physical standalone machine, and the configuration item testing will be performed on the software running on the physical standalone machine.

[0106] Furthermore, in one embodiment, the test triggering module 10 is also specifically used for:

[0107] If the non-physical stand-alone device is an actively controlled stand-alone device, then the actively controlled stand-alone device is simulated to send a specific message in a specific time sequence or a specific state. The specific state includes the state of receiving control stimulus or the state of receiving preset variable value trigger.

[0108] If the non-physical stand-alone unit is a passive execution stand-alone unit, then the simulated passive execution stand-alone unit will perform the corresponding action after receiving the control message and transmit the feedback information to the CAN bus message monitoring channel.

[0109] If the non-physical stand-alone unit is a unidirectional output unit, then the simulated unidirectional output motor periodically outputs preset messages to the CAN bus.

[0110] Furthermore, in one embodiment, the software system testing apparatus further includes a construction module, used for:

[0111] Establish a message protocol family corresponding to software testing operations;

[0112] Configure the basic database corresponding to the software testing service based on the aforementioned message protocol family;

[0113] Configure controls for the software system test interface and set the display settings for the physical quantities corresponding to the software test business;

[0114] In the corresponding compilation environment, pre-compile the CAN message trigger event and status trigger event functions. The status trigger events include control trigger events and timer trigger events.

[0115] The functions of each module in the above-mentioned software system testing device correspond to the steps in the above-mentioned software system testing method embodiment, and their functions and implementation processes will not be described in detail here.

[0116] Fourthly, embodiments of the present invention also provide a readable storage medium.

[0117] The present invention provides a software system test program stored on a readable storage medium, wherein when the software system test program is executed by a processor, it implements the steps of the software system test method described above.

[0118] The method implemented when the software system test program is executed can be referred to in various embodiments of the software system test method of the present invention, and will not be repeated here.

[0119] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0120] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0121] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, 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 storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of the present invention.

[0122] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A software system testing method, characterized in that, The software system testing methods include: Obtain the test business options triggered by the software system test interface controls, and perform corresponding tests based on the test business options; Acquire process data during the test based on CAN message-triggered events or status-triggered events; The process data is processed to obtain the data processing result; Link the environment variables of the software system test interface window to the data processing results, and display the functional test results and CAN interface test results of each piece of equipment software based on the data processing results; Before the step of obtaining the test service options triggered by the software system test interface control and performing the corresponding test based on the test service options, the following steps are included: Determine whether each node running the software for each piece of equipment is a physical standalone machine; If it is determined that the node machines running the software of each equipment are all physical single machines, then the test service option is to perform system testing on all software running on the physical single machines; If it is determined that the node machines running the software of each equipment are not all physical single machines, then the test service option is to test the configuration items of the software running on the physical single machines. The steps for conducting corresponding tests based on the test service options include: If the test service option is to test the configuration items of the software running on a physical stand-alone machine, then the corresponding service of the non-physical stand-alone machine will be simulated based on the type of non-physical stand-alone machine, and the configuration items of the software running on the physical stand-alone machine will be tested. The steps for simulating the corresponding business of a non-physical standby machine based on the type of non-physical standby machine include: If the non-physical stand-alone device is an actively controlled stand-alone device, then the actively controlled stand-alone device is simulated to send a specific message in a specific time sequence or a specific state. The specific state includes the state of receiving control stimulus or the state of receiving preset variable value trigger. If the non-physical stand-alone unit is a passive execution stand-alone unit, then the simulated passive execution stand-alone unit will perform the corresponding action after receiving the control message and transmit the feedback information to the CAN bus message monitoring channel. If the non-physical stand-alone unit is a unidirectional output unit, then the simulated unidirectional output motor periodically outputs preset messages to the CAN bus.

2. The software system testing method as described in claim 1, characterized in that, Before the step of obtaining the test service options triggered by the software system test interface control and performing the corresponding test based on the test service options, the following steps are included: Establish a message protocol family corresponding to software testing operations; Configure the basic database corresponding to the software testing service based on the aforementioned message protocol family; Configure controls for the software system test interface and set the display settings for the physical quantities corresponding to the software test business; In the corresponding compilation environment, pre-compile the CAN message trigger event and status trigger event functions. The status trigger events include control trigger events and timer trigger events.

3. A software system testing device, characterized in that, The software system testing device includes: The test triggering module is used to obtain the test business options triggered by the test interface control of the software system, and to perform the corresponding test based on the test business options; The acquisition module is used to acquire process data during the test based on CAN message-triggered events or status-triggered events. The data processing module is used to process the process data and obtain the data processing results; The display module is used to link the environment variables of the software system test interface window to the data processing results, and to display the functional test results and CAN interface test results of each piece of equipment software based on the data processing results. The software system testing device further includes a determining module, used for: Determine whether each node running the software for each piece of equipment is a physical standalone machine; If it is determined that the node machines running the software of each equipment are all physical single machines, then the test service option is to perform system testing on all software running on the physical single machines; If it is determined that the node machines running the software of each equipment are not all physical single machines, then the test service option is to test the configuration items of the software running on the physical single machines. The test triggering module is also specifically used for: If the test service option is to test the configuration items of the software running on a physical stand-alone machine, then the corresponding service of the non-physical stand-alone machine will be simulated based on the type of non-physical stand-alone machine, and the configuration items of the software running on the physical stand-alone machine will be tested. The test triggering module is also specifically used for: If the non-physical stand-alone device is an actively controlled stand-alone device, then the actively controlled stand-alone device is simulated to send a specific message in a specific time sequence or a specific state. The specific state includes the state of receiving control stimulus or the state of receiving preset variable value trigger. If the non-physical stand-alone unit is a passive execution stand-alone unit, then the simulated passive execution stand-alone unit will perform the corresponding action after receiving the control message and transmit the feedback information to the CAN bus message monitoring channel. If the non-physical stand-alone unit is a unidirectional output unit, then the simulated unidirectional output motor periodically outputs preset messages to the CAN bus.

4. A software system testing device, characterized in that, The software system testing equipment includes a processor, a memory, and a software system testing program stored in the memory and executable by the processor, wherein when the software system testing program is executed by the processor, it implements the steps of the software system testing method as described in claim 1 or 2.

5. A readable storage medium, characterized in that, The readable storage medium stores a software system test program, wherein when the software system test program is executed by a processor, it implements the steps of the software system test method as described in claim 1 or 2.

Images