JP2013161182A - Test item generation device and test item generation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To generate a test item in software development.SOLUTION: A test item generation device including a flow diagram storage part storing a flow diagram indicating a plurality of nodes from a start node to an end node in information processing which is a test object and flow connecting the nodes reads the flow diagram stored in the flow diagram storage part, extracts a plurality of routes from the start node to the end node indicated by the read flow diagram, determines one basic route which is a normal system among the plurality of extracted routes, generates an intermediate file for which information indicating that it is basic flow is added to the flow on the basic route, generates the test item for each of the plurality of routes including at least the basic route among the plurality of extracted routes on the basis of the generated intermediate file, and preferentially outputs the test item corresponding to the basic route.

Description

  The present invention relates to a technique for supporting testing in software development.

  There is a software tool for supporting unit tests and integration tests in software development (for example, Non-Patent Document 1). For example, based on a flow diagram showing the flow of information processing as a test target, there is one that exhaustively searches for information processing routes, generates a route list, and outputs the list. The tester can perform a comprehensive test by generating test items based on such a route list.

“Introduction of astah * quality suite”, [online], [searched on 09 December 2011], Internet <URL: http: //astah.change-vision.com/en/qs/index.html>

  However, when generating exhaustive test items for the processing path to be tested, a large number of test items may be generated if the information processing to be tested includes many branches and loops. Conceivable. For this reason, it is considered that among the information processing paths to be tested, test items corresponding to basic paths that are normal systems may be buried in a large number of test items. Here, in general, it is desirable to perform a branch test or an abnormal test after performing a basic normal test for software. This is because the time required for testing is limited in the software development process, and it may be difficult to carry out all of the comprehensive test items. In addition, when the test is performed according to the test item, it is because the test execution efficiency is higher if the test item is described with priority from the normal test item.

  The present invention has been made in view of such circumstances, and provides a test item generation apparatus and a test item generation method for generating test items in software development.

  In order to solve the above-described problem, the present invention is a flow in which a flow diagram showing a plurality of nodes from a start node to an end node in information processing to be tested and a flow connecting the nodes is stored. A diagram storage unit; a route extraction unit that reads the flow diagram stored in the flow diagram storage unit; and extracts a plurality of routes from a start node to an end node indicated by the read flow diagram; and the route extraction unit An intermediate file generation unit that determines one basic route that is a normal system among a plurality of routes extracted by, and generates an intermediate file to which information indicating that the flow is a basic flow is added to the flow on the basic route And, based on the intermediate file generated by the intermediate file generation unit, at least the path among the plurality of paths extracted by the path extraction unit Generate test items for each of the plurality of routes include the route, characterized in that it comprises a test item generation unit which outputs a test item corresponding to the basic path preferentially.

  In the present invention, the intermediate file generation unit is a flow to which information indicating the basic route is not added among a plurality of flows included in the flow diagram, and an end node in the basic route The information indicating that it is an alternative flow is added to the flow on the route that reaches the same end node, and both the information indicating the basic flow and the information indicating the alternative flow are Information indicating that the flow is an exception flow is added to a flow that has not been added, and the test item generation unit is configured based on information added to the flow by the intermediate file generation unit and a predetermined priority level. A test item is output.

  Further, according to the present invention, the intermediate file generation unit determines that a route that has the maximum number of nodes from the start node to the end node and does not pass through the same node among the plurality of routes is a basic route. It is characterized by that.

  According to the present invention, the intermediate file generation unit is a normal one of the plurality of paths based on whether a predetermined keyword is included in a node or flow on the plurality of paths. The basic route is determined.

  Further, according to the present invention, the intermediate file generation unit determines that the shortest path from the start node to the end node that is predetermined as the end node of the basic path is the basic path among the plurality of paths. It is characterized by doing.

  The present invention further includes an input unit that receives input of information indicating which of the plurality of routes is a basic route, and the intermediate file generation unit receives information input to the input unit. On the basis of this, one basic route which is a normal system among the plurality of routes is determined.

  In the present invention, the test item generation unit prioritizes a test item corresponding to a path including a node including a database access process or a node including a shared variable update process among the test items generated for each path. It is characterized in that the output is made automatically.

  Further, the present invention is characterized in that the test item generation unit outputs a number of test items according to a predetermined number of test items.

  Further, the present invention provides a test comprising a flow diagram storage unit in which a flow diagram showing a plurality of nodes from a start node to an end node in information processing to be tested and a flow connecting the nodes is stored A test item generation method for an item generation apparatus, comprising: reading the flow diagram stored in the flow diagram storage unit; and extracting a plurality of paths from a start node to an end node indicated by the read flow diagram; A step of determining one basic route that is a normal system among the extracted routes, and generating an intermediate file with information indicating that the flow is a basic flow for the flow on the basic route; Based on the intermediate file, a test item is generated for each of a plurality of routes including at least the basic route among the plurality of routes. Is a test item generation method characterized by comprising the steps of: outputting a test item corresponding to the basic path preferentially.

  As described above, according to the present invention, a flow diagram storage that stores a plurality of nodes from a start node to an end node in information processing that is a test target and a flow that connects the nodes is stored. The test item generation device including the unit reads the flow diagram stored in the flow diagram storage unit, extracts a plurality of routes from the start node to the end node indicated by the read flow diagram, and among the extracted plurality of routes , Determine one basic route that is normal, generate an intermediate file with information indicating that it is a basic flow for the flow on the basic route, and extract a plurality of extracted files based on the generated intermediate file Generate test items for each of multiple routes that include at least the basic route, and preferentially output test items corresponding to the basic route Since the, it is possible to generate the appropriate test items in the software development.

