JP3105279B2 - Program unit test data generation method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for generating a test data pattern used for verifying the function of a program, that is, a so-called unit test case in a program development process, and more particularly, to a method for efficiently generating test data values of the test case in a design stage. The present invention also relates to a method for generating unit test data of a program to be generated effectively. Note that the unit test refers to performing verification without combining a divided program unit with another program.

[0002]

2. Description of the Related Art In a unit test of a program, a white box test in which a unit test case is generated by combining conditions directly understood from an internal structure of a source program of a test target program, and a unit test case in which only conditions understood from specifications are combined. Black box tests are generated and performed.

The white box test is a method for generating and testing a test case according to the internal structure of a source program to be tested. Here, the target of analysis as a structure is a program execution path mainly composed of branch conditions and the like, and the execution of a test by one test case is a program obtained from a combination of branch conditions extracted from a source program. Corresponds to tracing one execution path. A set of execution paths corresponding to a group of test cases indicates the thoroughness of the test,
It is an evaluation of coverage. The thoroughness and coverage shown here are:
This is a measure for evaluating the proportion of execution paths that can be verified by the group of test cases for all execution paths in the program. The advantage of the white box test is that since the execution path can be actually grasped from the internal structure of the source program, a test case that increases the degree of thoroughness can be selected. On the other hand, a disadvantage is that it is not possible to determine whether the program satisfies the determined specifications, since the test case is determined from the source program itself. That is, a mismatch between the specification and the source program cannot be detected.

[0004] The black box test is a method of determining a test case in accordance with the specifications of a program, and is a test form in which the correct realization of the functions of the program specified in the specifications can be confirmed. An advantage is that a unit test case can be generated from the design stage based on the external specifications of the program without depending on the source program, so that a defect in the specification of the source program can be found. The disadvantage is that it is not possible to arbitrarily select a test case that increases the degree of thoroughness, such as a white box test, because it is not possible to consider internal branching conditions and the like that cannot be seen from the specification when selecting a unit test case.

[0005] The simplest test case selection method in the black box test is a random generation method, in which a test case is randomly selected and a test is performed, and is not necessarily an effective selection method. In addition, there is a method that uses a test case generation tool, etc., to identify the features of the function of the test target program specified in the specifications, and creates and uses test cases according to given distributions and conditions. , But many bugs can be found and it is effective, but at present the specific guidelines have not been established.

[0006] The best test method of the black box test is to use as many combinations of input conditions defined in the specifications as possible, but when the range of the upper and lower limits of the data area of the input conditions is wide, the test is performed. The number of cases becomes enormous, and in reality, not all data values in the data area are combined, but only a part of the combination is used as a test case. At that time, how to select a subset of test cases and how to efficiently and easily narrow the range to be tested can be a challenge of test case generation by a black box.

Conventionally, as a test case selection method for solving such a problem of the black box test, an equivalence division method, a limited value analysis method, a cause-result graph, and the like are known.

In the equivalence division method, a program input / output data area is divided into several areas called equivalence classes, and a representative value is extracted from each equivalence class and used as test data. In other words, the division of the input data area into equivalence classes is a method in which data judged to be processed by the same procedure in the program as determined from the specification is incorporated into the same equivalence class.

The limit value analysis method is an extension of the equivalence division method. In this method, when it is considered that the internal processing of the program changes depending on a certain value of the input data, an attempt is made also to the surrounding values. That is,
The boundary value in the equivalence division and its surrounding values are adopted as test cases. Furthermore, focusing not only on the input but also on the area of the output data, the input data necessary for realizing the vicinity of the boundary of the output data specified in the specification is selected and added to the test case.

The cause-result graph graphically and logically shows the input condition and the operation of the program corresponding to the input condition.
By combining input conditions that cause a certain result, it is easy to select an effective test case. However, application to large-scale software is difficult because graph display is complicated.

Regarding the application of the above-described test case generation method by the white box test and the black box test, in the unit test for testing the procedure, which is the lowest component of the program, the black box is checked in order to confirm that there is no missing specification. At the same time as testing, white box tests are often used together based on the internal structure of the program, and the ratio of white boxes tends to be high. References in this type of field include, for example, Tamai et al., "Software Testing Techniques" (Kyoritsu Shuppan, 1988).

[0012]

