Automatic testing method, system and equipment for ground equipment software and storage medium

Abstract

A ground equipment software automatic testing method, system and device and a storage medium relate to the field of simulation testing, and the method comprises the following steps: running GUI test software on a preset equivalent verification platform to generate a plurality of test scripts of tested ground equipment software; editing the test script to generate a target test script, the editing including variable addition, assertion, loop logic and a communication instruction of the equivalent verification platform and peripheral equipment simulation software; and executing the target test script through the GUI test software according to the first test strategy to drive the measurement and control software operation equipment to test the ground equipment software to obtain a test result, thereby solving the technical problem that the efficient and accurate test requirements of the ground equipment software are difficult to meet due to dependence on manual test of the ground equipment software in related technologies, and improving the test efficiency. The test quality and efficiency of the ground equipment software can be remarkably improved, and then performance optimization and safety guarantee of the whole system are promoted.

Description

Technical Field

[0001] This application relates to the field of simulation testing, and particularly to a method, system, device, and storage medium for automated testing of ground equipment software. Background Art

[0002] With the continuous increase in the complexity of ground equipment, the verification and validation of ground equipment software have become increasingly important and complex.

[0003] Patent CN117724975A discloses a method and system for dynamic testing of ground equipment software, which includes: an external device simulation platform sends periodic messages to the ground equipment software, and the periodic messages include self-check information and status information; when the ground equipment software starts to execute a task, it sends a control message to the external device simulation platform; after receiving the control message, the external device simulation platform decomposes the control message, determines the command name corresponding to the control message, and obtains the corresponding preset control command and control command parameters through the command name, generates a control feedback message according to the control command and control command parameters, and modifies the periodic message; the external device simulation platform sends the control feedback message and the modified periodic message to the ground equipment software to complete the test. This method mainly relies on manual testing of ground equipment software, which not only takes a long time and has high costs, but also is prone to human errors and is difficult to meet the efficient and accurate testing requirements of ground equipment software. Especially for dynamic testing, manual operations cannot effectively cover all possible test scenarios and condition combinations, which directly affects the reliability and safety of ground equipment software.

[0004] Therefore, there is an urgent need for an automated testing method for ground equipment software to solve the above problems. Summary of the Invention

[0005] This application provides a method, device, device, and computer-readable storage medium for automated testing of ground equipment software, which can solve the technical problem in the prior art that relies on manual testing of ground equipment software and is difficult to meet the efficient and accurate testing requirements of ground equipment software.

[0006] In a first aspect, an embodiment of this application provides a method for automated testing of ground equipment software, and the method for automated testing of ground equipment software includes:

[0007] By running GUI test software on a preset equivalent verification platform, multiple test scripts for the ground equipment software to be tested are generated;

[0008] Edit the test scripts to generate target test scripts, where the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the external device simulation software;

[0009] Execute the target test script according to the first test strategy through the GUI test software to drive the measurement and control software to run the device to test the ground equipment software, and obtain the test results.

[0010] Combined with the first aspect, in one implementation, the generation of the test script for the ground equipment software under test by running the GUI test software on the preset equivalent verification platform includes:

[0011] Run the GUI test software on the main control software running device of the preset equivalent verification platform, so that the GUI test software running on the main control software running device records the operation information and key feature information of the ground equipment software under test;

[0012] Generate a test script according to the operation information and the key feature information.

[0013] Combined with the first aspect, in one implementation, before running the GUI test software on the main control software running device of the preset equivalent verification platform, so that the GUI test software running on the main control software running device records the operation information and key feature information of the ground equipment software under test, it further includes:

[0014] Generate test cases according to the actual test requirements;

[0015] Store the test cases in a fixed folder of the peripheral simulation software running device in the XML file format, and each XML file corresponds to a test case, and each of the XML files has a corresponding number;

[0016] According to the test cases, the tester operates the preset equivalent verification platform to test the ground equipment software to generate operation information and key feature information, where the operation information includes the operation information of the mouse and keyboard, and the key feature information includes voltage information and current information.

[0017] Combined with the first aspect, in one implementation, before running the GUI test software on the main control software running device of the preset equivalent verification platform, so that the GUI test software running on the main control software running device records the operation information and key feature information of the ground equipment software under test, it further includes:

[0018] Generate test cases according to the actual test requirements;

[0019] Store the test cases in a fixed folder of the peripheral simulation software running device in the XML file format, and each XML file corresponds to a test case, and each of the XML files has a corresponding number;

[0020] According to the test case, the tester operates a preset equivalent verification platform to test the ground equipment software, so as to generate operation information and key feature information, where the operation information includes operation information of a mouse and a keyboard, and the key feature information includes voltage information and current information.

[0021] In combination with the first aspect, in an implementation manner, after the target test script is executed by the GUI test software according to the first test strategy to drive the measurement and control software to run the device to test the ground equipment software, it further includes:

[0022] By establishing communication with the simulation software running device in advance to obtain the first feedback information sent by the simulation software running device, where the first feedback information includes the first test process feedback information and the first test problem feedback information, and the first feedback information is sent by a peripheral device on the ground device connected to the simulation software running device;

[0023] According to the first test problem feedback information, determine whether to adjust the first test strategy.

[0024] If it is determined to adjust the first test strategy, then adjust the first test strategy according to the first test problem feedback information, and continue to execute the target test script by the GUI test software according to the adjusted first test strategy and the first test process feedback information to drive the measurement and control software to run the device to test the ground equipment software, so as to obtain a test result, where adjusting the test strategy includes the duration of pausing the test process, adjusting test parameters, switching test cases, and / or a retry mechanism;

[0025] If it is determined not to adjust the first test strategy, then obtain a test result.

[0026] In combination with the first aspect, in an implementation manner, the adjusting the first test strategy according to the anti-first feedback information includes:

[0027] When it is detected that the first test problem feedback information contains information on voltage overlimit, obtain the pause duration;

[0028] When it is detected that the first test problem feedback information contains a problem feedback information on key parameter overlimit, obtain the test parameter to be adjusted;