It is a block diagram which shows the structural example of the test item production | generation apparatus by one Embodiment of this invention. It is a figure which shows the example of the flowchart memorize | stored in the flowchart memory | storage part by one Embodiment of this invention. It is a figure which shows the example of data of the design model intermediate | middle file by one Embodiment of this invention. It is a figure which shows the example of data of the priority level memorize | stored in the priority level memory | storage part by one Embodiment of this invention. It is a figure which shows the example of data of the test model intermediate file by one Embodiment of this invention. It is a figure which shows the example of data of the priority level threshold value by one Embodiment of this invention. It is a figure which shows the example of the test item table | surface by one Embodiment of this invention. It is a flowchart which shows the operation example of the test item generation apparatus by one Embodiment of this invention.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram illustrating a configuration of a test item generation apparatus 10 according to the present embodiment. The test item generation device 10 is a computer device that generates test items in software development, and includes a flow diagram storage unit 11, a path extraction unit 12, an intermediate file generation unit 13, an input unit 14, and an intermediate file storage unit 15. A priority level storage unit 16, a test item generation unit 17, and an output unit 18.

  The flow diagram storage unit 11 stores a flow diagram showing a plurality of nodes from the start node to the end node in the information processing to be tested, and a flow for connecting the nodes. For example, a software design document to be tested can be applied to the flow diagram. FIG. 2 is a diagram illustrating an example of a flow diagram stored in the flow diagram storage unit 11. In this example, an activity diagram in UML (Unified Modeling Language) is described as an example of a flow diagram, but a so-called flowchart may be used, and a diagram showing a plurality of steps included in information processing and transitions between the plurality of steps. I just need it. Here, the flow diagram may be at the unit test level or the integration test level, as long as it is a process that can be represented in the flow diagram.

  Reference numerals a1 to a12 are nodes in the information processing shown in the flowchart. Reference numeral a1 is a start node of information processing shown in the flowchart, and indicates a start point. Reference numerals a10 and a12 are end nodes of the information processing shown in the flowchart, and indicate end points. Thus, some flowcharts show a plurality of end points. Reference numerals a2, a3, a4, a7, a9, and a11 are nodes indicating processes (activity, action) in the flowchart, and the contents of the process are indicated by character strings. Reference numerals a5, a6, and a8 are nodes indicating conditional branches in the flow diagram. Reference numerals b1 to b13 denote flows (transitions) for connecting nodes. A character string indicating the condition is added to a flow connected for each condition in a node that is a conditional branch. Reference symbol c indicates a database accessed by processing in the node indicated by reference symbol a4. The flow diagram may be, for example, an XML format file indicating each node or each flow as an object in a tag, or may be a drawing file.

  The route extraction unit 12 reads the flow diagram stored in the flow diagram storage unit 11 and exhaustively extracts a plurality of routes from the start node to the end node indicated by the read flow diagram. For example, the route from the code a1 to b10 through the b1, a2, b2, a3, b3, a4, b4, a5, b5, a6, b6, a7, b7, a8, b8, a9, b9 There is a route that branches to b10 at a5 and reaches a12 through a11 and b11. Here, a comprehensive search is performed for all routes that reach a plurality of end nodes from a loop, conditional branch, or start node. Here, when the flow diagram is an XML file, the route extraction unit 12 can search for a route based on each object indicated by the tag. Alternatively, when the flow diagram is a drawing, it is also possible to search the route by performing image analysis of the drawing to extract each node and flow.

  The intermediate file generation unit 13 determines one basic route that is a normal system among the plurality of routes extracted by the route extraction unit 12, and displays information indicating that the flow is a basic flow with respect to the flow on the basic route. Generate an added design model intermediate file. Further, the intermediate file generation unit 13 is a flow to which information indicating that it is a basic flow among a plurality of flows included in the flow diagram is not added in the design model intermediate file, and a basic route indicated by the basic flow The information indicating that it is an alternative flow is added to the flow on the route that reaches the same end node as the end node in the information, and both the information indicating the basic flow and the information indicating the alternative flow are Information indicating an exception flow is added to a flow that has not been added. As described above, in this embodiment, each flow in the flowchart is identified by classification into the basic flow, the alternative flow, and the exception flow.

  FIG. 3 is a diagram illustrating a data example of the design model intermediate file generated by the intermediate file generation unit 13. Here, each node and each flow in the flow diagram are shown in association with XML format tags, the symbols a1 to a12 correspond to the nodes a1 to a12 in FIG. 2, and the symbols b1 to b13 are This corresponds to the flow of symbols b1 to b13 in FIG. Here, a basic route from the reference a1 to b10 through b1, a2, b2, a3, b3, a4, b4, a5, b5, a6, b6, a7, b7, a8, b8, a9, b9 “Type =“ basic ”is information indicating a basic flow for the tags b1, b2, b3, b4, b5, b6, b7, b8, b9 that are flows included in this route. "" Attribute is added. In addition, information indicating that it is an alternative flow for the tags b12 and b13, which are flows on the route reaching the end node, with no information indicating that it is a basic flow. The attribute of “type =“ alternative ”” is added. Also, information indicating an exception flow for the tags b10 and b11, which are flows to which neither the information indicating the basic flow nor the information indicating the alternative flow is added. The attribute of “type =“ exception ”” is added. Here, an example in which the character strings of “basic”, “alternative”, and “exception” are added as tag attributes in this way is shown, but not limited to adding such a character string as an attribute to the tag, For example, it may be indicated by a single alphabetic character predetermined for each type of flow, as long as the type of flow can be identified.

  Here, examples of the first to fourth determination methods in which the intermediate file generation unit 13 determines the basic route will be described. In the first determination method, the intermediate file generation unit 13 selects a route that has the maximum number of nodes from the start node to the end node among the plurality of routes extracted by the route extraction unit 12 and does not pass through the same node. It is determined that the route is a basic route. In the example of the flowchart shown in FIG. 2, since there are a plurality (two) of end nodes, it is necessary to determine which of the end nodes is a normal route. Here, it is assumed that a path shorter than the other paths (the number of passing nodes and flows) among the plurality of paths is a path that is terminated by an abnormal process. That is, such a route is an exceptional route, and it can be estimated that a longer route (having a large number of nodes and flows to pass through) is a basic route. Furthermore, since a route passing through the same node is considered to pass through the same node by a loop, it can be estimated that a route that does not loop is a basic route.

  In the second determination method, the intermediate file generation unit 13 determines whether a predetermined keyword is included in the nodes or flows on the plurality of routes extracted by the route extraction unit 12. Then, one basic route that is a normal system is determined. For example, if there is a flow with the character string “if succeeded” and a flow with the character string “if error” added to the flow added to the conditional branch, “if successful” It can be estimated that there is a high possibility that this flow is a normal route. Therefore, the normal basic route is determined based on such keywords as “success” and “error”. For example, in the case of a conditional branch, if “T” indicating True and “F” indicating False are present, it can be estimated that “T” is a normal path. For example, the intermediate file generation unit 13 stores a list of keywords that are likely to indicate such a normal system and a list of keywords that are highly likely to indicate a non-normal system in its storage area in advance. Compare with each node read from the flow diagram and the character string added to the flow, there are more nodes and flows with keywords that are more likely to indicate normal, normal A node to which a keyword having a high possibility of indicating that it is not a system or a route with fewer flows is determined as a basic route. Here, an example in which a keyword is extracted from a character string added to a node or a flow has been shown, but a basic path can also be determined by performing natural language analysis of a character string, for example.

  In the third determination method, the intermediate file generation unit 13 selects the shortest route from the start node to the end node that is predetermined as the end node of the basic route among the plurality of routes extracted by the route extraction unit 12. It is determined that the route is a basic route. For example, when there are a plurality of end nodes as shown in FIG. 2, information indicating the end node in the basic route is associated in advance with one of the end nodes. For example, it is determined in advance that a character string “normally completed” is added to the end node of the basic route. In this example, a character string “normally completed” is added to the end node of the reference a10, and a character string “application error” is added to the end node of the reference a12. The intermediate file generation unit 13 detects an end node to which the character string “normally completed” is added from a plurality of end nodes, and assumes that the end node is an end node of the basic route, from the start node to the end node. Is determined to be the basic route.

  In the fourth determination method, the intermediate file generation unit 13 determines one basic route that is a normal system among a plurality of routes based on information input to the input unit 14 by the user. For example, the flow diagram shown in FIG. 2 is displayed on the screen of the display unit included in the test item generation device 10, and information indicating whether the flow is a basic flow, an alternative flow, or an exceptional flow is input for each flow. Accept. The intermediate file generation unit 13 determines that the route indicated by the input flow as the basic flow is the basic route.

  Here, examples of the first to fourth determination methods have been described, but these determination methods may be combined. For example, the determination result by each of the first to third determination methods is scored, and a route with a higher score can be determined as a basic route. Alternatively, any one or a plurality of determination results from the first to the third are displayed on the screen of the test item generation device 10 to allow the user to confirm the determination results and, if necessary, accept a correction input of the flow type that is the determination result. You can also.

