JPH0962529A - Test program running device - Google Patents

Abstract

(57) [Abstract] [PROBLEMS] To provide a test program running device capable of managing the running condition of a test program, taking over the execution progress, and executing this to uniformly test all devices. SOLUTION: A test travel management table 31 storing test travel information indicating whether a test of each device is being executed, execution completed, or not executed, and a test program execution instruction from a system operation console 40 is provided. In response, the test device management unit A refers to the test run management table 31 and causes the test program execution unit B to execute the test program with the device being executed in order and the device not yet executed as the test target device. In response to the supply, the test run information of the corresponding device is changed to the execution completion and the test result is supplied to the system operation console 40.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a test program running device, and more particularly, to a running condition of a test program,
The present invention relates to a test program running device that allows a test target device to have a uniform number of tests.

[0002]

2. Description of the Related Art The execution of a test program for a plurality of hardware devices connected to a conventional computer system is performed in a computer system as disclosed in, for example, Japanese Patent Laid-Open No. 61-153742. A table indicating the correspondence between the device name of the peripheral device, the device information of the device and the device type, and the table indicating the correspondence between the test program and the device type are stored in the main storage device in advance, and the operator activates the test program. By notifying the central processing unit, the central processing unit searches the above two tables for a peripheral device that is currently disconnected from operation, searches for a test program corresponding to the peripheral device, and activates the test program.

This conventional test program starting method is as follows:
A system resource management table that stores each peripheral device and its device information and device type stored in the main memory, a test program table that shows the correspondence between each device type and the test program name, and an instruction to execute the test program from the operator. , The device information in the system resource management table is sequentially read to check whether the peripheral device is disconnected from the operating system, and if it is disconnected, the test program table is searched based on the corresponding device type. The test program corresponding to the device type is retrieved and the test program having this test program name is executed, and two tables, a system resource management table and a test program table, are prepared in the main storage device in advance. By issuing the instruction, the central processing unit is instructed to execute the test program. Only that, selecting a predetermined program to the peripheral device is disconnected from the production can be started.

On the other hand, as shown in the block diagram of FIG. 7, a running device for a test program for a hardware device connected to a conventional general computer system includes a central processing unit 100 for controlling the entire computer system. , A system operation console 400 for inputting the execution of the test program and displaying a message indicating the execution result of the test program.

The central processing unit 100 stores a storage unit 200 in which a device configuration management table 210 for knowing all the devices connected to the system is recorded in advance. The central processing unit 100 further receives an instruction to execute the test program from the system console 400, refers to the device configuration management table 210, and causes the test program to be executed only for the device in the available state "S". , A test apparatus management unit C for receiving the execution result and displaying the execution result on the system console 400, and a test program execution section D for receiving the test program execution instruction from the test apparatus management unit C and executing the test program on the apparatus. Have and.

A device configuration management table 21 of the storage unit 200
As shown in FIG. 8, the format of 0 is composed of a device name 220 and usable / unusable information 230. As usable / unusable information 230, S represents a usable state and U represents an unusable state.

FIG. 9 is a flow chart for explaining the operation of the test run management unit of FIG. 7, and FIG. 10 is a flow chart for explaining the operation of the test program execution unit.

Next, a conventional test program running device will be described with reference to FIGS.

In FIG. 7, the execution of the test program is instructed from the system operation console 400. Test equipment management section C
As shown in the flow chart of FIG.
When instructed to execute the test program (step C
1), the usable / unusable information 230 is in the usable state in order from the head of the device configuration management table 210 in the storage unit 200 ″
Only one device name 220 of the device having S ″ is input (step C2), it is determined whether the device name 220 can be input (step C3), and if the device name 220 can be input, The input device name 220 is passed to the test program execution unit D (step C4).

At this time, the test program execution section D executes the test program for the device name 220 passed from the test apparatus management section C as shown in the flowchart of FIG. 10 (step D1), and the test program ends normally. It is determined (step D2), and if it ends normally, it is passed to the test apparatus management unit C (step D3). If it is abnormally ended, that fact is passed to the test apparatus management unit C (step D3). D4).

