JP5651050B2 - Data generation apparatus and data generation program - Google Patents

Description

  The present invention relates to a data generation device and a data generation program.

  Conventionally, in the development of a business application program using a Web browser or a GUI (Graphical User Interface), a test related to the developed business application program is performed. In such a test, a person who executes the test creates test data corresponding to the test content using a text editor or the like, and various tests are performed using the created test data.

  For example, the person in charge creates test data for input values to be entered from the business application screen, and uses the created test data for input values to determine whether the business application operates as expected with respect to the input values. Testing. Further, the person in charge creates display value test data displayed on the screen of the business application, and tests whether the displayed value is as expected using the created display value test data. The person in charge uses a large amount of test data to test whether the processing of the business application is executed without delay.

  Here, several techniques for creating test data used for testing business application programs are known. For example, a technique for creating test data similar to existing test data is known as a technique for creating test data. In addition, for example, a technique for creating test data that maintains the consistency of the data reference relationship based on data definition information and key information from an existing database is known. In addition, for example, a technique for creating test data that maintains the consistency of the data reference relationship based on the correspondence between tables stored in a database is known.

JP 2010-140166 A JP 2008-226056 A JP 2009-99126 A

  However, the above-described conventional technique has a problem that test data in which consistency between data is maintained cannot be easily created. For example, in the conventional technology described above, it is difficult to create test data that is not similar to existing test data, and it is not possible to easily create test data that maintains the consistency of new reference relationships. In addition, for example, in the above-described conventional technology, test data cannot be created when there is no definition information or key information about data, or information about correspondence between tables, and the consistency of the reference relationship between the data is reduced. Maintained test data cannot be easily created.

  Accordingly, in view of the above-described problems of the conventional technology, the technology of the present disclosure provides a data generation device and a data generation program that can easily create test data in which consistency between data is maintained. With the goal.

  In order to solve the above-described problems and achieve the object, the disclosed apparatus includes a data information acquisition unit and a data generation unit. For each item of data used by the business application to be tested, the data information acquisition unit includes information on a data item indicating the attribute of the data and reference information indicating a reference relationship between data regarding the data used by the business application. get. A data generation part produces | generates the test data according to at least one among the information relation of the data item acquired by the said data information acquisition part, and the reference information for every item of the said data.

  The disclosed apparatus makes it possible to easily create test data in which consistency between data is maintained.

