Satellite comprehensive test scheme automatic test method, medium and electronic equipment

Through automated testing methods, satellite test cases are retrieved and executed cycles, solving the problem of low satellite testing efficiency in the existing technology, and achieving an efficient and automated satellite testing process.

CN119473871APending Publication Date: 2025-02-18SHANGHAI GUOXING ZHILIAN AEROSPACE TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411401987.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-09
Publication Date
2025-02-18

AI Technical Summary

Technical Problem

In the prior art, satellite testing efficiency is low, especially when the number of commands and the number of whole-satellite testing tasks is large, a large amount of manpower is required.

Method used

Provide an automated test method for satellite comprehensive testing schemes. By judging whether there are test cases in the test scheme table, recyclely retrieve and execute test cases, obtain test results and generate test reports, and realize the automation of satellite tests.

Benefits of technology

It improves the efficiency of satellite testing, reduces labor costs, can quickly execute a large number of satellite test cases, and generates detailed test reports.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119473871A_ABST
    Figure CN119473871A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses an automatic test method for a satellite comprehensive test scheme, a medium and electronic equipment, relates to the technical field of satellite test, and aims to solve the problem of low satellite test efficiency in a satellite development process in the prior art. According to the method, the satellite test is automatically carried out by circularly reading the test cases in the test scheme table, firstly, whether the test cases exist in the test scheme table or not is judged, the test cases are called from the test scheme table one by one for execution under the condition that the test cases exist in the test scheme table, and when one test case is executed, the satellite test is automatically carried out. According to the method, whether the test cases exist in the test scheme table or not is judged, after all the test cases are executed, the test report is automatically generated finally according to the test results of the test cases, rapid execution of a large number of satellite test cases can be achieved, and the test efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of satellite testing technology, and in particular to an automated testing method, medium and electronic equipment for a satellite comprehensive testing solution. Background Art

[0002] Traditional satellite testing uses manual sending of test commands and manual reading of telemetry data to determine whether the commands are executed successfully. For satellite testing with few commands and a small amount of tests, the work efficiency is barely acceptable. However, for satellite testing with a large amount of commands and many tasks for the entire satellite test, especially when multiple satellites are tested simultaneously, manual sending of test command sequences and manual interpretation of telemetry are not only inefficient, but also require a large number of testers. How to improve test efficiency and reduce labor costs is an urgent problem that the satellite development industry needs to solve. Summary of the invention

[0003] The main purpose of this application is to provide an automated testing method, medium and electronic equipment for a satellite comprehensive testing solution, aiming to solve the problem of low testing efficiency of satellites during the satellite development process in the prior art.

[0004] To achieve the above objectives, the technical solutions adopted in the embodiments of the present application are as follows:

[0005] In a first aspect, an embodiment of the present application provides an automated testing method for a satellite integrated testing solution, comprising the following steps:

[0006] Determine whether there are test cases in the test plan table;

[0007] If the result of the judgment is yes, the target test case is retrieved from the test plan table and executed to obtain the test result of the target test case; wherein the target test case is any test case in the test plan table;

[0008] Update the test plan table and return to the step of determining whether there is a test case in the test plan table until the result of the determination is no, and generate a test report based on the test result of the target test case.

[0009] In a possible implementation manner of the first aspect, before determining whether there is a test case in the test plan table, the satellite integrated test plan automated testing method further includes:

[0010] Build test cases according to task requirements;

[0011] Generate a test plan table based on the test cases.

[0012] In a possible implementation of the first aspect, constructing a test case according to task requirements includes:

[0013] According to the task requirements, the use case construction parameters are obtained; wherein the use case construction parameters include at least one of a precondition, an expected value of at least one telemetry indicator, a failure strategy, a timeout, an interval, and an execution completion strategy;

[0014] Build test cases based on the use case construction parameters.

[0015] In a possible implementation of the first aspect, retrieving a target test case from a test plan table and executing the target test case to obtain a test result of the target test case includes:

