Test scenario generation system and test scenario generation method

Abstract

To support generation of a test scenario for further improving coverage of a test.SOLUTION: A test scenario generation system includes a test scenario database that includes a processor and a memory and stores a test scenario described using one or more keywords representing an operation and a target of the operation, and an additional test scenario generation unit that generates a new test scenario by comparing a first test scenario stored in the test scenario database with a second test scenario different from the first test scenario and adding a keyword included only in the second test scenario to the first test scenario.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a test scenario generation system and a test scenario generation method. [Background technology]

[0002] Keyword-driven testing, in which the execution test procedures for a program are described using "keywords" not only for the contents of the test data but also for the operations on the test data, is a testing method that can improve the efficiency and maintainability of test scenario creation by reusing keywords (test procedures), as well as the readability of test scenarios.

[0003] Patent Document 1 discloses a generating device that automatically generates keywords for keyword-driven testing based on test code and design information.

[0004] Furthermore, Patent Document 2 discloses a test scenario variation generation device that generates new test scenarios for software to be tested from test scenarios created in test design for software other than the software to be tested. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent Publication No. 2021-179764 [Patent Document 2] Japanese Patent Application Laid-Open No. 2015-22356 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the technology described in Patent Document 1 generates test scenarios from existing test code, so the test code must already exist. Furthermore, the technology described in Patent Document 2 assumes the existence of test scenarios for other products (software). It is difficult to comprehensively generate appropriate keyword lists and test scenarios in the early stages of development when test code and test scenarios for other products do not exist. In particular, since test scenarios are generally generated for each function (e.g., software module), it is difficult with the above-mentioned technology to comprehensively generate tests, including test scenarios for verifying defects caused by interrupts in the operation of different functions.

[0007] The present invention has been made in light of the above circumstances, and its purpose is to provide a test scenario generation system and a test scenario generation method that can support the generation of test scenarios that further improve test coverage. [Means for solving the problem]

[0008] One aspect of the present invention for solving the above problems is a test scenario generation system having a processor and a memory, and including a test scenario database that stores test scenarios written using one or more keywords that represent operations and targets of the operations, and an additional test scenario generation unit that compares a first test scenario stored in the test scenario database with a second test scenario that is different from the first test scenario, and generates a new test scenario by adding keywords that are contained only in the second test scenario to the first test scenario. [Effects of the Invention]

[0009] According to the present invention, it is possible to support the generation of test scenarios that further improve the coverage of tests. Configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of the configuration of a test scenario generation system. [Figure 2] FIG. 2 illustrates an example of a functional configuration of a test scenario generation support device. [Figure 3] FIG. 2 illustrates an example of a hardware configuration of a test scenario generation support device. [Figure 4] FIG. 10 is a process flow diagram illustrating an additional keyword generation process. [Figure 5] FIG. 10 is a diagram illustrating an example of an initial keyword list. [Figure 6] FIG. 10 is a diagram illustrating an example of a keyword matrix. [Figure 7] FIG. 10 is a diagram showing an example of an additional keyword display screen. [Figure 8] FIG. 10 is a diagram illustrating an example of an additional keyword list. [Figure 9] FIG. 10 is a process flow diagram illustrating an additional test scenario generation process. [Figure 10] FIG. 10 is a diagram for explaining an outline of an additional test scenario generation process. [Figure 11] FIG. 10 is a process flow diagram illustrating a merge test scenario generation process. [Figure 12] FIG. 10 is a diagram illustrating an example of an additional test scenario display screen. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings. In the following explanation, various types of information may be described using expressions such as "table," "list," and "queue," but the various types of information may also be expressed using data structures other than these. To indicate that the information is not dependent on the data structure, "XX table," "XX list," etc. may be referred to as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable. When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. However, when there is no need to distinguish between these multiple components, the subscripts may be omitted. Furthermore, in the following description, processing performed by executing a program may be described, but the program is executed by a processor (e.g., a CPU or a GPU) to perform the specified processing while appropriately using storage resources (e.g., a memory) and / or interface devices (e.g., a communication port), and therefore the subject of the processing may be the processor. Similarly, the subject of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing a program may be any computing unit, and may include a dedicated circuit (e.g., an FPGA or an ASIC) that performs a specific processing. A program may be installed on a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0012] <Test scenario generation system> Figure 1 illustrates an example configuration of a test scenario generation system. In software development ordered by a customer, defects can arise due to the customer's operating environment or a misunderstanding or lack of understanding of the requirements. Therefore, in the early stages of development, it is possible to design test scenarios based on keyword-driven testing and then discuss them with the customer to provide feedback on the requirements specification. However, defects arising from the customer's operating environment or a misunderstanding or lack of understanding of the requirements are often caused by the interruption of the operation of different functions (e.g., software modules, hereinafter simply referred to as "modules"). Therefore, it is necessary to generate test scenarios that include the interruption of the operation of other modules. However, in software development, different developers often work on different modules, and developers may lack understanding of modules other than the one they are responsible for. Therefore, in keyword-driven testing, test scenarios are typically generated for each module. Therefore, in the early stages of development, it is difficult to comprehensively generate a list of keywords and test scenarios that can detect defects caused by the interruption of different modules.