As described above, in the conventional unit test of a program, a test is generally performed using both a white box test focusing on a source program and a black box test focusing on a function based on specifications. . However, a unit test case is generated from a source program that has not been checked whether it satisfies the functions specified in the specification like the white box test, that is, the execution path according to the specification is not reflected or guaranteed. This may leak the required execution path of the test indicated in the specification or generate a test case containing an unnecessary execution path, so that a mismatch between the specification and the source program cannot be detected. Is considered unreasonable.

As a solution, it is necessary to apply only the black box test to the unit test, or to increase the ratio of the black box test compared to the white box test. However, when a unit test is performed by a black box test, it is best to generate a test case in consideration of all combinations of parameters, but the number of test cases is enormous. In particular, regarding parameters for which a wide range is specified, if all parameter values are used as test cases, it cannot be said that the number of test cases is realistic. In the random generation method, which is one of the methods for efficiently generating test cases for a black box test, since the test case selection is random, some of the functions for verifying the generated test cases are performed. Tend to be biased toward Equipartition,
The method using the limit value analysis method is effective in that a test case can be created at the design specification creation stage, but since no guidelines for dividing the data area of parameters are given, the equivalence division method and the limit value analysis method It is not easy to extract the division points according to, and the test case generation efficiency is not high.

An object of the present invention is to solve the above-mentioned conventional problems, reduce the number of test data under input conditions, and efficiently generate a test case in a unit test.

[0015]