[0029] When it is detected that the first test problem feedback information contains a problem feedback information on test anomaly, obtain the test case to be switched;

[0030] When it is detected that the first test problem feedback information contains a problem feedback information on temporary anomaly, obtain a retry instruction;

[0031] Adjust the first test strategy by pausing the duration of the test process, adjusting test parameters, switching test cases, and / or retry mechanisms.

[0032] In combination with the first aspect, in an implementation, the method of using the GUI test software to execute the target test script according to the first test strategy to drive the measurement and control software to run the device to test the ground equipment software includes:

[0033] The GUI test software retrieves the test case corresponding to the target test script and sends the XML file number information of the test case to the simulation software running device, so that the simulation software running device loads the test case based on the XML file number information of the test case, so that the simulation software running device simulates the status information of the peripheral device;

[0034] Drive the measurement and control software running device to test the ground equipment software connected to the simulation software running device.

[0035] In combination with the first aspect, in an implementation, after obtaining the test result, it further includes:

[0036] When the GUI test software obtains the test result, it sends information to the simulation software running device, and the information includes the XML file number of the next test case to be executed;

[0037] The simulation software running device loads the XML file of the next test case to be executed and clears the initialization to start executing the next test case.

[0038] In a second aspect, an embodiment of the present application provides a ground equipment software automated test system, and the ground equipment software automated test system includes:

[0039] A generation module, configured to generate a test script for the ground equipment software to be tested by running the GUI test software on a preset equivalent verification platform, where the preset equivalent verification platform includes a main control software running device and a measurement and control software running device;

[0040] An editing module, configured to edit the test script to generate a target test script, where the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the peripheral device simulation software;

[0041] A test module, configured to execute the target test script through the GUI test software to drive the equivalent verification platform connected thereto to test the ground equipment software corresponding to the target test script.

[0042] In a third aspect, an embodiment of the present application provides a ground equipment software automated testing device, which includes a processor, a memory, and a ground equipment software automated testing program stored on the memory and executable by the processor. When the ground equipment software automated testing program is executed by the processor, the steps of the ground equipment software automated testing method as described above are implemented.

[0043] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, characterized in that a ground equipment software automated testing program is stored on the computer-readable storage medium. When the ground equipment software automated testing program is executed by a processor, the steps of the ground equipment software automated testing method as described above are implemented.

[0044] The beneficial effects brought by the technical solutions provided in the embodiments of the present application include: by running the GUI testing software on a preset equivalent verification platform, multiple test scripts for the ground equipment software to be tested are generated; the test scripts are edited to generate target test scripts, where the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the peripheral device simulation software; the GUI testing software executes the target test scripts according to the first test strategy to drive the measurement and control software to run the device to test the ground equipment software and obtain test results, solving the technical problems in the related art that relying on manual testing of ground equipment software not only takes a long time and has high costs, but also is prone to human errors and is difficult to meet the efficient and accurate testing requirements of ground equipment software. Especially for dynamic testing, manual operations cannot effectively cover all possible test scenarios and condition combinations, which directly affects the reliability and safety of ground equipment software. The present application can significantly improve the testing quality and efficiency of ground equipment software, and further promote the performance optimization and safety guarantee of the entire system. Description of the Drawings

[0045] Figure 1 It is a schematic flowchart of an embodiment of the ground equipment software automated testing method of the present application;

[0046] Figure 2 For the present application Figure 1 It is a detailed flowchart of step S30;

[0047] Figure 3 It is a schematic diagram of the functional modules of an embodiment of the ground equipment software automated testing device of the present application;

[0048] Figure 4 It is a schematic diagram of the hardware structure of the ground equipment software automated testing device involved in the solution of the embodiment of the present application. Detailed Embodiments

[0049] To enable those skilled in the art to better understand the solution of this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this application.

[0050] First, some technical terms in this application will be explained to facilitate the understanding of this application by those skilled in the art.

[0051] To make the purpose, technical solution and advantages of this application clearer, the embodiments of this application will be further described in detail below in conjunction with the accompanying drawings.

[0052] In a first aspect, an embodiment of this application provides a method for automated testing of ground equipment software.

[0053] In one embodiment, referring to Figure 1 , Figure 1 is a schematic flowchart of the first embodiment of the method for automated testing of ground equipment software in this application. As Figure 1 shown, the method for automated testing of ground equipment software includes:

[0054] Step S10: Generate test scripts for the ground equipment software under test by running GUI test software on a preset equivalent verification platform, and multiple such test scripts are generated.

[0055] Exemplarily, generating test scripts for the ground equipment software under test by running GUI test software on a preset equivalent verification platform specifically includes the following steps:

[0056] 1. Deploy GUI test software on a preset equivalent verification platform. The preset equivalent verification platform includes a main control software running device and a measurement and control software running device, which are connected through a communication interface (such as a serial port, a network interface, etc.).

[0057] 2. According to the test cases, operate the preset equivalent verification platform to test the ground equipment software, and generate operation information and key feature information. The operation information includes operation information of the mouse and keyboard, such as mouse clicks, slides, keyboard inputs, etc. This information is recorded by the GUI test software to generate an operation log. The key feature information includes voltage information, current information, temperature information, self-check information, and process information. This information is collected by sensors and recorded by the GUI test software.

[0058] 3. Record the operation information and key feature information on the preset equivalent verification platform by running GUI test software on the preset equivalent verification platform.

[0059] 4. Generate test scripts: Based on the recorded operation information and key feature information, the GUI test software automatically generates initial test scripts. The scripts include the operation procedures and expected results of the ground equipment software.

[0060] Through the above steps, the generation of automated test scripts for the ground equipment software is achieved, reducing the workload of manually writing test scripts.

[0061] Specifically, before running the GUI test software on the main control software running device of the preset equivalent verification platform to record the operation information and key feature information of the ground equipment software to be tested, it further includes: generating test cases according to actual test requirements; storing the test cases in a fixed folder of the peripheral simulation software running device in the XML file format, and each XML file corresponds to a test case, and each of the XML files has a corresponding number; according to the test cases, the tester operates the preset equivalent verification platform to test the ground equipment software to generate operation information and key feature information, where the operation information includes the operation information of the mouse and keyboard, and the key feature information includes voltage information and current information.

