Test case generation support device and test case generation support method

Abstract

To support efficient program testing.SOLUTION: A test case generation support device 10 is a device for supporting generation of test cases that are data including combinations of factors and levels used in execution tests of a predetermined program, and executes: overlap determination processing of storing multiple test policies that are data defining combinations of factors and levels in the test cases, specifying, for each test policy selected from the multiple test policies, a test case group generated based on the test policy, and specifying, from among the specified test case groups, overlapping test cases that are the test cases whose contents overlap between at least two or more test policies; and overlap result output processing of outputting information on the specified overlapping test cases.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a test case generation support device and a test case generation support method. [Background technology]

[0002] In recent years, as software development processes have become more complex, the importance of the testing process to test whether the developed software operates correctly is increasing. In the testing process, it is preferable to perform comprehensive testing that assumes various execution conditions. On the other hand, the larger the scale of the software, the greater the number of work items. Since a program contains a mixture of parts that should be checked intensively and parts that should not, simply considering comprehensiveness may impair development efficiency.

[0003] As a technique for testing software, for example, Patent Document 1 discloses a test case generation method in which a computer executes a process of receiving a first test case and a second test case to be combined, extracting common variables common to the first and second test cases, extracting in the first test case an appearance pattern of a conditional clause including the extracted common variable, extracting at least one representative test case for each extracted appearance pattern, and combining the representative test case extracted for each appearance pattern in the first test case with the second test case to generate a new test case. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2017-207959 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in Patent Document 1, as the scale of software increases, a large number of test cases are generated. As a result, program testing may include test cases that are not necessarily necessary. This makes test case management cumbersome, and conversely, there is a risk that necessary test cases will not be performed. It is preferable to perform only necessary program testing.

[0006] The present invention has been made in view of the above background, and an object of the present invention is to provide a test case generation support device and a test case generation support method that are capable of supporting efficient program testing. [Means for solving the problem]

[0007] One of the present inventions for solving the above problems is an apparatus for supporting the generation of test cases, which are data including combinations of factors and levels used in execution testing of a specified program, comprising a storage device for storing multiple test policies, which are data that specify combinations of factors and levels in test cases, and a control device that executes an overlap determination process for identifying a group of test cases generated based on the test policies for each test policy selected from the multiple test policies, and identifying overlap test cases among the identified group of test cases, which are test cases whose contents overlap between at least two or more test policies, and an overlap result output process that outputs information on the identified overlap test cases. Effect of the Invention

[0008] According to the present invention, it is possible to assist in carrying out program testing efficiently. Configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0009] [Figure 1]FIG. 1 is a diagram illustrating an example of a configuration of a test case generation support system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating an example of functions of the test case generation support device. [Diagram 3] FIG. 13 is a diagram illustrating an example of factor level information. [Figure 4] FIG. 13 illustrates an example of a test policy rule table. [Diagram 5] FIG. 2 is a diagram illustrating an example of hardware included in a test case generation assistance device. [Figure 6] FIG. 11 is a flow diagram illustrating an example of a test case generation support process. [Figure 7] FIG. 13 is a diagram illustrating an example of test policy information. [Figure 8] FIG. 13 is a diagram illustrating an example of test policy information. [Figure 9] 13 is a diagram illustrating an example of information stored in a test case recording unit; [Figure 10] FIG. 13 is a diagram illustrating an example of a duplicate test case display screen. [Figure 11] FIG. 13 is a diagram showing another example of the overlapping test case display screen. [Figure 12] 13 is a diagram illustrating an example of information on test policy combination candidates stored in a test policy candidate recording unit; FIG. [Figure 13] FIG. 13 is a diagram illustrating an example of a test policy candidate display screen. [Figure 14] FIG. 13 is a diagram showing another example of a test case display field on the test policy candidate display screen. [Figure 15] FIG. 13 is a diagram showing another example of the test policy candidate display screen. [Figure 16] FIG. 11 is a flow diagram illustrating an example of a test policy check process. [Figure 17] 11 is a diagram illustrating an example of a process based on first test policy information and a first test policy rule. FIG. [Figure 18] 13 is a diagram showing an example of a screen displayed on a screen of a user terminal as a result of processing based on first test policy information and a first test policy rule. FIG. [Figure 19] 13 is a diagram illustrating an example of a process based on second test policy information and a second test policy rule. FIG. [Figure 20] 13 is a diagram showing an example of a screen displayed on a screen of a user terminal as a result of processing based on second test policy information and a second test policy rule. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described with reference to the drawings. The test case generation support system of this embodiment generates test cases, which are data including combinations of factors (variables) and levels (values) that define the content of execution tests to be performed on a program under development (hereinafter, referred to as a target program). At this time, the test case generation support system generates test case groups (multiple test cases may be generated for each test policy) using multiple test policies, which are data that define the criteria for generating test cases.