FIG. 1 is a diagram illustrating an example of the configuration of the test data generation apparatus according to the first embodiment. FIG. 2 is a diagram illustrating a first example of a GUI displayed and output by the display device according to the first embodiment. FIG. 3 is a diagram for explaining information acquired by the database information acquisition unit according to the first embodiment. FIG. 4 is a diagram illustrating an example of data types according to the first embodiment. FIG. 5A is a diagram illustrating an example of reference information according to the first embodiment. FIG. 5B is a schematic diagram illustrating an example of processing performed by the test data structure creation control unit according to the first embodiment. FIG. 5C is a diagram illustrating an example of an SQL sentence received by the test data structure input receiving unit according to the first embodiment. FIG. 6 is a diagram illustrating a first example of test data generated by the test data generation unit according to the first embodiment. FIG. 7 is a schematic diagram illustrating an example of a business application screen according to the first embodiment. FIG. 8 is a diagram illustrating an example of the source code of the screen processing according to the first embodiment. FIG. 9 is a diagram illustrating an example of the external definition of the input check according to the first embodiment. FIG. 10 is a diagram illustrating an example of a framework check definition according to the first embodiment. FIG. 11 is a diagram illustrating a second example of a GUI displayed and output by the display device according to the first embodiment. FIG. 12A is a diagram illustrating a second example of test data generated by the test data generation unit according to the first embodiment. FIG. 12B is a diagram illustrating a third example of the test data generated by the test data generation unit according to the first embodiment. FIG. 13 is a diagram illustrating an example of a test data search screen displayed by the test data generation apparatus according to the first embodiment. FIG. 14 is a flowchart for explaining a procedure of data type acquisition processing from the database by the test data generation apparatus according to the first embodiment. FIG. 15 is a flowchart for explaining the procedure of the data item reference relationship determination process performed by the test data generation apparatus according to the first embodiment. FIG. 16 is a flowchart for explaining a first procedure of test data generation processing by the test data generation apparatus according to the first embodiment. FIG. 17 is a flowchart for explaining the creation of related data as the second procedure of the test data generation process performed by the test data generation apparatus according to the first embodiment. FIG. 18 is a flowchart for explaining a third procedure of the test data generation process performed by the test data generation apparatus according to the first embodiment. FIG. 19 is a flowchart for explaining the procedure of the data type acquisition process from the source code for the screen processing implemented by the test data generation apparatus according to the first embodiment. FIG. 20 is a flowchart for explaining the procedure for acquiring information for each data item from the framework input check definition by the test data generation apparatus according to the first embodiment. FIG. 21 is a flowchart for explaining a fourth procedure of the test data generation process performed by the test data generation apparatus according to the first embodiment. FIG. 22 is a diagram for explaining a computer that executes a data generation program according to the second embodiment.

  Exemplary embodiments of a data generation device and a data generation program disclosed in the present application will be described below in detail with reference to the accompanying drawings. Note that the data generation device and the data generation program disclosed in the present application are not limited to the following embodiments.

  The test data generating apparatus according to the first embodiment generates test data used for a program test executed when developing a business application. Specifically, the test data generation device according to the first embodiment acquires data item information indicating an attribute of the data for each item of data used by the business application to be tested. Then, the test data generation apparatus according to the first embodiment acquires reference information indicating a reference relationship between data regarding data used by the business application. The test data generation device according to the first embodiment generates test data corresponding to at least one of the data attribute and the reference relationship of the reference information for each data item.

  For example, the test data generation apparatus according to the first embodiment acquires data item information indicating data attributes for each data item for generating test data from a source code that implements database definition or screen processing. The test data generation apparatus according to the first embodiment acquires a table correspondence or a reference relationship between data from an SQL (Structured Query Language) sentence set by the user for each data item. Then, the test data generation apparatus according to the first embodiment generates test data corresponding to the data attribute, test data corresponding to the reference relationship, and the like for each data item. Therefore, the test data generation apparatus according to the first embodiment can create test data that is not similar to existing test data, for example. In addition, the test data generation apparatus according to the first embodiment can create test data by using an SQL statement even when there is no definition information or key information regarding data, or information regarding correspondence between tables. it can. As a result, the test data generation apparatus according to the first embodiment can easily create test data in which consistency between data is maintained.

  First, the configuration of the test data generation apparatus according to the first embodiment will be described. FIG. 1 is a diagram illustrating an example of the configuration of the test data generation apparatus 100 according to the first embodiment. As shown in FIG. 1, the test data generation device 100 includes an input device 110, a display device 120, a test data structure creation control unit 130, a data information acquisition unit 140, a test data structure input reception unit 150, a test A data creation control unit 160, a database data acquisition unit 170, a test data generation unit 180, and a related data generation unit 190 are included. As shown in FIG. 1, the test data generation apparatus 100 is connected to a terminal 200 on which a business application is executed and a database 300 in which various data are stored. As shown in FIG. 1, the test data generation apparatus 100 uses a variety of data stored in the database 300 and a business application source file / data definition file 201 stored in the terminal 200 and the like for load testing. Test data 181, display test test data 182, input test test data 183, related data 191, and the like are generated.

  The terminal 200 stores, for example, a business application source file created using a development framework and a development framework definition file. Then, the terminal 200 executes various processes related to the stored business application. The database 300 stores, for example, a relational database indicating various data used in a business application executed by the terminal 200 and a reference relationship between tables.

  The load test test data 181 is test data for testing whether or not business application processing is executed without delay. The display test test data 182 is test data for testing whether or not the value displayed on the screen of the business application is as expected. The input test test data 183 is test data for testing whether or not the business application operates as expected with respect to an input value input from the screen of the business application. The related data 191 will be described later.

  The input device 110 is, for example, a keyboard, a mouse, and the like, and accepts various information input processes by the user. For example, the input device 110 accepts input processing such as information indicating test contents and an SQL sentence indicating a reference destination when generating test data. The display device 120 is, for example, a display, and displays and outputs the processing result to the user under the control of the test data structure creation control unit 130 described later. For example, the display device 120 displays and outputs a test data generation process to the user via the GUI.

  FIG. 2 is a diagram illustrating a first example of a GUI displayed and output by the display device 120 according to the first embodiment. For example, as shown in FIG. 2, the display device 120 displays and outputs a “PT (Program Test) data generation tool” window. As shown in FIG. 2, the “PT (Program Test) data generation tool” window displayed and output by the display device 120 has a “generation data setting” tab and a “DB connection setting” tab. The “generation data setting” tab is a tab on which setting items for generating test data are displayed, and information on data for which test data is to be generated is displayed.

  As shown in FIG. 2, the “generation data setting” tab includes an upper window in which “generation target”, “table name”, “Japanese name”, and “number of generated data items” are associated, and “column number”. , “Item Name”, “Type”, “Number of Digits”, “Japanese Name”, “Data Generation Method”, “Data Digits” and “Data Generation Pattern” are associated with the lower window . In the upper window, information regarding a table including data to be generated as test data is displayed. For example, in the upper window, as shown in FIG. 2, “table name: M_SHAIN, Japanese name: employee master (common)” is displayed. The “generation target” in the upper window is an area where the user selects a table for which test data is to be generated. The “number of generated data items” is an area where the number of test data items to be generated is input by the user.

  In the lower window, information for each item of data included in the table selected in the upper window is displayed. For example, in the lower window, as shown in FIG. 2, “Column No. 1, Item name: SOSHIKIZU_CD, Type: varchar, Number of digits: 6, Japanese name: Organization chart code, Data generation method: Full-width Japan “Word, number of data digits: 6”, etc. are displayed. The above-described information is obtained when the user selects “table name: M_SEDAI, Japanese name: generation management master (common)” in the upper window, and the lower window for the items of data included in the selected table. Is displayed. Details of information for each item in the lower window will be described later. The “DB connection setting” tab is a tab on which connection settings between the test data generating apparatus 100 and the database 300 are displayed.

  Returning to FIG. 1, the test data structure creation control unit 130 controls various processes related to the structure determination of the test data to be created. Specifically, the test data structure creation control unit 130 first selects an information acquisition destination for each data item based on the test content specified by the user. More specifically, the test data structure creation control unit 130 selects either the database 300 or the terminal 200 as an acquisition source of information for each data item based on the test content information input via the input device 110. Select one.

  For example, when the test data structure creation control unit 130 receives information indicating that the test content is a load test, the test data structure creation control unit 130 selects the database 300 as an acquisition source, and stores information for each data item from the table information stored by the database 300. The database information acquisition unit 141 of the data information acquisition unit 140, which will be described later, is controlled so as to acquire. When the test data structure creation control unit 130 receives information indicating that the test content is a display test or an input test, the test data structure creation control unit 130 selects the terminal 200 as an acquisition destination and stores the source code or frame of the business application stored by the terminal 200 The screen information acquisition unit 142 of the data information acquisition unit 140 (to be described later) is controlled so as to acquire information for each data item from the work definition file.

  Then, the test data structure creation control unit 130 stores in the internal memory information reflecting the information for each item of data acquired by the database information acquisition unit 141 or the screen information acquisition unit 142 of the data information acquisition unit 140. Then, control is performed so that the window is displayed on the display device 120 based on the stored information. In the following, first, the case where data item information is acquired from the database 300 and load test test data is generated will be described, and then data item information is acquired from the terminal 200 to generate input test test data. The case where it does is demonstrated.

  As shown in FIG. 1, the data information acquisition unit 140 includes a database information acquisition unit 141 and a screen information acquisition unit 142. For each data item used by the business application to be tested, an attribute of the data is acquired. The information of the data item to be displayed and the reference information indicating the reference relationship between the data related to the data used by the business application are acquired. The database information acquisition unit 141 acquires, for each data item used by the test target business application, data item information indicating the attribute of the data. Specifically, the database information acquisition unit 141 acquires table information of the data from the database 300 that stores information related to data used by the test target business application under the control of the test data structure creation control unit 130. . Then, when a table that is a test data generation target is selected by the user, the database information acquisition unit 141 acquires information for each item of data included in the selected table.

  FIG. 3 is a diagram for explaining information acquired by the database information acquisition unit 141 according to the first embodiment. FIG. 3 shows a state after information for each data item is acquired by the database information acquisition unit 141. For example, the database information acquisition unit 141 first acquires table information such as “table name: M_SHAIN, Japanese name: employee master (common)” shown in the area (2) of FIG. Then, as shown in the area (1) of FIG. 3, when the table “table name: M_SEDAI, Japanese name: generation management master (common)” is selected by the user from the table information, the database information acquisition unit 141 3, for each data item included in the selected table of “table name: M_SEDAI, Japanese name: generation management master (common)”, as shown in areas (3) and (4) of FIG. The information of the data item indicating the attribute is acquired from the database 300. For example, the database information acquisition unit 141 acquires the data type “type: varchar, number of digits: 6, Japanese name: organization chart code” of “item name: SOSHIKIZU_CD”. Furthermore, the database information acquisition unit 141 acquires a data reference relationship from the database 300 for each item. The data generation method shown in the pull-down method in the area (5) of FIG. 3 is displayed by the test data structure creation control unit 130 based on the data item information acquired by the database information acquisition unit 141 and the data reference relationship. The content to be determined is determined. In the data generation pattern shown in the area (6) of FIG. 3, reference destination information is displayed based on the data generation method selected by the user from the pull-down shown in the area (5) of FIG.

  Here, details of contents set in the areas (4) to (6) of FIG. 3 will be described. The “type” shown in the area (4) of FIG. 3 means the type of the data item, and includes, for example, a numerical value, a character, and a date. That is, “Type” in FIG. 3 indicates what character string the data of each item is created. For example, “varchar” is generated by characters such as Japanese. It shows that. Further, “int” in FIG. 3 indicates that data is generated by a numerical value, and “datetime” indicates that data is generated by a date format. “Number of digits” means the maximum number of digits of the data item. For example, the number of digits “8” indicates a character string created with data of 8 digits or less. Next, “Japanese name” indicates the name of the data item in Japanese. Information on these character strings is acquired from definition information stored in the database 300.

  The data generation method shown in the area (5) of FIG. 3 is based on the type information and the information acquired by the database information acquisition unit 141, that is, based on the information shown in the area (4) of FIG. The data type is set by the test data structure creation control unit 130. FIG. 4 is a diagram illustrating an example of data types according to the first embodiment. For example, in the data generation method, one of the data types shown in FIG. 4 is automatically selected and set based on the data item information. For example, when “type” is “datatime” and the number of digits is “8”, “date type_date (YYYYMMDD format)” is selected as the data type. As another example, when “type” is “varchar” and the number of digits is “6”, “character type_half-width & number” is selected as the data type. Here, as a criterion for selecting the data type, it may be determined depending on what character string represents the Japanese name of the data type. For example, when the Japanese name of the data type is represented by a character string of “˜code”, it is determined that the required test data is a numerical code, and “character type_half-width & number” is selected.

  On the other hand, when the reference information indicating the reference relationship is stored in the database 300, the test data structure creation control unit 130 sets a data generation method and a data generation pattern as described below. FIG. 5A is a diagram illustrating an example of reference information according to the first embodiment. FIG. 5A shows reference information in which a reference relationship is indicated by a primary key (PK) and a foreign key (FK). For example, when generating test data for the product data shown in FIG. 5A, the data of “item: category code” is a data generation method and data generation pattern so that the category code in the category data of the reference destination is used. Is set.

  FIG. 5B is a schematic diagram illustrating an example of processing performed by the test data structure creation control unit 130 according to the first embodiment. FIG. 5 shows a part of the window when “item: category code (CATEGORY_CD)” is targeted. When the reference information shown in FIG. 5A is stored in the database 300 and acquired by the database information acquisition unit 141, the test data structure creation control unit 130 sets the data generation method to “external reference” as shown in FIG. 5B. And set. Then, as shown in FIG. 5B, the test data structure creation control unit 130 sets “M_CATEGORY.CATEGORY_CD”, which is information indicating that the category code of the category data is the reference destination, as the data generation pattern. In addition, “random generation” or “SQL setting” can be set as a data generation method by user selection. When the data generation method is “random generation”, the data is generated in a format that matches the data type “type” and “number of digits”. When the data generation method is “SQL setting”, a SQL statement is set in the data generation pattern, and data is generated according to the set SQL. In this case, the SQL sentence is set as a data generation pattern. The data generation method is pull-down as shown in FIGS. 3 and 5B. That is, a plurality of contents to be set as the data generation method can be set, and the final data generation method can be selected by the user.

  Returning to FIG. 1, the test data structure input receiving unit 150 reflects the setting input from the user via the input device 110 in the window shown in FIG. 3. For example, the test data structure input accepting unit 150 accepts selection of a table to be a test data generation target or selection of a data generation method by pull-down, and reflects it in each setting item. In addition, the test data structure input receiving unit 150 receives the number of data items generated for each data item and reflects the number of data items generated in the window.

  Further, when “SQL setting” is set as the data generation method, the test data structure input receiving unit 150 receives an SQL sentence as reference information and reflects it in the data generation pattern in the window. FIG. 5C is a diagram illustrating an example of an SQL sentence received by the test data structure input receiving unit 150 according to the first embodiment. For example, as shown in FIG. 5C, the test data structure input receiving unit 150 receives an SQL statement “SELECT BUMON_CD FROM M_BUMON” to “select department code data from the department master” via the input device 110. Set to generation pattern. Similarly, the test data structure input receiving unit 150, as shown in FIG. 5C, the SQL statement “Selecting data with department codes 010 to 250 when selecting department code data from the department master”. "SELECT BUMON_CD FROM M_BUMON WHERE BUMON_CD BETWEEN '010' AND'250 '" is received via the input device 110 and set as a data generation pattern.

  Returning to FIG. 1, the test data creation control unit 160 controls various processes related to generation of test data based on the window information set by the test data structure creation control unit 130 and the test data structure input reception unit. Specifically, the test data creation control unit 160 controls processing by a database data acquisition unit 170, a test data generation unit 180, and a related data generation unit 190 described later.

  The database data acquisition unit 170 acquires data used for generating test data from the database 300 based on the window information set by the test data structure creation control unit 130 and the test data structure input reception unit 150. For example, when “external reference” is set as the data generation method, the database data acquisition unit 170 acquires data from “category data” to “category code” shown in FIG.

  The test data generation unit 180 has at least one of data type attribute or reference information, SQL setting, or random generation set based on the data type information acquired by the database information acquisition unit 141 for each data item. Generate test data according to Specifically, the test data generation unit 180 generates test data based on the data generation method and data generation pattern included in the window information.

  For example, when the data generation pattern is not set, the test data generation unit 180 generates the set number of test data corresponding to the setting contents of the data generation method. For example, when generating the test data of “SOSHIKIZU_CD” in FIG. 3, the data generation pattern is not set, and the data generation method is “data generation method: full-width Japanese”. For this reason, the test data generation unit 180 generates a 6-byte random Japanese character string as test data. Similarly, when the data generation method is “random generation”, data is randomly generated in a format that matches the data type “type” and “number of digits”. For example, when the type is “int” and the number of digits is “3”, the test data generation unit 180 generates a random three-digit number as test data.

  On the other hand, when the data generation pattern is set, the test data generation unit 180 generates the set number of test data according to the data generation method and the setting contents of the data generation pattern. As an example, when the test data of “CATEGORY_CD” in FIG. 5B is generated, the data generation method is “external reference”, and “M_CATEGORY.CATEGORY_CD” is set as the reference destination in the data generation pattern. Therefore, the test data generation unit 180 refers to “M_CATEGORY.CATEGORY_CD” as a reference destination of the external reference, and generates test data of “CATEGORY_CD”. Specifically, the database data acquisition unit 170 acquires a plurality of values of “CATEGORY_CD” registered in the “M_CATEGORY” table from the database 300. Then, the test data generation unit 180 arbitrarily selects data from the acquired plurality of data and generates it as test data. Similarly, when the data generation method is “SQL setting” and the SQL statement is set in the data generation pattern, the test data generation unit 180 uses the reference destination data described in the SQL statement as test data. Generate. Specifically, the database data acquisition unit 170 executes the set SQL statement in the database 300 and acquires a plurality of data as the execution result. The test data generation unit 180 arbitrarily selects data from a plurality of data acquired as an execution result by the database data acquisition unit 170 and generates it as test data for the item.

  FIG. 6 is a diagram illustrating a first example of test data generated by the test data generation unit 180 according to the first embodiment. FIG. 6 shows test data generated based on information set in the window shown in FIG. For example, as shown in FIG. 6, the test data generation unit 180 displays “Organization chart code: Organization 1-1, Generation code: 20, Usage start date: April 1, 211, Usage end date: March 31, 2010, current classification: 1111, registration date: 200909031, registered employee code: employee ID 0111, update date: 20009211, updated employee code: employee ID 0222 "is generated and stored in the database 300. Similarly, the test data generation unit 180 generates test data of generation management data as shown in FIG.

  Returning to FIG. 1, when the related data generation unit 190 generates test data between data in which reference information indicating a reference relationship is set, if the data is not registered in the reference destination, the reference destination data Is generated as related data. Specifically, when external reference is set as the data generation method and data is not registered in the reference destination set in the data generation pattern, data corresponding to the data type is generated as related data 191. The generated data is registered in the database 300.

  For example, the related data generation unit 190 refers to “type” and “number of digits” in the same column when data is not registered in the reference destination “M_CATEGORY.CATEGORY_CD” shown in the data generation pattern of FIG. 5B. The “type” is “varchar”. Since the “digit number” is “6”, the related data generation unit 190 generates 6-character data. Then, the related data generation unit registers the generated data in “M_CATEGORY.CATEGORY_CD”.

  As described above, when generating test data for load testing, the test data generation device 100 according to the first embodiment acquires data item information from the database 300 and generates test data. Subsequently, a case where data item information is acquired from the terminal 200 and test data for input test is generated will be described.

  Returning to FIG. 1, the screen information acquisition unit 142 acquires, for each data item used by the test target business application, data item information indicating the attribute of the data. Specifically, the screen information acquisition unit 142 acquires from the terminal 200 the source code or framework definition in which the screen processing of the business application to be tested is implemented under the control of the test data structure creation control unit 130. FIG. 7 is a schematic diagram illustrating an example of a business application screen according to the first embodiment. For example, as shown in FIG. 7, the screen of the business application according to the first embodiment includes “product code”, “maker code”, “maker product code”, “product name”, “category code”, “product description”. "And" Unit price "input items are set in the product information editing screen. In the following, a case where data item information is acquired from source code in which screen processing is implemented will be described, and then a case where data item information is acquired from the framework definition will be described.

  When acquiring data item information from the source code in which screen processing is implemented, the screen information acquisition unit 142 acquires a list of source codes inheriting the screen common processing class of the framework, thereby obtaining FIG. Get a list of programs with screen processing as shown. Then, the screen information acquisition unit 142 acquires the data item for generating the test data from the input check implementation location of the acquired source code.

  FIG. 8 is a diagram illustrating an example of the source code of the screen processing according to the first embodiment. FIG. 8 shows source code in which the input check process for the screen shown in FIG. 7 is implemented. For example, the screen information acquisition unit 142 first acquires a target variable name from the list of input check processing methods of the framework. For example, the screen information acquisition unit 142 acquires a list of “Set Default Validation” methods from the source code illustrated in FIG. 8. Then, the screen information acquisition unit 142 acquires an item as a test data generation target from the acquired method argument. For example, the screen information acquisition unit 142 may be configured from “validator. Set Default Validation (Me. Search Shohin Cd,“ product code (search) ”, Input Validator. Check Type. Length Check, 0, 4)”, “Che”, “Che”. "As an item name and" "product code (search)" "as a Japanese name.

  When acquiring data item information from the framework definition, the screen information acquisition unit 142 acquires a screen list in which the input check is defined from the input check definition of the framework. FIG. 9 is a diagram illustrating an example of the external definition of the input check according to the first embodiment. For example, as illustrated in FIG. 9, the screen information acquisition unit 142 acquires the items of the Screen tag that are <Screen id =...> To </ Screen> as a screen list. Then, the screen information acquisition unit 142 acquires an input check definition tag from the screen input check definition. For example, the screen information acquisition unit 142 acquires a “Check” tag illustrated in FIG. 9 as an input check definition tag.

  And the screen information acquisition part 142 acquires the item used as the production | generation object of test data from the acquired Check tag. For example, the screen information acquisition unit 142 selects “ShoinCd” as the item name and ““ Product code ”” from “<Check DisplayName =“ Product code ”ControlId =“ ShohinCd ”Name =“ Product code ”>” shown in FIG. Get as a word name.

  Here, the screen information acquisition unit 142 refers to the check definition of the framework and sets a data type such as a type for each item of acquired data. FIG. 10 is a diagram illustrating an example of a framework check definition according to the first embodiment. As shown in FIG. 10, in the check definition of the framework, the contents of the input check, the outline of the check, and the conditions 1 and 2 of the input check are associated with each input check type (Check Type).

  For example, when the data type is set for “Japanese name: product code” shown in FIG. 8, the input check processing method related to “Japanese name: product code” is “validator.Set Default Validation (Me. ShohinCd, “Product Code”, InputValidator.CheckType.NullCheck,,) ”,“ validator.Set Default Validation (Me. ShohinCald, “Product Code”, InputValidator.CheckType. (Me. ShohinCd, “Product Code”, InputValidator. CheckTy e.Natural Number Check,,) ”,“ Type: Numeric ”,“ Number of Digits: 4 Digits ”,“ Japanese Name: Product Code ”,“ Data Generation Method: Numeric ”,“ Data Digits: A data type “4 digits” is set.

  Also, for example, when the data type is set for “Japanese name: slip number” shown in FIG. 9, the Check tag related to “Japanese name: slip number” is <Check CheckType = “Natural Number Check”> <Check Arg1 = “10000” Arg2 = “99999” CheckType = “Range Check” />, <Check Arg1 = “0” Arg2 = “5”, CheckType = “Length Check” /> “Number Check” and “Range Check” are defined as 10,000 to 99999, and “Length Check” are defined as 0 to 5 characters. Therefore, “Type: Numeric”, “Number of Digits: Five Digits”, “Japanese Name: Slip” number" , “Data generation pattern: 10000 to 99999 is set as an abnormal value, normal value, and threshold” is set.

  Also in the acquisition of data item information by the screen information acquisition unit 142 described above, the test data structure creation control unit 130 displays and outputs a window. FIG. 11 is a diagram illustrating a second example of a GUI displayed and output by the display device according to the first embodiment. For example, as shown in FIG. 11, when the screen name is acquired from the source code by the screen information acquisition unit 142 and “product information edit master” is selected as the test data generation target, the input included in the product information edit master The items are expanded, and “type”, “digit number”, “Japanese name”, “data generation method”, “data digit number”, and “data generation pattern” are set for each item. Here, an SQL statement is set as an external reference in the data generation pattern shown in the area (5) of FIG.

  The test data generation unit 180 generates test data based on the information set in the window described above. FIG. 12A is a diagram illustrating a second example of test data generated by the test data generation unit according to the first embodiment. FIG. 12A shows test data generated based on information set in the window shown in FIG.

  For example, as shown in FIG. 12A, the test data generation unit 180 uses “product code: S0002, manufacturer code: F001, manufacturer product code: 28745684, product name: as test data to be input to the business application of the terminal 200. Test data with “Epis X, category code: 01, product description: stationery, unit price: 200” is generated and output as input test data 183. Similarly, as shown in FIG. 12A, the test data generation unit 180 outputs display test data 182 as test data of product data as test data registered in the database 300 for display by the business application of the terminal 200. . Further, the related data generation unit 190 generates reference destination test data. FIG. 12B is a diagram illustrating a third example of the test data generated by the test data generation unit according to the first embodiment. For example, when the data generation method is set to “external reference” and the data generation pattern is set to “CATEGORY.CATEGORY_CD”, the related data generation unit 190 displays “category code: 01, category name” as shown in FIG. 12B. : The related data 191 for “stationery” is generated and stored in the database 300.

  As described above, the test data generation apparatus 100 according to the first embodiment generates test data for a business application using a database definition, a source code on which screen processing is implemented, and a framework definition. Then, the test data generation apparatus 100 according to the first embodiment stores the generated test data in the database 300 or the terminal 200. The test data generation apparatus 100 according to the first embodiment can also execute a search for the test data generated in this way. FIG. 13 is a diagram illustrating an example of a test data search screen displayed by the test data generation apparatus 100 according to the first embodiment.

  For example, the test data generation device 100 according to the first embodiment receives a plurality of search conditions such as “product code”, “maker code”, and “maker product code” as shown in FIG. It is also possible to display the search result of the logical product of.

  Next, a processing procedure of the test data generation apparatus 100 according to the first embodiment will be described with reference to FIGS. FIG. 14 is a flowchart for explaining the procedure of the data type acquisition process from the database by the test data generation apparatus 100 according to the first embodiment. FIG. 14 shows processing after the acquisition source of the data type corresponding to the test content is determined.

  As illustrated in FIG. 14, in the test data generation device 100 according to the first embodiment, the database information acquisition unit 141 acquires a table list from the database 300 (step S101). Then, the test data structure input receiving unit 150 receives selection of a target table for creating test data (step S102). Thereafter, the database information acquisition unit 141 acquires data items for creating test data from the selected table (step S103).

  Then, the test data structure input receiving unit 150 receives a change / input of a data item for creating test data (step S104). Thereafter, the database information acquisition unit 141 acquires data item information of the target table from the database 300 (step S105). Then, the test data structure input receiving unit 150 receives a change / input of data item information (step S106). Subsequently, the test data structure creation control unit 130 determines a data type for each data item (step S107). Then, the test data structure input receiving unit 150 receives the data type change for each data item (step S108), receives the data generation pattern input (step S109), and ends the process.

  FIG. 15 is a flowchart for explaining the procedure of the data item reference relation determination process performed by the test data generation apparatus 100 according to the first embodiment. FIG. 15 shows the processing after the data item is determined.

  As illustrated in FIG. 15, in the test data generation device 100 according to the first embodiment, the database information acquisition unit 141 acquires table related information from the database 300 (step S201). Then, the test data structure creation control unit 130 determines the relationship for each data item from the related information of the table acquired by the database information acquisition unit 141 (step S202). Thereafter, the test data structure input receiving unit 150 receives an input related to the data item (step S203), and ends the process.

  FIG. 16 is a flowchart for explaining a first procedure of the test data generation process performed by the test data generation apparatus 100 according to the first embodiment. FIG. 16 shows a test data generation process when information for each data item is acquired from the database 300. FIG. 16 shows a process after the data generation method and data generation pattern for each data item are set.

  As illustrated in FIG. 16, in the test data generation device 100 according to the first embodiment, the test data generation unit 180 acquires the data generation pattern of the data item (step S301), and the data type is set in the data generation pattern. It is determined whether or not (step S302). Here, when the data type is set in the data generation pattern (Yes at Step S302), the test data generation unit 180 creates test data according to the data type (Step S303), and the set number of cases. Is determined (step S304).

  Here, when the set number of cases has not been generated (No at Step S304), the test data generation unit 180 returns to Step S303 and creates test data according to the data type. On the other hand, when the set number of cases has been generated (Yes at Step S304), the test data generation unit 180 executes the determination at Step S310.

  If the data type is not set in the data generation pattern in step S302 (No in step S302), the test data generation unit 180 generates test data corresponding to the data generation pattern. When the data generation pattern is set to random generation (step S305), the test data generation unit 180 randomly generates test data according to the data type (step S306), and generates the set number of cases. Is determined (step S307).

  Here, when the set number of cases has not been generated (No at Step S307), the test data generation unit 180 returns to Step S306 and executes the process in the case of the random generation setting. On the other hand, when the set number of cases is generated (Yes at Step S307), the test data generation unit 180 executes the determination at Step S310. Similarly, in the case where the data generation pattern is the external reference setting (step S308) and the SQL setting (step S309), it is determined whether or not the number of items set by generating test data is generated for each setting. (Step S307). The procedure of the test data generation process when the data generation pattern is the external reference setting and the procedure of the test data generation process when the SQL setting is set will be described with reference to FIGS.

  When the set number of test data in each setting is generated (Yes at Step S304, Yes at Step S307), the test data generation unit 180 determines whether all data items have been processed (Step S310). If all the data items have not been processed (No at Step S310), the test data generation unit 180 returns to Step S301 and acquires the data generation pattern of the unprocessed data item. On the other hand, when all the data items have been processed (Yes at step S310), the test data generation unit 180 ends the process.

  FIG. 17 is a flowchart for explaining the creation of related data as the second procedure of the test data generation process performed by the test data generation apparatus 100 according to the first embodiment. FIG. 17 shows the processing between step S308 and step S307 in FIG.

  As illustrated in FIG. 17, in the test data generation device 100 according to the first embodiment, when the data generation pattern is the external reference setting (FIG. 16, step S308), the database information acquisition unit 141 performs the reference table It is determined whether or not there is registered data (step S311). Here, when there is registration data in the reference table (Yes in step S311), the database data acquisition unit 170 acquires a list of registration data from the reference table (step S312).

  Then, the test data generation unit 180 randomly selects one value from the acquired data (step S313), generates the selected data as test data (step S314), and ends the process. On the other hand, in the determination in step S312, if there is no registered data in the reference table (No in step S311), the related data generation unit 190 generates test data according to the data type (step S315) and generates It is determined whether or not the processed data is in the reference table (step S316).

  If the generated data is in the reference table (Yes at step S316), the related data generation unit ends the process. On the other hand, if the generated data is not in the reference destination table (No at step S316), the related data generation unit 190 creates key data as the related data 191 in the reference destination table (step S318), and ends the process. To do. When the process shown in FIG. 17 ends, the determination process in step S307 shown in FIG. 16 is executed.

  FIG. 18 is a flowchart for explaining a third procedure of the test data generation process performed by the test data generation apparatus 100 according to the first embodiment. Note that FIG. 18 shows processing between step S310 and step S308 in FIG.

  As shown in FIG. 18, in the test data generation apparatus 100 according to the first embodiment, when the data generation pattern is SQL setting (FIG. 16, step S309), the test data generation unit 180 sets the SQL check. It is determined from the setting of the data generation pattern whether or not it is done (step S318). If the SQL check is not set (No at Step S318), the test data generation unit 180 acquires a list of SQL execution results (Step S319).

  Then, the test data generation unit 180 randomly selects one value from the acquired data (step S320), generates the selected data as test data (step S321), and ends the process. On the other hand, when the SQL check is set (Yes at Step S318), the test data generation unit 180 generates test data according to the data type (Step S322) and is set to the data generation pattern. SQL is executed by the database data acquisition unit 170. Then, the database data acquisition unit 170 determines whether or not the generated data is included in the SQL execution result (step S323).

  If the generated data is not included in the SQL execution result (No at Step S323), the test data generation unit 180 determines that there is a data reference error and does not generate data (Step S324). ), The process is terminated. On the other hand, when the generated data is included in the execution result of SQL (Yes in step S323), the test data generation unit 180 ends the process. When the process shown in FIG. 18 ends, the determination process in step S307 shown in FIG. 16 is executed.

  FIG. 19 is a flowchart for explaining the procedure of the data type acquisition process from the source code for the screen processing implemented by the test data generation apparatus 100 according to the first embodiment. Note that FIG. 19 shows processing after the acquisition source of the data type corresponding to the test content is determined.

  As illustrated in FIG. 19, in the test data generation device 100 according to the first embodiment, the screen information acquisition unit 142 acquires a source list of screen processing implementation from the terminal 200 (step S401). Then, the test data structure input receiving unit 150 receives selection of a screen for creating test data (step S402). Thereafter, the screen information acquisition unit 142 acquires a data item for creating test data from the input check implementation location of the screen source (step S403).

  Then, the test data structure input receiving unit 150 receives a change / input of a data item for creating test data (step S404). Thereafter, the screen information acquisition unit 142 acquires check definition information of the target screen from the input check implementation, and sets it as a test data creation item (step S405). Then, the test data structure input receiving unit 150 receives a change / input of data item information (step S406). Subsequently, the test data structure creation control unit 130 receives an input of a data generation pattern (step S407) and ends the process.

  FIG. 20 is a flowchart for explaining the procedure of the information acquisition process for each data item from the framework input check definition by the test data generation apparatus 100 according to the first embodiment. Note that FIG. 20 shows processing after the acquisition destination of information for each data item corresponding to the test content is determined.

  As illustrated in FIG. 20, in the test data generation device 100 according to the first embodiment, the screen information acquisition unit 142 acquires a screen list in which the input check definition is defined from the terminal 200 (step S501). Then, the test data structure input receiving unit 150 receives selection of a screen for creating test data (step S502). Thereafter, the screen information acquisition unit 142 acquires a data item for creating test data from the input check definition on the screen (step S503).

  Then, the test data structure input receiving unit 150 receives a change / input of a data item for creating test data (step S504). Thereafter, the screen information acquisition unit 142 acquires check definition information of the target screen from the input check definition and sets it as a test data creation item (step S505). Then, the test data structure input receiving unit 150 receives a change / input of data item information (step S506). Subsequently, the test data structure creation control unit 130 receives an input of a data generation pattern (step S507) and ends the process.

  FIG. 21 is a flowchart for explaining a fourth procedure of the test data generation process performed by the test data generation apparatus according to the first embodiment. FIG. 21 shows a test data generation process when the data type for each data item is acquired from the source code for implementing the screen process or the input check definition of the framework. FIG. 21 shows processing after the data type, data generation method, and data generation pattern for each data item are set.

  As illustrated in FIG. 21, in the test data generation device 100 according to the first embodiment, the test data generation unit 180 acquires the data generation pattern of the data item (step S601), and the data type is set in the data generation pattern. It is determined whether or not (step S602). Here, when the data type is set in the data generation pattern (Yes in step S602), the test data generation unit 180 creates test data corresponding to the data type (step S603), and the set number of cases Is determined (step S604).

  If the set number has not been generated (No at Step S604), the test data generation unit 180 returns to Step S603 and creates test data corresponding to the data type. On the other hand, when the set number of cases is generated (Yes at Step S604), the test data generation unit 180 executes the determination at Step S609.

  In step S602, when the data type is not set in the data generation pattern (No in step S602), the test data generation unit 180 generates test data corresponding to the data generation pattern. If the data generation pattern is set to random generation (step S605), the test data generation unit 180 generates test data randomly according to the data type (step S606), and whether or not the set number has been generated. Is determined (step S607).

  If the set number has not been generated (No at Step S607), the test data generation unit 180 returns to Step S605 and executes the process for the case of random generation setting. On the other hand, when the set number of cases is generated (Yes at Step S607), the test data generation unit 180 executes the determination at Step S609. Similarly, when the data generation pattern is SQL setting (step S608), it is determined whether test data is created for each setting and the number of cases set is generated (step S607). The procedure of the test data generation process when the data generation pattern is SQL setting is the same as that in FIG.

  When the set number of test data in each setting is generated (Yes in Step S604, Yes in Step S607), the test data generation unit 180 determines whether or not all data items have been processed (Step S609). If all the data items have not been processed (No at Step S609), the test data generation unit 180 returns to Step S601 and acquires the data generation pattern of the unprocessed data item. On the other hand, when all the data items have been processed (Yes at step S609), the test data generation unit 180 ends the process.

  As described above, according to the first embodiment, the database information acquisition unit 141 or the screen information acquisition unit 142 sets the data item information indicating the attribute of the data for each item of data used by the business application to be tested. The test data structure creation control unit 130 acquires the data type and sets the data type. In addition, the database information acquisition unit 141 or the screen information acquisition unit 142 acquires reference information indicating a reference relationship between data regarding data used by the business application. Then, the test data generation unit 180 generates test data corresponding to at least one of the attribute of the data type set by the test data structure creation control unit 130 and the reference relationship of the reference information for each data item. Therefore, for example, the test data generation apparatus 100 according to the first embodiment creates test data that is not similar to existing test data, or there is no definition information or key information about data, or information about correspondence between tables. Test data can be created easily, and test data in which the consistency of the reference relationship between the data is maintained can be easily created.

  Further, according to the first embodiment, the database information acquisition unit 141 acquires information on data items of the data from the database 300 that stores information on data used by the business application to be tested. In addition, the database information acquisition unit 141 acquires reference information using a table definition stored in the database 300 or an SQL sentence set by a user. Then, when the reference information is not included in the tables in which the reference relationship is defined by the table definition, the test data generation unit 180 uses the database information acquisition unit as the reference information between the tables in which the reference relationship is defined. 141 generates data corresponding to the data type acquired in 141. Therefore, the test data generation apparatus 100 according to the first embodiment can generate test data in an amount desired by the user while maintaining consistency between data.

  Further, according to the first embodiment, the screen information acquisition unit 142 acquires data item information of data input to the screen from the source code of the screen in the business application to be tested. The screen information acquisition unit 142 acquires reference information using an SQL sentence set by the user. Therefore, the test data generation apparatus 100 according to the first embodiment can generate test data that reliably maintains consistency between data.

  According to the first embodiment, the test data structure input receiving unit 150 receives test contents. Then, when the test content received by the test data structure input receiving unit 150 is a load test, the database information acquisition unit 141 stores the data from the database 300 that stores information on data used by the business application to be tested. Get information about the data item. When the test content received by the test data structure input receiving unit 150 is an input test or a display test, the screen information acquiring unit 142 is data input to the screen from the source code of the screen in the business application to be tested Get information about the data item. In addition, when the test content received by the test data structure input reception unit 150 is a load test, the database information acquisition unit 141 refers to the table definition stored in the database 300 or the SQL sentence set by the user. Get information. Then, when the test content received by the test data structure input receiving unit 150 is an input test or a display test, the screen information acquisition unit 142 acquires reference information using an SQL sentence set by the user. Therefore, the test data generating apparatus 100 according to the first embodiment can automatically generate test data corresponding to the test contents.

  For example, in the prior art, a large amount of test data can be randomly generated according to data item information or the like, but there are many cases where consistency between data is not ensured. As a result, the business application is tested using test data that does not maintain consistency between the data. When a problem occurs during the test, it is determined whether the problem is a test data problem or a business application problem. It could be difficult to do. Furthermore, in the conventional technique, since consistency between data is not maintained, when registering the created test data from the screen, for example, it is necessary to select input from the screen by pull-down. In some cases, the input of the created test data cannot be selected from the pull-down menu.

  In the test data generation device 100 according to the present embodiment, it is possible to generate a large amount of test data in which consistency between data is maintained, and it is possible to easily generate test data according to the test characteristics. To do. As a result, the test data generation apparatus 100 according to the present embodiment can also accurately test a business application.

  Although the first embodiment has been described above, the present invention may be implemented in various different forms other than the first embodiment described above.

  In the first embodiment described above, test data generation that executes both acquisition of information for each data item from the database and acquisition of information for each data item from the source code or the framework input check definition that implements screen processing The apparatus 100 has been described. However, the disclosed technique is not limited to this. For example, one of the techniques may be executed.

  In addition, for example, a device that acquires information for each data item from a database is connected to a device that acquires information for each data item from a source code or framework input check definition that implements screen processing. Thus, the same process as that performed by the test data generation apparatus 100 according to the first embodiment may be executed.

  In the first embodiment described above, the case where the test data generation device 100 is independent from the terminal 200 and the database 300 has been described. However, the disclosed technique is not limited to this, and for example, the test data generation apparatus 100 may be built in the terminal 200.

