JPH0659937A - Device for supporting single body test of load module - Google Patents

Abstract

PURPOSE:To support the single body test of a large program to be divided into plural load modules in respect to a test for a computer program. CONSTITUTION:An input device 1-1 inputs information required by respective devices. A source program storage device 1-2 stores a source described in a temporary storage device. A data information analyzer 1-3 analyzes the described contents of the temporary storage device. A data information storage device 1-4 stores the analyzed contents of the analyzer 1-3. A program formation device 105 executes the self-coding of a driver program. A test data input device 1-6 inputs a test data value. A driver program storage device 1-7 stores a driver program. A test data storage device 1-8 stores a test data value inputted by the device 1-6.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer program test, and more particularly to a unit test support for a large-scale program in which a plurality of LMs are divided.

[0002]

2. Description of the Related Art In a large-scale program that divides an LM into a plurality of pieces, data is transferred by a temporary storage device. Conventionally, when performing a test for each LM, a driver program that has a definition description of a temporary storage device and writes the passed data to the temporary storage device is newly added so that the LM operates independently. I had to code.

Further, the data in the temporary storage device is often given as an initial value in the driver program, and when performing a data test of various patterns, it is time-consuming to carry out the LM alone. I was going after the completion.

[0004]

In the above-mentioned conventional technique, the developer of each LM has a problem that it takes time because a driver program is newly created. In addition, the quality of each LM is not sufficient unless each LM is sufficiently tested with data of various patterns.
The incidence of bugs is high in the test stage after connecting all LMs. Furthermore, since it is difficult to find out from which LM the bug has occurred, there is a problem that it takes a great deal of time to test and modify the program.

[0005]

A load module unit test support device of the present invention includes an input device for inputting an identifier of a temporary storage device used for data transfer between LM units, an input device for inputting an identifier of a program to be created, and a source. A data information analysis device for analyzing detailed information of the temporary storage device and data information by analyzing the data description part of the program, a data information storage device for storing the information analyzed by the data information analysis device, and a driver program A program creation device that creates a test data, a test data input device that repeatedly inputs test data and a judgment of input end, a driver program storage device that stores the created driver program, and a test data that is input It has a test data storage device.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing the functional arrangement of an embodiment of the present invention.

In the following, a source program written in the COBOL85 language will be described as an example.

The input device 1-1 includes an identifier of the source program storage device 1-2 to be analyzed, an identifier of a driver program to be created, an identifier of a temporary storage device referred to by the data information storage device 1-4, and a test. Enter the data value used in.

The source program storage device 1-2 is a device in which the source in which the definition for the temporary storage device is described in each source program for one LM is stored.

The data information analysis device 1-3 is an input device 1
Source program storage device 1-specified by
The contents indicated by the identifier 2 are read and detailed information of the temporary storage device (for example, file organization, blocking coefficient, record length) and information of each data (for example, data name, data length)
Is stored in the data information storage device 1-4.

The data information storage device 1-4 is a device for storing detailed information of the temporary storage device analyzed by the data information analysis device 1-3 and information of each data.

The program creating device 1-5 is an input device 1
-1 and the details of the temporary storage device stored in the data information storage device 1-4 and the information of each data are referred to, the driver program is automatically created, and the created driver program is used as the driver program. This is a device for storing in the storage device 1-7.

The test data input device 1-6 refers to the detailed information of the temporary storage device stored in the data information storage device 1-4, and the test data storage device 1-8 stores the same information as the temporary storage device. The area is secured, the test data value is input by the input device 1-1, and the test data storage device 1
It is a device that repeats the process of storing in -8 and confirms at the end of input whether test data has been defined for all temporary storage devices in the LM.

The driver program storage device 1-7 is
A storage device for storing the driver program created by the program creating device 1-5.

The test data storage device 1-8 is a storage device for storing the value of the test data input by the test data input device 1-6.

Below, a series of operations until the driver part program is automatically generated and the test data is created will be described with reference to FIGS.

First, in accordance with the procedure of FIG. 2, information (for example, file organization, blocking coefficient, etc.) of a required temporary storage device (for example, a temporary file on a magnetic disk) is stored.
Record length, data name, data length). The input device 1-1 (for example, CRT or keyboard) specifies the identifiers of all temporary storage devices used for data transfer between LMs, and the source program storage device 1-2 that defines these ( 2-1 processing).

In the data information analysis device 1-3, a description part (for example, INPUT-OUTPUT) about the temporary storage device is provided.
SECTION or FILE SECTION) is searched from the source program storage device 1-2 (process 2-2), and detailed information on the temporary file (for example, file organization,
Analyze the blocking factor, record length) and the information of the data used there (eg data name, data length) (2
-3 processing). Then, information of these analysis results is stored in the data information storage device 1-4 (for example, memory) (2
-4 processing).

Next, the driver program is automatically generated according to the procedure shown in FIG.

The input unit 1-1 specifies the main CU identifier in the LM and the identifier of the driver program to be created (process 3-1).

In the program creating device 1-5, the detailed information of the temporary storage device and the data information are displayed in the data information storage device 1-
4 (processing of 3-2), the temporary storage device, and the coding of the part that defines the test data area (for example, permanent file) on the test data storage device 1-8 (for example, magnetic disk) that takes the same area as that. Automatically generated (process 3-3). Then, a process of calling the main CU from the information of the designated CU identifier, a process of copying the designated test data area identifier (for example, a file name, hereinafter simply referred to as a test data identifier) to a temporary storage device, and , Generate the coding of the input processing of the test data identifier designated by the input device 1-1 to complete the driver program (processing of 3-4),
The driver program storage device 1-7 (for example, a magnetic disk) is stored with the designated program identifier (3
-5 processing).

