JP5492006B2 - Test code generation program and apparatus - Google Patents

Description

  Each embodiment of the present invention relates to a test code generation program and apparatus for generating a test code used in a test process of Web application development.

  In the test process in Web application development, for example, a test for checking screen items on a Web browser, a test for checking screen transitions by entering values, and a result value for a Web application created from a design document Various tests are performed such as As a method for executing these tests, there are a method that is executed manually and a method that is executed by a test automation tool. In recent years, a method of automatically executing by a test automation tool is generally used.

  However, the method executed by the test automation tool needs to create a test code input to the test automation tool. Since it takes time to create a test code, several methods for automatically generating a test code integrated with a test procedure from a design document or the like have been proposed.

Japanese Patent No. 4148527 JP 2002-366387 A

  However, the technology for automatically generating the test code as described above usually has no problem. However, according to the study of the present inventor, a test automation tool is used to generate the test code integrated with the test procedure. It is difficult to reuse only the test procedure.

  Even when the test procedures are separated, it is necessary to define a test procedure for each piece of software to be tested, which is expensive.

  An object of the embodiment disclosed in the present specification is to provide a test code generation program and apparatus that can reuse a test procedure and does not need to define a test procedure for each software to be tested.

  A test code generation device according to an embodiment of the present invention described below is connected to a database unit as a related table that stores a physical name value to be searched and a search result value in association with each other, and a plurality of designs in a Web application Test code used by test automation tool is generated from document data.

  The test code generation device according to the embodiment is screen transition design document data among the respective design document data, and regarding the transition of each screen of the Web application, the item and value of the screen transition ID, the item and value of the scenario name The input of the screen transition design document data indicating the items and values of the request generation screen URL and the items and values of the transition destination screen URL in association with each other is received.

  The test code generation device according to the embodiment is screen item design document data among the respective design document data, and relates to the item of each screen of the Web application, the item and value of the screen item ID, and the item and value of the HTML element. Among the screen item IDs, the item and value of the first element among the items and values of the default value, the item and value of the Name attribute, and the item and value of the physical name of the related table, the item of the HTML element And the value indicating the title, the item of the default value and the value are associated with each other, the item and value of the second screen item ID of the screen item ID, the value of the item of the HTML element and the text area, the Name The attribute item and the physical name value to be searched, and the physical name item and value in the association table are shown in association with each other, and the third screen item ID item in the screen item IDs Receives an input of the screen item design document data indicating associating a value, indicating the item and execution of the items and the values indicating the input of HTML elements, and the Name attribute.

  The test code generation device according to the embodiment is screen list design document data of the respective design document data, and for each screen of the Web application, screen ID items and values, and screen URL items and values. The input of the screen list design document data shown in association is accepted.

  The test procedure pattern storage means of the test code generation device of the embodiment includes a test procedure pattern ID composed of the same character string as any value of the scenario name, and a plurality of test procedure names arranged in the test order. The test procedure pattern information is stored.

  The operation storage means of the test code generation device of the embodiment stores the test procedure name, operation, and test code fragment ID in association with each other.

  The test code fragment storage means of the test code generation device of the embodiment includes the test code fragment ID and a variable part, and the variable part includes an item of the request generation screen URL, an item of the transition destination screen URL, A plurality of pieces of test code fragment information individually including values indicating the items and titles of the HTML elements, values indicating the items and inputs of the HTML elements, and items of screen item values are stored.

  The test code generation apparatus according to the embodiment extracts a scenario name item and a value from the screen transition design document data that has received the input.

  The screen transition object generation unit of the test code generation device of the embodiment includes the extracted scenario name value, and further includes an identification number when another scenario name value identical to the scenario name value is extracted. A screen transition object including an object name including a property and a property, and the property includes a request generation screen URL item associated with a scenario name value in the object name in the screen transition design document data, and A request generation screen ID value including a value and a transition destination screen URL item and value, and a screen ID value associated with the screen URL value in the screen list design document that matches the request generation screen URL value; A request indicating a request generation screen object with the item and the value of the request generation screen ID as an object name Occurrence screen item, a transition destination screen ID consisting of a screen ID value associated with the value of the screen URL in the screen list design document that matches the value of the transition destination screen URL, and the value of the transition destination screen ID The screen transition object including the transition destination screen item indicating the transition destination screen object having the object name as the object name is generated.

  The generation screen object generation means of the test code generation device of the embodiment is a request generation screen object including an object name consisting of a value of the request generation screen ID of the screen transition object and a property, The request generation screen object including the screen item including the value of the screen item ID in the screen item design document that matches the value of the request generation screen ID in the middle is generated.

  The generation screen item object generation unit of the test code generation device of the embodiment is a request generation screen item object including an object name including a value of a screen item ID of the request generation screen object and a property, and the property includes , A first generation screen item composed of an HTML element item and value and a default value item and value associated with the screen item ID value in the screen item design document, and the screen item ID value. The second generation screen item consisting of the item and value of the HTML element and the item and value of the Name attribute and the physical name item and value of the related table associated with each other in the design document, and the screen item design in the value of the screen item ID Any of the HTML element items and values associated in the document and the third occurrence screen item consisting of the Name attribute items and values It contains Kano generation screen item, individually generates the request generation screen item objects.

  The transition destination screen object generation means of the test code generation device of the embodiment is a transition destination screen object including an object name consisting of a value of the transition destination screen ID of the screen transition object and a property, and the property includes The transition destination screen object including the screen item including the value of the screen item ID in the screen item design document that matches the value of the transition destination screen ID in the middle is generated.

  The transition destination screen item object generation unit of the test code generation device of the embodiment is a transition destination screen item object including an object name including a value of a screen item ID of the transition destination screen object and a property, and the property Is a first transition destination screen item consisting of an HTML element item and value and a default value item and value associated with the value of the screen item ID in the screen item design document, and the value of the screen item ID. The HTML element item and value associated in the screen item design document, the Name attribute item and value, the second transition destination screen item consisting of the physical name item and value of the related table, and the value of the screen item ID Transition of any of the HTML element items and values associated with the screen item design document and the third transition destination screen item consisting of the Name attribute item and value Includes previous screen item, individually generates the transition destination screen item objects.

  The design information object generation means of the test code generation device of the embodiment includes a design information object including the screen transition object, the request generation screen object, the request generation screen item object, the transition destination screen object, and the transition destination screen item object Is generated.

  The test procedure pattern reading means of the test code generation device according to the embodiment includes the test procedure pattern information including a test procedure pattern ID that matches a scenario name value included in the object name of the screen transition object in the design information object. Read from the procedure pattern storage means.

  The test code generation device of the embodiment reads the test procedure name in the read test procedure pattern information along the test order, and associates it with the test procedure name in the operation storage unit that matches the read test procedure name The read test code fragment ID is read from the operation storage means.

  The test code generation device according to the embodiment reads test code information including a test code fragment ID that matches the read test code fragment ID from the test code fragment storage unit, and the read test code information in the test order. To create test code template information.

  The test code generation device according to the embodiment includes a variable portion indicating “the request generation screen URL item” or “the transition destination screen URL item” among the variable portions in the test code template information as the design information. The value of the item that matches the variable part in the object is replaced, and among the variable parts, the variable part indicating “the value of the default value indicating the title of the item of the HTML element” is set in the design information object. Replace with the value of the default value in the same object as the variable part, and in each of the variable parts, "the value of the Name attribute that the HTML element item indicates input" or "the value that the physical name indicates id" The variable part shown is replaced with the value of the Name attribute in the same object as the variable part in the design information object, and the “value indicating the physical name indicates id” is indicated. For the variable part, the value of the search result associated with the physical name value in the database that matches the physical name value in the same object is inserted into the line next to the value of the replaced Name attribute. The test code is generated from the test code template information.