[0016] Retrieve the target test case from the test plan table and wait for the interval time;

[0017] According to the judgment result of whether the precondition exists and whether the precondition is satisfied, the target test case is executed to obtain the test result of the target test case.

[0018] In a possible implementation manner of the first aspect, executing a target test case includes:

[0019] Determine whether to configure the expected value of the telemetry indicator;

[0020] If the result of the judgment is yes, the actual measured value of the telemetry indicator is obtained;

[0021] When the return time does not exceed the timeout period, determine whether the expected value is equal to the measured value;

[0022] If the result of the judgment is not equal, update the measured value and the return time, and return to the step of judging whether the expected value is equal to the measured value when the return time does not exceed the timeout time, until the return time exceeds the timeout time or the measured value is equal to the expected value, and obtain the test result of the target test case.

[0023] In a possible implementation of the first aspect, the use case construction parameters also include test instructions, which are used to send to the satellite so that the satellite executes the test instructions and returns the measured value of the telemetry indicator.

[0024] In a possible implementation of the first aspect, the measured value of the telemetry indicator is stored in a dictionary data structure, where the dictionary key is the telemetry name, and the dictionary value is the measured value of the telemetry indicator.

[0025] In a possible implementation of the first aspect, after retrieving and executing a target test case from the test plan table and obtaining a test result of the target test case, the satellite integrated test plan automated testing method further includes:

[0026] According to the test result of the target test case, at least one of the failure strategy and the completion strategy is executed to exit or continue the test.

[0027] In a second aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program. When the computer program is loaded and executed by a processor, an automated testing method for a satellite integrated measurement scheme as provided in any one of the first aspects above is implemented.

[0028] In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory, wherein:

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

[0030] The processor is used to load and execute a computer program so that the electronic device executes an automated testing method for a satellite integrated measurement solution as provided in any one of the first aspects above.

[0031] Compared with the prior art, the beneficial effects of this application are:

[0032] The satellite comprehensive test scheme automation test method, medium and electronic device proposed in the embodiment of the present application include: judging whether there is a test case in the test scheme table; when the result of the judgment is yes, calling the target test case from the test scheme table and executing it to obtain the test result of the target test case; wherein the target test case is any test case in the test scheme table; updating the test scheme table and returning to the step of judging whether there is a test case in the test scheme table, until the result of the judgment is no, generating a test report according to the test result of the target test case. The present application realizes the automatic satellite test by cyclically reading the test cases in the test scheme table, firstly judging whether there is a test case in the test scheme table, calling the test cases one by one from the test scheme table to execute if there is a test case, judging whether there is any test case in the test scheme table once each time a test case is executed, and finally automatically generating a test report according to the test result of the test case after all the test cases are executed, which can realize the rapid execution of a large number of satellite test cases and improve the test efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A schematic diagram of a flow chart of an automated testing method for a satellite integrated testing solution provided in an embodiment of the present application;

[0034] Figure 2 A schematic diagram of a flow chart of an automated testing method for a satellite integrated testing solution provided in an embodiment of the present application in one implementation manner;

[0035] Figure 3 A schematic diagram of a flow chart of executing a single test case in the automated test method for the satellite integrated test solution provided in an embodiment of the present application;

[0036] Figure 4 A schematic diagram of the information flow of the satellite comprehensive test solution automation test platform provided in the embodiment of the present application; DETAILED DESCRIPTION

[0037] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0038] The method of the embodiment of the present application can be executed in a program-based electronic device. The electronic device may include a processor, a storage medium, etc. The storage medium is used to store the program for executing the method of the present embodiment, and the processor is used to load and execute the computer program. The processor calls the virtual device stored in the memory and executes the satellite comprehensive measurement scheme automated testing method provided in the embodiment of the present application.

[0039] See attached Figure 1 Based on the hardware device of the foregoing embodiment, the embodiment of the present application provides an automated testing method for a satellite integrated test solution, comprising the following steps:

[0040] S10: Construct test cases according to task requirements.