[0011] Furthermore, the test case generation support system of this embodiment searches for overlapping test cases among the test case groups generated by each test policy, and displays information about the overlapping test cases, as well as information about other combinations of test policies (candidate test policy combinations) that minimize overlaps.

[0012] In addition, the test case generation support system checks whether there are any defect elements other than duplications between the test policies that would hinder the efficiency of execution testing of the target program in the group of test cases to be generated (for example, whether unnecessary test policies are included).

[0013] These functions improve maintainability by reducing test policies, shorten the time required to generate test cases, and prevent defects from being overlooked due to an increase in test cases.

[0014] The type of language of the target program is not particularly limited, and the content of the target program is not particularly limited as long as it performs processing using variables.

[0015] 1 is a diagram showing an example of the configuration of a test case generation support system 1 according to this embodiment. The test case generation support system 1 includes a user terminal 20 and a test case generation support device 10. The user terminal 20 and the test case generation support device 10 are communicatively connected to each other via a wired or wireless communication network 5 such as the Internet, a LAN (Local Area Network), a WAN, or a dedicated line.

[0016] The user terminal 20 is an information processing device used by a user who generates test cases and performs execution tests of a target program. The test case generation support device 10 is an information processing device that generates test cases based on instructions from the user terminal 20 and displays information on unnecessary (contradictory or duplicated) test cases on the user terminal 20.

[0017] 2 is a diagram for explaining an example of functions provided in the test case generation support device 10. The test case generation support device 10 stores a combination generation program 110, a test policy candidate search program 120, and a test policy rule check program .

[0018] Of these, the combination generation program 110 has a test policy input unit 111 , a test policy recording unit 112 , a test case generation unit 113 , a factor level storage unit 114 , and a test case recording unit 115 .

[0019] The test policy input unit 111 sets a plurality of test policies and the maximum number of test cases (maximum number of test cases) to be generated by the test policies. The test policy recording unit 112 stores these test policies in the test policy information 700 described later.

[0020] In this embodiment, the test policies include full coverage, flow coverage, N-factor coverage, and simple coverage.

[0021] Exhaustive coverage is a policy that generates test cases for each combination of all factors and all levels.

[0022] Flow coverage is a policy that fixes the levels of certain factors (hereafter referred to as axes) among multiple factors, and generates test cases for the other factors (hereafter referred to as opponents) that set combinations of the factor and all levels.

[0023] N-factor coverage (N=1, 2, . . .) is a policy that generates test cases for each of N types of factors among multiple factors, with each combination of the factor and all levels.

[0024] Simple coverage is a policy in which, for a predetermined factor among a plurality of factors (for example, a factor that has an independent relationship with other factors), only a predetermined level is set in the test case.

[0025] Next, the factor level storage unit 114 stores factor level information that stores possible combinations of variables (factors) of the target program and the values ​​(levels) of the variables. The details of the factor level information will be described later.

[0026] The test case generation unit 113 specifies a plurality of test cases (test case group) to be generated from each test policy based on the factor level information for each test policy selected from the plurality of test policies set by the test policy input unit 111. The test case recording unit 115 stores information on the test case group to be generated.

[0027] Next, the test policy candidate search program 120 includes an overlap determination unit 121 , an overlap result recording unit 122 , an overlap result display unit 123 , a test policy search unit 124 , a test policy candidate recording unit 125 , and a test policy candidate display unit 126 .

