JPH04199436A - Software check system - Google Patents

Abstract

PURPOSE:To reduce the necessary file capacity by arranging the check programs into a single file, taking out only a program of the desired check contents to edit it together with a common part and checking a due program based on the edited program. CONSTITUTION:A check subject program 104 is checked based on a check program control file 101, a check execution system 102, and a console 103. Then these check results are arranged into an output result file 105 for each check item. Thus all programs necessary for check are arranged and controlled in a single file. Then the necessary programs are taken out for each desired check item. When the check of each item is complete, the contents of an edited check program are erased end an idle area is increased in a secondary storage. Then an editing means for a new program necessary for the next check its provided. Thus the effective check is attained for the check programs with the least file capacity.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a software testing system, and particularly to a processing means for a testing program used to verify the operation of a program.

[Conventional technology]

Generally, program operation verification is performed using a test program. In recent years, as the scale of software has increased and its functionality has become more sophisticated, its testing programs have become extremely complex, and a single developed program must be verified using multiple types of testing programs. situation.

Under such circumstances, conventionally, as shown in Figure 4, each inspection program is divided into inspection items and independent files are created for each, and the program is verified by accessing files that match the inspection items as needed. was. FIG. 4 shows a system block diagram when a program is verified using a test program with N test items. The inspection program is stored in N independent files 309, 310, 311 for each inspection item number, and verification is executed by inputting each file to the inspection target program 104. The result is file 105-
Stored in L 105-2, 105-3 and output result 10
Recorded as 5. This recorded result becomes the inspection result of the program to be inspected.

[Problems to be Solved by the Invention] However, while it is preferable to prepare separate files for each inspection item as in the past from the viewpoint of ease of managing inspection programs, there are various problems as described below. Contains.

That is, looking at each inspection program individually, as shown in FIG. 5, each file of the inspection program has an area 304 where a different program is written for each inspection content,
307, and areas 301 and 308 in which programs necessary for program pre-processing and post-processing are written. Of these, areas 301 and 308 are common program areas for all inspection programs.

However, in the conventional method where independent files are provided for each inspection item and one inspection item is inspected using one of the files, independent common program areas 301 and 308 must be provided for each file. The major drawback is that the capacity is enormous.

Furthermore, the allocation of secondary storage area for one file on a secondary storage device (hard disk or floppy disk) is usually done in bytes from a minimum of 512 bytes to a maximum of 16 bytes, and the allocated area cannot be used by other files. Can not do it. For this reason, when there are many files of about 100 bytes, keeping these files separate on the secondary storage device creates a lot of free space that cannot be used for other files. (For units of 512 bytes: (5
12-100) ÷ 512 = approximately 80%, and in the case of 16 bytes: (16384-100) ÷ 16384 = approximately 99% free space), which is very uneconomical. However, in the conventional software inspection system, there is no effective means to solve these problems, so an independent file management format has no choice but to be adopted.

An object of the present invention is to provide a software testing system that can perform efficient testing with a small file capacity.

Means for Solving the Problem] In the present invention, all the programs necessary for inspection are managed in one place, the necessary programs are retrieved and edited for each desired inspection item, and when the inspection of each item is completed, By deleting the contents of one edited test program to increase the free space on the secondary storage device, and providing a means to newly edit the program required for the next test, the file size can be minimized. It is characterized by enabling efficient inspection.

In the present invention, in a single inspection program management file, a common program area A necessary for preprocessing of each inspection program is first set, and an inspection content program that describes each inspection content is provided for each item. Finally, a common program area B necessary for post-processing of the program is provided, and the start keyword and item number are placed at the start address of each inspection content program, and the end keyword and item number are placed at the end address. We are trying to reduce the size of inspection program files.

Embodiment] Hereinafter, one embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a system block diagram of this embodiment, which is a feature of the present invention, including an inspection program management file 101 and an inspection execution system that extracts and edits an inspection program corresponding to a necessary inspection item from this management file. 10
2 and a console 103 are newly provided, and these are used to test the program to be tested 104 and the results are compiled into an output result file 105 for each test item.

As shown in FIG. 2, the operating procedure begins with the console 103.
Input the inspection item number and the name of the program to be inspected (step 201), and then create an inspection program in the inspection execution system 102 according to the input inspection item number (step 202).

