Design method for configuration item test case of comprehensive function resolving software

Abstract

The invention relates to a method for designing a configuration item test case of comprehensive function resolving software. Comprising the following steps: abstracting a software demand item into a logic expression; two original test cases are designed by taking a criterion that a first condition in the logic expression independently influences an output result of the test cases, and other conditions in the logic expression are valued according to an upper-layer node type; the next condition is used as the current condition for iteration in sequence, the value of the current condition is obtained by negation of the original test case, all direct correlation preconditions of the current condition are determined, the value of the current condition is transmitted to the direct correlation preconditions of the current condition in sequence until the direct correlation precondition is the first condition, and the direct correlation precondition is the second condition; the values of the original test case are kept by the values of other conditions, and the test case of the current condition is obtained; traversing all the conditions to obtain a test case set of the software demand items; and mapping actual variables according to the test case set to obtain an actual test case set.

Description

Technical Field

[0001] The present application belongs to the field of software configuration item level test case design, and in particular, relates to a configuration item test case design method for comprehensive functional solution software. Background Art

[0002] As an important application software of the aircraft flight control system, the quality of the aircraft integrated management system application software directly affects the pilot's flight experience. As a key component of the aircraft management system application software, the comprehensive function solving software is mainly responsible for receiving the signals of the redundancy management software and performing multiple logical combinations of the signals to realize the configuration warning function and the comprehensive warning suppression function. The comprehensive function solving software has the characteristics of large signal volume and many logical combinations. The huge amount of input signals and complex logical combinations bring great challenges to the configuration item testing of the software. In order to ensure 100% coverage of functional requirements, software testers need to design a large number of input combination logics to verify whether the functional requirements are met.

[0003] Therefore, it is desired to have a technical solution to overcome or at least alleviate at least one of the above-mentioned defects of the prior art. Summary of the invention

[0004] The purpose of this application is to provide a configuration item test case design method for comprehensive functional solution software to solve at least one problem existing in the prior art.

[0005] The technical solution of this application is:

[0006] The first aspect of the present application provides a configuration item test case design method for comprehensive functional solution software, comprising:

[0007] Step 1: Abstract software requirements into logical expressions;

[0008] Step 2: Design two original test cases based on the principle that the first condition in the logic expression alone affects the output result of the test case, and the other conditions in the logic expression are evaluated according to the upper-layer node type;

[0009] Step 3, iterate the next condition as the current condition in turn, the value of the current condition is obtained by negating the original test case, determine all directly related preconditions of the current condition, and pass the value of the current condition to the directly related preconditions of the current condition in turn until the directly related precondition is the first condition, and the values ​​of other conditions all keep the values ​​of the original test case, so as to obtain the test case of the current condition;

[0010] Step 4: Repeat step 3 until all conditions are traversed to obtain a test case set for the software requirement item;

[0011] Step 5: Map the actual variables according to the test case set to obtain the actual test case set.

[0012] In at least one embodiment of the present application, in step 1, abstracting the software requirement item into a logical expression includes:

[0013] Extract the textual description of the software requirement items from the software requirement specification according to the requirement identifier;

[0014] Determine the conditions and interface relationships of the software requirement items according to the textual description;

[0015] The conditions of the software requirement items are abstracted into logical expressions according to the interface relationship.

[0016] In at least one embodiment of the present application, the logic expression includes nodes having a hierarchical relationship, wherein the nodes at the bottom layer are conditions of software requirement items.

[0017] In at least one embodiment of the present application, in step 2,

[0018] When the upper node is "logical AND", the conditional value is "true";

[0019] When the upper node is "logical or", the conditional value is "false".

[0020] In at least one embodiment of the present application, it also includes:

[0021] Step 6: Verify the input signal according to the actual test case set to complete the functional test of the software requirement item.

[0022] In at least one embodiment of the present application, it also includes:

[0023] Step 7: Obtain all software requirement items of the comprehensive function solving software, perform functional testing on each of the software requirement items according to steps 1 to 6, and complete the functional testing of the comprehensive function solving software.