[0028] The overlap determination unit 121 identifies overlapping test cases, which are test cases whose contents overlap with at least two or more test policies, from among the test case group identified by the test case generation unit 113. The overlap result recording unit 122 stores information on the identified test cases (test policy information 700).

[0029] Based on the test policy information stored in the test policy recording unit 112, the test policy search unit 124 identifies other combinations of test policies (test policy combination candidates) such that the number of test cases whose contents overlap between at least two or more test policies is less than the number of overlapping test cases identified by the overlap determination unit 121, and outputs information on the other combinations of the identified test policies. The test policy candidate recording unit 125 stores information on the identified combinations of test policies.

[0030] Furthermore, the test policy search unit 124 identifies the number of test cases (the number of unique test cases) whose contents are different from each other among the test cases generated based on the above-mentioned identified combinations of other test policies (test policy combination candidates), and outputs information on the above-mentioned identified combinations of other test policies when the number of identified test cases does not exceed the above-mentioned maximum number of test cases. The test policy candidate display unit 126 displays information on the identified combinations of test policies (test policy combination candidates).

[0031] Next, the test policy rule check program 130 has a test policy rule input unit 131 , a test policy rule recording unit 132 , a rule judgment unit 133 , a rule judgment result recording unit 134 , and a rule judgment result display unit 135 .

[0032] The test policy rule input unit 131 sets constraints between a plurality of test policies (hereinafter, referred to as test policy rules). The test policy rule recording unit 132 stores the set test policy rules in a test policy rule table 400, which will be described later.

[0033] The rule determination unit 133 identifies an inclusion relationship between the test policies regarding the test cases to be generated, based on the test policy rule table 400. That is, the rule determination unit 133 determines whether one test policy substantially includes another test policy, making the other test policy unnecessary.

[0034] Furthermore, the rule determination unit 133 identifies combinations of factors in test cases generated from test policies for each test policy related to flow coverage.

[0035] The rule decision result recording unit 134 stores the processing results of the rule decision unit 133 .

[0036] The rule determination result display unit 135 displays information on the inclusion relationship identified by the rule determination unit 133 .

[0037] Furthermore, the rule determination result display unit 135 outputs information on test policies having the same combination of factors identified by the rule determination unit 133. That is, the rule determination result display unit 135 outputs information on a combination of test policies related to flow coverage in which the axis and the partner are in a swapped relationship.

[0038] (factor level information) 3 is a diagram showing an example of factor level information 300. The factor level information 300 includes information on factors 301 (variables present in a target program) that can be set in a test case, and each level 302 at which the levels of factors that can be set in a test case (values ​​that can be set for variables in a target program) are set.

[0039] (Test policy rule table) 4 is a diagram showing an example of a test policy rule table 400. The test policy rule table 400 has data items of a rule number 401 in which the number of each test policy rule is set, a rule 402 in which the content of each test policy rule is set, and a description 403 in which an explanatory text of each test policy rule is set.

[0040] In the example shown in the figure, the test policy rules include a first test policy rule 404 which states that a test case generated from one test should not completely include a test case generated from the other test policy, and a second test policy rule 405 which states that the axis and the other party in a test policy related to one flow coverage should not be merely a swap of the axis and the other party in a test policy related to the other flow coverage.

[0041] 5 is a diagram showing an example of hardware included in the test case generation support device 10. The test case generation support device 10 includes a processor 11 (control device) such as a CPU (Central Processing Unit), a memory 12 such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a storage device 13 such as a HDD (Hard Disk Drive) or an SSD (Solid State Drive), an input device 14 such as a keyboard, a mouse, a touch panel, an output device 15 such as a display, and a communication device 16 including a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like. The user terminal 20 also includes a similar hardware configuration.