[0041] In the specific implementation process, the mission requirements are determined according to certain functions or instructions of the satellite to be tested. One or more test cases are required according to the mission requirements. For example, two test cases are required to test whether the safety power switch instruction on the satellite is effective. In order to improve the test coverage and effectively handle various situations that may occur during satellite testing, the properties of the test cases are further designed. Specifically: According to the mission requirements, test cases are constructed, including:

[0042] According to the task requirements, the use case construction parameters are obtained; wherein the use case construction parameters include at least one of a precondition, an expected value of at least one telemetry indicator, a failure strategy, a timeout, an interval, and an execution completion strategy;

[0043] Build test cases based on the use case construction parameters.

[0044] In the specific implementation process, the use case construction parameters are the parameters required to build a test case, which may include basic properties, preconditions, expectations, and error messages. The basic properties and their descriptions are as follows:

[0045] Use case ID: represents the use case ID, which is an integer type and is the unique identifier of the use case in the same test suite and cannot be repeated.

[0046] Use Case Name: Use case name, repeatable.

[0047] Instruction number: The instruction number corresponding to the instruction to be executed by the use case.

[0048] Failure strategy: The strategy after the use case execution fails, which may include: ① Not set: This item is not selectable and is reserved for program design; ② Exit test: It means exiting the entire automated test and no longer executing subsequent use cases; ③ Continue: Continue to execute subsequent use cases; ④ Pause: The program pauses here and waits for the user to click Stop or continue to execute subsequent use cases.

[0049] Timeout: The maximum waiting time for the use case to pass, in seconds; if the use case assertion returns true within this time range after the instruction is sent, the use case passes, otherwise the use case fails.

[0050] Interval time: The time to wait when executing this use case, in seconds.

[0051] The prerequisites and their descriptions are as follows:

[0052] Parameter name: unique identifier of the parameter, globally unique in the "prefix" and "postfix", cannot be repeated, and can be referenced in both the "prefix expression" and the "expected value expression".

[0053] Telemetry physical value type: identifies the type of telemetry physical value, such as int (4-byte integer), long (8-byte integer), fl oat (4-byte floating point number), double (8-byte floating point number), str (string type). If you are not sure about the telemetry physical value type of non-string type, select double if it is a decimal, and select long if it is an integer.

[0054] Processed physical value: This value is invalid in the actual use case execution and is only used for the "test expression" function.

[0055] Prefix expression: ① If this item is not empty, this expression will be executed before executing the instruction. If the expression is not true, the instruction associated with this use case will not be sent, and the execution result of this use case will be set to failure; if the expression is true, the instruction associated with this use case will be sent and enter the subsequent process; ② At least one of the "prefix expression" and "expected value expression" must be not empty, otherwise the new test case will fail.

[0056] Test expression: used to verify whether the input expression has syntax errors. You can test the correctness of the expression by modifying the processed physical value corresponding to the referenced parameter in the expression. For example: parameter name: a, telemetry physical value type: double, processed physical value: 100; pre-expression: a.phy=101. Click "Test expression" and "xxxxx expression is not true" will be output in the "Message list".

[0057] The expected items and their descriptions are as follows:

[0058] ① The parameters are consistent with the preceding items. If there is an expected value expression, the expected value expression result will be calculated after the instruction is executed; if the expected value expression is not filled in, the expected value expression result will not be calculated;

[0059] ② The expected value expression can reference the parameters in the preceding expression, but the parameters in the preceding item will not be automatically prompted in the expected value expression input box;

[0060] ③ Example of expected item referencing the preceding item:

[0061] Instruction C0, but there is no telemetry available for this instruction. It can only be judged by checking whether the count of receiving instructions by the satellite service is increased by 1. Therefore, the following use case can be designed:

[0062] Instruction number: C0;

[0063] Pre-item parameters: a, telemetry name: satellite service receiving command count, telemetry physical value type: i nt;

[0064] Expected item parameters: b, telemetry name: satellite service receiving command count, telemetry physical value type: i nt;