The end result of the test program is received by the test apparatus management section C at step C5 in the flowchart of FIG. 9, and it is judged whether the result of the test program is normally completed (step C6). This is displayed on the system console 400 and the test program is interrupted (step C8). In the case of normal termination, the device configuration management table 21
From 0, enter the next device name 220 whose usable / unusable information 230 is in the usable state "S" (step C
7) and returns to the process of step C3. In step C3, it is determined whether the device name 220 has been input. If the device name 220 cannot be input, the device names 220 of all the devices to be tested have been input. Display on 400 (Step C
9), end the processing.

[0012]

DISCLOSURE OF THE INVENTION Problems to be Solved by the Invention
In the test program start-up method of Japanese Patent No. 53742, there is a problem that a device that is in a state of being disconnected from the system is a test target device and the test program cannot be started for a device that is operating a computer system.

In the conventional general test program running apparatus, when the test program is being executed, an emergency stop of the system due to a failure of the system or a failure of the power supply, or a case where the system is stopped after the processing of one day is completed. , It is always recorded at the beginning of the device configuration management table when trying to execute the test program again because it is not known how many devices that were previously recorded in the device configuration management table have been executed. The test program is re-executed in order from the device.

Therefore, in order to execute the test program on the device for which the test program was not executed last time, the test program should be executed again for the device executed in the previous test and then executed. Becomes Therefore, the device recorded at the end of the device configuration management table has a relatively small number of executions of the test program, and there is a problem that it is difficult to uniformly execute the test on all devices.

An object of the present invention is to manage a running condition of a test program of usable devices in a system, to carry out the test program while taking over the execution progress, and to test all devices uniformly. To provide a traveling device.

[0016]

A test program running device according to a first aspect of the present invention uses a device for indicating whether or not each device is usable based on a physical connection state of each of a plurality of devices connected to a system. A first storage unit that stores in advance a device configuration management table that stores state information, and a test that indicates whether a test by a test program of each device is being executed or has not been executed for each device. Second storage means for storing a test travel management table for storing travel information, input / output means for inputting an execution instruction of the test program and outputting a message indicating an execution result of the test program, and a test program execution target A test program executor that executes a test program corresponding to the device corresponding to the device identifier in response to the supply of the device identifier and outputs the result. In response to the supply of the test program execution instruction from the input / output means, the test running management table is referred to and the device in which the test running information is being executed and then the unexecuted device The identifier of the test target device is supplied to the test program execution means as a test target device which is updated during execution, and when the test travel management table is not created, the device configuration management table is referenced to use the usage status information. A test run management table in which the test run information is set to unexecuted is created for all the devices in the enabled state, and the test run information is updated in execution by sequentially referring to this table and the test target device is set. As an identifier, the identifier of the device to be tested is supplied to the test program executing means, and the corresponding device responds to the supply of the test result from the test program executing means. Test drive information to change the execution completion test program running device which comprises a test device management means for supplying the test result to the output means.

The test program running device of the second invention is
In the test program running device of the first invention, the second storage means for storing the test travel management table is a non-volatile storage means.

[0018]

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of a test program running device of the present invention.

As shown in FIG. 1, the test program running device of the present embodiment has a central processing unit 10 for controlling the entire computer system and a test running management table 31.
And a system operation console 40 for inputting the execution of the test program and displaying a message indicating the execution result of the test program.

The central processing unit 10 stores a storage unit 20 that preliminarily stores a device configuration management table 21 for knowing all the devices connected to the system.

FIG. 2 is a device configuration management table 21 which is recorded in the storage unit 20 of FIG. 1 and manages the physical connection state of the device.
It is a format diagram showing the format of. The format of the device configuration management table 21 of the storage unit 20 is device name 22 and usable /
In the usable / unusable information 23, S represents a usable state and U represents an unusable state.