[0024] A second aspect of the present application provides a configuration item test case design system for comprehensive function solving software, comprising:

[0025] Logical expression acquisition module, used to abstract software requirement items into logical expressions;

[0026] The original test case acquisition module is used to design two original test cases based on the principle that the first condition in the logic expression affects the output result of the test case alone, and the other conditions in the logic expression are valued according to the upper node type;

[0027] The test case acquisition module of the current condition is used to iterate the next condition as the current condition in turn, the value of the current condition is obtained by negating the original test case, all directly related preconditions of the current condition are determined, and the value of the current condition is passed to the directly related preconditions of the current condition in turn until the directly related precondition is the first condition, and the values ​​of other conditions all keep the values ​​of the original test case, so as to obtain the test case of the current condition;

[0028] A test case set acquisition module, used to acquire a test case set for the software requirement item;

[0029] The variable mapping module maps actual variables according to the test case set to obtain an actual test case set.

[0030] In at least one embodiment of the present application, in the logic expression acquisition module, the software requirement items are abstracted into logic expressions, including:

[0031] Extract the textual description of the software requirement items from the software requirement specification according to the requirement identifier;

[0032] Determine the conditions and interface relationships of the software requirement items according to the textual description;

[0033] The conditions of the software requirement items are abstracted into logical expressions according to the interface relationship.

[0034] In at least one embodiment of the present application, the logic expression includes nodes having a hierarchical relationship, wherein the nodes at the bottom layer are conditions of software requirement items.

[0035] In at least one embodiment of the present application, in the original test case acquisition module,

[0036] When the upper node is "logical AND", the conditional value is "true";

[0037] When the upper node is "logical or", the conditional value is "false".

[0038] In at least one embodiment of the present application, it also includes:

[0039] The requirement item functional testing module is used to verify the input signal according to the actual test case set to complete the functional testing of the software requirement item.

[0040] In at least one embodiment of the present application, it also includes:

[0041] The software function testing module is used to obtain all software requirement items of the comprehensive function solving software, perform function testing on each of the software requirement items, and complete the function testing of the comprehensive function solving software.

[0042] The invention has at least the following beneficial technical effects:

[0043] The configuration item test case design method of the comprehensive function solving software of the present application can solve the limitations of complex logic function test case design during configuration item testing and the problem of heavy workload for testers and difficulty in reuse of test cases due to excessive input signals. This method can be used to quickly generate configuration item test cases on the basis of meeting full functional coverage, thereby reducing the workload of testers. Finally, by forming an automated test script using this method, test cases that meet the requirements can be automatically generated. The test cases generated using this method are fixed in form and easy to reuse. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 It is a flow chart of a configuration item test case design method of a comprehensive function solving software according to an implementation mode of the present application;

[0045] Figure 2 It is a schematic diagram of a logical expression of a software requirement item of an implementation mode of the present application;

[0046] Figure 3 is a schematic diagram of an original test case of an implementation method of the present application;

[0047] Figure 4 It is a test case diagram of condition 2 of an implementation mode of the present application;

[0048] Figure 5 is a schematic diagram of a test case set of an implementation method of the present application;

[0049] Figure 6 It is a schematic diagram of an actual test case set of an implementation method of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical scheme and advantages of the implementation of this application clearer, the technical scheme in the embodiment of this application will be described in more detail below in conjunction with the drawings in the embodiment of this application. In the drawings, the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The described embodiments are part of the embodiments of this application, not all of them. The embodiments described below with reference to the drawings are exemplary and are intended to be used to explain this application, and should not be construed as limitations on this application. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. The embodiments of this application are described in detail below in conjunction with the drawings.

[0051] In the description of the present application, it should be understood that the terms "center", "longitudinal", "lateral", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as limiting the scope of protection of the present application.

[0052] The following is combined with Figures 1 to 6 This application is described in further detail.