[0065] Expected value expression: b.phy=a.phy+1.

[0066] The error message description is as follows:

[0067] Indicates the error information of the use case itself. If there is error information, the use case cannot be executed and the user needs to check the relevant errors and make modifications.

[0068] Once the test case construction parameters required by the test case are determined, the test case can be constructed.

[0069] Preconditions, i.e. precondition parameters, are in JSON format and are defined as follows:

[0070] key: parameter name, such as "key": "a", the parameter name is a. The purpose is to make a name and telemetry name mapping. The corresponding telemetry can be queried through the name in name a.

[0071] name: the telemetry name associated with the parameter, such as "key": "a", "name": "Safety Power Supply On", which means that the telemetry name corresponding to parameter a is "Safety Power Supply On". Parameter a will be used later. To obtain the value in parameter a, you only need to use the name value in a as the search condition and pass it to the comprehensive testing server to query the telemetry data corresponding to a. After the query is completed, use the queried data to fill in other attributes of parameter a, such as phy, info, and code.

[0072] type: The data type of the telemetric physical value corresponding to the parameter, such as "type": "i nt", which means that the telemetric physical value type corresponding to the parameter is an integer type.

[0073] phy: The telemetry physical value corresponding to the parameter name.

[0074] code: The telemetry source code corresponding to the parameter name.

[0075] ifo: The telemetry display information corresponding to the parameter name.

[0076] S20: Generate a test plan table based on the test case.

[0077] In the specific implementation process, a test plan table contains one or more test cases. A test plan is usually a collection of related instructions. For example, to test whether the safety power switch instruction on the control satellite is effective, two instructions need to be sent, corresponding to the execution of two test cases. The following table 1 shows a test plan table:

[0078] Table 1 - Test plan table

[0079]

[0080]

[0081] In the above table, each row represents a test case, and each column represents a test case construction parameter in a test case.

[0082] S30: Determine whether there is a test case in the test plan table.

[0083] In the specific implementation process, since the method of cyclically calling test cases is adopted, it is necessary to determine whether there are test cases for execution in the test plan table. If there are no test cases, it can be divided into two situations. One situation is that the test case exists, but it has been called and executed. The other situation may be due to reasons such as the wrong file being given or the file being damaged, resulting in the initial test plan table being an empty table with no test cases in the table. In this case, the test can be directly terminated to generate the corresponding test report.

[0084] S40: If the result of the judgment is yes, retrieve the target test case from the test plan table and execute it to obtain the test result of the target test case; wherein the target test case is any test case in the test plan table.

[0085] In the specific implementation process, when calling test cases from the test plan table, only one test case is called for execution each time, and after the call, the test case needs to be excluded from the test plan table. The call can be a random call or can be called in a certain order. For example, according to the test plan table shown in Table 1 in the aforementioned embodiment, starting from the first test case, the existing test cases are called in sequence, that is, test case 1 is called for the first time, test case 2 is called the next time, and so on.

[0086] In one embodiment, retrieving a target test case from a test plan table and executing it to obtain a test result of the target test case includes:

[0087] Retrieve the target test case from the test plan table and wait for the interval time;

[0088] According to the judgment result of whether the precondition exists and whether the precondition is satisfied, the target test case is executed to obtain the test result of the target test case.

[0089] In the specific implementation process, the interval time is the time you need to wait before executing the test case. For example, if the interval time set for the retrieved test case 1 is 3 seconds, then you need to wait for 3 seconds before executing the test case. After starting the execution, you need to determine whether the precondition exists and whether the precondition is established, and then decide how to execute the test case based on the result of the determination.