[0042] The functions of the functional units of each information processing device in the test case generation support system 1 described above are realized by the processor reading out a program from a memory or a storage device. Each program can be recorded on, for example, a portable or fixed recording medium and distributed. Note that all or a part of these programs may be realized using virtual information processing resources provided using a virtualization technology, a process space separation technology, or the like, such as a virtual server provided by a cloud system. Also, all or a part of these programs may be realized by a service provided by a cloud system via an API (Application Programming Interface), for example. Next, the processing performed by the test case generation support system 1 will be described.

[0043] 6 is a flow diagram illustrating an example of a test case generation support process that outputs information about overlapping test cases in test cases generated based on a test policy. The test case generation support process is started, for example, when a predetermined instruction is input from the user terminal 20.

[0044] First, the test policy input unit 111 of the test case generation support device 10 sets a test policy (s11: No). For example, the test policy input unit 111 accepts an input of a test policy from a user, or receives information of a test policy from another information processing device. The test policy recording unit 112 stores the set test policy in the test policy information 700.

[0045] 7 and 8 are diagrams showing an example of test policy information 700. The test policy information 700 has information on one or more test policies. One or more test cases (combinations of factors and levels) can be generated from one test policy. The test policy information 700 includes a test policy number 701 assigned to each test policy, and details 702 of the test policy (a method for generating a test case).

[0046] (First Policy Information) The test policy information shown in FIG. 7 (hereinafter referred to as first test policy information 700A) has a first test policy 711 that generates test cases by covering two factors among factors X, Y, and Z, a second test policy 712 that generates test cases by fixing the level of factor X and generating all combinations of the levels that factors Y and Z can take, and a third test policy 713 that generates test cases by fixing the level of factor Y and generating all combinations of the levels that factors X and Z can take.

[0047] (Second Policy Information) Test policy information 700 shown in FIG. 8 (hereinafter referred to as second test policy information 700B) has a fourth test policy 714 which generates test cases by fixing the level of factor X and generating all combinations of the levels that factors Y and Z can take; a fifth test policy 715 which generates test cases by fixing the level of factor Y and generating all combinations of the levels that factors X and Z can take; a sixth test policy 716 which fixes the levels of factors Y and Z and generates test cases that combine all levels that factor X can take; and a seventh test policy 717 which generates test cases by covering all factors between factors X, Y, and Z.

[0048] 6, when the test policy information 700 is set (s11: Yes), the test case generation unit 113 starts generating test cases (s12: No). For example, the test case generation unit 113 receives an input of an instruction to generate test cases from a user.

[0049] When the generation of test cases is started (s12: Yes), the test case generation unit 113 generates test cases corresponding to the respective test policies set in s11 (s13).

[0050] Specifically, the test case generation unit 113 selects a target test policy based on a predetermined selection criterion or by user specification from the test policy information 700. The test case generation unit 113 acquires the contents 702 of each selected test policy from the test policy information 700, and generates a combination of factors and levels (i.e., a test case) that satisfies the acquired test policy while extracting the contents of each factor 301 and level 302 from the factor level information 300.

[0051] The test case generation unit 113 stores each test case generated in s13 (s14).Then, the test case generation unit 113 searches for combinations of factors and levels that are the same between at least two or more test policies, i.e., test cases (hereinafter referred to as duplicate test cases), and other test cases (hereinafter referred to as unique test cases) (s15).

[0052] If the duplicate test case is found (s16: Yes), the duplicate determination unit 121 executes the process of s17. If the duplicate test case is not found (s16: No), the test case generation support process ends.

[0053] In s17, the test case recording unit 115 stores information about the overlapping test case identified in s15. In addition, the overlap determination unit 121 causes the screen of the user terminal 20 to display information about the overlapping test case.

[0054] 9 is a diagram showing an example of information stored by the test case recording unit 115 by the processing of s17. This information includes the number 901 of each test policy, the contents 902 of each test policy, the number 903 of test cases generated by each test policy, the number 904 of test cases that overlap with test cases generated by other test policies (duplicate test cases), and the number 905 of test cases that are not duplicate test cases (unique test cases) among all the test cases generated.

[0055] FIG. 10 is a diagram showing an example of a duplicate test case display screen on which information on a duplicate test case is displayed.

