Airborne maintenance application software testing system and method

Abstract

The invention relates to an airborne maintenance application software testing system and method, and the system comprises a task management module which is used for creating and calling a plurality of sub-function task modules, and adding the created and called sub-function task modules into a task queue; the sub-function task module corresponds to an independent test task; the scheduling management module is used for adjusting the execution sequence of the sub-function task modules in the task queue on the basis of a trigger type round-robin scheduling strategy; and the data management module is used for periodically storing data generated when the sub-function task module is executed. According to the invention, the flexibility, real-time performance and expansibility of the system can be improved.

Description

Technical Field

[0001] The present invention relates to the technical field of software testing, and in particular to an onboard maintenance application software testing system and method. Background Art

[0002] With the development of avionics technology, airborne maintenance systems play an increasingly important role in the operation and maintenance of aircraft. As the core part of the airborne maintenance system, the stability and functionality of the central maintenance software are directly related to the operating efficiency and safety of the entire system. Therefore, the testing of the central maintenance software is particularly important. At present, the testing of airborne maintenance application software mainly relies on traditional testing methods, which have some limitations when dealing with complex and changing testing requirements.

[0003] At present, the industry's test methods for airborne maintenance systems mostly use integrated test solutions, which usually combine test tasks into one or more large test modules. For example, some traditional test systems rely on pre-set test scripts to perform a series of maintenance function verifications. The test process of such systems is usually linear, that is, a set of pre-defined test tasks are executed in a fixed order, and the execution of each task is independent, without dynamic interaction with other tasks. In addition, the test results are usually output through simple log files or screen displays, and real-time status monitoring or task scheduling cannot be achieved. And because the test scripts are pre-defined, it is difficult to cope with sudden demands or changes, especially if the test tasks need to be temporarily adjusted during the test process, the scripts often need to be rewritten or modified. Secondly, this test method cannot realize the dynamic scheduling of multiple tasks, resulting in inflexible resource allocation, affecting the efficiency and accuracy of the test. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide an onboard maintenance application software testing system and method, which can improve the flexibility, real-time performance and expansibility of the system.

[0005] The technical solution adopted by the present invention to solve the technical problem is: to provide an airborne maintenance application software testing system, comprising:

[0006] A task management module, used to create and call multiple sub-function task modules, and add the created and called multiple sub-function task modules to the task queue; the sub-function task module corresponds to an independent test task;

[0007] A scheduling management module, used to adjust the execution order of sub-function task modules in the task queue based on a triggered round-robin scheduling strategy;

[0008] The data management module is used to periodically store the data generated when executing the sub-function task module.

[0009] The task management module includes:

[0010] A receiving and parsing unit, used for receiving a test case and parsing the test case to obtain a plurality of sub-test tasks;

[0011] A judging unit, used for traversing each sub-test task and judging whether there is a sub-function task module corresponding to the sub-test task in the sub-function task library;

[0012] A calling unit, used for calling the sub-function task module from the sub-function task library when there is a sub-function task module corresponding to the sub-test task in the sub-function task library;

[0013] A creating unit is used to create a sub-function task module corresponding to the sub-test task when there is no sub-function task module corresponding to the sub-test task in the sub-function task library, and save the created sub-function task module into the sub-function task library.

[0014] The scheduling management module includes:

[0015] A detection module, used to detect whether there is a newly added sub-function task module in the task queue;

[0016] A priority determination module, used to determine whether the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue;

[0017] A state judgment module, used for judging whether the original sub-function task module is in an execution state when the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue;

[0018] The adjustment module is used to adjust the newly added sub-function task module to the front of the original sub-function task module when the original sub-function task module is not in the execution state; when the original sub-function task module is in the execution state, adjust the newly added sub-function task module to the back of the original sub-function task module.

[0019] The data generated when executing the sub-function task module includes test results, task status and execution log.

[0020] The onboard maintenance application software testing system further comprises: a comprehensive display module for displaying in real time the test execution results and task status when executing the sub-function task module.

[0021] The integrated display module is also used to provide user-defined interface options.

[0022] The technical solution adopted by the present invention to solve the technical problem is: to provide an onboard maintenance application software testing method, using the above-mentioned onboard maintenance application software testing system, comprising the following steps:

[0023] Get the test cases sent by the user;

[0024] The task management module creates and calls multiple sub-function task modules according to the test case, and adds the created and called multiple sub-function task modules to the task queue;

[0025] The scheduling management module adjusts the execution order of the sub-function task modules in the task queue based on the triggered round-robin scheduling strategy;

[0026] The sub-function task modules in the adjusted task queue are executed, and the data generated when the sub-function task modules are executed are periodically stored using the data management module.

[0027] The task management module creates and calls multiple sub-function task modules according to the test case, specifically including:

[0028] Parsing the test case to obtain multiple sub-test tasks;