[0090] There is a precondition in test case 1, and the precondition processing is as follows: the parameter name in the "precondition parameter" is a, the master control terminal initiates a query request to the comprehensive testing server, and queries the telemetry data corresponding to parameter a (the telemetry corresponding to the precondition parameter a of test case 1 is: safety power supply switch status) (on the comprehensive testing server, query the telemetry data with the telemetry name of "safety power supply switch status"). Here, the physical value (represented by phy in the test plan table) and display information (represented by i nfo in the test plan table) with the telemetry name of "safety power supply switch status" will actually be queried, and the actual telemetry data queried will be brought into the precondition expression: a.phy=0, that is, a.phy will be replaced with the physical value of the queried safety power supply switch status.

[0091] In one embodiment, executing a target test case includes:

[0092] Determine whether to configure the expected value of the telemetry indicator;

[0093] If the result of the judgment is yes, the actual measured value of the telemetry indicator is obtained;

[0094] When the return time does not exceed the timeout period, determine whether the expected value is equal to the measured value;

[0095] If the result of the judgment is not equal, update the measured value and the return time, and return to the step of judging whether the expected value is equal to the measured value when the return time does not exceed the timeout time, until the return time exceeds the timeout time or the measured value is equal to the expected value, and obtain the test result of the target test case.

[0096] In the specific implementation process, in the first case: if the result of the judgment on whether the precondition exists is no, and in the second case: if the result of the judgment on whether the precondition exists is yes, and the result of the judgment on whether the precondition is satisfied is yes, both cases can enter the normal test phase and start sending instructions for testing. The expected value of the telemetry indicator is used to compare with the measured value of the returned telemetry indicator to obtain the test result. If the expected value of the telemetry indicator does not need to be configured, the test can be completed directly. If configuration is required in the test case, the telemetry data, that is, the value of the measured telemetry indicator, can be obtained and compared with the configured expected value. If they are equal, the test is completed. If they are not equal, the measured value is updated in real time and then compared. However, it should be noted that the return time, that is, the time when the measured value of the current comparison is received, cannot be after the timeout time, that is, no comparison is performed after the timeout time, and the test can be considered completed.

[0097] The automatic comparison and judgment can be realized by designing the parameters as specific expressions. The expression parsing engine can be used for this. The logical operations supported by the expression are: &&, ||, >, <, >=, <=, !=, =, and the arithmetic operations supported include addition, subtraction, multiplication and division. The variables appearing in the expression are type-safe, that is, 1 and "1" represent different values. The former is an integer 1, and the latter is a string type 1. The former can participate in arithmetic operations and can get the expected value, while the latter cannot participate in arithmetic operations. In the platform, a telemetry data includes at least physical value (phy) and display information (i nfo). For example, if telemetry A is a variable a, then a.phy represents the physical value of telemetry A, and a info represents the display information of telemetry A. Therefore, the expression: a.phy=10&&a.info="communication is normal" means that the physical value of telemetry A is equal to 10 and the display information is "communication is normal", and the entire expression is valid.

[0098] For example, the designed test case fragment includes instruction Cmd001, the associated telemetry is a, the expected value is a.phy=100||ai nfo="communication is normal", and the timeout is 5 seconds. Then after the instruction Cmd001 is sent, the time is recorded as t0, the data of telemetry a is queried, and the value of a is substituted into the expression for calculation. If the expression is established, the test passes. If the expression is not established and the current time -t0≤5s, the value of telemetry a is queried again and substituted into the expression for calculation. If the expression is established, the test passes. If it fails and the current time -t0>5s, the value of telemetry a is no longer queried, the test fails, and the current case is executed.

[0099] In one embodiment, after the target test case is retrieved from the test plan table and executed, and the test result of the target test case is obtained, the satellite integrated test plan automated testing method further includes:

[0100] According to the test result of the target test case, at least one of the failure strategy and the completion strategy is executed to exit or continue the test.

[0101] In the specific implementation process, the execution failure strategy and the execution completion strategy are strategies used to control the continuation or exit of the test during the test process. For example, the physical value of the queried "safety power switch status" is 1. After the predicate expression is substituted, the predicate expression is: 1=0. If the predicate expression is not established, the failure strategy can be executed. By judging whether the predicate expression (i.e. a.phy=0) is established, if it is established, the instruction can be sent to continue the test. If it is not established, the failure strategy can be executed. It should be noted that the continued test here means continuing the test and pausing to wait for the resumption of the test, and does not completely exit the test.

