Signal interface test method and system based on configuration table

Abstract

The invention discloses a signal interface test method and system based on a configuration table. The method comprises the steps of performing normalization design on a signal interface function test design script and an execution script; a component test framework is adopted for the test case, and the component test framework is automatically constructed through source codes; automatically executing an execution record generated by result analysis, if the function realized by the control code is consistent with the data requirement in the IO configuration table, passing the use case, otherwise, not passing the use case; analyzing the problem, and then carrying out iteration again until all the use cases pass the operation; the system comprises a signal interface module, a test framework module, an execution recording module and an iteration module. The efficiency is improved, and the speed is increased by more than ten times compared with manual testing; testing is sufficient, closed-loop data is achieved, detailed test case execution results are automatically generated, and rapid defect positioning is assisted; the cost is optimized, the labor hour is reduced, the automation of the test process is realized in continuous integration, and the product iteration is accelerated.

Description

Technical Field

[0001] This invention relates to the field of aero-engine control software, and in particular to a signal interface testing method and system based on a configuration table. Background Technology

[0002] As the core control unit of the power system, the gas turbine controller (ECU) requires its software to process input signals from sensors (such as the gas turbine inlet total temperature and lubricating oil temperature) in real time and generate precise actuator control commands through algorithms. Among these, the signal interface processing function is a key module for ensuring control accuracy, involving functions such as BIT fault diagnosis, signal calibration, signal extreme value diagnosis, signal slope diagnosis, and signal filtering. Based on testing standards such as "GB_T 25000.51 2016 Quality Requirements and Test Details for Ready and Usable Software Products (RUSP)" and "TE-BTCG-003 2021 Military Software Testing Guidelines," the testing of the signal interface processing function generally adopts equivalence class and boundary value testing methods. Currently, manual testing is commonly used, which has significant limitations: firstly, the test coverage is low, making it difficult to cover many scenarios; secondly, it relies on human experience and judgment, which is prone to subjective errors leading to leakage; and finally, the testing efficiency is low, with repetitive tasks being time-consuming and difficult to automate. Therefore, it is necessary to design a new configuration table-based signal interface testing method to solve the above problems. Summary of the Invention

[0003] Purpose of the invention: The purpose of this invention is to provide a signal interface testing method and system based on a configuration table.

[0004] Technical solution: The signal interface testing method based on configuration table described in this invention includes the following steps:

[0005] S1. Standardized design of signal interface function test design scripts and execution scripts;

[0006] S2. Use a component testing framework for test cases, and automatically build the component testing framework from the source code;

[0007] S3. If the execution record generated by the automated execution and result analysis is consistent with the data requirements in the IO configuration table, the test case passes; otherwise, it fails.

[0008] S4. Analyze the problem, then iterate again until all test cases pass.

[0009] Furthermore, the carrier of the standardized test design script in step S1 is an Excel spreadsheet. The signal function configuration table includes channel ID, whether it is mapped, extreme value mode, extreme minimum value, extreme maximum value, extreme value determination time, extreme value recovery time, slope function related information, BIT function related information, filtering function related information, and calibration curve.

[0010] Furthermore, the process of generating the test design document in step S1 includes:

[0011] S11, Calibration function, located on the "Calibration" sheet in Excel;

[0012] S12, BIT function, is located on the "bit" sheet in Excel;

[0013] S13, Extreme Values ​​function, located on the "Extreme Values" sheet in Excel;

[0014] S14, Filtering function, located on the "Filter" sheet in Excel.

[0015] Further, step S2 includes:

[0016] S21. Initialize the environment, create a new working directory Workplace, and uniformly deploy the project files and environment configurations required for the component testing environment;

[0017] S22. Load the software under test and load the control code into the corresponding location in the working directory;

[0018] S23. Automatic instrumentation of control code: The component testing environment requires special processing of related code in the control code, such as deleting unnecessary files, removing unrecognized files, and redefining referenced external variables.

[0019] Further, step S3 includes:

[0020] S31. Execute SuiteSetUp to open the test case Excel document;

[0021] S32. Execute the TestSuite function;