[0062] Exemplarily, for example, the tester creates a set of test cases for the air conditioner function test, including:

[0063] Test case 1: Verify that the turning on and off functions of the air conditioner are normal.

[0064] Operation information:

[0065] Mouse operation: Double-click the "switch button";

[0066] Keyboard operation: None.

[0067] Expected result:

[0068] The air conditioner starts successfully.

[0069] Operation information record:

[0070] The coordinates and timestamp of the mouse click on the target position;

[0071] The system log record shows that the air conditioner status has changed from "off" to "on".

[0072] Key feature information record:

[0073] The voltage value (such as 220V) and current value (such as 3A) during the startup process;

[0074] The system record shows that the device is within the normal working range.

[0075] Test Case 2: Verify that the air conditioner can be set to a normal temperature of 25°C.

[0076] Operation Information:

[0077] Mouse Operation: Click on the "Temperature Setting" icon;

[0078] Keyboard Operation: Enter "25".

[0079] Expected Result:

[0080] The temperature of 25°C is displayed on the display screen.

[0081] The air conditioner starts to cool and blows cold air.

[0082] Operation Information Record:

[0083] The time point and accuracy of entering "25" (judge whether there is an error in input resulting in a temperature difference from the expected value). System response time: Record the duration from input to display screen update.

[0084] Key Feature Information Record:

[0085] The operating voltage and current after setting the temperature.

[0086] The response time of the temperature control module to ensure accurate temperature setting.

[0087] Test Case 3: Verify that the air conditioner's wind speed can be adjusted to medium speed normally.

[0088] Operation Information:

[0089] Mouse Operation: Click the "Wind Speed Adjustment" button and select "Medium Speed".

[0090] Expected Result:

[0091] The wind speed at the air outlet increases significantly to medium speed.

[0092] Operation Information Record:

[0093] The position and time of the mouse click.

[0094] The confirmation signal after wind speed adjustment.

[0095] Key Feature Information Record:

[0096] The current change before and after adjusting the wind speed to avoid overload.

[0097] Ensure that the equipment operates stably during the wind speed change process without abnormal voltage fluctuations.

[0098] Test Case 4: Verify that the air conditioner can enter the automatic mode normally.

[0099] Operation Information:

[0100] Mouse operation: Click the "Mode Switch" button and select "Automatic Mode".

[0101] Expected result:

[0102] The system enters the automatic mode and adjusts autonomously according to the ambient temperature.

[0103] Operation information record:

[0104] Click event of the mode switch button;

[0105] Time of system switch confirmation and status update.

[0106] Key feature information record:

[0107] Voltage and current before and after mode switching, and whether there are abnormal fluctuations during the judgment process;

[0108] Change frequency of voltage and current during the automatic adjustment process to ensure that the energy consumption is within a reasonable range.

[0109] Each test case is independently saved as an XML file, and the file name contains the number for easy identification and management.

[0110] Each test case is independently saved as an XML file with the file name "TC_number.xml".

[0111] Store all the XML test case files in a fixed folder of the peripheral simulation software running device, such as the. / test_cases / directory. Ensure that each file name corresponds to a unique number for convenient subsequent management and invocation.

[0112] The tester logs in to the preset equivalent verification platform using credentials, navigates to the XML folder storing all test cases in the platform, i.e.,. / test_cases / . According to the test requirements, select the test cases to be executed, such as TC_001.xml to TC_004.xml.

[0113] Specifically, the generation of the test script for the ground equipment software under test by running the GUI test software on the preset equivalent verification platform includes: running the GUI test software on the main control software running device of the preset equivalent verification platform to record the operation information and key feature information of the ground equipment software under test by the GUI test software running on the main control software running device; generating the test script according to the operation information and the key feature information.

[0114] Exemplarily, a ground equipment software whose functions include starting the device, setting parameters, and monitoring the operating status. To perform automated testing on this software, install and run the GUI testing software on the master control software operating device of the preset equivalent verification platform.

[0115] Master control software operating device: It can be a computer configured with a Windows or Linux operating system.

[0116] GUI testing software: Such as mainstream automated testing tools like Selenium or Appium.

[0117] Generating a test script for the ground equipment software to be tested by the GUI testing software specifically includes the following steps:

[0118] 1. Initial configuration: In the GUI testing software, configure information such as the running path of the ground equipment software and test environment parameters.

[0119] 2. Record operation information:

[0120] In the running GUI testing software, record the operations on the ground equipment software and record the operation information.

[0121] Specific examples of operation information:

[0122] Mouse operations: Double-click the desktop icon of the ground equipment software to start the program; click the "Settings" button on the software interface; slide the slider on the "Settings" interface to adjust the parameters.

[0123] Keyboard operations: Enter the username and password on the "Login" interface; enter "100" as the test value in the "Input Parameter" box.

[0124] Recording process:

[0125] The GUI testing software will automatically record the above operations and generate corresponding operation logs.

[0126] For example, the operation of double-clicking to start the program will be recorded as: mouse.double_click(300,400) # Assuming (300,400) is the coordinate of the program icon;

[0127] Keyboard input of username and password is recorded as: keyboard.send_keys("username") and keyboard.send_keys("password");

[0128] Voltage information is recorded as: voltage = get_voltage();

[0129] The current information is recorded as: current = get_current().

[0130] 3. Record key feature information

[0131] During the operation, in addition to recording the user's operation information, it is also necessary to collect the key feature information of the ground equipment software during operation.

[0132] Specific examples of key feature information:

[0133] Voltage information: When starting the device, the voltage output by the power supply module is 12V, and the allowable deviation is ±0.5V.

[0134] Current information: During operation, the current output by the power supply module is 5A, and the allowable deviation is ±0.2A.

[0135] Collection process:

[0136] The voltage and current information is collected in real time through sensors and transmitted to the main control software running device through communication interfaces (such as serial ports, CAN buses).