[0102] S50: Update the test plan table and return to the step of determining whether there is a test case in the test plan table, until the result of the determination is no, and generate a test report according to the test result of the target test case.

[0103] In the specific implementation process, after a test case is retrieved from the test plan table and executed, the test case can be removed from the test plan table or configured as unrecognizable. It should be noted that whether there is a test case in the test plan table in this embodiment refers to whether there is an executable test case, which may be that there is no test case or that no available test case is identified. When there is no executable test case in the test plan table, a test report is generated in combination with the test results obtained in the above steps to realize the automated execution, judgment and processing of the execution results of the satellite test.

[0104] In this embodiment, the satellite test is automatically performed by cyclically reading the test cases in the test plan table. First, it is determined whether there is a test case in the test plan table. If so, the test cases are retrieved one by one from the test plan table for execution. After each test case is executed, it is determined whether there is any test case in the test plan table. After all the test cases are executed, a test report is automatically generated according to the test results of the test cases. This can achieve rapid execution of a large number of satellite test cases and improve test efficiency.

[0105] As attached Figure 4 As shown, the embodiment of the present application also provides a satellite comprehensive test solution automation test platform for implementing the method provided in the embodiment of the present application. The satellite comprehensive test solution automation test platform includes: a master control terminal, a comprehensive test server and a 422 serial port device, and its information flow is as shown in the attached Figure 4 As shown, the relevant instructions are sent to the satellite by the master control terminal, the integrated test server, and the 422 serial port device in sequence, and the telemetry data are sent to the master control terminal by the satellite, the 422 serial port device, and the integrated test server in sequence.

[0106] The 422 serial port device and the satellite computer on the satellite are directly connected using the 422 serial port to establish a bridge for data communication between the satellite and the outside world; the comprehensive measurement server: used to receive instructions sent by the master control terminal, and send the instructions to the satellite through the 422 serial port device. The instructions are handed over to the satellite computer on the satellite for execution. At the same time, the comprehensive measurement server is also responsible for receiving the telemetry data returned by the satellite. When the comprehensive measurement server stores telemetry data, it stores the telemetry data in the data structure of a dictionary. A dictionary is a data structure that stores structures in the form of key-value pairs. The telemetry name is used as the dictionary key, and the telemetry data is used as the dictionary value, which greatly improves the efficiency of telemetry data retrieval. That is, the measured value of the telemetry indicator is stored in the data structure of the dictionary. The dictionary key of the dictionary is the telemetry name, and the dictionary value is the measured value of the telemetry indicator.

[0107] The master control terminal is responsible for instruction management, test case management, test case execution and test result analysis. Each test case contains an instruction to be tested, and each instruction is associated with one or more telemetry indicators. When the master control terminal executes a test case, it first sends the instruction in the case to the comprehensive testing server. The comprehensive testing server forwards the instruction to the satellite. The satellite computer on the satellite receives the instruction and sends it to the corresponding subsystem. The instruction is finally executed on the subsystem; then the master control terminal waits for a few seconds (the waiting time for each test case is configurable). During the waiting time, the master control terminal will continuously query the telemetry information associated with the instruction from the comprehensive testing server, that is, the case construction parameters also include test instructions, which are used to send to the satellite so that the satellite executes the test instruction and returns the actual measured value of the telemetry indicator.

[0108] The instruction data is saved in an Excel file. When executing each test case, the instruction data is searched in the instruction data file through the instruction number in the test case, thus avoiding the coupling between the instruction data and the test case. If the actual telemetry value obtained during the waiting time is the same as the expected telemetry value in the case configuration, the waiting ends early and the instruction test passes. Otherwise, the instruction test fails, that is, the case execution fails. Finally, the case execution results are saved, a test report is generated, and the automated test is completed.