[0022] S33. Execute the CaseSetUp function; when performing component testing, if the SetupIfCaseBegine function determines that the current behavior is the start of a test case, then the CaseSetUp function is executed.

[0023] S34. Call the CaseSetUpCmd function to execute the "initialization and constraint" statements of the test case;

[0024] S35. Execute the CaseTearDown function; When performing component testing, if the TearDownIfCaseEnd function determines that the current behavior marks the end of a test case, the CaseTearDown function will be executed.

[0025] S36. Execute SuiteTearDown to close the currently open Excel document.

[0026] The signal interface testing system based on a configuration table according to the present invention includes:

[0027] The signal interface module is used for test design scripts and execution script standardization design.

[0028] The test framework module is used to apply a component test framework to test cases and automatically build the component test framework from the source code.

[0029] The execution log module is used to automatically execute and analyze the generated execution logs. If the function implemented by the control code is consistent with the data requirements in the IO configuration table, the test case passes; otherwise, it fails.

[0030] The iteration module is used to analyze the problem and iterate again until all test cases have passed.

[0031] Beneficial effects: Compared with the prior art, the present invention has the following significant advantages: The present invention improves efficiency, speeding up testing by more than ten times compared with manual testing; it provides thorough testing by using the function point processing paradigm to fully test the signal interface functions, meeting the testing requirements of equivalence classes and boundary values; it provides data closure by automatically generating detailed test case execution results to assist in quickly locating defects; and it optimizes costs by reducing manual labor hours, automating the testing process in continuous integration, and accelerating product iteration. Attached Figure Description

[0032] Figure 1 This invention defines the sheet page;

[0033] Figure 2 This is the BIT use case design page for this invention;

[0034] Figure 3 This is the page for designing extreme use cases for this invention;

[0035] Figure 4 This is the page for designing filter use cases for this invention;

[0036] Figure 5 This is a diagram illustrating the implementation process of signal interface testing based on a configuration table. Detailed Implementation

[0037] The technical solution of the present invention will be further described below with reference to the accompanying drawings.

[0038] This application extracts and summarizes the functions of the gas turbine signal interface, adopts a function point processing paradigm + component automated testing framework, and automatically generates test cases and test execution scripts based on signal type and function configuration item table. These are then executed within the automated testing framework, generating detailed test execution records, thereby achieving automated verification of the signal interface functions. The process mainly consists of three steps.

[0039] S1. Standardized design of signal interface functional test design scripts and execution scripts.

[0040] The standardized test design script is presented using Microsoft Office's Excel spreadsheet. A specific signal is used as an example to illustrate the standardized design process in detail. Other signals are processed using a similar method.

[0041] The signal function configuration table (hereinafter referred to as the "IO configuration table") includes channel ID, mapping status, extreme value mode, minimum extreme value, maximum extreme value, extreme value determination time, extreme value recovery time, slope function related information, BIT function related information, filtering function related information, and calibration curves. All expected data for the corresponding function can be obtained through the IO configuration table. Based on this, a data-driven approach is adopted to generate standardized test design documents using the data in the configuration table. The generation process is as follows:

[0042] S11, Calibration function, located on the "Calibration" sheet in Excel.

[0043] The calibration curve for the gas turbine inlet temperature 1 is shown in the IO configuration table as follows:

[0044] 1770,5634,9426,13162,16778,20338,23789,27184,30513,32484,32766 :-50,0,50,100,150,

[0045] 200, 250, 300, 350, 380, 383, meaning there are 11 points on the X-axis and 11 points on the Y-axis. When designing test cases, it's necessary to set the input calibration code values ​​outside the two endpoints, taking the values ​​from both endpoints, and also covering the values ​​at all calibration points. Based on this, configuration table data is retrieved using a tool, and a template is used to design, for example... Figure 1 As shown.

[0046] S12, the BIT function, is located on the "bit" sheet in Excel.

[0047] The IO configuration table shows that the BIT diagnostic mode for gas turbine inlet temperature 1 is BIT_TWO, with a value of [0, 31128], a fault confirmation cycle of 5, and a recovery cycle of 10. When designing use cases, the repeated establishment and clearing of the gas turbine inlet temperature 1 BIT fault needs to be considered. Various boundary values ​​need to be used when designing the threshold. Based on this, configuration table data is captured using a tool, and a template is used to design, for example... Figure 2 As shown.

