JPH11120029A - Software test data generation support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To support the generation of test data for a test (single-body test) of one module and to support the generation of test data for a test (combined test) of a plurality of the modules. SOLUTION: When the data for the single-body test are generated, only fields which need to have values determined are shown to a user with operation sequence definitions 100 and data format definitions 101. The generated test data are registered as the single-body test data 106. When the combined test data are generated, a single-body test generation support part 102 further reduces only fields which need to have values determined with the single-body test data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for supporting test data creation in software testing,
The present invention relates to a test data creation support method in a case where a module constituting software is tested alone and a case where a test is performed by combining a plurality of modules.

[0002]

2. Description of the Related Art With respect to software consisting of a plurality of modules, when a certain module is tested, other modules are not completed, and there is no hardware for operating other modules. , An alternative module for testing (driver /
Stubs). In a test using a driver / stub, it is necessary to manually input test data at the time of test execution or to manually generate test data in advance.

[0003] For the creation of the driver / stub, see, for example, the 51st National Convention of the Information Processing Society of Japan, 5th volume pp.
As described in “Development of a unit test tool in an embedded microcomputer system” described in 5-17 to 5-18, there is a technique for automatically creating a driver / stub based on the calling relation of modules.

[0004]

However, in the above-mentioned prior art, no support by a computer is taken into consideration for the creation of test data, and the test data is input manually or at the time of test execution. It is necessary to create test data manually in advance.

Therefore, a first object of the present invention is to support the creation of test data in a test (unit test) for one module.

Further, a second object of the present invention is to support creation of test data in a test (combination test) for a plurality of modules.

[0007]

According to a first aspect, in order to achieve the first object, test data necessary for a test is indicated to a user by using format definition information of data used for notification between modules. In addition, the creation of test data is supported by indicating which of the fields constituting the test data require a specific value to be determined.

In a second aspect, when test data created for a unit test is managed and registered, and test data for a combination test is created, a data value is reused from the test data for a unit test to specify a value. By reducing the fields that need to be provided, the number of test data creation steps is reduced.

[0009]

Embodiments of the present invention will be described below with reference to the drawings. The present invention is not limited by the embodiments of the present invention.

FIG. 1 is a functional block diagram showing an embodiment of a software test data creation support method according to the present invention.

FIG. 2 is a hardware configuration diagram when the present invention is used by a single user. It comprises a processing device 201, an input device 202, a display device 203, a memory 204, and an external storage device 205.

Returning to FIG. 1, operation sequence definition 100
Is a set of one operation of the software that defines in time series the notification between the modules constituting the software and the data format at that time.

FIG. 3 shows an example of the operation sequence definition 100. In this example, one line indicates one notification, column 300 indicates the name of the operation sequence, and a blank indicates that the line is a continuation of the operation sequence from above. Column 301,
The column 302 shows the issuer module name and issuer module name of the notification, respectively. A column 303 is a name given to the notification. A column 304 is a data format name for transmitting the contents of the notification.

One operation sequence "initialization" represented by rows 310 to 317 can be represented as shown in FIG. Notifications 400 to 407 correspond to rows 310 to 317 in FIG. 3, respectively.

Returning to FIG. 1, the data format definition 101 defines, for the notification data used in the entire operation sequence, the constituent fields, the module that refers to the value of each field, and the field of another format that is the source of the value determination. Things.

FIG. 5 shows an example of the data format definition 101.
In this example, one row means one field, and column 501
Indicates a format name, and a blank indicates that the line is a continuation of the data format from above. Lines 510 to 513 have the format “A
B ", lines 514-516 form" BC ", line 517
519 define format “DC”, lines 520 and 521 define format “CB”, and line 522 defines format “EB”. Column 5
02 and a column 503 indicate the data type of the name and value of the field, respectively. A column 504 indicates a module that refers to the value of the field. For example, in the line 510, the value of the field “Req2D” of the format “AB” is not referred to by the module B, but is transmitted to the module D and referred to. In the row 511, the value of the field “Req2BC” in the same format is referred to by the module B and transmitted to the module C for reference. Columns 505 and 506 show the format name and field name of the transfer source when the value of the field is transferred from a field of another format.

Returning to FIG. 1, unit test creation support unit 10
2 designates an operation sequence to be tested as an operation sequence designation 105 from the operation sequence definition 100 and designates a test target module as a single module designation 104
After the user specifies the test data, the test data that needs to be created is presented to the user by using the data format definition 101, and the fields in which the values must be specified are presented. 1
Support 06.

FIG. 6 shows the contents of the unit test data creation support processing 103 for performing this processing. Step 600
Presents to the user a list of the operation sequences stored in the operation sequence definition 100, and prompts the user to specify one of them in step 601 (operation sequence designation 1).
05). In step 602, a list of modules related to the operation sequence specified in step 601 is presented to the user based on the columns 301 and 302 of the operation sequence definition 100, and in step 603, one of the modules is designated by the user ( Single module designation 104). Step 6
In 04, it is determined whether there is a notification in which the module designated in step 603 in the sequence is the column 302 and the processing after step 605 is not performed, and if not, the processing ends. If the notification exists, one of them is selected in step 605, and in step 606, the data format for the notification described in the column 304 is searched from the data format definition 101. At step 607, one of the fields for which the processing of step 608 and thereafter has not been performed is selected. In step 608,
In step 603, it is determined whether or not the module specified in the column 504 is included. If included,
In step 609, the user inputs the value (test data input 106).
In step 10, an undefined value (arbitrary value determined by this process) is set as the value of the field. In step 611, it is determined whether or not there is any field in the format that has not been subjected to the processing of step 608 and subsequent steps. If not, test data is created by combining the values of all the fields in step 612, registered in the unit test data 107, and then returns to step 604 to perform another notification process.