[0137] The GUI test software synchronously records this information with the operation information to form complete test data.

[0138] Recording example:

[0139] When starting the device, record the voltage information:

[0140] During operation, record the current information:

[0141] 4. Generate test script

[0142] Based on the recorded operation information and key feature information, the GUI test software automatically generates a preliminary test

[0143] script.

[0144] Specific content of the test script:

[0145] Operation steps: Include the user's mouse and keyboard operations, such as double-clicking to start the program, clicking the "Settings" button, etc.

[0146] Key feature information: Include the expected values and actual values of parameters such as voltage and current.

[0147] Step S20: Edit the test script to generate a target test script, where the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the peripheral device simulation software;

[0148] Exemplarily, the generated test script can be further edited and optimized to meet different test requirements. For example:

[0149] Add variables: Add variables to the test script to support multiple test scenarios. For example, add variables for simulating different user operation modes or different environmental conditions.

[0150] Add assertions: Add assertions to the test script to verify whether the test results meet expectations. For example, add assertions to check whether the output of the ground equipment software is within the expected range.

[0151] Add loop logic: Add loop logic to the test script to support the execution of the same test case multiple times. For example, implement repeated testing of the ground equipment software through loop logic to verify its stability.

[0152] Add communication instructions: Add communication instructions with the peripheral device simulation software to the test script. Through these instructions, the GUI test software can interact with the peripheral device simulation software to simulate a real hardware environment.

[0153] Script optimization: Optimize the test script, including deleting redundant code, merging repeated operations, optimizing the test process, etc., to improve test efficiency.

[0154] Through this step, the generated target test script has high flexibility and scalability and can adapt to different test requirements.

[0155] Step S30: Execute the target test script through the GUI test software according to the first test strategy to drive the measurement and control software to run the device to test the ground equipment software and obtain the test results.

[0156] Exemplarily, the GUI test software executes the target test script according to the first test strategy to drive the measurement and control software to run the device to test the ground equipment software, including the following steps:

[0157] 1. Load the target test script: Load the edited target test script into the GUI test software.

[0158] 2. Initialize the test environment: Initialize the preset equivalent verification platform and the peripheral device simulation software through the GUI test software to ensure that the test environment is in the expected state.

[0159] 3. Execute the test script: Execute the target test script through the GUI test software to drive the connected equivalent verification platform to simulate the operations of real users on the ground equipment software.

[0160] 4. Collect feedback information:

[0161] Test process feedback information: including information such as the execution status and execution results of the test process.

[0162] Test problem feedback information: including information such as anomalies and errors found during the test process.

[0163] 5. Dynamically adjust the test strategy: Dynamically adjust the test strategy according to the feedback information. For example:

[0164] When feedback information indicating that the voltage exceeds the limit is detected, delay the preset duration of the test process and record and save the feedback information indicating that the voltage exceeds the limit.

[0165] After the delay ends, continue to execute the test process according to the test script.

[0166] Before each new test case is executed, the simulated software running device needs to be cleaned and initialized to ensure that each test case runs in a clean environment. These operations include: resetting the status of all simulated devices, cleaning the log files or data caches, and restoring to the initial configuration.

[0167] Specifically, after the target test script is executed according to the first test strategy by the GUI test software to drive the measurement and control software running device to test the ground equipment software, it further includes: establishing communication with the simulated software running device in advance to obtain the first feedback information sent by the simulated software running device, where the first feedback information includes the first test process feedback information and the first test problem feedback information, and the first feedback information is sent by the peripheral devices on the ground device connected to the simulated software running device; determining whether to adjust the first test strategy according to the first test problem feedback information, if it is determined to adjust the first test strategy, then adjust the first test strategy according to the first test problem feedback information, and continue to execute the target test script according to the adjusted first test strategy and the first test process feedback information by the GUI test software to drive the measurement and control software running device to test the ground equipment software to obtain the test results, where adjusting the test strategy includes pausing the duration of the test process, adjusting the test parameters, switching the test cases, and / or the retry mechanism; if it is determined not to adjust the first test strategy, then obtain the test results.

[0168] Exemplarily, load the predefined target test script (such as "Communication Relay Test Script") through the GUI test software and start the automated test process according to the first test strategy (such as "Standard Communication Protocol Test Plan"). The system drives the measurement and control software (such as "Device Control Terminal") to run the actual or simulated ground equipment software and starts to execute the test task. Example:

[0169] The test script executed steps such as "initializing the communication link", "sending control instructions", and "receiving device status feedback" to verify whether the basic functions of the ground equipment software meet the expectations.

[0170] During the test, the system needs to obtain the feedback information sent by the device running the simulation software in real time to judge the test progress and discover potential problems. The GUI test software establishes a communication link with the device running the simulation software, and the latter sends two types of feedback information:

[0171] Feedback information for the first test process: such as "communication link established successfully", "instruction execution completed", "data transmission in progress", etc., reflecting the normal progress of the test process.

[0172] Feedback information for the first test problems: such as "communication timeout", "instruction execution failed", "data CRC check error", etc., reflecting the anomalies or errors encountered during the test. Example:

[0173] During the test, the feedback information returned by the device running the simulation software may include: {"test process feedback": "communication link established successfully, waiting for instruction execution...", "test problem feedback": "packet loss detected, current packet loss rate is 5%."} This feedback information is sent to the test control end through the peripheral devices (such as the log recording module) on the device running the simulation software.

[0174] According to the test problems in the feedback information, the system needs to dynamically adjust the test strategy to address the discovered problems. Specific operations:

[0175] Judge whether to adjust the strategy: The test system analyzes the "test problem feedback information" (such as the packet loss rate exceeding the threshold) to decide whether to adjust the test strategy.

[0176] Adjust the strategy: If adjustment is needed, select an appropriate adjustment method according to the problem feedback information. For example:

[0177] Duration of pausing the test process: If a communication timeout is detected, the system can extend the waiting timeout threshold (such as from 500ms to 1000ms).