Next, test data is input according to the procedure shown in FIG.

The input device 1-1 inputs the temporary storage device identifier for which data is to be defined and the test data identifier to be created (process 4-1).

In the test data input device 1-6, the detailed information of the temporary storage device is referred to from the data information storage device 1-4, and the same area is assigned the test data identifier designated on the test data storage device 1-8. It is attached and secured (the process of 4-2, for example, an operation of allocating a permanent file on the magnetic disk).

Next, the information of each data is sequentially referred from the data information storage device 1-4 (processing of 4-3) and displayed on the input device 1-1 (for example, CRT), and correspondingly, each is displayed. Data values are input (process 4-4). The input data value is input to the test data storage device 1-8 by the input device 1.
The test data identifier input at -1 is added and stored (processing of 4-5, for example, operation of writing data to file). These operations are performed until values are input for all data (process 4-6).

When the input of the test data to one temporary storage device is completed, the test data input device 1-1 requests the input of the next temporary storage device identifier and the test data identifier. The input process is repeated for each storage device for the number of test data to be tested (process of 4-7).

After creating all the test data, the test data input device 1-6 is used to test each test data in the test data storage device 1-8 and the data information storage device 1-8.
The definition information of each temporary file of No. 4 is compared, it is confirmed whether the test data is defined for all the temporary storage devices used by the LM, and the process is ended (process of 4-8). At this time, if there is a temporary storage device in which the test data is not defined, the test data input process is performed again.

After the driver part program is created and each test data to be used is created, the driver program is compiled into a CU and then the LM to be tested
As a CU. When the LM incorporating the completed driver program is executed, the test data identifier used for the test can be specified, so the identifier of the test data created by this device is specified. In this way
The LM alone can be tested using various test data.

FIG. 5 is an example of a configuration diagram of the source program storage device 1-2.

FIG. 6 is a block diagram of the data information storage device 1-4.
Is an example. The file information storage section stores the file name,
Information such as file organization and key name is stored in the data information storage unit, and information such as level, name, attribute type, number of digits, and repeat designation of each data is stored.

FIG. 7 shows a driver program storage device 1-
7 is an example of a configuration diagram of FIG.

The created driver program selects the test data identifier to be tested by the input device 1-1, and sets the value of each test data in the test data storage device 1-8 having the same area as the temporary storage device. It includes a process of reading and copying to the temporary storage device (for example, a process of copying all the contents of the permanent file to the temporary file) and a process of calling the main CU of the LM.

FIG. 8 shows an example of the test data storage device 1-8. The area 8-1 contains test data with the identifier "TEST-1", and the area 8-2 contains the identifier "TEST-".
2 "of test data are stored respectively. These have the same area size as the temporary storage device (for example, temporary file) used in the LM.

[0035]

As described above, according to the present invention, in the test of each LM alone in the development of a large-scale program having a plurality of LMs, the program of the driver part for operating each LM alone is automatically generated. Reduce the time to create a driver program.

Further, since the test data defining various patterns can be created at one time, the contents of the data in the temporary storage device, which transfers the data at the time of the test, can be easily changed, which is more efficient. You can test.

Then, at the stage of the unit test, high quality L
Since it can be set to M, it is possible to reduce the occurrence and correction of bugs in the subsequent testing of the entire program in which each LM is connected.

[Brief description of drawings]

FIG. 1 is a block diagram showing an overall configuration of the present invention.

FIG. 2 is a diagram of a work procedure showing a flow of analysis of data information of each temporary storage device.

FIG. 3 is a diagram of a work procedure showing a flow of automatic generation of a driver program.

FIG. 4 is a diagram of a work procedure showing a flow of creating test data.

FIG. 5 is an example of a configuration diagram of a source program storage device 1-2.

FIG. 6 is an example of a configuration diagram of a data information storage device 1-4.

FIG. 7 is an example of a configuration diagram of a driver program storage device 1-7.

FIG. 8 is an example of a configuration diagram of a test data storage device 1-8.

[Explanation of symbols]

1-1 Input device 1-2 Source program storage device 1-3 Data information analysis device 1-4 Data information storage device 1-5 Program creation device 1-6 Test data input device 1-7 Driver program storage device 1-8 Test Data storage device 8-1 Area in which test data of identifier "TEST-1" is stored 8-2 Area in which test data of identifier "TEST-2" is stored

Claims (1)

[Claims] 1. In order to test each LM unit of a large-scale program in which a plurality of load modules (hereinafter referred to as LMs) are divided, a program (driver required for enabling the LM to operate independently). When creating a program, an input device for inputting an identifier of a temporary storage device used for passing data between individual LMs, an identifier of a program to be created, and a temporary storage device by analyzing a data description part of a source program. Detailed information and data information analysis device that extracts data information, a data information storage device that stores the information analyzed by the data information analysis device, a program creation device that creates a driver program, and repeat test data Enter the test data input device that determines the input and the end of input and the created driver program. A load module unit test support device comprising a driver program storage device for storing and a test data storage device for storing input test data.