1 is a block diagram illustrating a test code generation device and its peripheral configuration according to a first embodiment. It is a flowchart for demonstrating the operation | movement in the embodiment. It is a schematic diagram which shows the structure of the screen transition design document data which concerns on 2nd Embodiment. It is a schematic diagram which shows the structure of the screen item design document data in the embodiment. It is a schematic diagram which shows the structure of the table item design document data in the embodiment. It is a schematic diagram which shows the structure of the exception process design document data in the embodiment. It is a schematic diagram which shows the structure of the screen list design document data in the embodiment. It is a schematic diagram which shows an example of the input screen in the embodiment. It is a schematic diagram which shows an example of the test code fragment information in the same embodiment. It is a schematic diagram which shows an example of the test code fragment information in the same embodiment. It is a schematic diagram which shows an example of the test code fragment information in the same embodiment. It is a schematic diagram which shows an example of the test code fragment information in the same embodiment. It is a schematic diagram which shows an example of the test procedure pattern information in the embodiment. It is a schematic diagram which shows an example of the design information object in the embodiment. It is a schematic diagram for demonstrating the production | generation operation | movement of the test code template information in the embodiment. It is a schematic diagram for demonstrating the production | generation operation | movement of the test code in the same embodiment. It is a schematic diagram which shows an example of the test code fragment information which concerns on 3rd Embodiment. It is a schematic diagram which shows an example of the test code fragment information in the same embodiment. It is a schematic diagram which shows an example of the test code fragment information in the same embodiment. It is a schematic diagram which shows an example of the test code fragment information in the same embodiment. It is a schematic diagram for demonstrating the production | generation operation | movement of the test code template information in the embodiment. It is a schematic diagram for demonstrating the production | generation operation | movement of the test code in the same embodiment.

  Each embodiment will be described below with reference to the drawings. Note that the following test code generation apparatus can be implemented with either a hardware configuration or a combination configuration of hardware resources and software. As the software of the combination configuration, a program that is installed in advance from a network or a storage medium into a computer serving as a test code generation device and realizes the function of the test code generation device is used. The test code generation device is not limited to this name, and may be called a Web application test support device because it supports a test process of Web application development, or a test code generation device or a test code automatic generation device. You may call by arbitrary names.