[0178] Adjust the test parameters: If the packet loss rate is too high, the system can reduce the data transmission rate (such as from 100Mbps to 50Mbps).

[0179] Switch test cases: If a specific test case continuously fails, the system can switch to other test cases with lower priorities.

[0180] Retry mechanism: If the instruction execution fails, the system can trigger the retry mechanism (such as the number of retries is 3 times, and the interval is 2 seconds).

[0181] Continue the test: Based on the adjusted test strategy and the feedback information of the test process, the system continues to execute the target test script, drives the measurement and control software to run the ground equipment software, and completes the remaining test tasks. Example: If "packet loss is detected during the test, and the current packet loss rate is 5%", the system may adjust the strategy as follows:

[0182] 1. Reduce the data transmission rate from 100 Mbps to 50 Mbps.

[0183] 2. Extend the timeout threshold from 500 ms to 1000 ms.

[0184] 3. Retry the execution of the failed instruction, set the number of retries to 3 times, with an interval of 2 seconds.

[0185] The GUI test software continues to execute the test script according to the adjusted strategy.

[0186] After the test is completed, the system outputs the final test results, including the detailed information of the passed tests and the specific reasons for the failures. : Through the measurement and control software to run the device, complete the function verification of the ground equipment software, and output the test report.

[0187] Specifically, the adjustment of the first test strategy includes: when it is detected that the first test problem feedback information contains information on voltage overlimit, obtain the pause duration; when it is detected that the first test problem feedback information contains problem feedback information on critical parameter overlimit, obtain the test parameters to be adjusted; when it is detected that the first test problem feedback information contains problem feedback information on test anomaly, obtain the test cases to be switched; when it is detected that the first test problem feedback information contains problem feedback information on temporary anomaly, obtain the retry instruction; adjust the first test strategy by pausing the duration of the test process, adjusting the test parameters, switching the test cases, and / or the retry mechanism.

[0188] Exemplarily, 1. When it is detected that the first test problem feedback information contains information on voltage overlimit, during the test, the voltage of a certain device or the device running the simulation software exceeds the preset safe range, which may affect the test process.

[0189] Specific operations:

[0190] Obtain the pause duration: The test system obtains the pause duration related to the voltage overlimit according to the predefined rules (for example: 5 minutes).

[0191] Pause the test process: After obtaining the pause duration, the test system will pause the current test process and wait for the device voltage to return to the normal range. Example:

[0192] During the testing of a certain ground equipment software, the feedback information sent by the simulated software operating device contains the problem of "voltage exceeding the limit". The specific information is: {"Test problem feedback information": "The device voltage exceeds the limit. The current voltage is 12.5V, exceeding the safe range [10V, 12V]", "Processing method": "Pause the test process and wait for the voltage to recover"}

[0193] The test system obtains the pause duration according to the rule (for example: 5 minutes) and pauses the test process until the voltage returns to normal.

[0194] 2. When it is detected that the first test problem feedback information contains the problem feedback information of key parameter exceeding the limit

[0195] Scenario description: During the test, some key parameters (such as temperature, pressure, frequency, etc.) exceed the preset range, which may lead to test failure or equipment damage.

[0196] Specific operations:

[0197] Obtain the test parameters to be adjusted: According to the feedback information of key parameter exceeding the limit, the test system obtains the parameters that need to be adjusted (for example: reduce the temperature from 80°C to 70°C).

[0198] Adjust the test parameters: The test system dynamically adjusts the range or threshold of the key parameters and reconfigures the test environment. Example:

[0199] During the testing of a certain communication equipment, the feedback information sent by the simulated software operating device contains the problem of "temperature exceeding the limit". The specific information is: {"Test problem feedback information": "The device temperature exceeds the limit. The current temperature is 85°C, exceeding the safe range [0°C, 80°C]", "Processing method": "Adjust the temperature threshold"}, and the test system obtains the parameters to be adjusted according to the rule (for example: adjust the temperature threshold from 80°C to 85°C) and reconfigures the test environment to ensure the smooth progress of subsequent tests.

[0200] 3. When it is detected that the first test problem feedback information contains the problem feedback information of test anomaly

[0201] Scenario description: During the test, an abnormal situation occurs during the execution of the test case, resulting in the inability to complete the test process normally.

[0202] Specific operations:

[0203] Obtain the test case to be switched: According to the feedback information of test anomaly, the test system obtains the test case that needs to be switched (for example: switch from the current test case to the standby test case).

[0204] Switch the test case: The test system dynamically switches the test case and continues to execute the test process. Example:

[0205] During the testing of an autonomous driving system, the feedback information sent by the simulation software running device contains the "testing anomaly" problem. The specific information is: {"Testing problem feedback information": "The test case execution failed. Reason: The intersection signs could not be correctly recognized.", "Handling method": "Switch the test case"}. The testing system obtains the test case to be switched according to the rules (for example: switch to the test case specifically for intersection sign recognition problems), and re-executes the testing process.

[0206] 4. When it is detected that the first test problem feedback information contains a problem feedback information of a temporary anomaly

[0207] Scenario description: During the testing process, the testing process has a temporary anomaly (such as network latency, communication interruption, etc.). However, it is not necessarily required to adjust the testing strategy, but the problem can be solved through a retry mechanism.

[0208] Specific operations:

[0209] Obtain the retry instruction: According to the feedback information of the temporary anomaly, the testing system obtains the retry instruction (for example: the number of retries is 3 times, and the retry interval is 2 seconds).

[0210] Execute the retry mechanism: The testing system re-executes the failed test steps according to the retry instruction, or waits for a certain period of time and then continues the testing process.

[0211] Example: During the testing of a network device, the feedback information sent by the simulation software running device contains the "temporary anomaly" problem. The specific information is: {"Testing problem feedback information": "Communication interruption. Reason: Network latency", "Handling method": "Retry mechanism"}. The testing system obtains the retry instruction according to the rules (for example: 3 retries, with an interval of 2 seconds), and re-tries to establish a communication connection to ensure the smooth completion of the testing process.