The input unit 14 is an input device such as a keyboard or a mouse, and receives an operation input from a user. For example, the input unit 14 receives input of information indicating which route is a basic route among a plurality of routes extracted by the route extraction unit 12.
The intermediate file storage unit 15 stores an intermediate file generated to generate a test item. For example, the intermediate file storage unit 15 stores the above-described design model intermediate file and a test model intermediate file described later.

  The priority level storage unit 16 stores the priority level of the test item according to the flow type added to the flow included in the route. FIG. 4 is a diagram illustrating an example of priority level data stored in the priority level storage unit 16. Here, the route, viewpoint, and extraction method are associated with the priority level. The priority level indicates the priority of the test item generated for each route, and the higher the priority, the more important the test item is. In this example, the smaller the priority level, the higher the priority. The route is a route for generating a test item, and indicates a route corresponding to a flow type included in the route. For example, the priority level 1 is associated with a route including only a flow whose flow type is a basic flow. Priority level 2 is associated with a route that passes through each alternative flow only once. The viewpoint indicates the viewpoint of testing the corresponding route. The extraction method indicates a method for extracting a corresponding route.

  The test item generation unit 17 includes at least a basic route determined by the intermediate file generation unit 13 among a plurality of routes extracted by the route extraction unit 12 based on the design model intermediate file generated by the intermediate file generation unit 13. The test item for each of the plurality of routes is generated, and the test item corresponding to the basic route is output with priority. “Preferentially outputting” means, for example, outputting a test item having a high priority before a test item having a low priority when outputting a plurality of test items in order. Specifically, the test item generation unit 17 first reads the design model intermediate file stored in the intermediate file generation unit 13, and the flow type added for each flow included in the read design model intermediate file; A test model intermediate file in which paths for generating test items are arranged in descending order of priority is generated based on the priority levels previously determined and stored in the priority level storage unit 16.

  FIG. 5 is a diagram illustrating a data example of the test model intermediate file generated by the test item generation unit 17. Here, the basic route is shown at the location of the symbol a, and the alternative route is shown at the location of the symbol b. For example, the test item generation unit 17 reads the priority level stored in the priority level storage unit 16, extracts paths from the highest priority level, and outputs them to the test model intermediate file. For example, the test item generation unit 17 extracts a route based on the extraction method corresponding to the priority level 1, and outputs the extracted route to the test model intermediate file. Next, a route is extracted based on the extraction method corresponding to priority level 2, and the extracted route is output to the test model intermediate file. In this way, the test item generation unit 17 outputs the paths for generating the test items in order of priority.

  Here, when the test item generation unit 17 outputs a route to the test model intermediate file, only a route corresponding to a predetermined priority level from a higher priority level can be output. In this case, the test item generation unit 17 stores, in advance in its own storage area, a table in which a threshold value of a priority level of a test to be performed on each flow diagram is associated with each test flow diagram. FIG. 6 is a diagram illustrating an example of priority level threshold data for each flowchart. Here, it is determined that test items up to priority level 3 are generated for flow diagram 1 (use case ID1), and test items up to priority level 5 are generated for flow diagram 2 (use case ID2). For flow diagram 3 (use case ID3), it is determined that test items up to priority level 6 are generated. The priority level for each flow diagram is determined based on the viewpoint of whether or not there is a node including database access processing or whether or not a node including update processing of shared variables is included in the flow diagram. . For example, for the flow diagram 1, only the routes corresponding to the priority level 1 to the priority level 3 are output to the test model intermediate file. As a result, it is possible to output in order from the route with the highest priority and to set the amount of test items to a number corresponding to the route.

  In addition, the test item generation unit 17 can set a threshold value for the number of test items to be output in advance, and output a route within the determined number of test items. For example, from the viewpoint of test density, a threshold value for the number of test items can be determined according to the scale of the program to be tested. For example, the test item generation unit 17 sets a test item generation condition that associates the code amount (number of steps) of a program that implements the function shown in the flow diagram with the number of test items to be executed for the function shown in the flow diagram. Stored in the storage area. When the test item generation condition stipulates that one test item is generated every 20 steps of the program, the test item generation unit 17 determines that the test target program is 1000 steps (1000/20 =) 50 items are calculated as threshold values for the number of test items to be generated. Thereby, the number of test items can be kept within a certain number. For example, even when the test time is limited, a predetermined number of tests can be performed from important test items. Further, the test item generation unit 17 can increase the priority of a path including a node including a database access process or a node including a shared variable update process and output such a path with priority.

  The test item generation unit 17 generates a test item table based on the test model intermediate file generated in this manner and stored in the intermediate file storage unit 15. Specifically, the test item generation unit 17 generates a test item table by using spreadsheet software or the like, reads the test model intermediate file stored in the intermediate file storage unit 15, and reads each path described in the test model intermediate file. Then, a test item passing through the route is generated and output to the test item table.

  FIG. 7 is a diagram illustrating an example of a test item table generated by the test item generation unit 17. In the symbol a, a system name, a business name, etc. to be tested are described. In the symbol b, identification information such as a procedure manual and a test code for performing a test item is described. Reference numeral c describes a test item to be performed on the test target software. Among the columns of reference c, reference c1 describes the viewpoint of the test. Reference numeral c2 describes an input value and an expected result in the test item. The input value and the expected result may be input by the user, for example, or may be read from another file or the like. Reference numeral c3 describes a path indicating a route output by the test item generation unit 17 according to the priority. Here, a character string added to a node on the route is described. Reference numeral c4 describes a precondition for performing the test. An example of an input value is written in the code c5. The expected result corresponding to the input value is written in the code c6.

  Here, for example, in a conventional software tool that generates a test item table by exhaustively searching for a route, the route is output according to the order in which nodes and flows are written in the flow diagram. In this case, a test item having a low priority may be output to a higher rank, and the test using such a test item table may not be efficient. Therefore, the test item generation unit 17 generates a test item table that displays test items with high priorities in accordance with the priorities of the test items, so that the test can be performed efficiently.

  The output unit 18 outputs the test item table generated by the test item generation unit 17. For example, the output unit 18 may be a display that outputs a test item table, a printer that prints and outputs a test item table, or the like. The tester of the software that is the test target performs an operation test of the software that is the test target based on the test item table output in this way.