[0029] Traverse each sub-test task and determine whether there is a sub-function task module corresponding to the sub-test task in the sub-function task library;

[0030] If there is a sub-function task module corresponding to the sub-test task in the sub-function task library, calling the sub-function task module from the sub-function task library;

[0031] If the sub-function task module corresponding to the sub-test task does not exist in the sub-function task library, a sub-function task module corresponding to the sub-test task is created, and the created sub-function task module is saved in the sub-function task library.

[0032] The scheduling management module adjusts the execution order of the sub-function task modules in the task queue based on the triggered round-robin scheduling strategy, specifically including:

[0033] Detect whether there is a newly added sub-function task module in the task queue;

[0034] Determine whether the priority of the newly added sub-function task module is higher than the original sub-function task module in the task queue;

[0035] If the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue, determining whether the original sub-function task module is in an execution state;

[0036] If the original sub-function task module is not in execution state, the newly added sub-function task module is adjusted to the front of the original sub-function task module;

[0037] If the original sub-function task module is in the execution state, the newly added sub-function task module is adjusted to behind the original sub-function task module.

[0038] The onboard maintenance application software testing method further includes: transmitting data generated when executing the sub-function task module to the integrated display module, and displaying the test execution results and task status when executing the sub-function task module in real time through the integrated display module.

[0039] Beneficial Effects

[0040] Due to the adoption of the above-mentioned technical solution, the present invention has the following advantages and positive effects compared with the prior art: the present invention creates multiple independent sub-function task modules so that each sub-function task module can be independently responsible for a specific test task, thereby realizing modular management of test tasks. At the same time, the introduction of a trigger-type round-robin scheduling strategy enables the system to dynamically adjust the execution order of tasks according to the importance and execution status of the tasks, thereby ensuring the rational allocation of resources and the efficient execution of the test process. In addition, the present invention also realizes real-time monitoring and visual display of test results through a comprehensive display menu module, thereby enhancing the operability of the system and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a structural schematic diagram of an onboard maintenance application software testing system according to a first embodiment of the present invention;

[0042] Figure 2 is a schematic diagram of the structure of a task management module in the first embodiment of the present invention;

[0043] Figure 3 is a schematic diagram of the structure of the scheduling management module in the first embodiment of the present invention;

[0044] Figure 4 is a flow chart of a method for testing airborne maintenance application software according to a second embodiment of the present invention;

[0045] Figure 5 It is a flow chart of the triggered round-robin scheduling strategy in the second embodiment of the present invention. DETAILED DESCRIPTION

[0046] The present invention will be further described below in conjunction with specific embodiments. It should be understood that these embodiments are only used to illustrate the present invention and are not intended to limit the scope of the present invention. In addition, it should be understood that after reading the content taught by the present invention, those skilled in the art can make various changes or modifications to the present invention, and these equivalent forms fall within the scope limited by the appended claims of the application equally.

[0047] The first embodiment of the present invention relates to an onboard maintenance application software testing system, such as Figure 1 As shown, including:

[0048] The task management module 101 is used to create and call multiple sub-function task modules, and add the created and called multiple sub-function task modules to the task queue; the sub-function task module corresponds to an independent test task, which has independent input, processing logic and output; the task management module in this embodiment can add or delete sub-function task modules according to needs, thereby realizing flexible management of test tasks.

[0049] like Figure 2 As shown, the task management module 101 in this embodiment includes:

[0050] A receiving and parsing unit 1011 is used to receive a test case and parse the test case to obtain a plurality of sub-test tasks;

[0051] The judging unit 1012 is used to traverse each sub-test task and judge whether there is a sub-function task module corresponding to the sub-test task in the sub-function task library;

[0052] The calling unit 1013 is used to call the sub-function task module from the sub-function task library when there is a sub-function task module corresponding to the sub-test task in the sub-function task library;

[0053] The creating unit 1014 is used to create a sub-function task module corresponding to the sub-test task when there is no sub-function task module corresponding to the sub-test task in the sub-function task library, and save the created sub-function task module into the sub-function task library.

[0054] It can be seen that this implementation method creates multiple independent sub-function task modules, so that each sub-function task module is independently responsible for a specific test task. This design realizes the modular management of test tasks, making the test tasks independent of each other and reducing the coupling between tasks. When the test requirements change, the sub-function task modules can be easily added or adjusted without having to make major modifications to the entire system, thereby greatly improving the flexibility and maintainability of the system.

[0055] The scheduling management module 102 is used to adjust the execution order of the sub-function task modules in the task queue based on the trigger-type round-robin scheduling strategy. Specifically, the scheduling management module dynamically adjusts the execution order according to the priority and real-time status of each sub-function task module. The scheduling management module ensures that high-priority tasks can be executed first through the round-robin scheduling mechanism, while ensuring the reasonable allocation of system resources.