[0212] Specifically, after obtaining the test result, it further includes: when the GUI testing software obtains the test result, it sends information to the simulation software running device. The information includes the XML file number of the next test case to be executed; the simulation software running device loads the XML file of the next test case to be executed, and clears and initializes it to start executing the next test case.

[0213] After the GUI test software executes a test script, it detects whether it has obtained the test result. If the test result is obtained, the GUI test software sends the number of the next test case to be executed to the peripheral simulation software running device. The peripheral device simulation software running device loads the corresponding XML file according to the received number, performs cleaning and initialization, and then starts to execute the new test case. For example: In the GUI test software, select and execute TC_001 (normal login test); after the test execution is completed, the GUI detects that TC_001 has been successfully run; the GUI sends the number of the next test case, TC_002 (user name is empty test), to the simulation device; the simulation device loads TC_002.xml, clears the current state, and initializes the environment; starts to execute the test steps of TC_002: when attempting to log in, the user name is empty, and it is expected that the system should prompt that the user name cannot be empty.

[0214] In this embodiment, by running the GUI test software on the preset equivalent verification platform, test scripts for the software of the ground equipment under test are generated, and there are multiple such test scripts; the test scripts are edited to generate target test scripts, where the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the peripheral device simulation software; the target test scripts are executed by the GUI test software according to the first test strategy to drive the measurement and control software running device to test the ground equipment software, and test results are obtained, solving the technical problem in the related art of the automated test of the ground equipment software, and solving the problem in the related art that relying on manual testing of the ground equipment software not only takes a long time and has high costs, but also is prone to human errors and is difficult to meet the efficient and accurate test requirements of the ground equipment software. This application can significantly improve the test quality and efficiency of the ground equipment software, and thus promote the performance optimization and safety guarantee of the entire system.

[0215] Further, in one embodiment, referring to Figure 2 , Figure 2 is the detailed process schematic diagram of step S30 in this application. As Figure 1 shown, the execution of the target test script by the GUI test software according to the first test strategy to drive the measurement and control software running device to test the ground equipment software includes: Figure 2 shown, the execution of the target test script by the GUI test software according to the first test strategy to drive the measurement and control software running device to test the ground equipment software includes:

[0216] Step S31: The GUI test software retrieves the test case corresponding to the target test script and sends the XML file number information of the test case to the simulation software running device, so that the simulation software running device loads the test case based on the XML file number information of the test case, so that the simulation software running device simulates the status information of the peripheral device;

[0217] Exemplarily, in the GUI test software, select the "Import Test Case" function and upload the above-prepared XML files (TC_001.xml, TC_002.xml, TC_003.xml). The software will parse the XML files and extract the XML number information of the test cases. On the user interface of the GUI test software, select the test cases to be executed. For example, select "TC_001.xml" to perform the air conditioner on / off test. The GUI test software sends the XML file number of the test case (such as TC_001) to the peripheral simulation software running device. After receiving the XML file number, the simulation software running device will load the corresponding test case based on this number. The simulation software running device loads the corresponding test case according to the XML file number (TC_001) and parses the operation steps and the status information of the simulation device in it. The peripheral device simulation software running device according to the <mock-device-info>Part, simulating the initial state information of the air conditioner. For example, when loading TC_001.xml, the simulation software sets the initial state of the peripheral device (air conditioner) to "off".

[0218] The GUI test software sends instructions to simulate user operations to the simulation software running device according to the operation steps in the XML file. For example, when executing TC_001.xml, the GUI test software sends an operation instruction of "double-click the switch button" to the simulation software running device. After receiving the operation instruction, the peripheral device simulation software running device will, according to the <mock-device-info>Simulate the state changes of some peripheral devices. For example, after receiving the operation of "double - click the switch button", the simulation software will change the state of the air conditioner from "off" to "on" and return the device state information after startup.

[0219] During the test execution, the GUI test software will record the timestamps and detailed logs of the information of each operation (such as mouse clicks, keyboard inputs). At the same time, the peripheral device simulation software running the device will record the state change information of the peripheral device, such as the on - off state of the air conditioner, the temperature setting value, the wind speed, etc.

[0220] The GUI test software will automatically verify the actual operation results according to the expected results in the XML file. For example, verify whether the air conditioner is successfully started or shut down, and verify whether the temperature displayed on the display screen is 25°C. After the test is completed, the GUI test software generates a detailed test report, including the passed test cases and the failed test cases. If a certain test case fails, the specific reason for the failure will be detailed in the report, such as "the display screen does not correctly display the target temperature" or "the air conditioner does not respond to the switch operation". The test report will be attached with the state information of the simulated peripheral device, such as the key parameters of the air conditioner during the test, such as voltage, current, temperature, etc. These information helps to further analyze the performance and stability of the air conditioner.

[0221] Step S32: Drive the measurement and control software running device to test the ground equipment software connected to the simulation software running device.

[0222] Exemplarily, the GUI test software performs corresponding automated operations according to the steps in the XML file. For example, perform the operation of double - clicking the switch button to simulate the tester testing the air conditioner function. The GUI test software automatically compares the actual operation results according to the expected results in the XML file to verify whether the air conditioner function works as expected. For example, verify whether the air conditioner is successfully started or shut down. After the test is completed, the GUI test software generates a detailed test report, including: the execution status of the test cases (passed / failed), operation information (such as mouse click coordinates, keyboard input content), state information (such as the state changes of peripheral devices), key feature information (such as voltage, current, temperature values).

[0223] In this embodiment, when the GUI test software retrieves the target test script, it sends the XML file number information of the target test script to the peripheral device, so that the peripheral device loads the target test script based on the XML file number information of the target test script;

[0224] When the peripheral device receives the XML file number information sent by the GUI test software, the GUI test software executes the test script corresponding to the XML file number information to control the equivalent verification platform to automatically test the ground equipment software under test, solving the technical problem in the related art that manual operations cannot effectively cover all possible test scenarios and condition combinations, which directly affects the reliability and safety of the ground equipment software. Through this embodiment, not only the flexibility and maintainability of the test are improved, but also the standardization and consistency of the test process are ensured. At the same time, with the support of the peripheral device and the equivalent verification platform, the ground equipment software under test can conduct comprehensive functional verification and performance testing in a virtualized environment, providing a reliable guarantee for its actual application.