[0048] S13, Extreme Values ​​function, located on the "Extreme Values" sheet in Excel.

[0049] The IO configuration table shows that the BIT diagnostic mode for gas turbine inlet temperature 1 is EX_BIT_TWO, with a value of [-50, 350], a fault confirmation cycle of 5, and a recovery cycle of 10. When designing use cases, the repeated establishment and clearing of extreme faults in gas turbine inlet temperature 1 needs to be considered. Various boundary values ​​need to be used when designing thresholds. Based on this, configuration table data is retrieved using tools, and a template is used to design, for example... Figure 3 As shown.

[0050] S14. Filtering function, located on the "Filter" sheet in Excel.

[0051] The IO configuration table shows that the filtering mode for the gas turbine inlet temperature 1 is inertial filtering, with a filtering coefficient of 0.2. When designing test cases, filtering should not be performed if the filtering condition for gas turbine inlet temperature 1 is not met; instead, it should be calculated according to the corresponding filtering formula when the filtering condition is met. Based on this, the configuration table data is retrieved using a tool, and a test case is designed according to a template, for example... Figure 4 As shown.

[0052] The above explanation focuses on one signal; other signals are processed using a similar method. By reading the IO configuration table information and based on the pre-designed test case paradigm, all test design scripts are generated in batches. This invention employs a component testing framework, requiring the design of test execution scripts to call all test design files, run the corresponding control code, and compare the actual results with the expected results to test whether the functionality has been implemented. This explanation uses the test execution script for the calibration function as an example; other functions use similar processing methods, differing only in variable names, function names, and calling files.

[0053] Input file: Test case design file for calibration function

[0054] Input variable: XX1, which is the variable mapped to the acquired code value of the signal.

[0055] Function processing function: XX(); Function to control the software to implement calibration.

[0056] Output variable: XX2, which is the actual calibrated value, used to compare with the expected data in the design file.

[0057] The function format for executing the script is as follows:

[0058] void IC_EM_CHAN_000::TestSuite_Sheet1()

[0059] {

[0060] LoadEcxelSheet("calibration");

[0061] Input signal data acquisition;

[0062] Obtain the expected value;

[0063] Call the function handling procedure and perform a comparison;

[0064] Print detailed execution results;

[0065] }

[0066] S2, Automated Construction of Component Testing Environment

[0067] The component testing framework is used for test cases. The automatic construction of the component testing framework through source code mainly involves three processes.

[0068] S21. Initialize the environment, create a new working directory Workplace, and uniformly deploy the project files and environment configurations required for the component testing environment;

[0069] S22. Load the software under test and load the control code into the corresponding location in the working directory;

[0070] S23. Automatic instrumentation of control code: The component testing environment requires special processing of related code in the control code, such as deleting unnecessary files, removing unrecognized files, and redefining referenced external variables.

[0071] S3, Automated Construction of Component Testing Environment

[0072] After the standardized test design scripts, execution scripts, and component testing environment are built, the final step is automated execution and result analysis. The execution sequence of the component testing framework is as follows:

[0073] S31. Execute SuiteSetUp to open the test case Excel document;

[0074] S32. Execute the TestSuite function (e.g., TestSuite_Sheet1);

[0075] S33. Execute the CaseSetUp function. When performing component testing, if the SetupIfCaseBegine function determines that the current behavior is the start of a test case, the CaseSetUp function will be executed.

[0076] S34. Call the CaseSetUpCmd function to execute the "initialization and constraint" statements of the test case.

[0077] S35. Execute the CaseTearDown function. When performing component testing, if the TearDownIfCaseEnd function determines that the current behavior marks the end of a test case, the CaseTearDown function will be executed.

[0078] S36. Execute SuiteTearDown to close the currently open Excel document;

[0079] If the generated execution logs show that the functionality implemented by the control code matches the data requirements in the IO configuration table, the test case passes; otherwise, it fails. It is necessary to analyze whether the issue is a system requirement problem or a code problem, and then iterate again until all test cases pass or additional explanations are provided.