In order to achieve the above object, the present invention provides a method for generating unit test cases based on a data type of input / output interface parameters of a program based on a method using a black box test format independent of a source program. Two types (set-oriented data
(A type type, a range-oriented data type type) are provided, and when a data definition statement of an input interface is input, according to the classification by the table,
From data definition statements belonging to one group (set-oriented data type type) , a combination of all data values in the parameter data value area is generated as a test case, and the other group is generated.
From the data definition statements belonging to (range-oriented data type type) , the data value area of the parameter is further divided into the data value areas divided by the dividing points indicated by the data definition statement of the input interface. It is generated.

[0016]

According to the present invention, the data type definition type of the input / output interface parameter of the program to be tested from the design stage is defined as a "range-oriented data type type" which is a numerical data type definition indicating the range of the data area. They are classified into two types: "set-oriented data type type", which is a set-type data type definition that has meaning. For input / output interface parameters, which are data types defined as "range-oriented data type type", the execution path branch of the program is not always separated for each parameter value of the parameter. Since there is a tendency to pass through the route, it is not meaningful to use all data values in the data value area as test cases, apply the equivalent data division method, limit value analysis test data selection method,
By clarifying the branch boundary value of the execution path branch in the program as design data and setting it in the data definition statement of the input interface, the division point of the parameter value becomes clear,
A part of values between boundary values of the data value area or values around the boundary value are generated as a test case of the unit test. For the input / output interface parameters that are data types defined as "set-oriented data type type",
Since the indicated value itself tends to be the branch boundary value of the execution path branch in the program, all the values are generated as test cases of the unit test.

As described above, in the test case generation at the unit test level, by adopting a test case generation method in a black box test format for generating a test case from a design stage, a white case for generating a test case from an untested source program is adopted. Compared to the box test format, the bug detection rate between the specification and the source program also increases in the unit test case,
The reliability for test cases is improved. For the test case generation of the black box test, by specifying the test case generation method of the unit test from the data type definition type of the input / output interface parameter, it is efficient to find many bugs with few test cases. Test cases can be easily generated.

[0018]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to embodiments.
In the embodiment, a procedure which is the lowest component of the unit test target program will be described as an example. However, the present invention can be implemented also in a module unit which is a collection of procedures.

FIG. 1 is a system configuration diagram of an embodiment of the present invention. In FIG. 1, reference numeral 1 denotes a CPU as a processing device;
Reference numeral 2 denotes a memory as a data unit, 3 denotes an input / output unit, 4 denotes a display unit, and 5 denotes a floppy disk (FD). The processing device 1 transfers the design data of the program corresponding to the corresponding procedure input from the input / output unit 3 to the memory 2 and retrieves the design data from the memory 2 to obtain the characteristic of the data, that is, the characteristic of the data. A unit test case extraction method is determined according to the definition type, a test case is generated, transferred to the memory 2, output to the input / output unit 3, and displayed on the display unit 4. Each operation status is always displayed on the display unit 4.

The program design data is created by an external device or the like different from the present device, and is stored on the FD 5.
Of the data on the FD 5 designed by the external device, only the procedure interface definition data table setting necessary data list and the branch data table data setting necessary data list are read out and transferred to the memory unit 2 of the present device. As shown in FIG. 18, the procedure interface definition data table setting required data list includes the procedure names, the interface names for the procedures, the parameter names for the interface names, the IN / OUT types of the parameters, and the data type definitions. And As shown in FIG. 19, the list of data required for setting the branch data table includes upper and lower limit values (upper limit value) corresponding to each procedure name, each interface name corresponding to the procedure, each parameter name corresponding to the interface, and the parameter. This indicates that one of a defined data group and a defined member data group is required. Which one is selected is determined by which data corresponding to the parameter indicates which of the contents of the program design data. The meaning of the range definition and the member definition in the branch data table setting necessary data list in FIG. 19 is as follows. Range definition: In the case of a division number data table group, the data area of the parameter is divided and the division number is set.
In addition, an upper limit, a lower limit, and an increase condition from the lower limit to the upper limit of each data division area are set. Member definition: In the case of a member table group, the data area of the parameter is divided and the number of divisions is set. Also, all members of each data division area are set.
However, the smallest member among the members of the data division area is set first, and the largest member is set last.

FIG. 2 is a functional block diagram according to the present embodiment. That is, the processing device 1 is functionally equivalent to the execution management unit 11, the data editing unit 12, the data reading unit 13,
It comprises a test case generation / editing unit 14 and a data management unit 15. The table group in the memory 2 includes a procedure interface definition data table 21, a range data table 22 and a set data table 23, both of which are nested tables of the data type classification definition tables, and a nest of branch data tables. The table includes a divided data table 24, a member table group 25, and a test case data table 26.

The execution management unit 11 manages an environment for creating a test case. More specifically, the input / output unit 3 interprets and executes an input command for executing and starting the apparatus, controls the transfer of data input / output to / from the memory 2, controls the display unit 4, and the like. is there. The data editing unit 12 stores the program design data on the FD 5 transferred from the execution management unit 11, the interface definition data table 21 on the memory 2, and the data type specification tables 22 and 2.
3. Since each of the branch data tables 24 and 25 and the test case data table 26 has a different format configuration, the program design data is analyzed and edited, and set in the corresponding table on the memory 2 through the data management unit 15. The data reading unit 13 reads the data set shown in the table of the procedure interface definition data table in FIG. 18 and the data set required in the branch data table in FIG.
The data of the data type classification definition tables 22 and 23 are read out through the data management unit 15 and transferred to the execution management unit 11. In the test case generation / editing unit 14, the execution management unit 1
A test case that receives the various data set in the memory 2 from 1 is created, set in the test case data table 26 in the memory 2 through the data management unit 15, and read out. The data management unit 15 manages reading and writing of the memory 2, which is a data unit.

FIGS. 3 to 8 are flowcharts of the basic processing in this embodiment. According to the flowchart, FIG.
Will be described in detail.

The unit test case generation starts with reading out the program design data on the FD 5. Here, the design data indicated by the program is design data created by another external device, and is shown in the procedure interface definition data table setting necessary data list of FIG. 18 and the branch data table setting necessary data list of FIG. 19 relating to the design. The program design data is various kinds of design data including data, and is stored on the FD 5. FIG.
FIG. 3 shows a procedure interface diagram of the design data on the FD 5 which is a target when a unit test case is generated. That is, the interface of the procedure includes an input interface B1, an output interface B2, another procedure call input interface B3, another procedure call output interface B4, a module data input interface B5, a module data output interface B6, and a procedure (in a unit) data input interface. B7 and a procedure (inside unit) data output interface B8.
Here, in the interface of the procedure to be subjected to the unit test, each data (called procedure interface definition data) shown in the procedure interface definition data table setting list of FIG.
To the procedure interface definition data table 21
Shows the process of setting to.

When the execution management unit 11 reads the FD 5 through the input / output unit 3 in response to a command input from the input / output unit 3, the program design data on the FD 5 is transferred to the interface S1, the input / output unit 3, the interface S2, The data is transferred to the management unit 11. The procedure interface data taken into the execution management unit 11 is as follows:
Since the data is created in the format of the program design data and needs to be edited into the format of the procedure interface definition data table on the memory 2, the data is edited and edited by the data editing unit 12 through the interface face S4. Then, the format-edited procedure interface definition data is
Via the interface S6, the data management unit 15, and the interface S10, it is set in the procedure interface definition data table 21 on the memory 2. In FIG.
Data editing from Y1 program design data to procedure interface definition data table (memory),
The setting corresponds to this processing.

FIG. 10 shows a configuration example of the procedure interface definition data table 21. Here, the procedure interface definition data table 21 has a 4-word interface head table 212 indicating each child table for each procedure of the procedure table 211. Interface head table 212
Indicates headers of the input / output interface table 223, the call procedure interface table 224, the call module data interface table 225, and the call procedure interface table 226. The configuration of the input / output interface table 223 indicates the interface name, each parameter name and the corresponding input / output type of IN information or OUT information, and the data type definition type. When the number of parameters does not satisfy the final area, the last Stopper value is set. The configuration of the call procedure interface table 224 indicates each call procedure interface name, each parameter name corresponding thereto, the input / output type of IN information or OUT information corresponding to the parameter name, and the data type definition type. If the final area is not satisfied, a stopper value is set for the last. The configuration of the call module data interface table 225 indicates an input / output type of IN information or OUT information and a data type definition type corresponding to each call module data name or member,
When the number of parameters does not satisfy the final area, a stopper value is set for the last. The same applies to the call procedure data interface table 226. The left column of the interface head table 212 is a valid / invalid indicator of each interface and parameter.
Is invalid and 1 is valid. In addition, each child table 223-
226 is an identifier in the leftmost column, 0 is empty, 1 is an interface, 2 is a parameter, and 3 is a stopper. Data is set in these tables at Y1.

When the editing and setting of each procedure interface parameter are completed, the data is edited in the branch data tables 24 and 25 from the program design data in Y2,
Make settings. That is, each data of the branch data table setting necessary data list in the program design data on the FD 5 is stored in the interface S1, the input / output unit 3, the interface S2, the execution management unit 11, the interface S4, the data editing unit 12, the interface S6, the data management Part 15,
Through the interface S11, it is set in the division point data table group 24 or the member table group 25 which is a nest table of the components of the branch data table.

FIG. 11 shows a configuration example of the branch data table. As described earlier in the branch data table setting necessary data list in FIG. 19, the branch data table is stored in the branch data procedure table 201 in units of procedure names.
It has a 4-word branch data interface head table 202 indicating each child table. The branch data interface head table 202 has a header configuration of an input / output interface table, a call procedure interface table, a call module data interface table, and a call procedure data interface table. The branch data parameter table 203 indicated by the branch data interface head table 202 is distributed for each interface name, whether it is the data of the division point data table group 24 or the data of the member table group 25. The distribution display is determined by the type of the next child table in the branch data parameter table 203. However, the setting of the next child table type is determined based on the data information of the program design data. When the next child table type indicates the division point data table group 24, it means that the design data of the program is set in the form of a lower limit value and an upper limit value. The number of divisions, which is the number of divided data areas, is set, and a value is set in the division point data upper / lower limit value table 242. Further, an increase condition is set in the division condition data increase condition table 243 so that data indicating the increase condition from the lower limit to the upper limit can be added mathematically. In addition, the corresponding parameter,
Alternatively, when the increment condition indicated by the corresponding data area of the parameter is not set in the program design data, the corresponding parameter, the division point data upper / lower limit value table 242 of the corresponding data area of the parameter, and the increase condition table 243 are not linked. Therefore, a valid / invalid indicator is provided in the increase condition header of the division point data upper / lower limit value table 242, and 0 is invalid and 1 is valid. On the other hand, when the next child table type in the branch data parameter table 203 indicates the member table group 25, the corresponding parameter data of the program setting data is indicated by the member, and the parameter of the parameter is stored in the member data parameter table 251. The number of divisions, which is the number of divided data areas, is set, and in the member data value display table 252, the number of members for each divided data unit and all member values are set.

When the setting of the branch data tables 24 and 25 is completed, the data type specification tables 22 and 2 are set at Y3.
The process proceeds to the reading process of No. 3. Here, the data type classification definition tables 22 and 23 on the memory 2 are positioned as semi-fixed data tables. That is, once set, it is a specified table that is not permanently changed. However, at the time of initial setting or in the case of newly adding a data type of a parameter, the setting can be made by canceling the guard rule.
The data type definition type is set according to the designation and setting of the operator from the input / output unit 3, and the interface S2, the execution management unit 11, the interface S4, the data editing unit 12, the interface S6, the data management unit 15, and the interface S
11, the specified data type definition type is individually set in the range data table 22 and the set data table 23 which are nest tables of the components of the data type type definition table on the memory 2.

FIG. 12 shows a classification standard and an example of a data type definition type defined as "range-oriented data type type" and "set-oriented data type type", which are features of the present invention, in a CCITT-recommended communication software description language. This will be described together with the features of performing a black box test using the CHILL language as an example. As shown in FIG. 12, the classification criterion is that a numerical data type definition indicating a range is a range-oriented data type type, and a set-like data type definition having a meaning in the value itself is a set-oriented data type type. In the data type definition tables 22 and 23 in the memory 2, the classification of the data type definition is set in advance according to the above classification.

FIG. 13 shows the structure of the data type classification rule table corresponding to the classification example shown in FIG. In FIG.
Data types that are range-oriented data type types are BIN and BIT
These are set in the range data table 22. The data type that is the set-oriented data type classification is C
HAR, PTR, and REF, which are set in the set data table 23. Flags indicated by 0 and 1 in the tables 22 and 23 are valid / invalid indicators of the member, where 0 is invalid and 1 is valid. The data type head table 200 holds the header values of the tables 22 and 23. As mentioned earlier, both tables are semi-fixed permanent tables.

At this point, the procedure interface definition data table 21 in the memory 2, the division point data table group 24 which is a nest table group of the branch data table components, the member table group 25, and the data type type definition table This means that the range data table 22 and the set data table 23, which are nest tables of components, have been set. These data tables are 1
It can be set in units of procedures, in units of multiple procedures, or in units of all procedures in the system. The amount of data to be set depends on the capacity of the memory 2.

Next, all parameters of all interfaces of the corresponding procedure are read from the memory 2 at Y4. Here, the procedure interface definition data table 21 is read, and the interface S13, the data management unit 15, the interface S7, the data reading unit 13,
The data is saved in a buffer in the execution management unit 11 through the interface S5. Next, at Y5, the range data table 22 and the set data table 23, which are nest tables of the components of the data type classification definition table, are read and saved in the buffer in the execution management unit 11 in the same manner. Then, in Y5, the data type type of one parameter of one interface is stored in the data type type definition tables 22 and 2.
The determination branch is performed according to the classification shown in FIG. That is, the data type of the corresponding parameter of the corresponding procedure interface is determined and branched in accordance with the classification shown in the data type specification tables 22 and 23. This processing is performed by the execution management unit 1
1, the corresponding procedure interface parameter is set to the “range-oriented data type type” parameter and “data type in the data type and data type specification tables 22 and 23 in the procedure interface definition data table 21. Set-oriented data type classification ". The result of the classification of both corresponds to Y6 and Y7.

As for the parameter of the range-oriented data type type (range data) of Y6, the data shown in the branch data table setting necessary data list of FIG. Get in. That is, the interface S15, the data management unit 15, the interface S7, the data reading unit 13, and the division point data table group 24 or the member table group 25, which are nest table groups of the components of the branch data table.
It is obtained by transferring to the buffer of the execution management unit 11 through the interface S5. Then, in Y9, it is determined whether the branch data of the corresponding parameter belongs to the division point data table group 24 or the member table group 25 of the branch data table. This determination is based on the branch data parameter table 203 having the branch data table configuration shown in FIG.
This is done by the value of the next child table type for the relevant parameter. That is, if the value of the next child table is 1, it is a division point data table group, and if it is 2, it is a member table group.

If the branch data of the corresponding parameter is a division point data table, it corresponds to Y10, and the process proceeds to acquisition of the division number data of Y12. This means reading the number of divisions of the division point data parameter table 241 of the division point data table group 24 having the branch data table configuration in FIG. 11, and the number of divisions means the number of data areas into which the parameters are divided. Is shown. Next, the process proceeds to the acquisition of the lower limit value and the upper limit value of Y13. This means the lower limit value and the upper limit value of the data area, and indicates the lower limit value and the upper limit value of the division point data upper / lower limit value table 242 of the division point data table group 24 in FIG. Next, a branching process is performed based on the determination of the presence / absence of the increase condition data of Y14. This is performed by the value of the presence / absence indicator of the increase condition data set in the increase condition header of the division point data upper / lower limit value table 242 in FIG. That is, when the value of the indicator is 0, there is no, and when it is 1, there is. Here, the increase condition is a mathematical expression using an arithmetic progression, a geometric progression, a difference progression, and the like. From the lower limit to the upper limit of one divided data area of the parameters described above, Is represented by a mathematical expression. Irregular ones have no increase conditions. Those that cannot be represented by numerical values are registered in the program design data as member values. The processing for the member value will be described later.

If there is increase condition data, an increase condition expression of Y16 is obtained. This corresponds to the division point data increase condition display table 24 of the branch data table group 24 shown in FIG.
3 is to extract the increase condition data in each parameter data area unit. Next, in Y17, all the values within the range of the lower limit value and the upper limit value are calculated by the increase condition expression, and the value obtained by the lower limit value− (the minimum increase condition value) and the upper limit value + (the minimum value) are obtained. (Increase condition value) is calculated. Next, test data extraction processing of Y18 is performed based on the calculated values. The extraction method is the lower limit already obtained,
One value selected from the upper limit and the value calculated in Y17, a value obtained by subtracting the minimum increase condition (1 increase condition) from the calculated lower limit, and a minimum increase condition (1 increase condition) from the upper limit ) Are used as test data. However, when the range of the lower limit value and the upper limit value data area is narrow and the value calculated and selected by the lower limit value, the upper limit value, or the increase condition formula overlaps, one of them is deleted. In the next Y19, it is determined whether or not all the parameter division numbers have been completed. That is, it is determined whether the test data has been extracted from all of the data areas obtained by dividing the parameters. If the processing has not been completed, the process returns to Y13, and the processing is repeated from the acquisition of the lower limit value and the upper limit value for the data area obtained by dividing the remaining parameters.