[0013] Therefore, the test scenario generation system 1 according to this embodiment analyzes the keyword list and test scenario for each module, and automatically generates a new keyword list and test scenario from a perspective that the developer is not aware of.

[0014] Here, a test scenario is data in which one or more keywords are registered (described) along with the execution order. In this embodiment, an example will be described in which keywords are registered in the test scenario in the order of execution from the beginning of the data to the end. A keyword is data that represents an "operation" and the "target" of the operation. A "target" is the target of the operation (e.g., data, object), and an "operation" is an operation on the target (e.g., action, data processing). For example, a keyword related to a user interface includes a user operation (e.g., "click") on a user's operation target (e.g., "calculate button"). Furthermore, a keyword related to an API (Application Programming Interface) includes processing on data to be sent and received (e.g., "request" or "response").

[0015] The test scenario generation system 1 includes a test scenario generation support device 10 and a generation AI (Generative Artificial Intelligence) 20.

[0016] The generation AI 20 is, for example, a large language model (LLM). The generation AI 20 receives a design specification 310 of the software (system) to be tested and a generation AI prompt 320 as input, and outputs an initial keyword list 330, a module list 340, and an initial test scenario list 350 to be input to the test scenario generation support device 10. The generation AI prompt 320 includes instructions for extracting the initial keyword list 330, the module list 340, and the initial test scenario list 350 from the design specification 310. The initial keyword list 330 is a list of keywords in keyword-driven testing. The module list 340 is a list of modules included in the software. The initial test scenario list 350 is a list of test scenarios for keyword-driven testing for each module.

[0017] The test scenario generation support device 10 is an information processing device that receives an initial keyword list 330, a module list 340, and an initial test scenario list 350 as input, and generates and outputs an additional keyword list 360 and an additional test scenario list 370. The test scenario generation system 1 outputs a keyword list 380 that combines the initial keyword list 330 and the additional keyword list 360, and a test scenario list 390 that combines the initial test scenario list 350 and the additional test scenario list 370. Note that the test scenario generation support device 10 may also output the keyword list 380 and the test scenario list 390.

[0018] <Test scenario generation support device> 2 is a diagram showing an example of the functional configuration of a test scenario generation support device 10. The test scenario generation support device 10 includes functional units: a keyword list input unit 101, an additional keyword generation unit 103, a test scenario input unit 104, and an additional test scenario generation unit 106. The test scenario generation support device 10 also stores a keyword database 102 and a test scenario database 105.

[0019] The keyword list input unit 101 receives the initial keyword list 330 and the module list 340 as input, and stores the input initial keyword list 330 in the keyword database 102. At this time, the keyword list input unit 101 may refer to the module list 340 and store the keywords in the initial keyword list 330 for each module in the keyword database 102.

[0020] The keyword database 102 is a database that stores the keywords included in the initial keyword list 330 and the keywords generated by the additional keyword generating unit 103 .

