JPH04199438A - Software check system - Google Patents

Abstract

PURPOSE:To shorten the checking time together with reduction of the storage capacity and improvement of the operability by preparing no independent file for each of check contents and registering collectively the necessary check contents into a control file. CONSTITUTION:A check program control file 101 and a check system 102 are provided, and a command option pattern outputted from the system 102 and a check program are inputted to a check subject program 103 for execution of the program check. The check results are outputted for each item number and recorded into the check result files 104-l-106-3 respectively. Thus plural command option patterns and plural check programs are registered into a single file. Then the check programs are edited. As a result, the necessary file capacity is reduced end also the check workability is improved.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a software inspection system, and more particularly to a software inspection system that performs inspection using a plurality of inspection programs according to a plurality of command option patterns.

[Conventional technology]

Conventionally, programs have been created using the procedure shown in FIG. That is, after creating a desired program in step 501, it is inspected in step 502, and whether or not the result is correct is checked in step 503. If the result is incorrect, the program is corrected in step 504, and then It is checked again in step 502 whether the modification is correct.

In this process, it is essential to check the command options written on the start line to check the program. In other words, do command options have unnecessary effects on each other? Also, when inputting the same inspection program as inspection data, do you get the expected difference when specifying different combinations of command options? inspection was necessary.

Conventionally, this inspection step was performed using a system as shown in FIG. That is, files 310, 311, and 312 are prepared for the number of necessary inspection programs, and the program to be inspected 103 is inspected by inputting command option patterns manually from the console 401.

A batch function has been used as a method to avoid manually inputting command option patterns from the console 401. This is a method of creating and executing a batch file 402 that describes the inspection program name and command option pattern.

[Problem to be solved by the invention]

The conventional software testing system described above has the disadvantage that it is very uneconomical because each testing program is managed in a separate file. That is, the allocation of secondary storage area for one file on a secondary storage device (hard disk or floppy disk) is usually a minimum of 512 hides to a maximum of 1.
6 bytes, and the allocated space cannot be used by other files. For this reason, 100
When there are many byte-sized files, keeping them separate on the secondary storage device creates a lot of free space that cannot be used for other files (512 bytes). For units:
(512-100) ÷ 512 = approximately 80%, in 16 byte units: (16384-100) ÷ 16384 =
(approximately 99% free space), making it very uneconomical.

Furthermore, the command option pattern is added to the console 401.
The method of manually inputting information one after another significantly reduces the operator's work efficiency, is inefficient, and involves the risk of erroneous input.

In addition, if you want to avoid manually inputting command option patterns from the console 401 and create a batch file and perform inspection using the batch function, you must create a batch file separate from the file containing the inspection program. This also causes the management of files necessary for inspection to become complicated. Furthermore, when it is necessary to modify the Al1 pattern of the command option pattern, it is necessary to modify multiple locations in the batch file, and there is a drawback that modifications are likely to be omitted.

An object of the present invention is to reduce the required file capacity and improve inspection workability in a software inspection system that performs inspection using multiple inspection programs and multiple command option patterns. .

[Means to solve the problem]

The software inspection system of the present invention includes a means for registering a plurality of command option patterns and a plurality of inspection programs in one file, and editing an inspection program corresponding to an inspection item from the registered file using an inspection item number as an index. and means for comparing and storing the plurality of command option patterns; and means for sequentially executing the corresponding inspection blocks using the edited file according to the plurality of command option patterns. It is something to do.

〔Example〕

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, in which an inspection program management file 101, which will be described later, and all command option patterns in the management file are extracted, and the inspection program in the management file corresponding to the specified item number is accessed. and an inspection system 102 that edits the command option pattern and the inspection program into one file, inputs the command option pattern and inspection program output from the inspection system 102 into the inspection target program 103, and performs inspection.
The results are output for each item number and each inspection result file 1
04-1~104-3,105-1~105-3,10
6-1 to 106-3.

FIG. 3 is a diagram showing the correspondence between the configuration of the inspection program management file 101 used in this embodiment and the generated inspection blocks. Area 301 where patterns 1, 2...N are continuously described
, 302, 303, . . . 304, and an examination content area in which a start keyword 305, an item number 306, and the examination contents of the corresponding item number are described as one set.