[System configuration, etc.]
Each component of each illustrated device is functionally conceptual, and does not necessarily need to be the same as the physically illustrated component. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the database information acquisition unit 141 and the screen information acquisition unit 142 illustrated in FIG. 1 may be integrated as one information acquisition unit. On the other hand, the test data structure creation control unit 130 shown in FIG. 1 may be distributed to a setting unit that sets a data generation method and a data generation pattern and a display control unit that causes the display device 120 to display and output a GUI. Good.

  In addition, all or a part of the processes described as being manually performed among the processes described in the present embodiment can be manually performed. For example, input processing for the number of test data items to be generated may be automatically performed. In such a case, for example, the number of data to be generated may be automatically determined based on the number of data generated in the past. Further, the test data generation unit 180 may be connected as an external device of the test data generation apparatus 100 via a network.

[Data generation program]
In the first embodiment, the case where various processes are realized by hardware logic has been described. However, the present embodiment is not limited to this, and a program prepared in advance is executed by a computer. Also good. Therefore, in the following, an example of a computer that executes a data generation program having the same function as the test data generation apparatus 100 shown in the first embodiment will be described with reference to FIG. FIG. 22 is a diagram for explaining a computer that executes a data generation program according to the second embodiment.

  As shown in FIG. 22, the computer 1000 includes, for example, a memory 1010, a CPU (Central Processing Unit) 1020, and a hard disk drive interface 1030. As shown in FIG. 23, the computer 1000 includes, for example, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080. .

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM (Random Access Memory) 1012 as shown in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1090 as shown in FIG. The disk drive interface 1040 is connected to the disk drive 1100 as shown in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to, for example, a mouse 1110 and a keyboard 1120 as shown in FIG. The video adapter 1060 is connected to a display 1130, for example, as shown in FIG.

  Here, as shown in FIG. 22, the hard disk drive 1090 stores, for example, an OS (Operating System) 1091, an application program 1092, a program module 1093, and program data 1094. That is, the data generation program is stored in, for example, a hard disk as a program module 1093 in which a command executed by the computer 1000 is described. Specifically, a data information acquisition procedure for executing processing similar to that of the data information acquisition unit 140 described in the above-described embodiment and a data generation procedure for executing processing similar to that of the test data generation unit 180 are described. A program module 1093 is stored in the hard disk.

  Further, like the data stored in the internal memory of the test data structure creation control unit 130 described in the above-described embodiment, data used for information processing by the rule inspection program is stored as program data, for example, on a hard disk. . Then, the CPU 1020 reads program modules and program data stored in the hard disk to the RAM 1012 as necessary, and executes a data information acquisition procedure and a data generation procedure.

  Note that the program module and program data related to the data generation program are not limited to being stored in the hard disk, but may be stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module and program data relating to the analysis program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and the CPU 1020 via the network interface 1070. May be read.