[0021] The additional keyword generation unit 103 generates additional keywords with reference to the keyword database 102, and outputs an additional keyword list 360, which is a list of the generated keywords. The additional keyword generation unit 103 also stores the generated additional keywords in the keyword database 102.

[0022] The test scenario input unit 104 receives the module list 340 and the initial test scenario list 350 as input, and stores the test scenarios in the input initial test scenario list 350 for each module in the test scenario database 105 by referring to the module list 340.

[0023] The test scenario database 105 is a database that stores the test scenarios included in the initial test scenario list 350 for each module to be tested.

[0024] The additional test scenario generation unit 106 references the keyword database 102 and the test scenario database 105 to generate additional test scenarios, and outputs an additional test scenario list 370, which is a list of the generated test scenarios.

[0025] The programs that realize the functions of the keyword list input unit 101, the additional keyword generation unit 103, the test scenario input unit 104, and the additional test scenario generation unit 106 can be recorded on, for example, a portable or fixed recording medium and distributed.

[0026] 3 is a diagram showing an example of the hardware configuration of a test scenario generation support device 10. As an example, the test scenario generation support device 10 includes a processing device 11 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 an HDD (Hard Disk Drive) or an SSD (Solid State Drive), an input device 14 such as a keyboard, a mouse, or a touch panel, an output device 15 such as a display or a printer, and a communication device 16 configured by a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like.

[0027] In the test scenario generation support device 10, data such as programs that realize the functions of the keyword list input unit 101, the additional keyword generation unit 103, the test scenario input unit 104, and the additional test scenario generation unit 106 are, for example, stored in the storage device 13, and the processing device 11 reads them into the RAM of the memory 12 and executes them.

[0028] Next, the processing performed by the test scenario generation support device 10 will be described.

[0029] <Additional keyword generation process> 4 is a process flow diagram explaining the additional keyword generation process executed by the additional keyword generation unit 103. The additional keyword generation process is executed, for example, when a predetermined input is made by the user to the test scenario generation support device 10 (for example, when the initial keyword list 330 and the module list 340 are input), or at a predetermined timing (for example, at a predetermined time, at a predetermined time interval, etc.).

[0030] First, the additional keyword generating unit 103 extracts a keyword from the keyword database 102, breaks down the extracted keyword into an "object" and an "operation," and registers each of these in a keyword matrix (S101).

[0031] (Initial keyword list) 5 is a diagram showing an example of an initial keyword list. In the example shown, the initial keyword list 330 includes the keywords “click the calculation button,” “select the tax-inclusive check box,” “enter a value in the unit price field,” and “clear the value in the unit price field.”

[0032] For example, the additional keyword generation unit 103 decomposes the keyword "click the calculation button" into the object "calculation button" and the operation "click". The additional keyword generation unit 103 also decomposes the keyword "select tax-inclusive check" into the object "tax-inclusive check" and the operation "select". The additional keyword generation unit 103 also decomposes the keyword "enter a value in the unit price field" into the object "unit price field" and the operation "enter a value". The additional keyword generation unit 103 also decomposes the keyword "delete the value in the unit price field" into the object "unit price field" and "delete the value". The additional keyword generation unit 103 then registers the decomposed objects and operations in the keyword matrix.

[0033] (Keyword Matrix) 6 is a diagram showing an example of a keyword matrix. In the illustrated example, keyword matrix 400 is data in a matrix format with each object as a row and each operation as a column. A "◯" at the intersection of an object and an operation in keyword matrix 400 indicates that the object is registered in keyword database 102, and an "X" indicates that the object is not registered in keyword database 102. For example, in the illustrated example, the keyword "click the calculation button", which is a combination of the object "calculate button" and the operation "click", is registered in keyword database 102, while the keyword "select the calculation button", which is a combination of the object "calculate button" and the operation "select", is not registered in keyword database 102.

[0034] Although FIG. 6 illustrates the keyword matrix 400 for all modules, the additional keyword generation unit 103 may generate the keyword matrix 400 for each module depending on the scale of the software (system) to be tested.

[0035] Next, the additional keyword generation unit 103 determines whether or not any remaining keywords (keywords that have not been broken down into targets and operations) are registered in the keyword database 102 (S102). If there are any remaining keywords (S102: Yes), the additional keyword generation unit 103 returns to the process of S101 and breaks down the remaining keywords into targets and operations.