[0109] In the attached Figure 2 , Attachment Figure 3 The present application is further described below in the following embodiments:

[0110] After the satellite test mission begins, first obtain the test plan table and determine whether there is a test case. If there is a test case, take out a test case and enter the following Figure 3 The execution flow of a single test case is shown below:

[0111] After the test task of a single test case starts, the test case is read. If the execution waiting time is configured, the test starts after waiting for the same length of time. First, it is determined whether the precondition exists and whether the precondition is established. Figure 3 The judgment situations shown execute different test processes. The test case 1 in Table 1 selected in the aforementioned embodiment is used to continue the explanation. When the sending instruction can be executed, the instruction data corresponding to the instruction number in the sending case is sent to the server. The master control terminal searches for the instruction data in the local instruction file through the "instruction number" (ie: 001) in the test case 1 (the instruction data is a string of binary sequences), and sends the instruction data corresponding to the instruction number 001 to the comprehensive testing server. The comprehensive testing server transmits the instruction data to the 422 serial port device, and the 422 serial port device sends the instruction data to the satellite. The master control terminal records the current time as t0 for use in timeout judgment.

[0112] After sending the instruction, the step of whether to configure the expected value is entered. If the expected value expression exists, it is processed according to the expected value processing flow. The processing flow has been described in detail in the previous embodiment and will not be repeated here. If the expected value expression is not established, the failure strategy is entered; determine whether the expected value expression is established. If it is established, the use case execution is passed and the execution completion strategy is entered; if it is not established and the current time - t0 <= 5s (the use case has not passed and has not timed out), the current time is updated and the measured value continues to be received; if it is not established and the current time - t0> 5s (the use case has not passed and has timed out), the failure strategy is entered.

[0113] The master control terminal executes the "execution completion strategy". If the "execution completion strategy" is "exit test", a test report corresponding to the current test plan is generated, and the task is terminated after the generation is completed. If the "execution completion strategy" is "pause", it waits for the user to "continue or exit". If the user chooses "continue", the next test case is executed. If the user chooses "exit", the task is terminated directly.

[0114] The master control terminal handles the problem according to the execution failure strategy. If the "failure strategy" is "pause", the automated execution will be paused and wait for the user to "exit or continue". If the user chooses "exit", the task will be ended directly. If the user chooses "continue", the execution completion strategy will be entered and handled according to the execution completion strategy. If the "failure strategy" is "continue", the execution completion strategy will be handled. If the "failure strategy" is "exit test", the test report corresponding to the current test plan will be generated, and the task will be ended after the generation is completed.

[0115] After executing the completion strategy and executing the failure strategy, the test of a single test case is completed and the process returns to the step of determining whether there is a test case in the test plan table. If there is a next test case, the test process of the aforementioned single test case is continued until there is no test case in the test plan. Then, a test report is generated and the entire satellite test mission is ended.

[0116] Based on the same inventive concept as in the aforementioned embodiments, an embodiment of the present application further provides a computer-readable storage medium storing a computer program. When the computer program is loaded and executed by a processor, an automated testing method for a satellite integrated measurement scheme as provided in an embodiment of the present application is implemented.

[0117] Based on the same inventive concept as in the above-mentioned embodiment, an embodiment of the present application further provides an electronic device, including a processor and a memory, wherein:

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

[0119] The processor is used to load and execute a computer program so that the electronic device executes an automated testing method for a satellite integrated measurement solution as provided in an embodiment of the present application.

[0120] In some embodiments, the computer readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or various devices including one or any combination of the above memories. The computer may be various computing devices including intelligent terminals and servers.

[0121] In some embodiments, executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0122] As an example, executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file that stores other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions).

[0123] By way of example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