[0053] The first aspect of the present application provides a configuration item test case design method for comprehensive function solving software, comprising the following steps:

[0054] Step 1: Abstract software requirements into logical expressions;

[0055] Step 2: Design two original test cases based on the principle that the first condition in the logical expression alone affects the output result of the test case. The other conditions in the logical expression are evaluated according to the upper-level node type.

[0056] Step 3: Iterate the next condition as the current condition in turn. The value of the current condition is obtained by negating the original test case. All directly related preconditions of the current condition are determined. The value of the current condition is passed to the directly related preconditions of the current condition in turn until the directly related precondition is the first condition. The values ​​of other conditions all keep the values ​​of the original test case, and the test case of the current condition is obtained.

[0057] Step 4: Repeat step 3 until all conditions are traversed to obtain a test case set for the software requirement item;

[0058] Step 5: Map the actual variables according to the test case set to obtain the actual test case set.

[0059] In the preferred implementation of the present application, the text requirements of the software requirement items in the software requirement specification are analyzed, the logical conditions are extracted, and the logical expression of the requirements is obtained. In step 1, the software requirement items are abstracted into logical expressions, including:

[0060] Extract the textual description of the software requirement items from the software requirement specification according to the requirement identifier;

[0061] Determine the conditions and interface relationships of software requirements based on textual descriptions;

[0062] Abstract the conditions of software requirements into logical expressions according to interface relationships.

[0063] In a preferred embodiment of the present application, the logical expression includes nodes having a hierarchical relationship, wherein the nodes at the bottom layer are conditions of software requirement items.

[0064] In a preferred embodiment of the present application, in step 2,

[0065] When the upper node is "logical AND", the conditional value is "true";

[0066] When the upper node is "logical or", the conditional value is "false".

[0067] The configuration item test case design method of the comprehensive functional solution software of the present application uses the configuration item test case automatic generation method proposed in this article to obtain a test case set that meets the functional coverage, and then converts the content of the test case set into specific conditions.

[0068] The configuration item test case design method of the comprehensive function solving software of the present application also includes:

[0069] Step 6: Verify the input signal according to the actual test case set to complete the functional testing of the software requirement items.

[0070] Step 7: Obtain all software requirement items of the comprehensive function solving software, perform functional testing on each software requirement item according to steps 1 to 6, and complete the functional testing of the comprehensive function solving software.

[0071] Figure 1 This is a flowchart for the rapid generation of configuration item-level test cases for comprehensive functional solution software. The specific implementation method is further explained in detail below with examples.

[0072] Step 1: Extract the conditions and interface relationships of a software requirement item in the software requirement specification and abstract them into the form of a logical expression, such as Figure 2 shown.

[0073] Step 2: According to Figure 2 The logical expression in the condition 1 is evaluated as "true" and "false" respectively. The other conditions in the logical expression are evaluated according to the upper node type. If the upper node is "logical and", the condition is evaluated as "true". If the upper node is "logical or", the condition is evaluated as "false". The two original test cases in which condition 1 affects the test results alone are obtained, such as Figure 3 shown.

[0074] Step 3: After getting the original test case, iterate condition 2 as the current condition. The value of condition 2 is obtained by negating the original test case, and then pass the value of condition 2 to condition 1. Since condition 1 is the first condition, the values ​​of other conditions remain the values ​​of the original test case, and the test case of condition 2 is obtained. Figure 4 shown.

[0075] Then take condition 3 as the current condition, the value of condition 3 is obtained by negating the original test case, and the value of condition 3 is passed to its directly related condition 2. Since condition 2 is not the first condition, the value of condition 2 is passed to condition 1 to obtain the test case of condition 3.

[0076] Step 4: By analogy, follow this step to iterate all conditions in turn and get the test case set for all conditions as follows Figure 5 shown.

[0077] Step 5: According to Figure 5 The test case set maps the logical value to the actual variable to obtain the test case corresponding to the software input, such as Figure 6 shown.

