JPH01112344A - System for controlling test of input/output control software - Google Patents

Abstract

PURPOSE:To generate pseudo interruption by providing a command generating means and an interruption data generating means which generates interruption data based on data set from the outside and outputs interruption and the interruption data at a timing designated from the outside in a test tool. CONSTITUTION:When it is desired to generate the interruption in the device driver (input/output control software) 11 of an object to be tested by the test tool 12, the command generating means 121 generates a command, and starts up an input/output control adaptor 2. The input/output control adaptor 2 applies the interruption on the test tool 12 based on the command. In the test tool 12, the interruption data generating means 122 applies the interruption on the device driver 11 at the timing designated from the outside, then, sends the interruption data. The interruption data is set on the test tool 12 by an operator. In such a way, it is not required to use the input/output control adaptor driven by the device driver of the object to be tested actually, and the interruption can be performed by simulation.

Description

[Detailed Description of the Invention] [Summary] This is an input/output control adapter for the purpose of generating a pseudo interrupt to input/output control software in connection with a test control method for input/output control software in workstations, controllers, etc. A test circuit for testing the input/output control software that drives the input/output control adapter includes a command generation means that generates a command to start the input/output control adapter, and a timing that generates interrupt data based on data set externally in advance. It is equipped with an interrupt data generation means that outputs interrupts and interrupt data, and uses a standardly implemented input/output control adapter to generate pseudo-simulation at any timing using arbitrarily set interrupt data for input/output control software. The configuration is configured to automatically generate an interrupt and perform the test.

[Industrial application field]

The present invention is a test control method for input/output control software in workstations, controllers, etc. In a test tool for input/output control software, a mechanism for simulating interrupts from an input/output control adapter is essential.

However, it is not easy to generate interrupts in accordance with the timing of the actual environment.

[Conventional technology]

In a test tool for input/output control software (generally called a device driver, hereinafter also referred to as a device driver), the test target is connected to an input/output control adapter in order to check its operation under the interrupt environment of the O8 (operating system). A mechanism for simulating interrupts is essential.

In the prior art, it was common to put test firmware into an input/output control adapter and use the input/output control adapter to actually drive the test.

FIG. 5 is a diagram showing a device driver testing mechanism according to the prior art.

As shown in the figure, a test tool above the device driver issues a command to the device driver, which in turn issues a command to the input/output control adapter. The input/output control adapter analyzed this and raised the specified interrupt.

[Problem that the invention seeks to solve]

In the conventional method, it was necessary to create test firmware for each input/output control adapter, which took a lot of time.

Furthermore, if you try to make modifications such as changing some of the interrupt data, you will have to recreate the firmware. In other words, there is no flexibility.

Moreover, correction cannot be realized with a human output control adapter that has firmware on the ROM.

Additionally, interrupts occur too quickly, making debugging difficult.

The present invention aims to provide a new test control method that solves these conventional problems.

[Means for solving problems]

FIG. 1 shows a principle block diagram of a device driver test control method according to the present invention.

In the figure, 1 is a main body such as a workstation and a controller.

2 is an input/output control adapter, which is implemented as an existing standard.

11 is input/output control software to be tested.

12 is a test tool.

A command generating means 121 generates a command to start the input/output control adapter.

Reference numeral 122 denotes an interrupt data generating means, which generates interrupt data based on preset data, and outputs the interrupt and interrupt data at a timing instructed from the outside.

[For production]