[0124] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0125] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0126] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory / random access memory, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a multimedia terminal device (which can be a mobile phone, a computer, a television receiver, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0127] In summary, the present application provides a satellite comprehensive test scheme automation test method, medium and electronic device, the method comprising: judging whether there is a test case in the test scheme table; when the result of the judgment is yes, calling the target test case from the test scheme table and executing it to obtain the test result of the target test case; wherein the target test case is any test case in the test scheme table; updating the test scheme table and returning to the step of judging whether there is a test case in the test scheme table, until the result of the judgment is no, generating a test report according to the test result of the target test case. The present application realizes the automatic satellite test by cyclically reading the test cases in the test scheme table, first judging whether there is a test case in the test scheme table, calling the test cases one by one from the test scheme table to execute if there is a test case, judging whether there is a test case in the test scheme table once each time a test case is executed, and finally automatically generating a test report according to the test result of the test case after all the test cases are executed, which can realize the rapid execution of a large number of satellite test cases and improve the test efficiency.

[0128] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. The automated testing method for satellite integrated testing scheme is characterized by: The following steps are involved: Determine whether there are test cases in the test plan table; If the result of the judgment is yes, retrieve the target test case from the test plan table and execute it to obtain the test result of the target test case; wherein the target test case is any one of the test cases in the test plan table; The test plan table is updated and the step of determining whether a test case exists in the test plan table is returned until the determination result is no, and a test report is generated according to the test result of the target test case.

2. The satellite integrated measurement scheme automated testing method according to claim 1, characterized in that: Before determining whether there is a test case in the test scheme table, the satellite integrated test scheme automated testing method further includes: Construct the test case according to the task requirements; Based on the test case, the test plan table is generated.

3. The satellite integrated measurement scheme automated testing method according to claim 2, characterized in that: The test case is constructed according to the task requirements, including: According to the task requirements, the use case construction parameters are obtained; wherein the use case construction parameters include at least one of a precondition, an expected value of at least one telemetry indicator, a failure strategy, a timeout, an interval, and an execution completion strategy; Construct the test case according to the test case construction parameters.

4. The satellite integrated measurement program automated testing method according to claim 3, characterized in that: The step of retrieving a target test case from the test plan table and executing the test case to obtain a test result of the target test case includes: Retrieve the target test case from the test plan table and wait for the interval time; According to the judgment result of whether the precondition exists and the judgment result of whether the precondition is satisfied, the target test case is executed to obtain the test result of the target test case.

5. The satellite integrated measurement program automated testing method according to claim 4, characterized in that: The executing the target test case comprises: Determining whether to configure the expected value of the telemetry indicator; If the result of the judgment is yes, obtaining the actual measured value of the telemetry indicator; In the case where the return time does not exceed the timeout time, determining whether the expected value is equal to the measured value; If the judgment result is not equal, update the measured value and the return time, and return to the step of judging whether the expected value is equal to the measured value when the return time does not exceed the timeout time, until the return time exceeds the timeout time or the measured value is equal to the expected value, to obtain the test result of the target test case.

6. The satellite integrated measurement program automated testing method according to claim 5, characterized in that: The use case construction parameters also include test instructions, which are used to be sent to a satellite so that the satellite executes the test instructions and returns the measured value of the telemetry indicator.

7. The satellite integrated measurement program automated testing method according to claim 5, characterized in that: The measured values ​​of the telemetry indicators are stored in a dictionary data structure, the dictionary key of the dictionary is the telemetry name, and the value of the dictionary is the measured value of the telemetry indicator.

8. The satellite integrated measurement program automated testing method according to claim 3, characterized in that: After retrieving the target test case from the test scheme table and executing it to obtain the test result of the target test case, the satellite integrated test scheme automated testing method further includes: According to the test result of the target test case, at least one of the failure strategy and the execution completion strategy is executed to exit or continue the test.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is loaded and executed by the processor, the automated testing method for the satellite integrated measurement scheme as described in any one of claims 1 to 8 is implemented.

10. An electronic device, characterized in that: comprising a processor and a memory, wherein: The memory is used to store computer programs; The processor is used to load and execute the computer program so that the electronic device performs the automated testing method for the satellite integrated measurement scheme as described in any one of claims 1-8.