When the number of divisions of the parameter of Y19 is completed, the test data of the data area unit obtained by dividing the parameter of Y24 is combined into the test data of the parameter. Next, in Y25, it is determined whether all the parameters of the corresponding procedure interface have been completed, and the process branches. Here, in the case of unfinished (Y26), the process is repeated from the process of branching the data type type of one parameter of one interface of Y5 according to the classification of the data type type definition tables 22 and 23. Y5 at this time corresponds to the processing of the corresponding one parameter. Note that all interfaces and all parameter data of the corresponding procedure have already been set in the buffer of the execution management unit 11 at Y4.

When the processing ends at Y25 (Y27)
In Y28, the generated test data of the parameter in the unit of the parameter of the corresponding procedure interface,
Combine them as interface test data. Then, in Y29, it is determined whether all the corresponding procedure interfaces of the procedure are completed, and the process branches. That is,
In Y29, in all interfaces of the procedure,
It is determined whether test data has been generated. If the processing has not been completed (Y30), the processing is repeated from the processing in Y5. Y5 at this time corresponds to the processing of the corresponding one procedure interface. When it ends in Y29 (Y31)
Is the test data of the procedure by combining the test data of the interface for each interface of the corresponding procedure. The test data at this time becomes a test case and a test data value in the unit test, and becomes output data as a final purpose (Y34).