The test tool 12 uses the device driver to be tested (
When it is desired to generate an interrupt in the input/output control software (input/output control software) 11, the command generation means 121 generates a command to activate the human output control adapter 2.

The input/output control adapter 2 interrupts the test tool 12 with the command.

In the test tool 12, the interrupt data generation means 122 generates a signal from the device driver 11 at a timing instructed from the outside.
Interrupts and sends interrupt data.

The interrupt data is set in the test tool 12 by the operator. Therefore, there is no need to modify the software due to differences in input/output devices or data changes.

The interrupt data includes device status information, control data, magnetic disk device read data, and the like.

The timing of the interrupt depends on the operator's instructions.

With the above configuration, the device driver 1 to be tested
4! It is not necessary to use the input/output control adapter that - actually drives, and the interrupt can be simulated and triggered.

Furthermore, if the model is of the same series, it can be applied to device drivers that drive different adapters by simply changing the interrupt data to be set.

〔Example〕

The present invention will be explained in more detail below with reference to embodiments shown in FIGS. 2 to 4.

FIG. 2 is a system configuration diagram of a system to which the present invention is applied.

FIG. 2 (al shows an example of the configuration of a workstation.

In the figure, 10 is the workstation main body, 2
0 is an adapter. 11 is a device driver.

40 is a magnetic disk device, 50 is a printer, and 60 is a display device.

FIG. 2(b) shows an example of the configuration of the controller.

In the figure, 10 is a controller main body, and 20 is an adapter.

11 is a device driver.

40, 50, and 60 are the same as in (a) (respectively a magnetic disk device, a printer, and a display device).

00 is the host computer.

1.00 is a workstation (WS) under the control of the controller 10.

FIG. 3 is a block diagram showing the configuration of an embodiment of the present invention.

In the figure, 1 is a main body such as a workstation and a controller.

2 is an existing standard adapter.

11 is a device driver to be tested.

12 is a test tool for testing the device driver 11;

3 is a terminal through which an operator registers interrupt data for the device driver 11 to be tested in the test tool 12;

The operation of this embodiment will be explained below.

(2) Using the terminal 3, the operator creates interrupt data for the device driver under test 11 and registers it in the test tool 12.

(2) The operator starts the test tool 12 and requests an interrupt.

■Test tool 12 starts and command generation procedure 121
is NOP (No 0PERATION) to adapter 2.
) command (a command that does nothing).

■Adapter 2 raises a completion interrupt for the NOP command.

■The test tool 12 receives an interrupt from the adapter 2.
The interrupt data generation procedure 122 raises an interrupt to the device driver 11 to be tested and sends the interrupt data.

With the configuration of the first embodiment, the device driver 11 actually
Any interrupt of any adapter can be raised to the device driver under test at the operator's direction without the need for an adapter to be driven by the device.

FIG. 4 is a diagram showing an example of interrupt data in an embodiment of the present invention. The data and area that are set at the time of an interrupt from the adapter (device) are as shown below, and the interrupt data generation procedure emulates this.

FIG. 4 (Part 1) shows the area set at the time of an interrupt.

In the figure, ACR is an adapter control register, which is used to notify that the adapter has raised an interrupt. The DCB, DCW, and buffer are areas provided in the main memory, and the DCB (device control block) sets completion information from the device (identification of error or normality, error details, etc.). A DCW address is set for interrupt data using a buffer.

In the DCW (device command word), what is set at the time of an interrupt is the address of the buffer area linked from here. For example, read data from a magnetic disk is set in the buffer.

FIG. 4 (part 2) is a diagram showing an example of the contents of each area.

〔Effect of the invention〕

As explained above, according to the present invention, there is no need to install an input/output control adapter, so testing can be performed even when there is no input/output adapter or there is a failure, and since the operator can freely create interrupt data, it is possible to test the actual It becomes possible to easily generate and test events that are difficult to occur with adapters, and the practical effects thereof are extremely large.

[Brief explanation of the drawing]

Fig. 1 is a block diagram of the principle of the present invention, Fig. 2 is a system configuration diagram of a system to which the present invention is applied, Fig. 3 is a block diagram showing the operation of an embodiment of the present invention, and Fig. 4 is a block diagram of the present invention. FIG. 5 is a diagram showing an example of interrupt data in one embodiment of the present invention. FIG. 5 is a diagram showing a device driver testing mechanism according to a conventional example. In the drawing, ≦ 1.10 is the controller body, 2.20 is the input/output control adapter, 3 is the terminal, 11 is the device driver, 1
2 is a test tool, 121 is a command generation means, 1
22 is an interrupt data generating means, 40 is a magnetic disk device, 50 is a printer, 60 is a display device, 00 is a host computer, and 100 is a work station (WS). Principle block diagram of the present invention Figure 2 Figure 3 Software to be tested Adapter (a) Figure 4 showing an example of interrupt data in the present invention (Part 1) (1) ACR ( 2) DCB □ □Device Status' +3 Device iD3 (DE normal, error, etc.) 1 byte 1--N is (3) DC", V Sets the buffer address when using the buffer. (b) Book Figure 4 shows an example of separate data in Invention no Ichiji Tabisho 1. Figure 4 (Part 2) Figure 5 shows the history of a device driver that relies on speed control.

Claims (1)

[Claims] A test tool (12) for testing input/output control software (11) that drives an input/output control adapter (2) in a main body (1) of a workstation, controller, etc.
) includes a command generating means (121) that generates a command to start the input/output control adapter (2), and a command generating means (121) that generates interrupt data based on data set from the outside and generates the interrupt and the interrupt data at a timing instructed from the outside. It is equipped with an interrupt data generation means (122) that outputs interrupt data, and uses a standardly installed input/output control adapter (2) to generate arbitrary output data using arbitrarily set interrupt data for the input/output control software (11). A test control method for input/output control software, characterized in that the test is performed by generating a pseudo interrupt at the timing of the input/output control software.