(First embodiment)
FIG. 1 is a block diagram showing a test code generation device and its peripheral configuration according to the first embodiment. The test code generation device 10 generates and outputs a test code based on design document data, test procedure pattern information, test code fragment information, and data in the database unit 20. The data in the database unit 20 is written by the table data generation unit 21 based on the design document data. The output test code is used for the test by the test automation tool unit 30.

  Such a test code generation device 10 includes a design document reading unit 11, a design information object generation unit 12, a test procedure pattern storage unit 13, an operation storage unit 14, a test code fragment storage unit 15, a test procedure pattern extraction unit 16, and a test. A code generation unit 17 is provided.

  Here, the design document reading unit 11 reads various design document data to be input by a user operation, and sends the read design document data to the design information object generation unit 12. As various design document data, there are screen transition design document data, screen item design document data, table item design document data, screen list design document data, and exception processing design document data. In addition, input of data or a command corresponding to a user operation is transmitted to the corresponding functional units 11 to 17 via a GUI (graphical user interface).

  The design information object generation unit 12 is extracted with a process target extraction function that extracts a test target process name (scenario name) from the screen transition design document data among the various design document data sent from the design document reading unit 11. Each test target process name has a design information object generation function for generating a design information object from the various design document data. Here, the design information object represents the high-level concept data (eg, data items and data related to the screen) of the design document data as the high-level object, and the low-level concept data (eg, in the screen). Data items and data) are represented as lower objects, and the upper and lower objects are associated with each other.

  The test procedure pattern storage unit 13 includes a single test procedure pattern name and a plurality of test procedure names described in the test order, and indicates a series of test procedure patterns in a certain function as a test target process Procedure pattern information is stored. Some functions include search, update, registration, and deletion, and can be added by the user. The test procedure pattern name is composed of the same character string as the test target process name extracted by the design information object unit 12. Such test procedure pattern information is previously written in the test procedure pattern storage unit 13 by the user. Further, the test procedure pattern information can be appropriately added, changed, or deleted by user operation.

  The operation storage unit 14 stores the test procedure name included in the test procedure pattern information in the test procedure pattern storage unit 13 and the test code fragment ID included in the test code fragment information in the test code fragment storage unit 15 in association with each other. To do. In the operation storage unit 14, each information is written in advance in association with a user operation.

  The test code fragment storage unit 15 stores test code fragment information in which a part of the test code is described including the test code fragment ID and the item in the design document object. The test code fragment information is previously written in the test code fragment storage unit 15 by a user operation. The test code fragment information may be called test code template fragment information.

  The test procedure pattern extraction unit 16 reads the test procedure pattern information from the test procedure pattern storage unit 13 based on the test target process name extracted by the design information object generation unit 12, and uses the test procedure pattern information as the test code generation unit. 17 to send to

  The test code generation unit 17 includes the test procedure pattern information sent from the test procedure pattern extraction unit 16 and the test code fragment ID associated in the operation storage unit 14 with each test procedure name in the test procedure pattern information. Based on the test code fragment information in the test code fragment storage unit 15, a test code template generation function for generating test code template information, the generated test code template information, and a design generated by the design information object generation unit 12 It has a test code generation function for generating a test code based on the information object and the value of the database unit 20 used in the test, and a test code output function for outputting the generated test code.

  The database unit 20 is a table for storing test data written by the table data generation unit 21 and can be read from the test code generation unit 17. Supplementally, the database unit 20 is used as an association table that stores a physical name value to be searched and a search result value in association with each other.

  The table data generation unit 21 has a function of generating test data based on table item design document data among various design document data and registering this data in the database unit 20. The table data generation unit 21 can use existing technology.

  The test automation tool unit 30 has a function of executing a test automation tool program for executing a software testing process indicated in various design document data using the test code output from the test code generation device 10.

  Next, the operation of the test code generation apparatus configured as described above will be described with reference to the flowchart of FIG. It is assumed that the test data is registered in the database unit 20 using existing technology.

  Now, in the test code generation device 10, the design document reading unit 11 reads various design document data to be input by a user operation (ST1). Various types of read design document data are sent from the design document reading unit 11 to the design information object generating unit 12.

  Next, the design information object generation unit 12 extracts the test target process name from the screen transition design document in the transmitted design document data (ST2), and various design document data for each extracted test target process name. A design information object is generated from (ST3).

  The test procedure pattern extraction unit 16 reads test procedure pattern information from the test procedure pattern storage unit 13 based on the extracted test target process name (ST4). The read test procedure pattern information is sent from the test procedure pattern extraction unit 16 to the test code generation unit 17.

  The test code generation unit 17 specifies test code fragment information to be used from the type of the test code fragment input from the GUI by the user (ST5). For example, in the case where there are a plurality of test automation tools A and B, if the type of the input test code fragment is “test code fragment for tool A”, the test code fragment information for tool A is identified and input If the type of the test code fragment is “test code fragment for tool B”, the test code fragment information for tool B is specified. Note that step ST5 can be omitted when there is no plurality of test automation tools.

  The test code generation unit 17 includes the test procedure pattern information sent from the test procedure pattern extraction unit 16 and the test code fragment ID associated in the operation storage unit 14 with each test procedure name in the test procedure pattern information. Based on the test code fragment information in the test code fragment storage unit 15, the test code fragment information is generated by combining the test code fragment information in the order of the test procedure names in the test procedure pattern information (ST6).

  Further, the test code generation unit 17 generates a test code based on the generated test code template information, the design information object generated by the design information object generation unit 12, and the value of the database unit 20 used in the test. Generate (ST7).

  For example, the test code generation unit 17 sets the “item in the design document object” included in the test code fragment information constituting the test code template information as “the value of the item in the design document object” or “in the design document object”. The test code is generated from the test code template information, the design document object, and the value of the database unit 20 by substituting the value in the database unit 20 associated with the value of the item.

  Thereafter, the test code generation unit 17 outputs the generated test code (ST8). The output test code is used for a test process by the test automation tool unit 30.

  As described above, according to the present embodiment, the test procedure and test code are separated by the configuration in which the test code is generated based on the test procedure pattern information and the test code fragment information stored in advance for the input design document data. Can easily adapt to changes in the test automation tool, and can efficiently generate test code with high maintainability based on the design document, thus reducing the overall cost of testing and contributing to improving the quality of Web applications. it can.

  Supplementally, according to the present embodiment, the test procedure is separated from the test code, and the test code is mechanically generated from the design document data and the general-purpose test procedure pattern. It is not necessary to define a test procedure every time, and the cost can be reduced.