DESCRIPTION OF SYMBOLS 100 Test data production | generation apparatus 110 Input device 120 Display apparatus 130 Test data structure creation control part 140 Data information acquisition part 141 Database information acquisition part 142 Screen information acquisition part 150 Test data structure input reception part 160 Test data creation control 170 Database data acquisition part 180 Test data generation unit 190 Related data generation unit 200 Terminal 300 Database

Claims (5)

For each item of data used by the business application to be tested, information on the data item indicating the attribute of the data and the reference relationship between the items of the table included in the database storing the data used by the business application A data information acquisition unit for acquiring a key and an external key, or an SQL sentence set by a user as to whether the test data of the business application is acquired from the database ;
Data generation for generating test data corresponding to at least one of the data item information acquired by the data information acquisition unit and the primary key and the foreign key or the SQL statement for each data item And
A data generation device comprising: For each item of data used by the test of the business application, and from said database for storing data used by the test of the business application data item of the data information, test data table definition or the business application the A data information acquisition unit for acquiring an SQL sentence set by a user as to which of the databases to acquire ;
For each data item, when data corresponding to a corresponding data item between tables in which a reference relationship is defined by the table definition or the SQL statement is not registered, reference between tables in which the reference relationship is defined As the information, a data generation unit that generates data according to the information of the data item acquired by the data information acquisition unit ,
A data generation device comprising: Te from the screen source code in strike target business application acquires information of a data item of data input to the screen, set by the user from a database that stores data used by the test of the business application SQL A data information acquisition unit for acquiring reference information corresponding to a sentence and indicating a reference relationship between data;
For each item of data, a data generation unit that generates test data according to at least one of the reference relationship of the data item information and reference information acquired by the data information acquisition unit;
A data generation device comprising: A reception unit that accepts test content ;
If the test contents received by front Symbol receiving unit was load test, the information of the data item of the data from a database that stores data used by the test subject of business applications, the table definition or user A database information acquisition unit that acquires reference information indicating a reference relationship between data corresponding to the set SQL sentence;
Screen information for acquiring data item information of data input to the screen from the source code of the screen in the business application to be tested when the test content received by the reception unit is an input test or a display test With the acquisition department
For each item of the data, a data generation unit that generates test data according to at least one of the data item information acquired by the database information acquisition unit or the screen information acquisition unit, the reference relationship of the reference information,
A data generation device comprising: From a database that stores data used by the test of the business application, and for each item of data used by the test of the business application,
Information on the data item indicating the attribute of the data and the primary key and foreign key indicating the reference relationship between the items of the table included in the database, or from which database the test data of the business application is acquired. A data information acquisition procedure for acquiring an SQL sentence set by the user ;
Data generation for generating test data corresponding to at least one of the data item information acquired by the data information acquisition procedure and the primary key and the foreign key, or the SQL statement for each data item Procedure and
A data generation program for causing a computer to execute.

Images