On the other hand, in Y14, if there is no increase condition data (Y22),
In Y23, the lower limit value and the upper limit value obtained in Y13 are set as test data values of the data area corresponding to the parameter. And Y1
The process proceeds to a process of determining whether the number of divisions of the nine parameters has been completed.

Next, when the branch data of the corresponding parameter belongs to the member table group in Y9 (Y11)
Acquires the division number data of the member data parameter table 251 of the member table group 25 having the branch data table configuration shown in FIG. This number of divisions also indicates the number of data areas into which the parameters are divided. Next, the process of Y36 is performed. In this process, FIG.
The number of all members of the corresponding data area of the parameter is obtained from the member data display value table 252 of No. 1. Next Y
At 37, all members for the number of members acquired at Y36 are acquired. In Y38, one of the member values obtained first and last among the obtained member values, and one of the member values other than both the member values are selected, and a total of three member values are set as test data. I do. If the number of member values is small and the member values overlap, one of the values is used as test data. Also, the member value management of the divided data area of the parameters of the procedure design data is such that if the numerical values or the magnitudes can be compared, the first set member value is the lower limit or the minimum, and the last set member value is The maximum value or maximum value is set in order. Next, in Y39, it is determined whether or not the processing has been completed for all the number of divisions of the parameter, and the process branches. That is, it is determined whether or not the test data has been extracted from all the data regions into which the parameters are divided, and the process branches. If not completed (Y40), Y36
Returning to step (Y41), the process is performed from step Y24.