Next, an operation example of the test item generation device 10 according to the present embodiment will be described with reference to the drawings. FIG. 8 is a flowchart illustrating an operation example of the test item generation apparatus 10 according to the present embodiment.
The flow diagram storage unit 11 of the test item generation device 10 stores in advance a flow diagram showing information processing of each function in the test target software. The route extraction unit 12 reads the flow diagram stored in the flow diagram storage unit 11 (step S1). Then, the route extraction unit 12 extracts nodes and flows included in the read flow diagram, and exhaustively extracts the routes shown in the flow diagram (step S2).

  The intermediate file generation unit 13 generates a design model intermediate file based on the flow chart stored in the flow diagram storage unit 11 and stores the design model intermediate file in the intermediate file storage unit 15. Then, the design model is determined by determining one basic route that is a normal system among the plurality of routes extracted by the route extraction unit 12 by a predetermined determination method, and adding the attribute of the basic flow to the flow on the basic route. Update intermediate files. Further, the intermediate file generation unit 13 adds the flow types of the alternative flow and the exception flow to the design model intermediate file stored in the intermediate file storage unit 15 and updates the design model intermediate file (step S3).

  The test item generation unit 17 reads the design model intermediate file stored in the intermediate file storage unit 15 and based on the attribute for each flow included in the design model intermediate file and the priority level read from the priority level storage unit 16. Then, a test model intermediate file in which paths as test items are arranged in order of priority is generated and stored in the intermediate file storage unit 15 (step S4). The test item generation unit 17 generates a test item table based on the test model intermediate file stored in the intermediate file storage unit 15 and outputs the test item table to the output unit 18 (step S5).

  As described above, according to the present embodiment, when generating test items based on the flow diagram, the test items passing through the basic route are output first, and the test items are output in order of priority. Software tests can be performed from important test items, and tests can be performed efficiently. In addition, since test items within the specified priority or within the specified number of items are generated, it is possible to prevent test items from being generated more than necessary or impossible. An appropriate amount of test items can be generated.

  In addition, the program for realizing the function of the processing unit in the present invention is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into the computer system and executed to generate test items. May be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer system” includes a WWW system having a homepage providing environment (or display environment). The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included.

  The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, what is called a difference file (difference program) may be sufficient.