[0056] like Figure 3 As shown, the scheduling management module 102 in this embodiment includes:

[0057] The detection module 1021 is used to detect whether there is a newly added sub-function task module in the task queue;

[0058] A priority determination module 1022 is used to determine whether the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue;

[0059] A state judgment module 1023, used for judging whether the original sub-function task module is in an execution state when the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue;

[0060] The adjustment module 1024 is used to adjust the newly added sub-function task module to the front of the original sub-function task module when the original sub-function task module is not in the execution state; when the original sub-function task module is in the execution state, adjust the newly added sub-function task module to the back of the original sub-function task module.

[0061] It is not difficult to find that this implementation introduces a triggered round-robin scheduling strategy to manage the test sub-function modules by establishing a task queue. This scheduling strategy dynamically adjusts the priority of tasks according to the importance and execution status of the tasks, achieving reasonable allocation of resources and efficient execution of the test process. This function ensures the optimal execution order of test tasks in the system, improves the overall test efficiency, and can better respond to sudden changes in demand.

[0062] The data management module 103 is used to periodically store the data generated when executing the sub-function task module. The data generated when executing the sub-function task module includes test results, task status and execution log. The data management module supports storing the data in the local hard disk for subsequent analysis and audit.

[0063] The onboard maintenance application software test system of this embodiment also includes a comprehensive display module 104, which is used to display the test execution results and task status when executing the sub-function task module in real time. The comprehensive display module 104 can display the test execution results and task status in real time by establishing a data transceiver port between PCs. Testers can use the comprehensive display module 104 to intuitively monitor the execution of each sub-function task module, find abnormalities and adjust the test strategy in time. It is worth mentioning that the comprehensive display module 104 also provides a variety of view options and user-defined interface options to meet the monitoring needs in different scenarios and realize a diversified and personalized user interaction experience.

[0064] The integrated display module of this embodiment presents the test results and task status in a visual manner, which effectively improves the operability of the system and the user experience, and enables testers to quickly identify and solve problems in the test.

[0065] The second embodiment of the present invention relates to an onboard maintenance application software testing method, which uses the onboard maintenance application software testing system of the first embodiment, such as Figure 4 As shown, the following steps are included:

[0066] Step 1: Get the test case sent by the user;

[0067] Step 2: The task management module creates and calls multiple sub-function task modules according to the test case, and adds the created and called multiple sub-function task modules to the task queue. This step specifically includes the following sub-steps:

[0068] Parsing the test case to obtain multiple sub-test tasks;

[0069] Traverse each sub-test task and determine whether there is a sub-function task module corresponding to the sub-test task in the sub-function task library;

[0070] If there is a sub-function task module corresponding to the sub-test task in the sub-function task library, calling the sub-function task module from the sub-function task library;

[0071] If the sub-function task module corresponding to the sub-test task does not exist in the sub-function task library, a sub-function task module corresponding to the sub-test task is created, and the created sub-function task module is saved in the sub-function task library.

[0072] Step 3: The scheduling management module adjusts the execution order of the sub-function task modules in the task queue based on the trigger-type round-robin scheduling strategy. Figure 5 As shown, specifically including:

[0073] Step A, obtain the current task queue of the system.

[0074] Step B, check whether the current task queue is empty. If the current task queue is empty, the current scheduling process ends directly. If the current queue is not empty, the system continues to execute step C.

[0075] Step C, read the first subtask function module to be processed from the task queue and enter the task execution phase. During the task execution process, the subtask function modules in the task queue are adjusted according to the dynamic scheduling strategy, as follows:

[0076] Detect whether there is a newly added sub-function task module in the task queue;

[0077] Determine whether the priority of the newly added sub-function task module is higher than the original sub-function task module in the task queue;

[0078] If the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue, determining whether the original sub-function task module is in an execution state;

[0079] If the original sub-function task module is not in execution state, the newly added sub-function task module is adjusted to the front of the original sub-function task module;

[0080] If the original sub-function task module is in the execution state, the newly added sub-function task module is adjusted to behind the original sub-function task module.

[0081] Step D: judge the read sub-function task module to check whether the sub-function task module has been completed. If the task has been completed, go to step 4; if the task has not been completed, go to step F.

[0082] Step 4: Use the data management module to record the data generated when executing the sub-function task module. The recorded data includes test results, execution logs, task status, etc. The data storage method supports local storage to ensure data integrity and security;

[0083] Step F: During the task execution process, if an abnormal situation is detected, the system records the abnormal state and subsequently debugs the test subsystem task to ensure the stable operation of the system.

[0084] Step G: Adjust the sub-function task module to the end of the task queue.

[0085] Step H: The system determines whether to continue to execute the next round of test tasks. If the test continues, the process returns to step A. If the test does not continue, the process ends.