[0225] In a second aspect, an embodiment of the present application further provides a ground equipment software automated testing device.

[0226] In one embodiment, referring to Figure 3 , Figure 3 is a schematic diagram of the functional modules of an embodiment of the ground equipment software automated testing device of the present application. As Figure 3 shown, the ground equipment software automated testing device includes:

[0227] A generation module 01, configured to generate a test script for the ground equipment software under test by running the GUI test software on a preset equivalent verification platform, where the preset equivalent verification platform includes a main control software running device and a measurement and control software running device;

[0228] An editing module 02, configured to edit the test script to generate a target test script, where the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the peripheral device simulation software;

[0229] A test module 03, configured to execute the target test script through the GUI test software to drive the equivalent verification platform connected thereto to test the ground equipment software corresponding to the target test script.

[0230] Further, in one embodiment, the generation module 01 is further configured to:

[0231] Run the GUI test software on the main control software running device of the preset equivalent verification platform, so that the GUI test software running on the main control software running device records the operation information and key feature information of the ground equipment software under test;

[0232] Generate a test script according to the operation information and the key feature information.

[0233] Further, in one embodiment, the generation module 01 is further configured to:

[0234] Generate test cases according to actual test requirements;

[0235] Store the test cases in a fixed folder of the peripheral simulation software running device in the XML file format, and each XML file corresponds to one test case, and each of the XML files has a corresponding number;

[0236] According to the test cases, the tester operates the preset equivalent verification platform to test the ground equipment software to generate operation information and key feature information, where the operation information includes operation information on the mouse and keyboard, and the key feature information includes voltage information and current information.

[0237] Further, in one embodiment, the test module 03 is further configured to:

[0238] Establish communication with the simulation software running device in advance to obtain the first feedback information sent by the simulation software running device, where the first feedback information includes the first test process feedback information and the first test problem feedback information, and the first feedback information is sent by the peripheral device on the ground device connected to the simulation software running device;

[0239] Determine whether to adjust the first test strategy according to the first test problem feedback information,

[0240] If it is determined to adjust the first test strategy, then adjust the first test strategy according to the first test problem feedback information, and continue to execute the target test script according to the adjusted first test strategy and the first test process feedback information through the GUI test software to drive the measurement and control software running device to test the ground equipment software to obtain a test result, where adjusting the test strategy includes the duration of suspending the test process, adjusting test parameters, switching test cases, and / or retry mechanism;

[0241] If it is determined not to adjust the first test strategy, then obtain the test result.

[0242] Further, in one embodiment, the test module 03 is further configured to:

[0243] When it is detected that the first test problem feedback information contains information on over-limit voltage, obtain the suspension duration;

[0244] When it is detected that the first test problem feedback information contains problem feedback information on over-limit key parameters, obtain the test parameters to be adjusted;

[0245] When it is detected that the first test problem feedback information contains problem feedback information on test anomalies, obtain the test cases to be switched;

[0246] When it is detected that the first test problem feedback information contains problem feedback information of a temporary anomaly, a retry instruction is obtained;

[0247] The first test strategy is adjusted by the duration of pausing the test process, adjusting test parameters, switching test cases, and / or a retry mechanism.

[0248] Further, in one embodiment, the test module 03 is further configured to:

[0249] After the GUI test software obtains the test result, it sends information to the simulation software running device, and the information includes the XML file number of the next test case to be executed;

[0250] The simulation software running device loads the XML file of the next test case to be executed, and clears and initializes it to start executing the next test case.

[0251] Further, in one embodiment, the test module 03 is further configured to:

[0252] The GUI test software retrieves the test case corresponding to the target test script and sends the XML file number information of the test case to the simulation software running device, so that the simulation software running device loads the test case based on the XML file number information of the test case, so that the simulation software running device simulates the status information of the peripheral device;

[0253] Drive the measurement and control software running device to test the ground equipment software connected to the simulation software running device.

[0254] Wherein, the function implementation of each module in the above-mentioned ground equipment software automation test device corresponds to each step in the above-mentioned ground equipment software automation test method embodiment, and its function and implementation process will not be elaborated here one by one.

[0255] In a third aspect, an embodiment of the present application provides a ground equipment software automation test device, and the ground equipment software automation test device can be a device with data processing functions such as a personal computer (PC), a notebook computer, a server, etc.

[0256] Refer to Figure 4 , Figure 4 This is a schematic diagram of the hardware structure of the ground equipment software automation test device involved in the embodiment solution of the present application. In the embodiment of the present application, the ground equipment software automation test device may include a processor, a memory, a communication interface, and a communication bus.

[0257] Among them, the communication bus can be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0258] The communication interface includes interfaces such as input / output (I / O) interfaces, physical interfaces, and logical interfaces for implementing the interconnection of components inside the ground equipment software automated test device, as well as interfaces for implementing the interconnection between the ground equipment software automated test device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0259] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical memory, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0260] The processor can be a general-purpose processor, which can call the ground equipment software automated test program stored in the memory and execute the ground equipment software automated test method provided by the embodiments of the present application. For example, the general-purpose processor can be a central processing unit (CPU). Among them, the method executed when the ground equipment software automated test program is called can refer to the various embodiments of the ground equipment software automated test method of the present application, which will not be elaborated here.

[0261] Those skilled in the art can understand that Figure 4 the hardware structure shown in

[0262] does not constitute a limitation to the present application, and may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0262] Fourthly, the embodiments of the present application also provide a computer-readable storage medium.

[0263] The ground equipment software automated test program is stored on the computer-readable storage medium of the present application. When the ground equipment software automated test program is executed by a processor, the steps of the ground equipment software automated test method as described above are implemented.

[0264] Among them, the method implemented when the ground equipment software automated test program is executed can refer to the various embodiments of the ground equipment software automated test method of the present application, which will not be elaborated here.