In FIG. 7, when the operation sequence illustrated in FIG. 3 is designated as the operation sequence designation 105 and the module B is designated as the unit module designation 104, the test data created by the unit test creation support unit 102 is Show. The test data created is 70
0,710,720. Of the fields, 702, 703, 711, and 721 shown by solid lines correspond to Step 6
09 indicates a field for which the user has specified a value. Also,
Steps 701, 704, and 712 indicated by dotted lines correspond to Step 61.
0 indicates an undefined field. In this figure, each field shows a field name, and an actual value is not described.

FIG. 8 shows test data created by the unit test creation support unit 102 when the module C is designated as the unit module designation 104 in the same operation sequence. Test data to be created is 800,810. The distinction between the fields by the solid line and the dotted line is the same as in FIG.

FIG. 9 shows unit test data 107 storing the test data shown in FIGS. Field 900
Tables denoted by 903 manage the created test data. Note that the actual values determined in step 609 or step 610 are described in each field of FIG. The value of the field represented by the dotted line is the value set as an undefined value in step 610. The value of the field represented by the solid line is the value set by Yuzu at step 609.

Returning to FIG. 1, the creation support unit 10 for the integration test
2 designates, from the operation sequence definition 100, an operation sequence to be tested as an operation sequence designation 105, and a plurality of modules to be tested 114
After the user specifies each, the test data that needs to be created is presented to the user by using the data format definition 101 and the unit test data 107, and the fields in which the values must be specified are presented. Supports the test data input 115.

FIG. 10 shows the contents of the integration test data creation support processing 113 for performing this processing. Step 60
0 to 606 are the same as those in FIG. Step 10
00 is a process for determining the value of each field for one notification, and details are shown in FIG. Step 1001
Creates test data by combining the values of all fields,
It is registered in the integration test data 116.

In FIG. 11, in step 1110, unit test data that has already been created is acquired from the unit test data 107 based on the operation sequence name. In step 1111, it is determined whether or not there is test data currently to be created from among them.
At 112, the data is copied and used as test data to be created. Regardless of the presence or absence in step 1111, in step 1113, it is determined whether there is a field whose value has not been determined. If not, the process ends. In some cases,
At step 1114, one of them is selected, and the value is determined as follows. The determination in step 1115 is as follows. In the data format definition 101, if the fields to be created are the fields 505 and 506 in the unit test data acquired in step 1110, the process proceeds to step 111.
6 adopts the value. The determination in step 1117 is as follows. In the data format definition 101, the fields indicated by the fields 505 and 506 of the field to be created are searched from the unit test data acquired in step 1110, and if they exist, the values are adopted in step 1118. I do. Steps 1119 to 1121 correspond to steps 1115 and 11
If the value cannot be determined in the determination of step 17, the user is prompted to input the value, as in steps 608 to 610 in FIG.
The value is undefined. By the above, step 1115
Determine the value of the field selected in step 1113
Return to

In FIG. 12, when the operation sequence illustrated in FIG. 3 is specified as the operation sequence specification 105 and the module B and the module C are specified as the plural module specification 114, the creation support unit 112 for the integration test is specified.
2 shows the test data created by. The fields having the same numbers as those in FIGS. 7 and 8 are the fields whose values are reused.

[0026]

According to the invention, the user has to consider only those fields for which values have to be determined. In addition, the test data created for the unit test is automatically managed and reused when the test data for the integration test is created, so that the number of fields for which values need to be determined further decreases.

As described above, the burden on the test data creator is reduced.

[Brief description of the drawings]

FIG. 1 is a functional configuration diagram according to an embodiment of the present invention.

FIG. 2 is a hardware configuration example for implementing the present invention.

FIG. 3 is an example of an operation sequence definition.

FIG. 4 is a schematic example of an operation sequence.

FIG. 5 is an example of a format data definition.

FIG. 6 shows the contents of unit test data creation support processing.

FIG. 7 shows an example of unit test data (part 1).

FIG. 8 shows an example of test data for module C unit test (part 2).

FIG. 9 is a configuration example of test data for a unit test.

FIG. 10 shows the processing content (part 1) of the integration test data creation support processing.

FIG. 11 shows processing contents (part 2) of the integration test data creation support processing.

FIG. 12 shows an example of test data for a combination test.

[Explanation of symbols]

100: operation sequence definition, 101: data format definition, 103: unit test data creation support processing,
107: unit test data, 116: combination test data, 113: combination test data creation support processing.

Claims (2)

[Claims] 1. A method for supporting test data creation of software comprising a plurality of modules, comprising: a step of allowing a user to specify an operation to be tested; a step of allowing the user to specify one test target module; A step of presenting a field for which a data value needs to be defined to the user based on the format definition information, and a step of allowing the user to specify the value of the field. 2. The software test data creation support according to claim 1, further comprising: a step of registering the created test data; a step of allowing a user to specify a plurality of test target modules; Presenting a field for which a data value needs to be defined to a user based on the definition information and the registered test data, to a user.