(Second Embodiment)
The second embodiment is an example specifically showing input / output in the configuration of FIG. 1 and the operation of FIG. 2 described in the first embodiment, and the design document data shown in FIGS. 3 to 7 is inputted. The test code of the test automation tool (tool A) whose code format is HTML (Hypertext Markup Language) is output. As the format of the design document data, any format can be used as long as necessary contents are written as shown in FIGS. 3 to 7, for example. However, the format is determined for convenience when the device is mounted.

  Here, as shown in FIG. 3, the screen transition design document data relates to the transition of each screen of the Web application, the screen transition ID item and value, the scenario name item and value, the request generation screen URL item and value, In addition, items and values of the transition destination screen URL are shown in association with each other.

  As shown in FIG. 4, the screen item design document data includes items and values of screen item IDs, items and values of HTML elements, items and values of default values, items of Name attributes, and items relating to items of each screen of the Web application. Among the items and values of the physical name of the value and related table, the item and value of the first screen item ID of the screen item ID, the value indicating the HTML element item and title, and the value of the default value are associated with the value. Of the second screen item ID of the screen item ID, the value indicating the HTML element item and the text area, the Name attribute item and the physical name value to be searched, and the physical name of the related table Item and value are shown in association with each other, and the item and value of the third screen item ID of the screen item ID, the value of the HTML element item and the input, and the item of the Name attribute and the value of execution are associated with each other. Shows Te.

  As shown in FIG. 5, the table item design document data is related to the table items of the related table used in the search processing of the Web application, the item name item and value, the physical name item and value, the primary key item and value, The type item and value, and the digit item and value are shown in association with each other.

  As shown in FIG. 6, the exception processing design document data relates to exception processing of the Web application, items and values of exception occurrence conditions, items and values of exception occurrence screen URLs, items and values of exception occurrence transition destination screen URLs, and Exception message items are associated with values.

  As shown in FIG. 7, the screen list design document data indicates the screen ID items and values and the screen URL items and values associated with each screen of the Web application.

  The type of design document data and test code fragment information is input from the input screen G10 shown in FIG. The type of test code fragment information can be selected by pull-down or list box g11, and the type of test code fragment information stored in advance in test code fragment storage unit 15 is displayed as an option.

  Here, examples of test code fragment information in the HTML format are shown in FIGS.

  The test code fragment information shown in FIG. 9 includes a test code fragment ID “open” and a variable portion, and the variable portion includes a request generation screen URL item “# request generation screen URL #”. As similar test code fragment information, test code fragment information (not shown) including a test code fragment ID “open” and a variable portion “# transition destination screen URL #” is also stored in the test code fragment storage unit 15.

  The test code fragment information shown in FIG. 10 includes a test code fragment ID “click” and a variable part. As the variable part, the value “name =” indicated by the Name attribute of the value in which the item of the HTML element is an input. #HTML element (input) .Name attribute # "" is included. Here, “name =“ # HTML element (input) .Name attribute # ”” is the value of the column title “Name attribute” whose value is the value of the column title “HTML element” in FIG. Means to enter the variable part. Then, after the variable part “#HTML element (input) .Name attribute #” is replaced with “search execution”, “name =“ search execution ””.

  The test code fragment information shown in FIG. 11 includes a test code fragment ID “assertTitle” and a variable part. The variable part includes a default value #HTML element (title element whose title is an HTML element item). ). Contains the default value # ”.

  The test code fragment information shown in FIG. 12 includes a test code fragment ID “type” and a variable part. As the variable part, the value “name =” indicated by the Name attribute whose value is an HTML element item is a text area. “#HTML element (textarea) .Name attribute #” ”is included. 9 to 12, the variable portion is shown as a portion sandwiched between symbols #, but the present invention is not limited to this, and a portion sandwiched between other symbols may be used as a variable portion. The same applies to other embodiments.

  In the test procedure pattern storage unit 13, as shown in FIG. 13, a test procedure pattern ID (search) consisting of the same character string as any one of the scenario name values (search) and a plurality of sequences arranged in the test order Test procedure pattern information including the test procedure name (access, check, type, click, check) is stored. The illustrated test procedure pattern information shows an example of a test procedure pattern for a general search process. The underlined test procedure name has a one-to-one correspondence with the operation in the operation storage unit 14 and the tool code fragment ID.

  The test code fragment storage unit 15 already stores test code fragments of several formats. The correspondence between the operation of the test procedure pattern and the operation of each test code is stored in the operation storage unit 14.

  Further, the database unit 20 is used as an association table that stores the physical name value to be searched and the search result value in association with each other, and is connected to the test code generation device 10.

  Next, the operation of the test code generation apparatus when using a specific example of data as described above will be described with reference to the flowchart of FIG.

  In step ST1, the design document reading unit 11 of the test code generation device 10 receives input of various design document data from the input screen G10 by a user operation. In addition, the design document reading unit 11 accepts selection of the type of test code fragment information by a user operation. The design document data shall conform to the format of this device. The design document reading unit 11 displays a verification error on the screen when design document data that does not conform to the format of the apparatus is input. Judgment of non-compliance can be executed by comparing items described in the format data of the device held in advance with items in the input design document data, and whether or not they match. ing.

  In step ST2, as shown in FIG. 3, the design information object generation unit 12 receives scenario input items and values (search, search, search, regist).

  In step ST3, the design information object generation unit 12 generates a design information object as shown in FIG. 14 for each extracted scenario name.

  The design information object is generated from screen transition design document data, screen item design document data, data item design document data, screen list design document data, and exception handling design document data. FIG. 14 shows the design information object of the first search (search1) extracted as the test target. The design information object generation procedure is shown below as steps ST3-1 to ST3-3.

  In step ST 3-1, the design information object generation unit 12 generates a search 1 object having properties of the request generation screen and the transition destination screen of search 1 from the screen transition design document data.

  Specifically, the design information object generation unit 12 includes the extracted scenario name value (search), and the scenario name value (search) that is the same as the scenario name value (search) is extracted elsewhere. Generates a screen transition object (search1 object) including an object name (search1) including the identification number (1) and a property. The properties of the screen transition object (search1 object) include the request generation screen URL item and value (searchIndex.jsp) associated with the scenario name value (search) in the object name in the screen transition design document data, and The transition destination screen URL item and value (searchResult.jsp), and the screen ID value (S1) associated with the screen URL value (searchIndex.jsp) in the screen list design document that matches the request generation screen URL value ) Request generation screen ID value (S1) and item, a request generation screen item indicating a request generation screen object (S1 object) with the request generation screen ID value as an object name (S1), and the transition destination The image associated with the screen URL value (searchIndex.jsp) in the screen list design document that matches the screen URL value (searchIndex.jsp) It includes a transition destination screen ID composed of a surface ID value (S2) and a transition destination screen item indicating a transition destination screen object (S2 object) with the value of the transition destination screen ID as an object name.

  In step ST <b> 3-2, the design information object generation unit 12 generates objects of a request generation screen and a transition destination screen having screen items as properties.

  Specifically, the design information object generation unit 12 generates a request generation screen object (S1 object) including an object name (S1) composed of the request generation screen ID value (S1) of the screen transition object (search1 object) and properties. Generate. As the property of the request generation screen object (S1 object), from the screen item ID value (S1-1, S1-2, S1-3) in the screen item design document that matches the request generation screen ID value in the middle The request generation screen object (S1 object) including the screen item is generated.

  Similarly, the design information object generation unit 12 obtains a transition destination screen object (S2 object) including an object name (S2) composed of a transition destination screen ID value (S2) of the screen transition object (search1 object) and a property. Generate. As the property of the transition destination screen object (S2 object), the value (S2-1, S2-2, S2-) of the screen item ID in the screen item design document that matches the transition destination screen ID value (S2) in the middle The screen item consisting of 3) is included.

  In step ST3-3, the design information object generation unit 12 further creates a screen item object whose property is a screen item element.

  Specifically, the design information object generation unit 12 creates an object name (S1-1, S1-2) composed of the screen item ID values (S1-1, S1-2, S1-3) of the request generation screen object (S1 object). , S1-3) and a request generation screen item object (S1-1 object, S1-2 object, S1-3 object) including properties.

  The properties of the request generation screen item object include the HTML element item and value (title) associated with the screen item ID value (S1-1) in the screen item design document, and the default value item and value (search The first occurrence screen item consisting of the condition screen), the HTML element item and value (textarea) associated with the screen item ID value (S1-2) in the screen item design document, the Name attribute item and value ( idFromForSearch) and the second generation screen item consisting of the physical name field and value (id) in the related table, and the HTML element field associated with the screen field ID value (S1-3) in the screen field design document It includes any occurrence screen item of a value (input) and Name attribute items and a third occurrence screen item consisting of a value (search execution).

  By making such an object state, the relationship between the screen and screen items and screen item elements can be understood.

  In addition, the design information object generation unit 12 generates the screen transition object, request generation screen object, request generation screen item object, transition destination screen object, and transition destination screen item object generated as shown in steps ST3-1 to ST3-3. A design information object including is generated.

  In step ST4, the test procedure pattern extraction unit 16 reads the test procedure pattern information from the test procedure pattern storage unit 13 based on the extracted test target process name. At that time, the object name of the design information object is used.

  Specifically, the test procedure pattern extraction unit 16 includes a test procedure pattern ID (search) that matches the scenario name value (search) included in the object name (search1) of the screen transition object in the design information object, for example. The procedure pattern information is read from the test procedure pattern storage unit 13.

  More specifically, the extraction of test procedure pattern information is executed according to the procedure shown in steps ST4-1 to ST4-2 below.

  In step ST4-1, it is determined from the screen transition design document data and the exception process design document data whether the test target process is an exception process. If the pair of the request generation screen URL and the transition destination screen URL of the screen transition design document data is the same as the pair of the exception generation screen URL and the exception generation transition destination screen URL of the exception processing design document data, the processing is referred to as exception processing. judge.

  Specifically, the test procedure pattern extraction unit 16 matches the scenario name value (search) included in the object name (search1) of the screen transition object in the design information object before reading the test procedure pattern information. The request generation screen URL value and the transition destination screen URL value associated with the scenario name value (search) in the screen transition design document data to be executed, the exception generation screen URL value in the exception processing design document data, and the exception generation It is determined whether or not the value of the transition destination screen URL matches, and when both match, it is determined as an exception process.

  In step ST4-2, if the two do not match (not the exception process), the corresponding test procedure pattern information is extracted from the test target process screen and the input items of the test target process. For example, even if the test process is the same search, if there are multiple input items (HTML element: screen item object including textarea) on the target screen, test procedure pattern information including test procedure pattern ID (searchDetail) for detailed search is extracted If the number of input items is one, test procedure pattern information including a test procedure pattern ID (search) for search is extracted.

  The test procedure pattern information extracted in steps ST4-1 to ST4-2 is as follows.

  When the scenario name “search” as the test target process name has one input item, the test procedure pattern information for the search (test procedure pattern ID: search) is extracted.

  When the scenario name “search” as the test target process name has a plurality of input items, test procedure pattern information (test procedure pattern ID: searchDetail) for detailed search is extracted.

  In the case of an exception process with the scenario name “search” as the test target process name, exception test procedure pattern information (test procedure pattern ID: error) is extracted.

  In the case of the scenario name “regist” as the test target process name, registered test procedure pattern information (test procedure pattern ID: regist) is extracted.

  In step ST5, the test code generation unit 17 specifies test code fragment information to be used from the type of test code fragment information selected on the input screen G10. Here, the test code fragment information to be used is specified from the type of test code fragment information for tool A corresponding to the HTML code format.

  In step ST6, the test code generation unit 17 performs test based on the test procedure pattern information read in step ST4 and the type of test code fragment information specified in step ST5, as shown in FIG. Generate code template information.

  Specifically, step ST6 is executed as shown in steps ST6-1 to ST6-2 below.

  In step ST6-1, the test code generation unit 17 reads the test procedure name in the test procedure pattern information read in step ST4 in the test order, and an operation storage unit that matches the read test procedure name. The test code fragment ID associated with the test procedure name in 14 is read from the operation storage unit 14.

  In step ST6-2, the test code generation unit 17 reads the test code information including the test code fragment ID that matches the read test code fragment ID from the test code fragment storage unit 15, and tests the read test code information. Test code template information is created by combining them in order.

  In step ST7, as shown in FIG. 16, the test code generating unit 17 generates the generated test code template information, the design information object generated by the design information object generating unit 12, and the database unit 20 used in the test. Test code is generated based on the value of.

  Specifically, step ST7 is executed as shown in steps ST7-1 to ST7-2 below.

  In step ST7-1, the test code generation unit 17 applies the information of the design information object to the variable part of the test code template information to generate a test code. The variable part of the test code template is the part enclosed by #.

  In step ST7-2, the test code generation unit 17 acquires an expected value from the database unit 20 when referring to a database value for confirmation of a search result or the like. The test code generation unit 17 acquires the physical name of the value used in the application search key from the design information object, and performs a database search on the table created based on the design document.

  Specifically, the test code generation unit 17 among the variable parts in the test code template information, a variable part indicating “request generation screen URL item” or “transition destination screen URL item” (# request generation The screen URL #) is replaced with the value (searchIndex.jsp) of the item that matches the variable part in the design information object.

  In addition, the test code generation unit 17 assigns a variable portion (#HTML element (title) .default value #) indicating a “default value indicating that the item of the HTML element indicates a title” of each variable portion as a design information object. Is replaced with the default value (search condition screen) in the same object (S1-1 object) as the variable part.

  Also, the test code generation unit 17 includes a variable portion indicating “a value of a Name attribute indicating that an HTML element item indicates an input” or “a value of a Name attribute indicating an text element” of each variable portion. ("#HTML element (input) .Name attribute #" or "#HTML element (textarea) .Name attribute #") is the same object (S1-3 object or S1-2 object) as the variable part in the design information object Replace with the value of “Execute Search” or “idFromForSearch”.

  Further, the test code generation unit 17 further adds the same object (S1-S1) to the variable portion (#HTML element (textarea) .Name attribute #) indicating the “value of the Name attribute indicating that the HTML element item is a text area”. Next to the value of the Name attribute (idFromForSearch) that replaced the value (1111) of the search result associated with the physical name value (id) in the database that matches the physical name value (id) in (2 objects) Insert in line (<td> <td>). In this way, the test code generation unit 17 generates a test code from the test code template information.

  In step ST8, the test code generation unit 17 outputs the generated test code.

  As described above, according to the second embodiment, in the configuration of the first embodiment, a configuration using specific design document data, test procedure pattern information, storage contents of the operation storage unit 14, and test code fragment information. Thus, in addition to the effects of the first embodiment, a test code having an HTML code format can be generated.

(Third embodiment)
The third embodiment is an example specifically showing input and output in the configuration of FIG. 1 and the operation of FIG. 2 described in the first embodiment, and the design document data shown in FIGS. 3 to 7 is input. The test code of the test automation tool (tool B) whose code format is Java (registered trademark) is output. Note that the various design document data, design information object, test procedure pattern information, and processes from step ST1 to ST4 are the same as those in the second embodiment, and thus redundant description is omitted.

  Below, it demonstrates from step ST5 of the flowchart of FIG.

  In step ST5, the test code generation unit 17 specifies test code fragment information to be used from the type of test code fragment information selected on the input screen G10. Here, the test code fragment information to be used is specified from the type of the test code fragment information for tool B corresponding to the Java code format.

  Here, examples of Java-format test code fragment information are shown in FIGS.

  The test code fragment information shown in FIG. 17 includes a test code fragment ID “open” and a variable portion, and the variable portion includes a request generation screen URL item “# request generation screen URL #”. As similar test code fragment information, test code fragment information (not shown) including a test code fragment ID “open” and a variable portion “# transition destination screen URL #” is also stored in the test code fragment storage unit 15.

  The test code fragment information shown in FIG. 18 includes a test code fragment ID (assertEquals) and a variable part. The variable part includes a default value (#HTML element (title)) in which the item of the HTML element indicates a title. Contains the default value #).

  The test code fragment information shown in FIG. 19 includes a test code fragment ID (type) and a variable part. As the variable part, the value of the Name attribute indicating the text area and the physical name are id. The indicated value (#HTML element (textarea) .Name attribute #, #physical name (id) #) is included.

  The test code fragment information shown in FIG. 20 includes a test code fragment ID (click) and a variable part. As the variable part, the value of the Name attribute (#HTML element (input)) in which the item of the HTML element indicates the input .Name attribute #).

  In step ST6, as shown in FIG. 21, the test code generation unit 17 performs a test based on the test procedure pattern information read in step ST4 and the type of test code fragment information specified in step ST5. Generate code template information.

  Specifically, step ST6 is executed as shown in steps ST6-1 to ST6-2 below.

  In step ST6-1, the test code generation unit 17 reads the test procedure name in the test procedure pattern information read in step ST4 in the test order, and an operation storage unit that matches the read test procedure name. The test code fragment ID associated with the test procedure name in 14 is read from the operation storage unit 14.

  In step ST6-2, the test code generation unit 17 reads the test code information including the test code fragment ID that matches the read test code fragment ID from the test code fragment storage unit 15, and tests the read test code information. Test code template information is created by combining them in order.

  In step ST7, as shown in FIG. 22, the test code generation unit 17 generates the generated test code template information, the design information object generated by the design information object generation unit 12, and the database unit 20 used in the test. Test code is generated based on the value of.

  Specifically, the test code generation unit 17 among the variable parts in the test code template information, a variable part indicating “request generation screen URL item” or “transition destination screen URL item” (# request generation The screen URL #) is replaced with the value (searchIndex.jsp) of the item that matches the variable part in the design information object.

  In addition, the test code generation unit 17 assigns a variable portion (#HTML element (title) .default value #) indicating a “default value indicating that the item of the HTML element indicates a title” of each variable portion as a design information object. Is replaced with the default value (search condition screen) in the same object (S1-1 object) as the variable part.

  In addition, the test code generation unit 17 includes a variable part (#HTML element (textarea) indicating the value of the Name attribute indicating that the HTML element item indicates a text area and the physical name indicating id) among the variable parts. .Name attribute #, # physical name (id) #) match the value of the Name attribute (idFromForSearch) and physical value (id) in the same object (S1-2 object) as the variable part in the design information object To the search result value (1111) associated with the physical name value (id) in the database to be replaced.

  In addition, the test code generation unit 17 assigns a variable part (#HTML element (input) .Name attribute #) indicating “value of Name attribute indicating that the HTML element item indicates input” among the variable parts to the design information object. Is replaced with the value of the Name attribute (search execution) in the same object (S1-3 object) as the variable part. In this way, the test code generation unit 17 generates a test code from the test code template information.

  In step ST8, the test code generation unit 17 outputs the generated test code.

  As described above, according to the third embodiment, instead of the test procedure pattern information of the second embodiment, the storage contents of the operation storage unit 14 and the test code fragment information, the test procedure pattern information corresponding to the Java format, In addition to the effects of the first embodiment, a test code having a Java code format can be generated by the configuration using the storage contents of the operation storage unit 14 and the test code fragment information.

  According to at least one embodiment described above, the test code template information is generated based on the test procedure pattern information and the test code fragment information, and based on the test code template information, the design information object, and the test value. With the configuration for generating the test code, the test procedure can be reused, and it is not necessary to define the test procedure for each software to be tested.

  Note that the methods described in the above embodiments are, as programs that can be executed by a computer, magnetic disks (floppy (registered trademark) disks, hard disks, etc.), optical disks (CD-ROMs, DVDs, etc.), magneto-optical disks. (MO), stored in a storage medium such as a semiconductor memory, and distributed.

  The storage medium may be in any form as long as it can store a program and can be read by a computer.

  In addition, an OS (operating system) running on a computer based on an instruction of a program installed in the computer from a storage medium, MW (middleware) such as database management software, network software, and the like realize the above-described embodiment. A part of each process may be executed.

  Furthermore, the storage medium in each embodiment is not limited to a medium independent of a computer, but also includes a storage medium in which a program transmitted via a LAN, the Internet, or the like is downloaded and stored or temporarily stored.

  Further, the number of storage media is not limited to one, and the case where the processing in each of the above embodiments is executed from a plurality of media is also included in the storage media in the present invention, and the media configuration may be any configuration.

  The computer in each embodiment executes each process in each of the above embodiments based on a program stored in a storage medium, and a single device such as a personal computer or a plurality of devices are connected to a network. Any configuration of the system or the like may be used.

  Furthermore, the computer in each embodiment is not limited to a personal computer, and includes a processing device, a microcomputer, and the like included in an information processing device, and is a generic term for devices and devices that can realize the functions of the present invention by a program. Yes.

  In addition, although some embodiment of this invention was described, these embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 10 ... Test code production | generation apparatus, 11 ... Design document reading part, 12 ... Design information object production | generation part, 13 ... Test procedure pattern memory | storage part, 14 ... Operation memory part, 15 ... Test code fragment memory | storage part, 16 ... Test procedure pattern extraction Reference numeral 17, Test code generation unit 20, Database unit 21, Table data generation unit 30, Test automation tool unit

Claims (3)

Connected to the database unit as a related table for storing the physical name value to be searched and the search result value in association with each other, and includes a test procedure pattern storage unit, an operation storage unit, a test code fragment storage unit, and a Web application A test code generation program used in a test code generation device for generating a test code used in a test automation tool from a plurality of design document data in
The test code generator for the previous term
Screen transition design document data of the design document data, and screen transition ID items and values, scenario name items and values, and request generation screen URL items and values related to the transition of each screen of the Web application , And means for receiving input of the screen transition design document data indicating the items and values of the transition destination screen URL in association with each other,
Screen item design document data of each of the design document data, regarding items of each screen of the Web application, items and values of screen item IDs, items and values of HTML elements, items and values of default values, Name Of the item and value of the attribute and the physical name item and value of the related table, the item and value of the first screen item ID of the screen item ID, the value indicating the item and title of the HTML element, and the default A value item and a value are shown in association with each other, the item and value of the second screen item ID in the screen item ID, the value of the HTML element item and text area, the item of the Name attribute and the physical name of the search target And the physical name item and value of the association table are shown in association with each other, the third screen item ID item and value of the screen item ID, and the HTML element item and input. The value indicating the door, and means for accepting input of the screen item design document data indicating associating a value, indicating the execution and items of the Name attribute,
Screen list design document data of the design document data, the screen list design document data indicating the screen ID items and values and the screen URL items and values associated with each screen of the Web application. Means to accept input,
Means for writing test procedure pattern information including a test procedure pattern ID consisting of the same character string as any value of the scenario name and a plurality of test procedure names arranged in the test order in the test procedure pattern storage means ,
Means for associating the test procedure name, operation and test code fragment ID in the operation storage means;
The test code fragment ID and the variable part are included, and the variable part includes the request generation screen URL item, the transition destination screen URL item, the HTML element item and the value indicating the title, the HTML element Means for individually writing a plurality of pieces of test code fragment information into the test code fragment storage means, each of which includes an item and a value indicating an input or an item of a screen item value;
Means for extracting the item and value of the scenario name from the screen transition design document data that has received the input;
If the extracted scenario name value includes another scenario name value that is the same as the scenario name value, the screen transition object further includes an object name including an identification number and a property. The properties include the request generation screen URL item and value associated with the scenario name value in the object name in the screen transition design document data, the transition destination screen URL item and value, and the request generation. The request generation screen ID value and the item including the screen ID value associated with the screen URL value in the screen list design document that matches the screen URL value, and the request generation screen ID value as the object name The request generation screen item indicating the request generation screen object and the screen that matches the value of the transition destination screen URL. A transition destination screen ID including a screen ID value associated with a screen URL value in the design document, and a transition destination screen item indicating a transition destination screen object having the transition destination screen ID value as an object name. Screen transition object generating means for generating the screen transition object;
A request generation screen object including an object name consisting of a request generation screen ID value of the screen transition object and a property, and the property includes the screen item design document that matches the request generation screen ID value in the middle Generating screen object generating means for generating the request generating screen object, including a screen item consisting of the value of the screen item ID
A request generation screen item object including an object name consisting of a screen item ID value of the request generation screen object and a property, and the property is associated with the value of the screen item ID in the screen item design document A first generated screen item composed of the items and values of the HTML element and the default value items and values, the HTML element items and values associated with the screen item ID value in the screen item design document, and the Name attribute Of the second generation screen item consisting of the item and value of the item and the physical name of the related table, and the value of the HTML element item and value associated with the value of the screen item ID in the screen item design document. The request generation screen item object including one of the generation screen items of the item and the third generation screen item composed of values. Generating screen item object generation means for generating individual,
A transition destination screen object including an object name including a transition destination screen ID value of the screen transition object and a property, and the property includes the screen item design document that matches the transition destination screen ID value in the middle A transition destination screen object generating means for generating the transition destination screen object, including a screen item consisting of a screen item ID value
A transition destination screen item object including an object name consisting of a screen item ID value of the transition destination screen object and a property, the property being associated with the value of the screen item ID in the screen item design document A first transition destination screen item consisting of the HTML element item and value and the default value item and value, and the HTML element item and value associated with the screen item ID value in the screen item design document, Name A second transition destination screen item composed of the attribute item and value and the physical name item and value of the related table, the HTML element item and value associated with the value of the screen item ID in the screen item design document, and Name The transition destination screen item object including one of the transition destination screen items of the attribute item and the third transition destination screen item composed of values is generated individually. Transition destination screen item object generating means,
Design information object generating means for generating a design information object including the screen transition object, the request generation screen object, the request generation screen item object, the transition destination screen object, and the transition destination screen item object;
A test procedure pattern reading unit that reads test procedure pattern information including a test procedure pattern ID that matches a scenario name value included in the object name of the screen transition object in the design information object from the test procedure pattern storage unit;
The test procedure name in the read test procedure pattern information is read in the test order, and the test code fragment ID associated with the test procedure name in the operation storage means that matches the read test procedure name is Means for reading from the storage means;
Test code information including a test code fragment ID matching the read test code fragment ID is read from the test code fragment storage means, and the read test code information is combined in the test order to obtain test code template information. Means to create,
Among the variable parts in the test code template information, the variable part indicating “the item of the request generation screen URL” or “the item of the transition destination screen URL” matches the variable part in the design information object. The value of the item is replaced with a variable part indicating “the value of the default value indicating that the item of the HTML element indicates a title” among the variable parts, and the default in the same object as the variable part in the design information object. In the design information object, a variable part indicating “value of Name attribute indicating that the item of the HTML element indicates input” or “value indicating a physical name indicating id” is replaced in the design information object. To replace the value with the value of the Name attribute in the same object as the variable part. By inserting the search result value associated with the physical name value in the database that matches the physical name value in the object into the line next to the value of the replaced Name attribute, from the test code template information Means for generating the test code;
Test code generation program to function as In the test code generation program according to claim 1,
The test code generation device;
Exception processing design document data among the respective design document data, regarding exception processing of the Web application, items and values of exception occurrence conditions, items and values of exception occurrence screen URLs, items of exception occurrence transition destination screen URLs Means for accepting an input of the exception process design document data indicating the item and value and the item and value of the exception message in association with each other;
Prior to the reading by the test procedure pattern reading means, it is associated with the value of the scenario name in the screen transition design document data that matches the value of the scenario name included in the object name of the screen transition object in the design information object. The determination of whether or not the request generation screen URL value and the transition destination screen URL value match the exception generation screen URL value and the exception generation transition destination screen URL value in the exception processing design data. means,
Further function as
The test procedure pattern reading unit reads the test procedure pattern information when the result of determination by the determination unit does not match. Test code that is connected to the database section as a related table that stores the physical name value to be searched and the search result value in association with each other, and generates test code used by the test automation tool from a plurality of design document data in the Web application A generating device,
Screen transition design document data of the design document data, and screen transition ID items and values, scenario name items and values, and request generation screen URL items and values related to the transition of each screen of the Web application And means for receiving input of the screen transition design document data indicating the items and values of the transition destination screen URL in association with each other;
Screen item design document data of each of the design document data, regarding items of each screen of the Web application, items and values of screen item IDs, items and values of HTML elements, items and values of default values, Name Of the item and value of the attribute and the physical name item and value of the related table, the item and value of the first screen item ID of the screen item ID, the value indicating the item and title of the HTML element, and the default A value item and a value are shown in association with each other, the item and value of the second screen item ID in the screen item ID, the value of the HTML element item and text area, the item of the Name attribute and the physical name of the search target And the physical name item and value of the association table are shown in association with each other, the third screen item ID item and value of the screen item ID, and the HTML element item and input. It means for receiving a value indicating the door, and an input of the screen item design document data indicating associating a value, indicating the execution and items of the Name attribute,
Screen list design document data of the design document data, the screen list design document data indicating the screen ID items and values and the screen URL items and values associated with each screen of the Web application. Means for accepting input,
Test procedure pattern storage means for storing test procedure pattern information including a test procedure pattern ID consisting of the same character string as any value of the scenario name and a plurality of test procedure names arranged in the test order;
Operation storage means for storing the test procedure name, operation and test code fragment ID in association with each other;
The test code fragment ID and the variable part are included, and the variable part includes the request generation screen URL item, the transition destination screen URL item, the HTML element item and the value indicating the title, the HTML element Test code fragment storage means for storing a plurality of pieces of test code fragment information, each of which includes an item and a value indicating an input, or an item of a screen item value;
Means for extracting the item and value of the scenario name from the screen transition design document data that has received the input;
If the extracted scenario name value includes another scenario name value that is the same as the scenario name value, the screen transition object further includes an object name including an identification number and a property. The properties include the request generation screen URL item and value associated with the scenario name value in the object name in the screen transition design document data, the transition destination screen URL item and value, and the request generation. The request generation screen ID value and the item including the screen ID value associated with the screen URL value in the screen list design document that matches the screen URL value, and the request generation screen ID value as the object name The request generation screen item indicating the request generation screen object and the screen that matches the value of the transition destination screen URL. A transition destination screen ID including a screen ID value associated with a screen URL value in the design document, and a transition destination screen item indicating a transition destination screen object having the transition destination screen ID value as an object name. Screen transition object generating means for generating the screen transition object;
A request generation screen object including an object name consisting of a request generation screen ID value of the screen transition object and a property, and the property includes the screen item design document that matches the request generation screen ID value in the middle A generation screen object generation means for generating the request generation screen object, including a screen item consisting of the value of the screen item ID
A request generation screen item object including an object name consisting of a screen item ID value of the request generation screen object and a property, and the property is associated with the value of the screen item ID in the screen item design document A first generated screen item composed of the items and values of the HTML element and the default value items and values, the HTML element items and values associated with the screen item ID value in the screen item design document, and the Name attribute Of the second generation screen item consisting of the item and value of the item and the physical name of the related table, and the value of the HTML element item and value associated with the value of the screen item ID in the screen item design document. The request generation screen item object including one of the generation screen items of the item and the third generation screen item composed of values. And generating screen item object generating means for generating separately,
A transition destination screen object including an object name including a transition destination screen ID value of the screen transition object and a property, and the property includes the screen item design document that matches the transition destination screen ID value in the middle A transition destination screen object generating means for generating the transition destination screen object, including a screen item consisting of the value of the screen item ID in
A transition destination screen item object including an object name consisting of a screen item ID value of the transition destination screen object and a property, the property being associated with the value of the screen item ID in the screen item design document A first transition destination screen item consisting of the HTML element item and value and the default value item and value, and the HTML element item and value associated with the screen item ID value in the screen item design document, Name A second transition destination screen item composed of the attribute item and value and the physical name item and value of the related table, the HTML element item and value associated with the value of the screen item ID in the screen item design document, and Name The transition destination screen item object including one of the transition destination screen items of the attribute item and the third transition destination screen item composed of values is generated individually. And the transition destination screen item object generating means,
Design information object generating means for generating a design information object including the screen transition object, the request generation screen object, the request generation screen item object, the transition destination screen object, and the transition destination screen item object;
A test procedure pattern reading unit that reads test procedure pattern information including a test procedure pattern ID that matches a scenario name value included in the object name of the screen transition object in the design information object from the test procedure pattern storage unit;
The test procedure name in the read test procedure pattern information is read in the test order, and the test code fragment ID associated with the test procedure name in the operation storage means that matches the read test procedure name is Means for reading from the storage means;
Test code information including a test code fragment ID matching the read test code fragment ID is read from the test code fragment storage means, and the read test code information is combined in the test order to obtain test code template information. Means to create,
Among the variable parts in the test code template information, the variable part indicating “the item of the request generation screen URL” or “the item of the transition destination screen URL” matches the variable part in the design information object. The value of the item is replaced with a variable part indicating “the value of the default value indicating that the item of the HTML element indicates a title” among the variable parts, and the default in the same object as the variable part in the design information object. In the design information object, a variable part indicating “value of Name attribute indicating that the item of the HTML element indicates input” or “value indicating a physical name indicating id” is replaced in the design information object. To replace the variable part with the value of the Name attribute in the same object, and for the variable part indicating the “value where the physical name indicates id”, By inserting the search result value associated with the physical name value in the database that matches the physical name value in the object into the line next to the value of the replaced Name attribute, from the test code template information Means for generating the test code;
A test code generation device comprising:

Images