[0265] It should be noted that the serial numbers of the embodiments of the present application above are only for description and do not represent the superiority or inferiority of the embodiments.

[0266] The terms "including" and "having" and any variations thereof in the specification, claims and drawings of the present application are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally further include steps or units not listed, or may optionally further include other steps or units inherent to these processes, methods, products or devices. The descriptions such as "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit that "first", "second" and "third" are different types.

[0267] In the description of the embodiments of the present application, terms such as "exemplary", "for example" or "for instance" are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary", "for example" or "for instance" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of terms such as "exemplary", "for example" or "for instance" is intended to present relevant concepts in a specific manner.

[0268] In the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B; the "and / or" in the text is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality of" means two or more than two.

[0269] In some processes described in the embodiments of the present application, a plurality of operations or steps appear in a specific order. However, it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or may be executed in parallel. The serial numbers of the operations are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

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

[0271] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A method for automated testing of ground equipment software, characterized in that: The ground equipment software automated testing method comprises: Generate a test script for the ground equipment software under test by running the GUI test software on a preset equivalent verification platform, wherein the test scripts are multiple; Editing the test script to generate a target test script, wherein the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the peripheral device simulation software; The target test script is executed by the GUI test software according to the first test strategy to drive the measurement and control software running device to test the ground equipment software and obtain the test results.

2. The ground equipment software automated testing method according to claim 1, characterized in that: The generating of the test script of the ground equipment software under test by running the GUI test software on the preset equivalent verification platform comprises: By running the GUI test software on the main control software running device pre-set with the equivalent verification platform, the GUI test software running on the main control software running device records the operation information and key feature information of the ground equipment software under test; A test script for the ground equipment software under test is generated based on the operation information and the key feature information.

3. The ground equipment software automated testing method according to claim 2, characterized in that: Before the GUI test software is run on the main control software running device pre-installed with the equivalent verification platform so that the GUI test software runs on the main control software running device to record the operation information and key feature information of the ground equipment software under test, the method further includes: Generate test cases based on actual test requirements; The test cases are stored in a fixed folder of the peripheral simulation software running device in XML file format, and each XML file corresponds to a test case, and each XML file has a corresponding number; According to the test case, the tester operates the preset equivalent verification platform to test the ground equipment software to generate operation information and key feature information, wherein the operation information includes operation information of the mouse and keyboard, and the key feature information includes voltage information and current information.

4. The ground equipment software automated testing method according to claim 1, characterized in that: After executing the target test script according to the first test strategy through the GUI test software to drive the measurement and control software running device to test the ground equipment software, the method further includes: Establishing communication with the simulation software running device in advance to obtain first feedback information sent by the simulation software running device, wherein the first feedback information includes first test process feedback information and first test problem feedback information, and the first feedback information is sent by a peripheral device on a ground device connected to the simulation software running device; determining whether to adjust the first test strategy according to the first test question feedback information, If it is determined to adjust the first test strategy, the first test strategy is adjusted according to the first test problem feedback information, and the target test script is continued to be executed through the GUI test software according to the adjusted first test strategy and the first test process feedback information, so as to drive the measurement and control software running device to test the ground equipment software to obtain the test results, wherein adjusting the test strategy includes pausing the duration of the test process, adjusting the test parameters, switching the test case and / or the retry mechanism; If it is determined not to adjust the first test strategy, a test result is obtained.

5. The ground equipment software automated testing method according to claim 4, characterized in that: The adjusting the first test strategy includes: When it is detected that the first test problem feedback information includes information about voltage exceeding the limit, the pause duration is obtained; When it is detected that the first test problem feedback information includes problem feedback information of a key parameter exceeding a limit, the test parameter to be adjusted is obtained; When it is detected that the first test problem feedback information includes problem feedback information of a test abnormality, obtaining a test case to be switched; When it is detected that the first test problem feedback information includes temporarily abnormal problem feedback information, obtaining a retry instruction; The first test strategy is adjusted by pausing the test process for a certain period of time, adjusting test parameters, switching test cases and / or a retry mechanism.

6. The ground equipment software automated testing method according to claim 1, characterized in that: The step of executing the target test script according to the first test strategy through the GUI test software to drive the measurement and control software running device to test the ground equipment software includes: Retrieving a test case corresponding to a target test script through the GUI test software, and sending XML file number information of the test case to the simulation software running device, so that the simulation software running device loads the test case based on the XML file number information of the test case, so that the simulation software running device simulates the status information of the peripheral device; The measurement and control software operation device is driven to test the ground equipment software connected to the simulation software operation device.

7. The ground equipment software automated testing method according to claim 1, characterized in that: After obtaining the test results, the method further includes: When the GUI testing software obtains the test result, it sends information to the simulation software running device, wherein the information includes the XML file number of the next test case to be executed; The simulation software running device loads the XML file of the next test case to be executed, and cleans up and initializes to start executing the next test case.

8. A ground equipment software automated testing system, characterized in that: The ground equipment software automatic testing system comprises: A generation module, used to generate a test script for the ground equipment software under test by running the GUI test software on a preset equivalent verification platform, wherein the preset equivalent verification platform includes a main control software running device and a measurement and control software running device; An editing module, used for editing the test script to generate a target test script, wherein the editing includes adding variables, assertions, loop logic, and communication instructions between the equivalent verification platform and the peripheral device simulation software; The test module is used to execute the target test script through the GUI test software, drive the equivalent verification platform connected thereto, and test the ground equipment software corresponding to the target test script.

9. A ground equipment software automation test device, characterized in that: The ground equipment software automation testing device includes a processor, a memory, and a ground equipment software automation testing program stored in the memory and executable by the processor, wherein when the ground equipment software automation testing program is executed by the processor, the steps of the ground equipment software automation testing method as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a ground equipment software automation testing program, wherein when the ground equipment software automation testing program is executed by the processor, the steps of the ground equipment software automation testing method as described in any one of claims 1 to 7 are implemented.

Images