[0080] The signal interface testing process based on the configuration table is as follows: Figure 5 As shown.

[0081] Step 1: Select the project directory and corresponding project configuration table where the control software under test is located;

[0082] Step 2, click "Test Verification", which mainly involves the following three processes:

[0083] 1) Based on the IO function configuration table and script conversion tool, generate test design scripts and test execution scripts according to the corresponding paradigms. For details of the conversion process, please refer to the invention content.

[0084] 2) Automatically construct the component testing framework environment based on the software under test;

[0085] 3) Through the component testing framework, batch execution of the execution scripts is realized, and component test execution records are generated and the execution results are analyzed. For details of the execution process, please refer to the invention content.

[0086] Step 3: View the detailed results and take the next step based on the execution information.

[0087] The signal interface testing system based on a configuration table according to the present invention includes:

[0088] The signal interface module is used for test design scripts and execution script standardization design.

[0089] The test framework module is used to apply a component test framework to test cases and automatically build the component test framework from the source code.

[0090] The execution log module is used to automatically execute and analyze the generated execution logs. If the function implemented by the control code is consistent with the data requirements in the IO configuration table, the test case passes; otherwise, it fails.

[0091] The iteration module is used to analyze the problem and iterate again until all test cases have passed.

Claims

1. A signal interface testing method based on a configuration table, characterized in that, Includes the following steps: S1. Standardized design of signal interface function test design scripts and execution scripts; S2. Use a component testing framework for test cases, and automatically build the component testing framework from the source code; S3. If the execution record generated by the automated execution and result analysis is consistent with the data requirements in the IO configuration table, the test case passes; otherwise, it fails. S4. Analyze the problem, then iterate again until all test cases pass.

2. The signal interface testing method based on a configuration table according to claim 1, characterized in that, The standardized test design script in step S1 is carried out using an Excel spreadsheet. The signal function configuration table includes channel ID, whether it is mapped, extreme value mode, minimum extreme value, maximum extreme value, extreme value determination time, extreme value recovery time, slope function related information, BIT function related information, filtering function related information, and calibration curve.

3. The signal interface testing method based on a configuration table according to claim 1, characterized in that, The process of generating the test design file in step S1 includes: S11, Calibration function, located on the "Calibration" sheet in Excel; S12, BIT function, is located on the "bit" sheet in Excel; S13, Extreme Values ​​function, located on the "Extreme Values" sheet in Excel; S14, Filtering function, located on the "Filter" sheet in Excel.

4. The signal interface testing method based on a configuration table according to claim 1, characterized in that, Step S2 includes: S21. Initialize the environment, create a new working directory Workplace, and uniformly deploy the project files and environment configurations required for the component testing environment; S22. Load the software under test and load the control code into the corresponding location in the working directory; S23. Automatic instrumentation of control code: The component testing environment requires special processing of related code in the control code, such as deleting unnecessary files, removing unrecognized files, and redefining referenced external variables.

5. The signal interface testing method based on a configuration table according to claim 1, characterized in that, Step S3 includes: S31. Execute SuiteSetUp to open the test case Excel document; S32. Execute the TestSuite function; S33. Execute the CaseSetUp function; when performing component testing, if the SetupIfCaseBegine function determines that the current behavior is the start of a test case, then the CaseSetUp function is executed. S34. Call the CaseSetUpCmd function to execute the "initialization and constraint" statements of the test case; S35. Execute the CaseTearDown function; When performing component testing, if the TearDownIfCaseEnd function determines that the current behavior marks the end of a test case, the CaseTearDown function will be executed. S36. Execute SuiteTearDown to close the currently open Excel document.

6. A signal interface testing system based on a configuration table, employing the method described in any one of claims 1-5, characterized in that, include: The signal interface module is used for test design scripts and execution script standardization design. The test framework module is used to apply a component test framework to test cases and automatically build the component test framework from the source code. The execution log module is used to automatically execute and analyze the generated execution logs. If the function implemented by the control code is consistent with the data requirements in the IO configuration table, the test case passes; otherwise, it fails. The iteration module is used to analyze the problem and iterate again until all test cases have passed.

Images