[0036] On the other hand, if there are no remaining keywords (S102: No), the additional keyword generation unit 103 selects one registered object and one registered operation, and sets the combination as an additional keyword candidate (S103). For example, the additional keyword generation unit 103 sets the keyword "select calculation button", which is a combination of the object "calculation button" and the operation "select", as a keyword candidate.

[0037] Next, the additional keyword generation unit 103 determines whether or not the generated additional keyword candidate is registered in the keyword database 102 (S104). If the additional keyword candidate is registered in the keyword database 102 (S104: Yes), the additional keyword generation unit 103 proceeds to the processing of S106.

[0038] On the other hand, if the additional keyword candidate is not registered in the keyword database 102 (S104: No), the additional keyword generation unit 103 presents the additional keyword candidate to the developer (user) as an additional keyword (S105). For example, the additional keyword generation unit 103 displays the additional keyword candidate on a predetermined display device or a user terminal used by the developer.

[0039] Next, the additional keyword generation unit 103 determines whether all combinations of targets and operations registered in the keyword matrix 400 have been set as additional keyword candidates (S106). If all combinations of targets and operations have not been set as additional keyword candidates (S106: No), the additional keyword generation unit 103 returns to the processing of S103. On the other hand, if all combinations of targets and operations have been set as additional keyword candidates (S106: Yes), the additional keyword generation unit 103 ends this additional keyword generation processing.

[0040] In the above flow, the additional keyword generation unit 103 breaks down the keywords into targets and operations in S101, but this is not limiting, and the keywords may be broken down into targets and operations in advance and registered in the initial keyword list 330 or the keyword database 102. For example, the generation AI 20 may generate the initial keyword list 330 of keywords broken down into operations and targets.

[0041] Furthermore, in the above-described flow, the additional keyword generating unit 103 presents additional keyword candidates to the developer one by one, but this is not limiting, and the developer may be allowed to select keywords to be added all at once.

[0042] (Additional keyword display screen) FIG. 7 is a diagram illustrating an example of an additional keyword display screen. The additional keyword display screen 500 is a display screen that presents keywords to be added to a developer. The additional keyword display screen 500 shown in this figure allows the developer to select all keywords to be added at once. The additional keyword display screen 500 includes a first area 510 for inputting keywords to be added and an add button 520. The first area 510 displays the keyword matrix 400 and accepts the selection and input of keywords to be added. In the first area 510, keywords registered in the keyword database 102 (intersections of combinations of targets and operations) are marked with a "◯" and keywords not registered in the keyword database 102 (intersections of combinations of targets and operations) are marked with a check box. The developer selects keywords to be added by checking the check box. In the illustrated example, the developer has selected the keyword "Enter value in calculation button," which combines the object "Calculate button" and the operation "Enter value," and the keyword "Deselect tax-included check," which combines the object "Tax included check" and the operation "Deselect."

[0043] When the additional keyword generation unit 103 receives an input from the developer to press the Add button 520 while a keyword is selected in the first area 510, the additional keyword generation unit 103 registers the selected keyword in the additional keyword list 360. Note that the additional keyword display screen 500 may display an operation guide for the developer, such as "Check the keyword you want to add and click the Add button."

[0044] (Additional Keyword List) 8 is a diagram showing an example of an additional keyword list. In the example shown, the additional keywords included in the additional keyword list 360 are "Enter a value in the calculation button" and "Deselect the tax included check box."

[0045] <Additional test scenario generation process> 9 is a process flow diagram explaining the additional test scenario generation process executed by the additional test scenario generation unit 106. The additional keyword generation process is executed, for example, when a predetermined input is made by the user to the test scenario generation support device 10 (e.g., when the module list 340 and the initial test scenario list 350 are input), or at a predetermined timing (e.g., at a predetermined time, at a predetermined time interval, etc.).

[0046] 10 is a diagram for explaining an outline of the additional test scenario generation process, which will be specifically explained below using the data example shown in FIG.