Here, the usable state means a state in which the system is physically connected to the system. A device that is not used for a certain work, that is, a device that is separated from the operation of the system for the work, but physically connected to the system, is made available.

FIG. 3 is a format diagram showing the format of the test running management table 31 recorded in the magnetic disk device 30 of FIG. 1 and managing the running state of the test program.
The format of the test run management table 31 of the magnetic disk device 30 is composed of a device name 32 and test program run information 33. As the test program run information 33, R is a test program running state and E is a test program run complete. A state, N represents a test program unexecuted state.

As the storage means for storing the test run management table, it is desirable to use a non-volatile storage means that does not lose its stored contents even if the power supply fails.

The central processing unit 10 shown in FIG. 1 receives a test program execution instruction from the system console 40, refers to the device configuration management table 21, and creates and updates the test run management table 31. The test program is executed, the execution result is received, and the execution result is displayed on the system console 40. The test apparatus management unit A and the test apparatus management unit A receive the test program execution instruction and execute the test program on the apparatus. It has a test program execution unit B for executing.

FIG. 4 is a flow chart for explaining a part of the operation of the test run management section, FIG. 5 is a flow chart for explaining the operation of the test run management section other than FIG. 4, and FIG. 6 is a test program execution section. 6 is a flowchart for explaining the operation.

Next, the operation of the present embodiment will be described with reference to FIGS.
This will be described with reference to FIG.

First, referring to FIG. 1, the system console 40
Instructs the test apparatus management unit A to execute the test program. Next, in FIG. 4, when the test apparatus management unit A is instructed to execute the test program by the system operator console 40 (step A1), the test apparatus management unit A confirms whether the test drive management table 31 exists in the magnetic disk device 30 (( Step A
2) If it does not exist (NO branch of step A2), only the device name 22 of the device whose usable / unusable information 23 is in the usable state “S” is stored from the device configuration management table 21 in the storage unit 20. By referring to the test drive management table 31 in the magnetic disk device 30 (step A9), all the test program drive information 33 of the test drive management table 31 is set to the test program non-execution state "N" (step A10). . If the test drive management table 31 in the magnetic disk device 30 exists (YES in step A2)
S branch), it is confirmed whether all the test program running information 33 of the test running management table 31 is in the test program execution completion state "E" (step A3), and the test program running information 33 is all execution completion state "E". If there is (YES branch in step A3), all the test program running information 33 is in the unexecuted state as in step A10 described above.
Set to N ″.

Next, it is confirmed whether or not the test program running information "R" exists in the test program running information 33 (step A4), and if the test program running information 33 with "R" set exists (step A4). YES branch of A4),
The device name 32 corresponding to the running state "R" of the test program running information 33 is passed to the test program execution unit B (step A5). When the test program running information 33 in which "R" is set does not exist (NO branch of step A4),
It is confirmed whether or not the unexecuted state "N" exists in the test program running information 33 (step A11). If the test program running information 33 with "N" set exists, the test program running information 33 The non-execution state "N" is set to the execution state "R" (step A12), and the device name 32 corresponding to the execution state "R" of the test program running information 33 is passed to the test program execution section B (step A).
5).

At this time, the test program execution unit B executes the test program for the device name 32 passed from the test device management unit A as shown in the flowchart of FIG. 6 (step B
1) It is determined whether the test program has ended normally (step B2). If the test program ends normally, the fact is passed to the test apparatus management section A (step B3). If it ends abnormally, the fact is notified. Hand over to the test equipment management section A (step B
4).

The end result of the test program is received by the test apparatus management section A at step A6 in the flowchart of FIG. 4 (step A6). Next, it is judged whether or not the result of the test program has ended normally (step A7).
The fact is displayed on the system console 40 and the test program is interrupted (step A13). In the case of normal termination, the running state "R" of the test program running information 33 is set to the execution completed state "E" (step A8), and step A4
Return to processing.