[0056] As shown in the figure, this overlapping test case display screen 1000 displays information on six types of combinations (test cases) of factors and levels for each of three test policies A, B, and C.

[0057] Specifically, for each test policy, a list 1003 of test cases generated from that test policy is displayed on the overlapping test case display screen 1000. Test cases with the same factors and levels are displayed aligned at the same height (row). A frame 1004 is displayed surrounding test cases with the same factors and levels. On the other hand, test cases with different factors or levels are displayed at different heights (rows).

[0058] Furthermore, the overlapping test case display screen 1000 displays, for each test policy, a total number 1001 of test policies generated from that test policy and a number 1002 of overlapping test cases.

[0059] Additionally, the overlapping test case display screen 1000 displays the number of unique test cases 1005 and the number of overlapping test cases 1006 in all test policies.

[0060] 11 is a diagram showing another example of the overlapped test case display screen. In this overlapped test case display screen 1100, a combination of each level for each factor 1101 is displayed at each height (row), and a list 1104 of numbers of test policies that generate test cases based on the combination of the factors 1101 and levels is displayed at each corresponding height (row). In other words, when two or more test policy numbers are displayed in the list 1104 of test policy numbers, the test cases corresponding to the test policies are overlapped test cases. In the overlapped test case display screen 1100, a frame 11105 that surrounds the rows related to such overlapped test cases is displayed.

[0061] Additionally, the overlapping test case display screen 1000 displays the number 1106 of unique test cases and the number 1107 of overlapping test cases in all test policies.

[0062] Next, as shown in FIG. 6, the test policy search unit 124 searches for a combination of test policies (hereinafter, called a test policy combination candidate) that results in a smaller number of overlapping test cases (overlap number) than the number of overlapping test cases identified in s15 (s18).

[0063] Specifically, the test policy search unit 124 acquires the contents 702 of all test policies in the test policy information 700, and generates all test cases for all test policies based on the acquired contents 702 of each test policy and the factor level information 300. The test policy search unit 124 selects a certain combination of test policies from all test policies, and identifies differences and similarities between the test cases related to each selected test policy, thereby counting the number of test cases (test cases with the same factors and levels) that are common to at least two or more test policies (the number of overlaps).

[0064] The test policy search unit 124 performs this counting process for all combinations of test policies. The test policy search unit 124 searches for a combination of test policies (candidate test policy combination) whose number of overlaps is less than the number of overlapping test cases identified in s15, from among the combinations of test policies whose number of overlaps has been counted.

[0065] The method of identifying test policy combination candidates described here is merely an example, and is not particularly limited.

[0066] The test policy search unit 124 judges whether or not a test policy combination candidate has been found in s18 (s19). If a test policy combination candidate has been found (s19: Yes), the test policy search unit 124 executes the process of s20, and if a test policy combination candidate has not been found (s19: No), the test case generation support process ends.

[0067] In s20, the test policy search unit 124 identifies test policy combination candidates having unique test cases that do not exceed the maximum number of test cases from among the test policy combination candidates identified in s18.

[0068] Then, the test policy candidate recording unit 125 stores information on the test policy combination candidates identified in s20. Furthermore, the test policy searching unit 124 causes the information on the test policy combination candidates to be displayed on the screen of the user terminal 20 (s21).

[0069] 12 is a diagram showing an example of information on a test policy combination candidate stored in the test policy candidate recording unit 125. This information includes a test policy combination candidate number 1201 and information 1202 on each test policy constituting the test policy combination candidate.

[0070] (Test policy candidate display screen) 13 is a diagram showing an example of a test policy candidate display screen that displays test policy combination candidates. This test policy candidate display screen 1300 has a test policy candidate display field 1310 that displays test policy combination candidates, and one or more test case display fields 1320 that display a list of each test case generated by each test policy combination candidate.

[0071] In the test policy candidate display field 1310, for each of the searched test policy combination candidates 1311, the contents 1312 of the test policies that make up the test policy combination candidate are displayed.