The inspection execution system 102 edits inspection programs for each inspection item. Subsequently, the program was inspected according to the inspection program and the results were designated with item numbers 105-1 and 10.
Record in either 5-2 or 105-3 (Step 2
03). By deleting the last edited inspection program and releasing the area of the secondary storage device occupied by the inspection program, free space is increased and preparations are made for editing the inspection program for the next inspection item ( Step 2
04). By executing this series of processing for all inspection items, the inspection of the program to be inspected is completed.

FIG. 3 is a configuration diagram of the inspection program management file 101 and the inspection program to be edited.

The inspection program management file 101 includes a common part A (preprocessing program for each test), followed by independent programs 304, 306, 307 in the order of test contents l...N, and finally a common part B (postprocessing program). common program) 308
will be established. Item number 303 at the beginning and end of each inspection content
A start keyword 302, an item number 303, and an end keyword 305 are arranged.

The procedure for editing an inspection program from the inspection program management file 101 is as shown in FIG. 4. First, the inspection program management file and the editing file are opened (step 401). Next, 1 from the inspection program management file.
Read the line (step 402). Check whether the file has ended (step 403), and repeat the following unless the file has ended. First, it is checked whether the start keyword exists in the read line (step 404), and if it does not exist, the read line is output as is to the editing file (step 405). If the start keyword exists, check whether the item number in the next item number section matches the specified inspection item number (step 406), and if it does, the data from that point to before the end keyword is created in the edit file. Output (step 408). If they do not match, the contents of the test item are not relevant, so reading is skipped until the next end keyword line is reached (step 407). The above steps are repeated until the file ends, and when the file ends, the inspection program management file and editing file are closed and an inspection program is generated.

For example, if you need an inspection program with item number 1, by specifying item number 1, common part A, inspection content 1, and common part B are extracted from management file 101 and saved in a small file in execution system 102. Edited.

The same applies to other inspection items.

Note that, when a plurality of inspection items are inspected in succession, it is clear that the common parts A and B can be used in common by rewriting only the inspection contents on the edit file.

〔Effect of the invention〕

As described above, according to the present invention, a large number of inspection programs to be used are combined into one file, only the desired inspection content program is extracted and edited along with the common parts, and the program to be inspected is inspected based on this edited program. This makes it possible to significantly reduce the required file capacity, and since each item is inspected based on the edited file, the edited file can be reduced to the size of one small file. It is economical to use.

[Brief explanation of the drawing]

FIG. 1 is an overall configuration diagram of the inspection system of the present invention, and FIG.
The figure is a flowchart of the processing of the inspection system, Figure 3 is a correspondence diagram of the structure of the contents of the inspection program management file input by the inspection system and the structure of the contents of the inspection program generated from it, and Figure 4 is the inspection program management FIG. 5 is a flowchart of a process for generating an inspection program from a file, FIG. 5 is a block diagram of a conventional inspection method, and FIG. 6 is a block diagram of the contents of a conventional inspection program. 101...Inspection program management file, 10
2... Inspection system, 103... Console, 104... Program to be inspected, 105...
...output result, 105-1...output result of item number 1, 105-2...output result of item number 2,
105-3...Output result of item number N, 201 to 20
4...Inspection system processing, 301...Inspection program common part A, 302...Start keyword L303...Item number part, 304...
...Inspection content of the inspection program 1.305... End keyword section, 306... Inspection content of the inspection program 2.307... Inspection content N of the inspection program, 308...・Inspection program common part B, 3
09...Inspection program for item number 1, 310...
...Inspection program for item number 2, 311...
・Inspection program of item number N, 401 to 409...
...Inspection system processing that generates an inspection program from an inspection program management file. Agent Patent Attorney Oto Hara Figure 2 Figure 3 Figure 4 END

Claims (1)

[Claims] In a software testing system that inputs a test program into the program to be tested and verifies the operation of the program based on the execution results, multiple test programs are separated into common parts and independent parts into one file. means for registering the inspection program in the registered file using the inspection item number as an index; means for generating an inspection program corresponding to the inspection item number; means for inputting and executing the inspection program into a program to be inspected; A software inspection system comprising: means for erasing a program.