A method and system for legal traversal testing of a ship information system information input interface
By automating parsing and designing multiple traversal strategies, combined with synchronous capture of heartbeat messages and logical judgment, the problems of low efficiency and insufficient coverage in the testing of input interfaces of traditional ship information systems have been solved, achieving efficient and accurate automated testing.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA SHIP DEV & DESIGN CENT
- Filing Date
- 2026-03-26
- Publication Date
- 2026-07-10
AI Technical Summary
Traditional ship information system input interface testing suffers from low efficiency, insufficient interface test case coverage, and low degree of automation in result determination, resulting in low testing efficiency and potential hidden dangers.
The system employs automated parsing of information interfaces to design data, and designs various traversal strategies and automatic evaluation methods, including value type, discrete quantity type, segment type, single message multi-field collaborative traversal, and multiple input message collaborative traversal strategies. Combined with heartbeat or status message synchronous capture and logical relationship determination, it achieves automated testing.
It improves the coverage of information interface traversal and testing efficiency, ensures the accuracy and automation of test results, and reduces the reliance on manual intervention.
Smart Images
Figure CN122364075A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of information technology, and in particular to a method and system for testing the legal traversal of information input interfaces in a ship information system. Background Technology
[0002] The ship's information system is the core of its command and control. It integrates data from various sensors, navigation and communication systems, control systems, execution systems, and external systems throughout the ship. Each device / software has numerous input / output interfaces with complex data formats. The correctness of the processing of input interface messages by each device / software directly affects the reliability and stability of the ship's system operation. Currently, the testing of ship information system input interfaces faces the following main challenges and technical limitations: (1) Low testing efficiency Traditional testing of input interfaces for ship information systems requires relying on input devices or software to simulate the corresponding interfaces for the device / software under test. Input interface fields need to be manually configured, or even impossible to be manually configured, in order to complete the test under a certain state. This makes it very inefficient to traverse the input interfaces.
[0003] (2) Insufficient coverage of interface test cases Traditional ship information system input interface testing has the problem of not covering all possible values of all fields, which poses a risk of missing inputs. Incomplete input conditions may cause hidden dangers to the subsequent operation of equipment / software.
[0004] (3) Low degree of automation in result determination Testing of the input interface of the ship information system mainly relies on manual methods. Testers need to manually construct test data according to the interface documentation and also manually check the response after input, which further reduces testing efficiency. Summary of the Invention
[0005] The purpose of this invention is to overcome the shortcomings of the above-mentioned background technology and provide a method and system for testing the legal traversal of information input interfaces in a ship information system, thereby improving the traversal coverage and testing efficiency.
[0006] This invention provides a method for legal traversal testing of information input interfaces in a ship information system, comprising the following steps: S1. Automated parsing of information interface design data: Extracting information interface field definitions, timing rules, and interaction logic from the information interface design data, identifying the type of each field, and providing a data foundation for input interface testing; S2. Setting traversal strategies based on information interface field definitions: Setting traversal strategies for various types of fields, a single message multi-field collaborative traversal strategy, and a multiple input message collaborative traversal strategy; S3. Automatic interface test evaluation based on legal traversal input: Evaluating the interface test results under traversal input based on whether the ship information system under test is working properly or whether the specific processing logic of the ship information system under test is correct.
[0007] In the above technical solution, in step S2, the various types of field traversal strategies include value type field traversal strategies, discrete quantity type field traversal strategies, and segmentation strategies that include both discrete quantity types and value types; the single message multi-field collaborative traversal strategies include field-by-field traversal strategies, all-field simultaneous traversal strategies, and field-by-field and multi-field simultaneous traversal strategies; the multiple input message collaborative traversal strategies include message-by-message traversal strategies, multi-message simultaneous traversal strategies, and message-by-message and multi-message simultaneous mixed traversal strategies.
[0008] In the above technical solution, in step S2, among the various field traversal strategies, the value type field traversal strategy is to set the traversal strategy according to the minimum value, maximum value, and multiple intermediate values; the discrete quantity type field traversal strategy is to traverse each discrete quantity according to its definition; the segment traversal strategy, which includes both discrete and value types, is to set both the value traversal strategy and the discrete quantity traversal strategy according to the segment; in the single message multi-field collaborative traversal strategy, the field-by-field traversal strategy is to traverse only one field and segment at a time, while keeping the values of other fields unchanged; the simultaneous traversal strategy of all fields is to perform the traversal of all fields or segments simultaneously according to the set traversal strategy. The traversal strategy includes forward, reverse, and random mixed traversal; the field-by-field and multi-field simultaneous mixed traversal strategy involves traversing certain fields of a selected message one by one while traversing other fields simultaneously; in the multi-input message collaborative traversal strategy, the one-message traversal strategy traverses multiple fields of each message while keeping the default values of other messages unchanged, and the message is set with a traversal strategy according to the single-message multi-field collaborative traversal strategy; the multi-message simultaneous traversal strategy traverses all input messages simultaneously according to the set field traversal strategy; the one-message and multi-message simultaneous mixed traversal strategy selects to traverse multiple messages one by one while simultaneously traversing multiple other messages.
[0009] In the above technical solution, in step S2, the value type field traversal strategy includes value traversal strategy one, setting the traversal strategy according to the minimum value, average value and maximum value; and value traversal strategy two, setting the traversal strategy according to the minimum value, maximum value and four equal division points.
[0010] In the above technical solution, in step S2, the traversal strategy is set by an orthogonal method.
[0011] In the above technical solution, step S3 evaluates the interface test results under the input traversal based on whether the ship information system under test is working properly. The specific process is as follows: S31. Only evaluate whether the ship information system under test is working properly. During the traversal of various input information interfaces, capture the heartbeat message or status message of the ship information system under test simultaneously; S32. If the heartbeat or status message is still being sent after all input information interfaces have been traversed, the input interface traversal test is passed; S33. If the heartbeat or status message is interrupted during the traversal of the input information interfaces, record the input interface message field values within one cycle of the heartbeat message after the last heartbeat or status message, and give the possible results of these messages causing the failure of the ship information system under test; S34. According to the input interface messages that may cause abnormalities, perform input tests one by one again, and check whether the output heartbeat message stops one by one to determine the input interface message field values that cause the failure of the ship information system under test.
[0012] In the above technical solution, step S3 involves evaluating the interface test results under the traversal input based on whether the specific processing logic of the tested ship information system is correct. The specific process is as follows: S31': Evaluate whether the specific processing logic of the tested ship information system is correct. When certain input information needs to be processed and output, and certain fields of the output message have a logical relationship with certain fields of the input message, arrange the judgment criteria for these logical input-output relationships, i.e., the calculation relationship between the output field and the input field; S32': During test execution, simultaneously record the input message and output message, and make real-time judgments based on the arranged calculation relationships. At the same time, judge the situation that causes the tested ship information system to malfunction according to the method for whether the tested ship information system is working normally; S33': When the calculation relationship is not equal, record the input message at this time and give the result that the tested ship information system has a processing error due to this message; S34': If only the processing error occurs and no malfunction occurs, the test does not need to be stopped until all test contents have been traversed.
[0013] In the above technical solution, in steps S1 to S3, interface message data is generated according to the input traversal strategy and sent according to the traversal sending timing, while all input messages and output messages of the device / software under test are collected.
[0014] The above technical solution also includes S4, storage information definition data, traversal strategy setting data, judgment test result evaluation data, interface collection data, and interface test result data.
[0015] This invention also provides a valid traversal test system for the information input interface of a ship information system, which has a computer program that can execute a valid traversal test method for the information input interface of a ship information system.
[0016] The present invention provides a method and system for testing the valid traversal of information input interfaces in a ship information system, which has the following beneficial effects: (1) A multi-traversal strategy for input information interface is proposed, which improves the traversal coverage of various types of fields in the input information interface of various devices / software in complex local area network information systems.
[0017] (2) An automatic matching and evaluation rule for input and output information interfaces is proposed, which improves the efficiency of testing the input information interfaces of various devices / software in complex local area network information systems. Attached Figure Description
[0018] Figure 1 This is an overall flowchart of the valid traversal test method for the information input interface of the ship information system of the present invention; Figure 2 This is a schematic diagram of the architecture of the ship information system information input interface legal traversal test system of the present invention. Detailed Implementation
[0019] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments, but these embodiments should not be construed as limiting the present invention.
[0020] The technical problems to be solved by this invention mainly include the following aspects: (1) Information interface design and automated data parsing problem For the information interface design data, extract the information interface field definitions, timing rules and interaction logic, and identify the type of each field to provide a data foundation for generating input interface test cases.
[0021] (2) Issues with setting traversal strategies based on information interface field definitions Ship information systems often have numerous input interfaces for certain devices / software, and each interface has a large number and types of fields. If each message and each field is traversed one by one, the efficiency will be low. One or more input interface field traversal strategies are needed to effectively improve efficiency.
[0022] (3) The problem of automatically evaluating test results based on input and output data When performing fast input interface traversal tests, it is necessary to collect the output information of the device / software, match and evaluate it with the input, and provide the information interface input test results.
[0023] Example 1 In order to solve the above problems, the present invention mainly proposes the following technical points, which are the essential technical contents of the present invention.
[0024] (1) Information interface design and data parsing Extract the field definitions, timing rules, and interaction logic of all information interface messages from the information interface protocol design file or database, identify the type and definition range of each field, and form an information interface library to provide a data foundation for generating input interface test cases.
[0025] (2) Design of a valid traversal strategy for the input interface based on the information interface parsing data Design different traversal strategies for different types of fields: For value-type fields, set multiple traversal strategies according to minimum value, maximum value, and multiple intermediate values, such as value traversal strategy 1 (minimum value, average value, maximum value), value traversal strategy 2 (minimum value, maximum value, four equal points), and so on; For discrete-value type fields, traverse them one by one according to the definition of all discrete values; For fields with both discrete and value types in segments, set value traversal strategy and discrete traversal strategy according to the segments.
[0026] Design a multi-field collaborative traversal strategy for a single message: a field-by-field traversal strategy (for mixed-type fields, traversing segment by segment), that is, only one field and segment are traversed each time, while the values of other fields remain unchanged; a simultaneous traversal strategy for all fields, that is, all fields or segments are traversed simultaneously each time according to the set traversal strategy in a forward, reverse, or random mixed manner; a mixed traversal strategy of field-by-field and multi-field traversal, that is, which field in a message can be traversed one by one and which field can be traversed simultaneously.
[0027] Design multiple input message collaborative traversal strategies: message-by-message traversal strategy, which traverses multiple fields of each message while keeping the default values of other messages unchanged, and the single message traversal strategy is set as described above; multi-message simultaneous traversal strategy, which traverses all input messages simultaneously according to the set field traversal strategy; and mixed message-by-message and multi-message simultaneous traversal strategy, which allows you to choose to traverse multiple messages message-by-message or to traverse multiple messages simultaneously.
[0028] When setting a traversal strategy, an orthogonal approach can be used to reduce the number of traversals and improve testing efficiency.
[0029] (3) Automatic interface testing and evaluation based on valid traversal input Multiple methods are used to automatically evaluate the interface test results under traversal input.
[0030] The first method assesses only whether the device / software under test (DUT) is functioning correctly. While traversing various input interfaces, it simultaneously captures the device / software's heartbeat or status messages. If heartbeats or status messages are still being sent after all input interfaces have been traversed, the input interface traversal test passes. If heartbeats or status messages are interrupted during the traversal, the values of the input interface message fields within one cycle of the heartbeat message following the last heartbeat or status message are recorded, indicating possible causes of DUT malfunctions. Based on these identified potentially abnormal input interface messages, the input tests are repeated one by one, and the output heartbeat messages are checked to see if they have stopped, thus accurately determining the input interface message field values that caused the DUT malfunction.
[0031] The second method assesses the correctness of specific processing logic within the device / software under test (DUT). When certain input information needs to be processed and output, and certain fields in the output message have logical relationships with certain fields in the input message, the criteria for determining these logical input-output relationships are pre-defined, i.e., the calculation relationship between the output field and the input field. During test execution, input and output messages are recorded simultaneously, and real-time judgments are made based on the pre-defined calculation relationships. Simultaneously, the methods described in the first method are used to determine situations that could lead to a DUT malfunction. When a calculation relationship is unequal, the input message at that moment is recorded, and the result indicating that this message caused a processing error in the DUT is given. If only a processing error occurs without a malfunction, the test does not need to be stopped until all test content has been traversed.
[0032] Example 2 The present invention will be further described in detail below with reference to the embodiments and accompanying drawings.
[0033] 1. Test method for valid traversal of information input interface in ship information system As attached Figure 1 As shown, another embodiment of the test process for traversing the information input interface of a complex ship information system mainly includes: 1) Information interface design and data parsing; 2) Configure the traversal strategy for each field of all input information interface messages; 3) Set a cooperative traversal strategy between the fields within each message. An orthogonal method can be used to reduce the number of traversals. 4) Configure a collaborative traversal strategy for all input messages of the device, which can traverse messages one by one or multiple messages simultaneously; 5) Configure the output heartbeat or status messages that this device needs to record; 6) Arrange the specific processing logic of the device / software, that is, arrange the correct calculation relationship between the output field and the input field; 7) Begin executing the input and output message acceptance test; 8) During the traversal of all input information interfaces, determine whether the heartbeat or status message is interrupted; 9) If interrupted, proceed to step 10); if not interrupted, proceed to step 12. 10) Identify all input interface messages in the cycle following the last heartbeat or status message; 11) Perform input tests on each identification message one by one, and check whether the output heartbeat message stops one by one. If an input message causes the heartbeat message to stop, give the result "Due to the value of field XX in input message XX, device / software malfunction is caused"; if the output heartbeat or status message does not stop when all input messages are entered one by one, proceed to step 13). 12) Determine whether the processing logic of fields with input-output relationships is correct. If correct, give the result "Input interface traversal test passed"; if incorrect, give the result "Due to the value filled in field XX of input message XX, the XX device / software processing is incorrect". 13) Give the result "The XX device / software malfunctioned due to the value filled in the XX field of the XX input message".
[0034] Example 3 2. Construction of a valid traversal test system for the information input interface of a ship information system like Figure 2 As shown, the present invention provides a ship information system information input interface legal traversal test system, which includes an information interface design data parsing module, an input interface traversal strategy and judgment rule setting module, an interface data sending and acquisition module, an input information interface traversal test result evaluation module, and a data storage module.
[0035] (1) Information interface design data parsing module Extract the field definitions, timing rules, and interaction logic of all information interface messages from the information interface protocol design file or database, identify the type and definition range of each field, and form an information interface library to provide a data foundation for generating input interface test cases.
[0036] (2) Input interface traversal strategy and judgment rule setting module Design different traversal strategies for different types of fields: For value-type fields, set multiple traversal strategies according to minimum value, maximum value, and multiple intermediate values, such as value traversal strategy 1 (minimum value, average value, maximum value), value traversal strategy 2 (minimum value, maximum value, four equal points), and so on; For discrete-value type fields, traverse them one by one according to the definition of all discrete values; For fields with both discrete and value types in segments, set value traversal strategy and discrete traversal strategy according to the segments.
[0037] Design a multi-field collaborative traversal strategy for a single message: a field-by-field traversal strategy (for mixed-type fields, traversing segment by segment), that is, only one field and segment are traversed each time, while the values of other fields remain unchanged; a simultaneous traversal strategy for all fields, that is, all fields or segments are traversed simultaneously each time according to the set traversal strategy in a forward, reverse, or random mixed manner; a mixed traversal strategy of field-by-field and multi-field traversal, that is, which field in a message can be traversed one by one and which field can be traversed simultaneously.
[0038] Design multiple input message collaborative traversal strategies: message-by-message traversal strategy, which traverses multiple fields of each message while keeping the default values of other messages unchanged, and the traversal strategy of a single message is set as described above; multi-message simultaneous traversal strategy, which traverses all input messages simultaneously according to the set field traversal strategy; and mixed message-by-message and multi-message simultaneous traversal strategy, which allows you to choose to traverse multiple messages message-by-message or to traverse multiple messages simultaneously.
[0039] The traversal rules also provide settings for the data cycle of the interface traversal.
[0040] The rules for determining whether the software runs normally under the input traversal test are as follows: if the heartbeat or status message has not stopped after all input information interfaces have been traversed, the test passes; if the heartbeat or status message is interrupted during the input information interface traversal, the test fails.
[0041] The rules for determining whether the software processes input correctly during the traversal input test are as follows: Based on the pre-arranged logical input-output relationship, if the input-output relationship conforms to the settings, the test passes; if the input-output relationship does not conform to the settings, the test fails.
[0042] (3) Interface data sending and acquisition module The interface message data is generated according to the input traversal strategy and sent according to the traversal sending time. At the same time, all input messages and output messages of the device / software under test are collected.
[0043] (4) Input information interface traversal test result evaluation module Based on the test result judgment rules, the normal operation of the device / software under test is evaluated. During the traversal of various input information interfaces, heartbeat or status messages of the device / software are captured synchronously. If heartbeat or status messages are still being sent after all input information interfaces have been traversed, the input interface traversal test passes. If heartbeat or status messages are interrupted during the input information interface traversal, the values of the input interface message fields within one cycle of the heartbeat message following the last heartbeat or status message are recorded, indicating the possible causes of device / software failure due to these messages. Based on these identified potentially abnormal input interface messages, input tests are performed again one by one, and the output heartbeat messages are checked one by one to accurately determine the input interface message field values that caused the device / software failure.
[0044] Based on the test result judgment rules, the correctness of specific processing logic of the device / software under test is evaluated. When certain input information needs to be processed and output, and certain fields of the output message have logical relationships with certain fields of the input message, the judgment criteria for these logical input-output relationships are arranged, i.e., the calculation relationship between the output field and the input field. During test execution, input and output messages are recorded synchronously, and judgments are made in real time according to the arranged calculation relationships. At the same time, the methods in the first method are used to determine the situations that may cause malfunctions in the device / software under test. When a calculation relationship is not equal, the input message at this time is recorded, and the result of the processing error caused by this message is given. If only a processing error occurs and no malfunction occurs, the test does not need to be stopped until all test contents have been traversed.
[0045] (5) Data storage module Centralized and unified management is implemented for information definition data, traversal strategy setting data, judgment rule setting data, interface collection data, and interface test result data.
[0046] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.
[0047] The contents not described in detail in this specification are existing technologies known to those skilled in the art.
Claims
1. A method for testing the valid traversal of an information input interface in a ship information system, characterized in that: Includes the following steps: S1. Automated parsing of information interface design data: For information interface design data, extract the information interface field definitions, timing rules and interaction logic, identify the type of each field, and provide a data foundation for input interface testing; S2. Set traversal strategies based on information interface field definitions: Set traversal strategies for various types of fields, collaborative traversal strategies for multiple fields in a single message, and collaborative traversal strategies for multiple input messages; S3. Automatic interface test evaluation based on valid traversal input: The interface test results under traversal input are evaluated based on whether the ship information system under test is working properly or whether the specific processing logic of the ship information system under test is correct.
2. The method for valid traversal testing of the information input interface of a ship information system according to claim 1, characterized in that: In step S2, the various field traversal strategies include value type field traversal strategy, discrete quantity type field traversal strategy, and segmentation strategy that includes both discrete quantity type and value type traversal strategy. The single message multi-field collaborative traversal strategy includes a field-by-field traversal strategy, a strategy of traversing all fields simultaneously, and a strategy of traversing both field-by-field and multi-field simultaneously. The multiple input message collaborative traversal strategy includes a message-by-message traversal strategy, a multi-message simultaneous traversal strategy, and a mixed traversal strategy of message-by-message and multi-message simultaneous traversal.
3. The method for valid traversal testing of the information input interface of a ship information system according to claim 2, characterized in that: In step S2, among the various field traversal strategies, the value type field traversal strategy is set according to the minimum value, maximum value, and multiple intermediate values. The traversal strategy for discrete quantity type fields is to traverse each discrete quantity definition one by one; the traversal strategy for segments that have both discrete quantity types and value types is to set both the value traversal strategy and the discrete quantity traversal strategy according to the segment. In the single message multi-field collaborative traversal strategy, the field-by-field traversal strategy traverses only one field and segment at a time, while keeping the values of other fields unchanged. The strategy of traversing all fields simultaneously is to perform forward, reverse, and random mixed traversal of all fields or segments at the same time each time according to the set traversal strategy; the strategy of traversing each field and multiple fields simultaneously is to select some fields in a message and traverse some other fields at the same time. In the multiple input message collaborative traversal strategy, the message-by-message traversal strategy traverses multiple fields of each message while keeping the default values of other messages unchanged. The message is set with a traversal strategy according to the single message multi-field collaborative traversal strategy. The multi-message simultaneous traversal strategy traverses all input messages simultaneously according to the set field traversal strategy. The strategy of simultaneous traversal of message-by-message and multiple messages is to perform message-by-message traversal on multiple messages while simultaneously traversing multiple other messages.
4. The method for valid traversal testing of the information input interface of a ship information system according to claim 3, characterized in that: In step S2, the value type field traversal strategy includes value traversal strategy one, setting the traversal strategy according to the minimum value, average value and maximum value; Value traversal strategy two: Set the traversal strategy according to the minimum value, maximum value, and four equal division points.
5. The method for valid traversal testing of the information input interface of a ship information system according to claim 4, characterized in that: In step S2, the traversal strategy is set using an orthogonal method.
6. The method for valid traversal testing of the information input interface of a ship information system according to claim 5, characterized in that: In step S3, the interface test results under the traversal input are evaluated based on whether the tested ship information system is working properly. The specific process is as follows: S31. Only assess whether the information system of the tested ship is working properly. When traversing various input information interfaces, capture the heartbeat message or status message of the information system of the tested ship simultaneously. S32. If all input information interfaces have been traversed and heartbeats or status messages are still being sent, then the input interface traversal test is passed. S33. If the heartbeat or status message is interrupted during the input information interface traversal, record the input interface message field values within one cycle of the heartbeat message after the last heartbeat or status message, and provide the possible results of these messages causing the failure of the tested ship information system. S34. Based on the input interface messages that may cause abnormalities, perform input tests one by one again, and check whether the output heartbeat messages have stopped, and determine the values filled in the fields of the input interface messages that caused the fault in the tested ship information system.
7. The method for valid traversal testing of the information input interface of a ship information system according to claim 6, characterized in that: In step S3, the interface test results under the traversal input are evaluated based on whether the specific processing logic of the tested ship information system is correct. The specific process is as follows: S31' Evaluate whether the specific processing logic of the tested ship information system is correct. When certain input information needs to be processed and output, and certain fields of the output message have a logical relationship with certain fields of the input message, arrange the judgment criteria for these logical input-output relationships, that is, the calculation relationship between the output field and the input field. S32' During test execution, input and output messages are recorded synchronously, and real-time judgments are made based on the pre-arranged calculation relationships. At the same time, the situation that causes the failure of the tested ship information system is judged according to the method of whether the tested ship information system is working properly. S33' When the calculation relationship is not equal, record the input message at this time and give the result of the error caused by this message in the information system of the tested ship. S34' If only a processing error occurs, but no failure occurs, the test does not need to be stopped until all test contents have been traversed.
8. The method for valid traversal testing of the information input interface of a ship information system according to claim 7, characterized in that: In steps S1 to S3, interface message data is generated according to the input traversal strategy and sent according to the traversal sending timing. At the same time, all input messages and output messages of the device / software under test are collected.
9. The method for valid traversal testing of the information input interface of a ship information system according to claim 8, characterized in that: It also includes S4, storage information definition data, traversal strategy setting data, judgment test result evaluation data, interface collection data, and interface test result data.
10. A valid traversal test system for information input interfaces of a ship information system, comprising a computer program, characterized in that: The computer program is capable of executing the valid traversal test method for the information input interface of the ship information system as described in any one of claims 1 to 9.