The operation of this embodiment will be explained below according to the operating procedure. First, the name of the program to be inspected is extracted from the management file 101, and then the command option patterns 1 to N are extracted and stored. Next, the user specifies the item number to be inspected, extracts and edits one of the inspection contents. When each test item uses all of the registered command option patterns, the command option patterns 1 to N can be used in common for each test item by simply storing them first.

As shown in FIG. 2, clear the inspection item number to m=o (step 201), then increment m by 1 (step 20).
2) As a result, test content 1 for performing the test with test item number l is edited as test program 310 (step 203). After that, clear n, = 0 (
Step 204), by adding 1 to n (Step 205), a program check is executed according to command option pattern 1, and the result is recorded in the file 104-1 of item number 1 in FIG. 1 (Step 206).
). Next, the command option pattern is judged (
Step 207), if the next command option pattern exists, n is further incremented by 1 (Step 205).
). As a result, the inspection based on command option pattern 2 is executed, and the result is file 105 with item number l.
-1 is recorded. Similarly, steps 205 to 207
is repeatedly processed, and all command option patterns for item number 1 have been checked. When the inspection is completed, the inspection system 102 deletes the inspection content for item number 1 (step 208), and determines whether there is an item number to be inspected next (step 209). If so, the process returns to step 202, the next inspection item is specified, and the inspection program is edited. Once all inspection items have been inspected, all inspections of the program have been completed.

According to this embodiment, it is possible to sequentially test any one test item using a plurality of command option patterns. It is clear that the inspection items may be specified sequentially or discontinuously.

〔Effect of the invention〕

According to the present invention, the necessary inspection contents are registered in a management file all at once, avoiding the need to prepare separate files for each inspection content, so it is no longer necessary to input various command option patterns from the console as in the past. This is not necessary and the inspection time can be significantly shortened.

Furthermore, by providing the management file, it is not necessary to create a large amount of wasteful free space in the secondary storage device, which is extremely economical. In addition, unlike the conventional method, there is no need to exchange files for each inspection program, which greatly simplifies operability.

Therefore, it will be understood that the present invention can be an extremely effective system, especially in the recent trend of increasing test items and command option patterns.

[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 diagram showing the structure of the content of the inspection program management file input by the inspection system and the correspondence between the inspection program generated from it, and Figure 4 is a diagram of the configuration of the conventional inspection method. , FIG. 5 shows a diagram of the program development procedure. 101...Inspection program management file, 10
2...Inspection system, 103...Program to be inspected, 104...Output result of command option pattern 1, 104-1...Output result of item number l , 104-2... Output result of item number 2, 104-3... Pressure result of item number M, 105... Command option pattern 2
105-1... Output result of item number 1, 105-2... Output result of item number 2,
105-3...Item number M pressure! Fruit, 1
06... Output result of command option pattern N, 106-1... Pressure result of item number l,
106-2... Pressure result of item number 2, 106
-3...Output result of item number M, 201 to 20
9... Inspection system processing, 301...
・Inspection target program name, 302...Command option pattern 1.303...Command option pattern 2.304...Command option pattern N, 305...Start Keyword section, 306...Item number section, 307...
...Inspection content of inspection program l, 308...
- Inspection content of inspection program 2.309... Inspection content M of inspection program, 310... Inspection program of item number 1 1.311... Inspection program of item number 2 2.312...Item number M
Inspection program 3.401...Console,
402...Batch file, 501-504...
...Each step of program development. Agent: Susumu Uchihara, patent attorney ↓N. ND Figure 3 Figure 5 TART ↓YES El, ID

Claims (1)

[Claims] In a software testing system that inputs a test program into the program to be tested and verifies the program's behavior based on the test results, multiple patterns of command options are specified to control the behavior of the software when starting the program to be tested. means for registering a plurality of inspection programs in one file; means for editing an inspection program corresponding to the inspection item number from the registered file using the inspection item number as an index; and means for editing the inspection program corresponding to the inspection item number from the registered file; A software inspection system comprising: means for extracting and storing the inspection program; and means for sequentially executing inspection according to the plurality of command option patterns using the generated inspection program.