[0047] First, the additional test scenario generation unit 106 retrieves a test scenario from the test scenario database 105 and extracts keywords contained in the retrieved test scenario (hereinafter, sometimes referred to as the "target test scenario") (S201). For example, when the additional test scenario generation unit 106 retrieves test scenario #1 of module A shown in Fig. 10, it extracts the keywords "Enter a value in the unit price field," "Select the tax-inclusive check box," and "Click the calculation button."

[0048] Next, the additional test scenario generation unit 106 breaks down the extracted keywords into targets and operations, and collects the target parts (S202). For example, in the case of test scenario #1 of module A shown in Figure 10, the additional test scenario generation unit 106 acquires the "unit price field," "tax included check," and "calculation button."

[0049] Next, the additional test scenario generation unit 106 extracts test scenarios that use the acquired target (hereinafter, sometimes referred to as "related test scenarios") from the test scenarios of other modules (S203). In the example shown in Fig. 10, the additional test scenario generation unit 106 extracts test scenario #6 of module B that includes the keyword "enter a value in the unit price field" that targets the "unit price field."

[0050] Next, the additional test scenario generator 106 executes the merge test scenario generation process using the extracted related test scenarios (S204).

[0051] <Merge test scenario generation process> 11 is a process flow diagram illustrating the merge test scenario generation process executed by the additional test scenario generator 106. The process shown in this diagram corresponds to the process in step S204 described above.

[0052] First, the additional test scenario generation unit 106 lists the keywords included in the extracted related test scenarios (S301). For example, in the example shown in Fig. 10, the additional test scenario generation unit 106 extracts the keywords "Enter a value in the unit price field" and "Delete the value in the unit price field" from test scenario #6 of module B.

[0053] Next, the additional test scenario generation unit 106 determines whether any of the listed keywords does not appear (is not included) in the target test scenario (S302). If there is no keyword that does not appear in the target test scenario (S302: No), the additional test scenario generation unit 106 ends the merge test scenario generation process.

[0054] On the other hand, if there are keywords that do not appear in the target test scenario (S302: Yes), the additional test scenario generation unit 106 presents the target test scenario and the keywords to be added to the developer (S303). The keywords to be added are keywords that do not appear in the target test scenario. For example, in the example shown in Figure 10, the keyword "delete the value of the unit price field" in test scenario #6 of module B does not appear in test scenario #1 of module A, so the keyword "delete the value of the unit price field" is the keyword that should be added.

[0055] (Additional test scenario display screen) 12 is a diagram showing an example of an additional test scenario display screen. The additional test scenario display screen 600 is a display screen that suggests to the developer whether keywords used in related test scenarios can be added to the target test scenario. The additional test scenario display screen 600 includes an eleventh area 610 that displays the target test scenarios in the order of the keywords to be executed, a twelfth area 620 that displays additional keywords that are keywords to be added, a thirteenth area 630 that displays related test scenarios, a fourteenth area 640 that displays candidate additional scenarios, and an add button 650. The eleventh area 610 includes a check box that specifies the insertion location (insertion position) at which the additional keyword is to be inserted.

[0056] When a developer selects a checkbox in the eleventh area 610, the additional test scenario generation unit 106 displays an additional test scenario candidate in the fourteenth area 640, in which an additional keyword has been added to the specified location. In the illustrated example, the part between "Select the tax-inclusive check box" and "Click the Calculate button" in test scenario #1 of module A is specified as the location for adding the additional keyword "Clear the value in the unit price field." Therefore, the additional test scenario generation unit 106 displays an additional test scenario candidate in the fourteenth area 640, in which the additional keyword "Clear the value in the unit price field" has been inserted between "Select the tax-inclusive check box" and "Click the Calculate button" in test scenario #1. That is, the additional test scenario generation unit 106 displays an additional test scenario candidate in the fourteenth area 640, in which the keywords are executed in the following order: "Enter a value in the unit price field," "Select the tax-inclusive check box," "Clear the value in the unit price field," and "Click the Calculate button." The additional test scenario display screen 600 may also display an operation guide for the developer, such as "Select the location where you want to insert the keyword and click the Add button."