[0072] The test case display field 1320 displays, for each searched test policy combination candidate 1311, a total number 1322 of test cases generated based on each test policy in that test policy combination candidate 1311, and a total number 1323 of test cases that overlap with test cases generated by other test policies (having the same factors and levels).

[0073] A list 1324 of test cases generated from each test policy in the test policy combination candidates is displayed in an aligned manner in a test case display field 1320. In this test case list 1324, test cases having the same factors and levels (duplicate test cases) are displayed at the same height. A frame 1325 is displayed surrounding the test cases having the same factors and levels.

[0074] Furthermore, the test case display field 1320 displays a total number 1326 of unique test cases generated by each test policy in the test policy combination candidate, and a total number 1327 of duplicate test cases. This total number 1327 of duplicate test cases is less than the total number of duplicate test cases identified in s15.

[0075] 14 is a diagram showing another example of the test case display field of the test policy candidate display screen. In this test case display field 1330, a combination of each level for each factor 1331 is displayed at each height (row), and a list 1332 of IDs of test policies that generate test cases based on the combination of the factors 1331 and levels is displayed at each corresponding height (row). In other words, when two or more test policies are displayed in the list 1332 of test policy IDs, the test cases corresponding to those test policies are overlapping test cases. In the test case display field 1330, a frame 1333 that surrounds the rows related to such overlapping test cases is displayed.

[0076] (Test policy candidate display screen) 15 is a diagram showing another example of a test policy candidate display screen. A test policy candidate display field 1510 in this test policy candidate display screen 1500 displays a first test policy combination candidate 1511 having a total number of 11 unique test cases and a total number of 7 overlapping test cases, and a second test policy combination candidate 1512 having a total number of 12 unique test cases and a total number of 0 overlapping test cases.

[0077] Here, if the maximum number of test cases is 11, the test case display field 1520 displays only a list 1521 of test cases generated by the first test policy combination candidate 1511 in which the total number of unique test cases does not exceed the maximum number of test cases.

[0078] <Test policy check process> 16 is a flow diagram illustrating an example of a test policy check process for checking the test policy set in the test case generation support process. The test policy check process is started, for example, when a predetermined instruction is input from the user terminal 20.

[0079] First, the test policy rule input unit 131 sets a test policy rule for checking a test policy (s21: No). For example, the test policy rule input unit 131 accepts an input of a test policy from a user, or receives information of a test policy from another information processing device. Then, the test policy rule recording unit 132 stores the set test policy in the test policy rule table 400.

[0080] When a test policy rule is set (s21: Yes), the rule determination unit 133 searches for a combination of test policies that violates the test policy rule based on the test policy rule table 400 set in s21 and the test policy information 700 set in s11 of the test case generation support process (s22).

[0081] The rule determination result recording unit 134 stores information about the combination of test policies that violates the test policy rule, which was found in s22. In addition, the rule determination unit 133 causes the screen of the user terminal 20 to display information about the combination of test policies that violates the test policy rule.

[0082] 17 is a diagram for explaining an example of the process s22 based on the first test policy information 700A and the first test policy rule 404. As shown in the figure, there is no inclusion relationship between a test case group 1701 generated by the first test policy 711 and a test case group 1702 generated by the second test policy 712, so the rule determination unit 133 determines that the combination of the first test policy 711 and the second test policy 712 does not violate the first test policy rule.

[0083] Furthermore, since the test case group 1703 generated by the third test policy 713 completely encompasses the test case group 1704 generated by the first test policy 711, the rule determination unit 133 determines that the combination of the third test policy 713 and the first test policy 711 violates the first test policy rule 404.

[0084] Furthermore, since the test case group 1705 generated by the third test policy 713 completely encompasses the test case group 1706 generated by the second test policy 712, the rule determination unit 133 determines that the combination of the second test policy 712 and the third test policy 713 violates the first test policy rule 404.

[0085] 18 is a diagram showing an example of a screen displayed on the screen of the user terminal 20 as a result of the process s22 based on the first test policy information 700A and the first test policy rule 404. As shown in the figure, the screen of the user terminal 20 displays a message indicating that the combinations of test policies that violate the first test policy rule 404 include the combination of the third test policy 713 and the first test policy 711, and the combination of the second test policy 712 and the third test policy 713.