Next, in Y5, the processing of the parameter (Y7; set data) whose value itself has a meaning according to the classification of the data type classification table in the data type classification of the one parameter of one interface is performed in Y42. The processing from Y42 to Y57 is performed from Y8 to Y2, which is processing for parameters (range data) for which the designation of a range is significant in Y5.
The processing is almost the same as the processing up to 1, but is different only in one place. The different processing is a test data selection method of the processing of Y18 in the case of the parameter for which the designation of the range is significant, and the processing of Y52 in the case of the parameter of the set-oriented data type. That is, when the range-oriented data type is classified in Y5, the processing in Y18 is performed by using the lower limit value, the upper limit value, and the value calculated by the increasing conditional expression using the value within the range of the lower limit value and the upper limit value of Y17. The test data is a value selected from one of the above, a value obtained by subtracting the minimum increase condition (1 increase condition) from a certain lower limit, and a value obtained by adding the minimum increase condition (1 increase condition) from the upper limit. However, in the processing of Y52, the lower limit value, the upper limit value,
All the values calculated by the increase condition formula with the values within the range of the lower limit value and the upper limit value of Y17 and the value obtained by adding the minimum increase condition (1 increase condition) from the lower limit value of Y17 are used as test data. . In other words, the difference between a parameter that is a range-oriented data type type and a parameter that is a set-oriented data type type is that a value selected from the parameter divided data area is used as test data or all values obtained from the parameter divided data area are used. Is test data.