[0078] Step 6: Input signal according to Figure 6 By verifying them one by one in the order mentioned above, the functional test of the software requirement items can be completed.

[0079] Step 7. Other software requirement items are analogous to each other, and a complete functional test case of the entire comprehensive functional solution software can be obtained, thereby completing the functional test of the comprehensive functional solution software.

[0080] The configuration item test case design method of the comprehensive function solution software of the present application uses this configuration item level test case rapid generation method to generate a fixed number of test cases, which is more standardized than the traditional traversal, and effectively reduces the number of test cases, reducing the burden on testers. Moreover, the test cases generated by this method are easy to reuse, and can realize rapid testing of the change logic in the regression stage, and it is also easy to realize version management. When actually carrying out the test, this test case rapid generation method is easy to locate the fault, and which input and output do not match, only the logical relationship related to the condition of the test case needs to be analyzed. And the test cases generated in this way can be directly made into a table form as an attachment to the test report, reducing the burden of writing the report. The present invention is particularly suitable for the functional testing of the software with complex and large combination logic such as comprehensive function solution, which is frequently changed in the early stage of development and the regression testing in the operation and maintenance stage.

[0081] In view of the large workload of configuration item testing in the early stage of comprehensive function solving software development and the difficulty of reusing conventional test methods, this application proposes a method for rapid design of configuration item test cases for comprehensive function solving software. This method expresses the text description requirements in the form of a logic block diagram, uses a fixed format test case automatic generation method for a large number of logic block diagrams, and quickly generates configuration item-level test cases that meet 100% coverage of the requirements. Finally, the input of the generated test case is converted into an actual input signal to complete the test process.

[0082] A second aspect of the present application provides a configuration item test case design system for comprehensive function solving software, comprising:

[0083] Logical expression acquisition module, used to abstract software requirement items into logical expressions;

[0084] The original test case acquisition module is used to design two original test cases based on the principle that the first condition in the logical expression affects the output result of the test case alone, and the other conditions in the logical expression are evaluated according to the upper-level node type;

[0085] The test case acquisition module of the current condition is used to iterate the next condition as the current condition in turn. The value of the current condition is obtained by negating the original test case, determining all directly related preconditions of the current condition, and passing the value of the current condition to the directly related preconditions of the current condition in turn until the directly related precondition is the first condition. The values ​​of other conditions all keep the values ​​of the original test case, and the test case of the current condition is obtained;

[0086] A test case set acquisition module is used to acquire the test case set of the software requirement item;

[0087] The variable mapping module maps the actual variables according to the test case set to obtain the actual test case set.

[0088] The configuration item test case design system of the comprehensive function solving software of this application, in the logic expression acquisition module, abstracts the software requirement items into logical expressions, including:

[0089] Extract the textual description of the software requirement items from the software requirement specification according to the requirement identifier;

[0090] Determine the conditions and interface relationships of software requirements based on textual descriptions;

[0091] Abstract the conditions of software requirements into logical expressions according to interface relationships.

[0092] In a preferred embodiment of the present application, the logical expression includes nodes having a hierarchical relationship, wherein the nodes at the bottom layer are conditions of software requirement items.

[0093] In a preferred embodiment of the present application, in the original test case acquisition module,

[0094] When the upper node is "logical AND", the conditional value is "true";

[0095] When the upper node is "logical or", the conditional value is "false".

[0096] In a preferred embodiment of the present application, it also includes:

[0097] The requirement item functional testing module is used to verify the input signal according to the actual test case set and complete the functional testing of the software requirement items.

[0098] In a preferred embodiment of the present application, it also includes:

[0099] The software function testing module is used to obtain all software requirement items of the comprehensive function solving software, perform function testing on each software requirement item, and complete the function testing of the comprehensive function solving software.