[0086] 19 is a diagram for explaining an example of the process s22 based on the second test policy information 700B and the second test policy rule 405. As shown in the figure, the axis and the partner factor in the test case 1901 generated by the fourth test policy 714 and the axis and the partner factor in the test case 1902 generated by the fifth test policy 7125 are not in a relationship in which the axis and the partner are interchanged with each other. Therefore, the rule determination unit 133 determines that the combination of the fourth test policy 714 and the fifth test policy 715 does not violate the second test policy rule 405.

[0087] In addition, the axis and the other factor in the test case 1903 generated by the fifth test policy 715 and the axis and the other factor in the test case 1904 generated by the sixth test policy 716 are not in a relationship of swapping the axis and the other factor with each other. Therefore, the rule determination unit 133 determines that the combination of the fifth test policy 715 and the sixth test policy 716 does not violate the second test policy rule 405.

[0088] In addition, the axis and the other factor in the test case 1905 generated by the fourth test policy 714 and the axis and the other factor in the test case 1906 generated by the sixth test policy 716 are in a relationship in which the axis and the other factor are swapped. Therefore, the rule determination unit 133 determines that the combination of the fourth test policy 714 and the sixth test policy 716 violates the second test policy rule 405.

[0089] 20 is a diagram showing an example of a screen displayed on the screen of the user terminal 20 as a result of the process s22 based on the second test policy information 700B and the second test policy rule 405. As shown in the figure, the screen of the user terminal 20 displays a message indicating that the combination of the fourth test policy 714 and the sixth test policy 716 is a combination of test policies that violates the second test policy rule 405.

[0090] As described above, the test case generation support device 10 of this embodiment identifies, for each test policy, a group of test cases to be generated based on the test policy, which is data that specifies the combination of factors and levels in a test case, identifies overlapping test cases from the identified group of test cases, whose contents overlap between at least two or more test policies, and outputs information on the identified overlapping test cases.

[0091] In this way, the test case generation support device 10 of the present embodiment outputs information on test cases that are generated in duplicate when test cases are generated based on multiple test policies. This allows the user to discover unnecessary test cases or test policies that make the test process redundant. This allows efficient execution testing of the program.

[0092] As described above, the test case generation support device 10 of this embodiment can support efficient program testing.

[0093] In addition, based on the test policy information 700, the test case generation support device 10 of this embodiment identifies other combinations of test policies (candidate test case combinations) such that the number of test cases whose contents overlap between at least two or more test policies is less than the number of overlapping test cases, and outputs information about the identified candidate test case combinations.

[0094] In this way, by identifying other combinations of test policies that result in less overlapping test cases, more efficient execution testing of the program can be performed.

[0095] In addition, the test case generation support device 10 of this embodiment identifies the number of test cases (unique test cases) whose contents differ from each other among the test policies in the test case combination candidate, which are generated based on the combination of other test policies identified above (test case combination candidate), and outputs information about the test case combination candidate if the number of identified unique test cases does not exceed the maximum number of test cases.

[0096] In this way, by outputting information on only test case combination candidates for which the number of generated unique test cases does not reach a certain number, it is possible to prevent the test process from becoming excessive and defects from being overlooked during testing.

[0097] Moreover, the test case generation support device 10 of this embodiment identifies inclusion relationships between the test policies regarding the test cases to be generated, and outputs information on the identified inclusion relationships.

[0098] This makes it possible to find cases where one test policy includes another test policy, making the other test policy unnecessary and leading to redundancy in the test process.

[0099] Furthermore, the test case generation support device 10 of this embodiment identifies, for each test policy, a combination of factors in a test case generated from the test policy, and outputs information on a combination of test policies having the same combination of factors.

[0100] This makes it possible to identify cases where the axis and the other party are in a swapped relationship between multiple flow coverages, and to discover cases that could lead to redundancy in the testing process.

[0101] The present invention is not limited to the above-described embodiment, and can be implemented using any components without departing from the scope of the present invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these contents as long as the features of the invention are not impaired. In addition, although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical idea of ​​the present invention are also included in the scope of the present invention.