[0057] When the additional test scenario generation unit 106 receives input from the developer pressing the Add button 650, it generates the additional test scenario candidate displayed in the fourteenth area 640 as a merge test scenario (S304). The additional test scenario candidate is a test scenario in which additional keywords have been added to the addition locations specified by the developer.

[0058] Next, the additional test scenario generation unit 106 determines whether there are any remaining keywords that do not appear in the target test scenario (S305). If there are any remaining keywords (S305: Yes), the additional test scenario generation unit 106 returns to the processing of S303. On the other hand, if there are no remaining keywords (S305: No), the merge test scenario generation process ends.

[0059] Returning to FIG. 9, the additional test scenario generation unit 106 then adds the generated merge test scenario to the additional test scenario list 370 as an additional test scenario (S205).

[0060] Next, the additional test scenario generation unit 106 determines whether or not additional test scenarios have been generated (the processes of S201 to S205 described above have been executed) for all test scenarios registered in the test scenario database 105 (S206). If the additional test scenario generation unit 106 has not executed the processes for all test scenarios (S206: No), the additional test scenario generation unit 106 returns to the process of S201. On the other hand, if the additional test scenario generation unit 106 has executed the processes for all test scenarios (S206: Yes), the additional test scenario generation unit 106 ends the additional test scenario generation process.

[0061] In the above flow, the additional test scenario generation unit 106 treats all keywords contained in the related test scenario as additional keywords, but this is not limited to this; it may also treat only the target keywords contained in the target test scenario as additional keywords.

[0062] In the above flow, the additional test scenario generation unit 106 inserts keywords included in the related test scenario into the target test scenario, but this is not limiting; additional keywords included in the additional keyword list 360 may also be inserted into the target test scenario. For example, the additional test scenario generation unit 106 may insert additional keywords of interest included in the target test scenario into the target test scenario.

[0063] In the above flow, the additional test scenario generation unit 106 defines a test scenario that includes the same target as the target of the target test scenario as a related test scenario, but this is not limited to this. A test scenario that includes the same keywords as the target test scenario may also be defined as a related test scenario.

[0064] As described above, the test scenario generation support device 10 of this embodiment stores a test scenario database 105 that stores test scenarios written using one or more keywords that represent an operation and the target of the operation, compares a first test scenario stored in the test scenario database 105 with a second test scenario that is different from the first test scenario, and generates a new test scenario by adding keywords that are included only in the second test scenario to the first test scenario.

[0065] That is, the test scenario generation support device 10 of this embodiment can generate new test scenarios by utilizing keywords used in other test scenarios. This makes it possible to generate new test scenarios from perspectives that the developer has not noticed, and can support the generation of test scenarios that improve the comprehensiveness of tests.

[0066] In addition, the test scenario generation support device 10 of this embodiment stores a test scenario for each module to be tested, and generates a new test scenario by adding to the first test scenario keywords that are included only in a second test scenario of a module different from the module of the first test scenario.

[0067] This configuration allows the behavior of different modules to be added to the test scenario, which makes it possible to generate test scenarios that include interrupts from different modules that the developer did not anticipate, i.e., test scenarios that are more likely to detect defects caused by interrupts from the behavior of different modules, thereby improving the comprehensiveness of the tests.

[0068] In addition, the test scenario generation support device 10 of this embodiment generates a new test scenario by adding to the first test scenario keywords of a second test scenario that include keywords with the same targets as the keywords included in the first test scenario.

[0069] Generating test scenarios randomly only increases the number of test scenarios and does not necessarily improve test coverage. By inserting keywords from other test scenarios that operate on the same target, it is possible to generate test scenarios that span multiple modules for functions (targets) used in multiple modules. This increases the likelihood of generating test scenarios that include keywords that may interrupt the operation of different modules, allowing for more efficient test scenario generation.

[0070] In addition, the test scenario generation support device 10 of this embodiment accepts from the user a specification of an insertion position where a keyword contained only in the second test scenario is to be inserted as a new operation performed between operations on a target in the first test scenario, and inserts the keyword contained only in the second test scenario at the insertion position specified by the user.