The corresponding parameter is a parameter indicating a data type which is a set-oriented data type type.
When the branch data of the corresponding parameter No. 3 belongs to the member table group of the branch data table, the processing is performed from Y58. However, when the corresponding parameter is a parameter specifying the range and belongs to the member table of the branch data table of the branch data. Is different from the processing of Y61. That is, in the process of Y38, which is a parameter for specifying the range, of the member values of the divided data area of the parameter, the first and the last read member values and the member values other than both member values are obtained. Above all 1
We chose one, and used a total of three values as test data.
Y6 which is the case of the parameter of the set-oriented data type classification
In 1, the test data is all the member values of the divided data area of the parameter. In other words, in the present invention, when extracting test data from the parameter divided data area, some values selected from the parameter divided data area are used as test data, and the parameter of the set-oriented data type type is set to the parameter divided data area. All the obtained values are used as test data.

As described above, a test case is generated together with the test data of the procedure, based on the combination of each parameter and the test data of each interface. These processes are performed by the execution management unit 11 and the test case generation / editing unit 14 via the interface S8.
The generated test case and test data are set in the test case data table 26 on the memory 2 through the test case generation / editing unit 14, the interface S9, the data management unit 15, and the interface S16. The test cases and test data set in the test case data table 26 can be displayed on the display unit 4 and output to the FD 5 via the input / output unit 3.

Next, a specific example of generating a test case and test data of a program will be described. Here, test data values when a program as shown by the procedure specifications in FIG. 14 are created are shown.

In the procedure specification of FIG. 14, the input parameter is a, a is an integer value of 0 to 15, and the variable range of a is 0 to 7 performs A processing, 8 to 15 performs B processing, and Other than that indicates that the C processing is performed. According to the procedure specification, when the a parameter is a division point data table group of the nest table of the component of the branch data table, the data area is from 0 to 15,
The data division area is from 0 to 7 and from 8 to 15.
The divided data of the lower limit value and the upper limit value of each data division area is 0
The data division areas from to 7 have a lower limit of 0 and an upper limit of 7, while the data division areas of 8 to 15 have a lower limit of 8 and an upper limit of 15. Further, when an increase conditional expression is set, b = lower limit value, equal difference with lower limit value as initial value = 1
The arithmetic progression of When an is an arithmetic progression, b is an initial value, c is an arithmetic difference, and n is the number of arithmetic progressions, an equation of an = b + (n−1) c holds. Then, the value of each an is obtained under the increasing condition and becomes all the test data. The test data is from a1 to a
7, from a8 to a15. The minimum increase condition value (1 increase condition) described above corresponds to equal difference = c = 1 in this case.

FIG. 15 and FIG. 16 show the results (test data value, number of test data, display images) of generating test data based on the above conditions. Here, (1) to (4) in FIG. 15 show the case where the parameters are set in the division point data table group, and (1) to (4) in FIG.
(2) shows a case where parameters are set in the member table group. Note that, in (3) of FIG. 16, not the numerical parameter values as shown in (1) and (2) but general data values that may actually become set members are set in the member table group. FIG. 9 shows an image in which test data is generated using a day of the week as an example.