In the flow chart of FIG. 4, if the unexecuted state "N" does not exist in step A11 (NO in step A11).
Branch), as shown in the flow chart of FIG. 5, it is judged whether all the test program running information 33 is in the execution completion state "E" (step A14), and if all the execution completion state "E", the test program ends. This is displayed on the system console 40 (step A15), and even one execution completed state "E"
If there is a device other than the above, the fact that an error has occurred in the test drive management table 31 in the magnetic disk device 30 is displayed on the system console 40, and the test drive management table 31 in the magnetic disk device 30 is deleted (step A16). ).

As described above, when the test program is executed during the operation of the computer system, the test run management table is created / updated in the magnetic disk device, and the test run management table shows the running state of the test program. By managing the unexecuted state and the execution completed state, even if the computer system is stopped, the test program is not executed from the first device, but the execution progress is taken over and the test program is always executed from the device that is not executing the test program. It has the effect that it can be restarted and the test program can be uniformly executed for all the devices.

[0035]

As described above, the test program running device of the present invention creates the test run management table in the magnetic disk device and executes the test run management table in the test run management table when executing the test program during the operation of the computer system. By managing the running state, unexecuted state, and execution completed state of the test program, the test program is not executed from the first device even if the computer system is stopped, but the execution progress is taken over and the test program is executed. Since the execution can always be resumed from the non-executed device, the test program can be uniformly executed in all the devices.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of a test program running device of the present invention.

FIG. 2 is a format diagram showing the contents of a device configuration management table of the device of FIG.

FIG. 3 is a format diagram showing the contents of the test travel management table of FIG.

FIG. 4 is a flowchart for explaining a part of the operation of the test travel management unit in FIG.

5 is a flowchart for explaining the operation of the test travel management unit of FIG. 1 other than that of FIG. 4;

FIG. 6 is a flowchart for explaining the operation of the test program execution unit in FIG.

FIG. 7 is a block diagram of an example of a conventional test program running device.

8 is a format diagram showing the contents of the device configuration management table of FIG.

9 is a flowchart for explaining the operation of the test travel management unit of FIG.

FIG. 10 is a flowchart for explaining the operation of the test program execution unit in FIG.

[Explanation of symbols]

 10, 100 Central processing unit 20, 200 Storage unit 21, 210 Device configuration management table 22, 32, 220 Device name 23, 230 Usable / unusable information 30 Magnetic disk device 31 Test run management table 33 Test program run information 40, 400 System operation console A, C Test equipment management unit B, D Test program execution unit

Claims (2)

[Claims] 1. A device configuration management table that stores in advance a device configuration management table that stores usage status information indicating whether or not each device can be used based on the physical connection status of each device connected to the system. And a second storage means for storing a test travel management table storing test travel information indicating whether a test by the test program of each device is being executed or has not been executed for each device. Storage means, input / output means for inputting an execution instruction of the test program and outputting a message indicating an execution result of the test program, and a device corresponding to the device identifier in response to supply of the device identifier of the test program execution target. The test program executing means for executing the test program corresponding to the above and outputting the result, and the instruction for executing the test program from the input / output means are provided. In response to the supply, referring to the test run management table, the device in which the test run information is being executed and then the unexecuted device are updated while the test run information is being executed to execute the test program as the device to be tested. The identifier of this device to be tested is supplied to the means, and when the test travel management table is not created, the device configuration management table is referred to and the usage status information is applied to all devices in the available status. The test travel management table in which the test travel information is set to unexecuted is created, and the test travel information is sequentially updated by referring to this table and the test program execution means is set as the test target device to the test program execution means. In response to the supply of the test result from the test program executing means, the test run information of the corresponding device is changed to the execution completion, and the test result is input / output. Test program running device which comprises a test device management means for supplying the means. 2. The test program running device according to claim 1, wherein the second storage means for storing the test travel management table is a non-volatile storage means.