[0071] This configuration allows the user (developer) to specify which keywords (operations on the target) to insert additional keywords between, making it possible to generate test scenarios that have been carefully vetted by the developer.

[0072] In addition, the test scenario generation support device 10 of this embodiment stores a keyword database 102 that stores keywords included in test scenarios stored in the test scenario database 105, extracts all objects and operations included in the keywords stored in the keyword database 102, combines the extracted objects and operations to generate new keywords that are not stored in the keyword database 102, and outputs the generated keywords.

[0073] This configuration makes it possible to extract all additional keywords that are not included in the initial test scenario list 350. This allows, for example, a developer to add new test scenarios using the additional keywords, thereby supporting the creation of new test scenarios that improve the comprehensiveness of tests.

[0074] Furthermore, the test scenario generation support device 10 of this embodiment receives a selection input of a combination of the extracted targets and operations from the user, and generates a new keyword based on the combination of targets and operations selected by the user.

[0075] With this configuration, the developer, who is the user, can decide whether to adopt a combination of target and operation as a keyword. This allows, for example, to generate only the additional keywords that the developer considers necessary. In other words, it is possible to prevent the generation of unnecessary additional keywords.

[0076] The present invention is not limited to the above-described embodiments, and can be implemented using any components within 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 characteristics of the invention are not impaired. Furthermore, 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 within the scope of the present invention.

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

[0078] Furthermore, each program of the test scenario generation system may be provided in another device, a program may consist of multiple programs, or multiple programs may be integrated into one program.

[0079] Furthermore, in the above-described embodiment, the generation AI 20 generates the initial keyword list 330, the module list 340, and the initial test scenario list 350, but this is not limited to this and they may be generated using other natural language processing techniques, or the initial keyword list 330, the module list 340, and the initial test scenario list 350 designed by the developer may be input to the test scenario generation support device 10. [Explanation of symbols]

[0080] 1 Test scenario generation system 10. Test scenario generation support device 101 Keyword list input section 102 Keyword Database 103 Additional Keyword Generation Unit 104 Test scenario input section 105 Test Scenario Database 106 Additional test scenario generation unit 20 Generation AI

Claims

1. a processor and a memory; a test scenario database that stores test scenarios written using one or more keywords that represent operations and targets of the operations; an additional test scenario generation unit that compares a first test scenario stored in the test scenario database with a second test scenario that is different from the first test scenario, and generates a new test scenario by adding keywords that are included only in the second test scenario to the first test scenario; A test scenario generation system comprising:

2. the test scenario database stores a test scenario for each module to be tested; the additional test scenario generation unit generates a new test scenario by adding to the first test scenario a keyword that is included only in the second test scenario of a module different from a module of the first test scenario; The test scenario generation system according to claim 1 .

3. the additional test scenario generation unit generates a new test scenario by adding to the first test scenario a keyword of the second test scenario, the keyword including the same target as a target in a keyword included in the first test scenario. The test scenario generation system according to claim 1 .

4. The additional test scenario generation unit receiving, from a user, a designation of an insertion position at which a keyword included only in the second test scenario is to be inserted as a new operation to be performed between operations on a target in the first test scenario; inserting a keyword contained only in the second test scenario into an insertion position designated by the user; The test scenario generation system according to claim 1 .

5. a keyword database for storing keywords included in the test scenarios stored in the test scenario database; an additional keyword generating unit that extracts all objects and operations included in the keywords stored in the keyword database, combines the extracted objects and operations to generate new keywords that are not stored in the keyword database, and outputs the generated new keywords; The test scenario generation system according to claim 1 , comprising:

6. The additional keyword generation unit: Accepting a selection input from the user for a combination of extracted targets and operations; generating a new keyword based on the combination of the target and operation selected by the user; The test scenario generation system according to claim 5 .

7. The information processing device an additional test scenario generation process that compares a first test scenario stored in a test scenario database that stores test scenarios written using one or more keywords that represent operations and targets of the operations with a second test scenario that is different from the first test scenario, and generates a new test scenario by adding keywords that are included only in the second test scenario to the first test scenario; A method for generating test scenarios to execute the above.

Images