[0100] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A configuration item test case design method for comprehensive function solving software, characterized in that: include: Step 1: Abstract software requirements into logical expressions; Step 2: Design two original test cases based on the principle that the first condition in the logic expression alone affects the output result of the test case, and the other conditions in the logic expression are evaluated according to the upper-layer node type; Step 3, iterate the next condition as the current condition in turn, the value of the current condition is obtained by negating the original test case, determine all directly related preconditions of the current condition, and pass the value of the current condition to the directly related preconditions of the current condition in turn until the directly related precondition is the first condition, and the values ​​of other conditions all keep the values ​​of the original test case, so as to obtain the test case of the current condition; Step 4: Repeat step 3 until all conditions are traversed to obtain a test case set for the software requirement item; Step 5: Map the actual variables according to the test case set to obtain the actual test case set.

2. The configuration item test case design method for comprehensive function solving software according to claim 1, characterized in that: In step 1, the software requirements are abstracted into logical expressions, including: Extract the textual description of the software requirement items from the software requirement specification according to the requirement identifier; Determine the conditions and interface relationships of the software requirement items according to the textual description; The conditions of the software requirement items are abstracted into logical expressions according to the interface relationship.

3. The configuration item test case design method for comprehensive function solving software according to claim 2, characterized in that: The logic expression includes nodes with a hierarchical relationship, wherein the nodes at the bottom layer are conditions of software requirement items.

4. The configuration item test case design method for comprehensive function solving software according to claim 3 is characterized in that: In step 2, When the upper node is "logical AND", the condition value is "true"; When the upper node is "logical or", the conditional value is "false".

5. The configuration item test case design method for comprehensive function solving software according to claim 4, characterized in that: Also includes: Step 6: Verify the input signal according to the actual test case set to complete the functional test of the software requirement item.

6. The configuration item test case design method for comprehensive function solving software according to claim 5, characterized in that: Also includes: Step 7: Obtain all software requirement items of the comprehensive function solving software, perform functional testing on each of the software requirement items according to steps 1 to 6, and complete the functional testing of the comprehensive function solving software.

7. A configuration item test case design system for comprehensive function solving software, characterized in that: include: Logical expression acquisition module, used to abstract software requirement items into logical expressions; The original test case acquisition module is used to design two original test cases based on the principle that the first condition in the logic expression affects the output result of the test case alone, and the other conditions in the logic expression are valued according to the upper node type; The test case acquisition module of the current condition is used to iterate the next condition as the current condition in turn, the value of the current condition is obtained by negating the original test case, all directly related preconditions of the current condition are determined, and the value of the current condition is passed to the directly related preconditions of the current condition in turn until the directly related precondition is the first condition, and the values ​​of other conditions all keep the values ​​of the original test case, so as to obtain the test case of the current condition; A test case set acquisition module, used to acquire a test case set for the software requirement item; The variable mapping module maps actual variables according to the test case set to obtain an actual test case set.

8. The configuration item test case design system for comprehensive function solving software according to claim 7, characterized in that: In the logical expression acquisition module, software requirement items are abstracted into logical expressions, including: Extract the textual description of the software requirement items from the software requirement specification according to the requirement identifier; Determine the conditions and interface relationships of the software requirement items according to the textual description; The conditions of the software requirement items are abstracted into logical expressions according to the interface relationship.

9. The configuration item test case design system for comprehensive function solving software according to claim 8, characterized in that: The logic expression includes nodes with a hierarchical relationship, wherein the nodes at the bottom layer are conditions of software requirement items.

10. The configuration item test case design system for comprehensive function solving software according to claim 9, characterized in that: In the original test case acquisition module, When the upper node is "logical AND", the condition value is "true"; When the upper node is "logical or", the conditional value is "false".

11. The configuration item test case design system for comprehensive function solving software according to claim 10, characterized in that: Also includes: The requirement item functional testing module is used to verify the input signal according to the actual test case set to complete the functional testing of the software requirement item.

12. The configuration item test case design system for comprehensive function solving software according to claim 11, characterized in that: Also includes: The software function testing module is used to obtain all software requirement items of the comprehensive function solving software, perform function testing on each of the software requirement items, and complete the function testing of the comprehensive function solving software.

Images