DESCRIPTION OF SYMBOLS 10 Test item production | generation apparatus 11 Flow diagram memory | storage part 12 Path | route extraction part 13 Intermediate | middle file production | generation part 14 Input part 15 Intermediate | middle file memory | storage part 16 Priority level memory | storage part 17 Test item production | generation part 18 Output part

Claims (9)

A flow diagram storage unit storing a plurality of nodes from the start node to the end node in the information processing to be tested, and a flow diagram showing a flow connecting the nodes;
A route extraction unit that reads out the flow diagram stored in the flow diagram storage unit and extracts a plurality of routes from a start node to an end node indicated by the read flow diagram;
Among the plurality of routes extracted by the route extraction unit, one basic route that is a normal system is determined, and an intermediate file in which information indicating that the flow is a basic flow is added to the flow on the basic route is generated. An intermediate file generator,
Based on the intermediate file generated by the intermediate file generation unit, a test item is generated for each of a plurality of routes including at least the basic route among the plurality of routes extracted by the route extraction unit, and the basic route is generated. A test item generator that preferentially outputs test items corresponding to
A test item generation apparatus comprising: The intermediate file generation unit is a flow to which information indicating the basic route is not added among a plurality of flows included in the flow diagram, and the intermediate file generation unit sets the same end node as the end node in the basic route. Information indicating that the flow is an alternative flow is added to the flow on the route to reach, and an exception is made to the flow in which neither the information indicating the basic flow nor the information indicating the alternative flow is added. Add information indicating that this is a flow,
The test item according to claim 1, wherein the test item generation unit outputs a test item based on information added to the flow by the intermediate file generation unit and a predetermined priority level. Generator. The intermediate file generation unit determines that a route that has the maximum number of nodes from a start node to an end node and does not pass through the same node among the plurality of routes is a basic route. The test item generation device according to claim 1 or 2. The intermediate file generation unit determines one basic path that is a normal system among the plurality of paths based on whether a predetermined keyword is included in a node or a flow on the plurality of paths. The test item generation device according to claim 1, wherein the test item generation device is a test item generation device. The intermediate file generation unit determines that the shortest route from the start node to the end node that is predetermined as the end node of the basic route is the basic route among the plurality of routes. The test item generation device according to any one of claims 1 to 4. An input unit that receives input of information indicating which of the plurality of routes is a basic route;
The intermediate file generation unit determines one basic route that is a normal system among the plurality of routes based on information input to the input unit. The test item generation device according to any one of the above. The test item generation unit preferentially outputs a test item corresponding to a path including a node including a database access process or a node including a shared variable update process among the test items generated for each path. The test item generation device according to claim 1, wherein the test item generation device is a test item generation device. The test item generation device according to any one of claims 1 to 7, wherein the test item generation unit outputs a number of test items according to a predetermined number of test items. Test item of test item generation device provided with flow diagram storage unit storing flow diagram showing a plurality of nodes from start node to end node in information processing to be tested and flow connecting between the nodes A generation method,
Reading the flow diagram stored in the flow diagram storage unit, extracting a plurality of paths from the start node to the end node indicated by the read flow diagram;
Determining one basic route that is a normal system among the plurality of extracted routes, and generating an intermediate file to which information indicating that it is a basic flow is added to the flow on the basic route;
Generating a test item for each of a plurality of routes including at least the basic route out of the plurality of routes based on the generated intermediate file, and preferentially outputting a test item corresponding to the basic route; ,
A test item generation method comprising:

Images