[0086] It is worth mentioning that the present embodiment also includes: transmitting the data generated when executing the sub-function task module to the integrated display module, and displaying the test execution results and task status when executing the sub-function task module in real time through the integrated display module.

[0087] It is not difficult to find that the present invention realizes modular management of test tasks by creating multiple independent sub-function task modules so that each module can be independently responsible for a specific test task. At the same time, the introduction of the trigger-type round-robin scheduling strategy enables the system to dynamically adjust the priority of tasks according to the importance and execution status of the tasks, ensuring the rational allocation of resources and the efficient execution of the test process. In addition, the present invention also realizes real-time monitoring and visual display of test results through a comprehensive display menu module, enhancing the operability of the system and user experience.

Claims

1. An onboard maintenance application software testing system, characterized in that: include: A task management module, used for creating and calling multiple sub-function task modules, and adding the created and called multiple sub-function task modules to a task queue; The sub-function task module corresponds to an independent test task; A scheduling management module, used to adjust the execution order of sub-function task modules in the task queue based on a triggered round-robin scheduling strategy; The data management module is used to periodically store the data generated when executing the sub-function task module.

2. The onboard maintenance application software testing system according to claim 1, characterized in that: The task management module includes: A receiving and parsing unit, used for receiving a test case and parsing the test case to obtain a plurality of sub-test tasks; A judging unit, used for traversing each sub-test task and judging whether there is a sub-function task module corresponding to the sub-test task in the sub-function task library; A calling unit, used for calling the sub-function task module from the sub-function task library when there is a sub-function task module corresponding to the sub-test task in the sub-function task library; A creating unit is used to create a sub-function task module corresponding to the sub-test task when there is no sub-function task module corresponding to the sub-test task in the sub-function task library, and save the created sub-function task module into the sub-function task library.

3. The onboard maintenance application software testing system according to claim 1, characterized in that: The scheduling management module includes: A detection module, used to detect whether there is a newly added sub-function task module in the task queue; A priority determination module, used to determine whether the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue; A state judgment module, used for judging whether the original sub-function task module is in an execution state when the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue; The adjustment module is used to adjust the newly added sub-function task module to the front of the original sub-function task module when the original sub-function task module is not in the execution state; when the original sub-function task module is in the execution state, adjust the newly added sub-function task module to the back of the original sub-function task module.

4. The onboard maintenance application software testing system according to claim 1, characterized in that: The data generated when executing the sub-function task module includes test results, task status and execution log.

5. The onboard maintenance application software testing system according to claim 1, characterized in that: Also includes: The comprehensive display module is used to display the test execution results and task status in real time when executing the sub-function task module.

6. The onboard maintenance application software testing system according to claim 5, characterized in that: The integrated display module is also used to provide user-defined interface options.

7. A method for testing airborne maintenance application software, characterized in that: Using the onboard maintenance application software testing system described in any one of claims 1 to 6, comprising the following steps: Get the test cases sent by the user; The task management module creates and calls multiple sub-function task modules according to the test case, and adds the created and called multiple sub-function task modules to the task queue; The scheduling management module adjusts the execution order of the sub-function task modules in the task queue based on the triggered round-robin scheduling strategy; executes the sub-function task modules in the adjusted task queue, and uses the data management module to periodically store the data generated when executing the sub-function task modules.

8. The onboard maintenance application software testing method according to claim 7, characterized in that: The task management module creates and calls multiple sub-function task modules according to the test case, specifically including: Parsing the test case to obtain multiple sub-test tasks; Traverse each sub-test task and determine whether there is a sub-function task module corresponding to the sub-test task in the sub-function task library; If there is a sub-function task module corresponding to the sub-test task in the sub-function task library, calling the sub-function task module from the sub-function task library; If the sub-function task module corresponding to the sub-test task does not exist in the sub-function task library, a sub-function task module corresponding to the sub-test task is created, and the created sub-function task module is saved in the sub-function task library.

9. The onboard maintenance application software testing method according to claim 7, characterized in that: The scheduling management module adjusts the execution order of the sub-function task modules in the task queue based on the triggered round-robin scheduling strategy, specifically including: Detect whether there is a newly added sub-function task module in the task queue; Determine whether the priority of the newly added sub-function task module is higher than the original sub-function task module in the task queue; If the priority of the newly added sub-function task module is higher than that of the original sub-function task module in the task queue, determining whether the original sub-function task module is in an execution state; If the original sub-function task module is not in execution state, the newly added sub-function task module is adjusted to the front of the original sub-function task module; If the original sub-function task module is in the execution state, the newly added sub-function task module is adjusted to behind the original sub-function task module.

10. The onboard maintenance application software testing method according to claim 7, characterized in that: Also includes: The data generated when the sub-function task module is executed is transmitted to the integrated display module, and the test execution result and task status when the sub-function task module is executed are displayed in real time through the integrated display module.

Images