FIG. 17 shows an example in which the procedure specification data values of FIG. 14 are set as actual data in the branch data table of FIG. In FIG. 17, as the next child table type of “* 1”, 0 is not set, and 1 is a data table group (data parameter table header).
Setting 2 indicates a member table group (member data parameter table header) setting. “* 2” is an indicator of the presence / absence of the condition for increasing the division point data.
Further, the supplementary explanation of the increase condition data of “* 3” is as follows.
n is an arithmetic progression value, which is a test data value. Here, lower limit value ≦ an ≦ upper limit value, b = initial value = lower limit value, c = equal difference (here, 1), and n = number of arithmetic progression.

The embodiment of the present invention has been described above. The procedure interface definition data table 21 in which the data definition types of the parameters are set and the nest table of the components of the data type type definition table in which the data definition types are set are set. By processing data according to a certain range data table 22 and a set table 23 and classifying the test case generation method, a test case generation method for selecting test data of a parameter of a corresponding procedure, or all members of a parameter (test data )
It can be seen that the unit test case generation is performed efficiently by dividing into the test case generation method to which the combination of is applied.

[0049]

As described above, according to the present invention, many bugs can be found with a small number of test cases by specifying a test case generation algorithm according to the characteristics of the data type of the interface parameter of the unit test procedure. And debugging can be performed easily and quickly.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of an embodiment of the present invention.

FIG. 2 is a functional block diagram of one embodiment of the present invention.

FIG. 3 is a part of a basic flowchart of an embodiment of the present invention.

FIG. 4 is also a part of the basic flowchart.

FIG. 5 is also a part of the basic flowchart.

FIG. 6 is also a part of the basic flowchart.

FIG. 7 is also a part of the basic flowchart.

FIG. 8 is also a part of the basic flowchart.

FIG. 9 is an interface diagram in a unit test target procedure.

FIG. 10 is a configuration example of a procedure interface definition data table.

FIG. 11 is a configuration example of a branch data table.

FIG. 12 shows a classification standard and a classification example of a data type definition type.

FIG. 13 is a configuration example of a data type classification definition table.

FIG. 14 is a specification example of a procedure.

FIG. 15 shows a test data generation result for the procedure specification of FIG. 14;

FIG. 16 is a test data generation result for the procedure specification of FIG. 14;

FIG. 17 is an example in which data values of the procedure specifications of FIG. 14 are set in a branch data table.

FIG. 18 is a list of necessary data set in a procedure interface definition data table.

FIG. 19 is a list of necessary data set in the branch data table.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Processing unit 2 Memory 3 Input / output unit 4 Display display unit 5 Program design data floppy disk 21 Procedure interface definition data table 22, 23 Data type type definition table 24, 25 Branch data table 26 Test case data table

──────────────────────────────────────────────────続 き Continuation of front page (72) Inventor Shinichiro Takada 1-6-1, Uchisaiwaicho, Chiyoda-ku, Tokyo Nippon Telegraph and Telephone Corporation (56) References JP-A-63-148339 (JP, A) Nikkei Electronics No. . 286 (1982-3-15), Nikkei McGraw-Hill, P.S. 124-152 (58) Field surveyed (Int. Cl. ⁷ , DB name) G06F 11/28 340

Claims (1)

(57) [Claims] An input interface of a program to be verified inputs various data values, and an output data value output from the program to be verified corresponding to the input data value and a function specification of the program to be verified are determined in advance. By comparing the predicted output data values, in a program unit test for verifying the function of the program to be verified,
A method for automatically generating a data value of the input data input from the input interface, wherein a type of various data definition statements used for the input interface is defined as a set-type data type having a meaning in the value itself.
(Hereinafter referred to as “set-oriented data type type”) and the range of the data area
Numerical data type definition (hereinafter, range-oriented data type)
A data type classification prescription table be categorized into two groups of type), the data definition statements in the input interface of the program to be verified is input, with reference to the data type classification defined table, the data definition statement said It is determined which of the two groups belongs to, and from the data definition statements belonging to the group of the set-oriented data type type , all of one or more data values set in the data definition statement, or the lower limit value and the upper limit value All or one of the data values included in the specified data value area is extracted and used as the input data value of the program unit test, and the data definition statement belonging to the range-oriented data type group is From one or more data values set in the definition statement, extract only a part of data from the data value area specified by both or both lower and upper limits A program unit test data generating method, wherein the program unit test data is input data values.