[0102] For example, part of the hardware included in each device of this embodiment may be provided in another device.

[0103] Furthermore, each program of each device may be provided in another device, a program may consist of multiple programs, or multiple programs may be integrated into one program.

[0104] Furthermore, the test policies and policy rules described in this embodiment are merely examples, and the present invention is also applicable to other types of test policies and policy rules.

[0105] In addition, in this embodiment, information about unnecessary test cases such as duplicate test cases is displayed on the screen, but test cases other than these unnecessary test cases may actually be generated and stored so that they can be used for testing the target program. [Explanation of symbols]

[0106] 1 Test case generation support system, 10 Test case generation support device, 113 Test case generation unit, 121 Duplication determination unit, 124 Test policy search unit, 133 Rule determination unit

Claims

1. An apparatus for supporting generation of test cases, which are data including combinations of factors and levels, used in an execution test of a predetermined program, comprising: a storage device that stores a test policy, which is data that specifies combinations of factors and levels in a plurality of test cases; and a duplication determination process for determining a test case group generated based on a test policy for each test policy selected from the plurality of test policies, and determining a duplicate test case, which is a test case whose contents are duplicated between at least two or more test policies, from the determined test case group; a control device that executes a duplicate result output process that outputs information on the identified duplicate test cases; A test case generation support device comprising:

2. the control device executes a test policy search process, based on the information of the plurality of test policies, to identify other combinations of test policies such that the number of test cases having overlapping contents between at least two or more test policies is less than the number of the overlapping test cases, and to output information on the other combinations of the identified test policies.

2. The test case generation support device according to claim 1.

3. The storage device stores a maximum value of the number of test cases; the control device, in the test policy search process, identifies the number of test cases whose contents differ between each test policy in the combination of test policies among the test cases generated based on other combinations of the identified test policies, and outputs information on the other combinations of the identified test policies when the number of identified test cases does not exceed the maximum value.

3. The test case generation support device according to claim 2.

4. the control device executes a rule determination process for identifying an inclusion relationship between the test policies with respect to the test cases to be generated, and outputting information on the identified inclusion relationship; 2. The test case generation support device according to claim 1.

5. the control device executes a rule determination process for identifying a combination of factors in a test case generated from each of the test policies, and outputting information on a combination of test policies having the same combination of factors; 2. The test case generation support device according to claim 1.

6. A method for supporting generation of test cases, which are data including combinations of factors and levels, used in an execution test of a predetermined program, by an information processing device having a control device and a storage device, comprising: The storage device stores a test policy, which is data that specifies a combination of factors and levels in a plurality of test cases; The control device includes: a duplication determination process for determining a test case group generated based on a test policy for each test policy selected from the plurality of test policies, and determining a duplicate test case, which is a test case whose contents are duplicated between at least two or more test policies, from the determined test case group; and executing a duplicate result output process for outputting information on the identified duplicate test cases. A method for assisting in test case generation.

7. the control device executes a test policy search process, based on the information of the plurality of test policies, to identify other combinations of test policies such that the number of test cases having overlapping contents between at least two or more test policies is less than the number of the overlapping test cases, and to output information on the other combinations of the identified test policies.

7. The test case generation support method according to claim 6.

8. The storage device stores a maximum value of the number of test cases; In the test policy search process, the control device identifies the number of test cases whose contents are different between each test policy in the combination of test policies among the test cases generated based on other combinations of the identified test policies, and outputs information on the other combinations of the identified test policies when the number of identified test cases does not exceed the maximum value.

8. The method for supporting test case generation according to claim 7.

9. the control device executes a rule determination process for identifying an inclusion relationship between the test policies with respect to the test cases to be generated, and outputting information on the identified inclusion relationship; 7. The test case generation support method according to claim 6.

10. the control device executes a rule determination process for identifying a combination of factors in a test case generated from each of the test policies, and outputting information on a combination of test policies having the same combination of factors; 7. The test case generation support method according to claim 6.

Images