JPH05233368A - External routine form component test tool - Google Patents

Abstract

PURPOSE:To shorten the time required for driver generation at the time of a component test and easily verify whether or not functions of components are sufficiently satisfactory on the same screen as an input screen by enabling a user to easily utilize the tool on a conversational basis according to a guide displayed on a terminal. CONSTITUTION:This tool is equipped with a component check device 2 which checks whether or not a component called from the screen is present in an executable state in a library having component information, a parameter input device 3 which inquires input parameters of an operator in order according to the component functions, a parameter check device 4 which makes an essential input item check on the input parameter data, a data check, etc., and a data editing device 5 which edits the input data.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an external routine type part test tool, and more particularly to a part test tool for passing input parameters by an interactive method on a screen and displaying output results for the input parameters on the screen.

[0002]

2. Description of the Related Art Conventionally, when testing an external routine type component, a driver (main routine for the component) had to be created for each component. Also, the results were output to a list and verified.

[0003]

In the above-described conventional component testing method, the driver has to be created for each individual component, and the time required for this is not small.

Further, it is not easy because it is necessary to output to a list and verify whether or not the function of the part is sufficiently satisfied.

[0005]

An external routine type part test tool of the present invention is a core part of the tool, which controls a start-up / control of another device and a presence check of a part called from a screen. The component check device to perform, the parameter input device to sequentially display the input parameter items on the screen according to the called part, the parameter check device to check whether or not the parameters are properly input, and the edit of the input data And a data editing device for performing.

[0006]

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

FIG. 1 is an explanatory view showing an embodiment of the present invention. In the figure, the external routine type component test tool of the present invention guides the operation of the tool to the terminal 1a in an interactive manner, inputs an instruction for the operation from the terminal 1a, and activates / controls another device. And a component check device 2 for checking whether or not the component called from the screen exists in the library having the component information in a test-executable state, and when the presence is confirmed by the component check device 2, the component Parameter input device 3 for sequentially inquiring the operator of input parameters according to function
And a parameter check device 4 for checking required input items of input parameter data, data check, and the like,
When it is confirmed by the parameter check device 4 that all the parameters have been normally input, the data check device 4 includes a data editing device 5 for editing the input data.

FIG. 2 is a flow chart showing the operation of the above external routine type component test tool.

First, in step 11, the terminal 1a
Input the command to start the tool from. Recognizing the command input, the control device 1 transmits to the terminal 1a a guide for allowing the user to input the name of the target external routine component program (hereinafter referred to as the member name). In step 12, the user inputs the target member name from the terminal 1a to this guide.

The control device which recognizes this signal activates the component checking device 2 and further transmits a signal to the component checking device 2. In step 13, whether or not the member exists in the library 1b in a test executable state. Check if the relevant member does not exist, or if it exists but is not in an executable state (a part has not been generated),
The terminal 1 via the control device 1 by the component check device 2
A is notified that the member does not exist in the library 1b, and the member name input guide is transmitted again. Here, the library 1b is a library in which component information is stored.

When it is confirmed by the component check in step 13 that the member can be tested, the relevant component information is stored in the control device 1 from the library 1b, and the control device 1 activates the parameter input device 3. The parameter input device 3 transmits a guide for inquiring the first parameter to the terminal 1a.

When the user inputs (or does not input) data to the terminal 1a in step 14, the control device 1 that recognizes this signal activates the parameter check device 4, and in step 15, the data signal is input to the control device 1. The data was transmitted to the parameter check device 4 via the check, and it was checked whether or not the data was input to the required input items and, if the data was input, whether or not the data was a normal value, and the check did not end normally. In this case, the parameter check device 4 returns an error message to the terminal 1a via the control device 1, and the parameter input device 3 again asks the terminal 1a via the control device 1 about the first parameter (the same parameter as the previous time). Send a guide to do.

When the check of the input parameter is normally completed in step 15, the input data is stored in the parameter check device 4, and in step 16, the parameter input device 3 confirms whether or not the second (next) parameter exists, When the existence of the second (next) parameter is confirmed, the parameter input device 3 further sends a guide for inquiring the second (next) parameter to the terminal 1a via the control device 1, and the user guides the user. Enter data according to.

Hereinafter, similarly, step 15 and step 16
Is processed. Second (next) in step 16
If the parameter does not exist, the process proceeds to step 17.

In step 17, the data editing device 5 is activated by the control device 1, and the data editing device 5 receives the data stored in the parameter checking device 4 via the control device 1 and the A part (function) is selected and the received parameter data is edited according to the function.

In step 18, when the value is normally obtained in step 17, the value is transmitted to the terminal 1a,
If the value is not normally obtained, an error message to that effect is transmitted to the terminal 1a, and the command is terminated.

[0017]

As described above, according to the present invention, the user can easily use the tool in a conversational manner according to the guide displayed on the terminal. It is possible to reduce the time, and it is possible to easily verify whether or not the functions of the parts are sufficiently satisfied on the same screen as the input screen.

[Brief description of drawings]

FIG. 1 is an explanatory view showing an embodiment of the present invention.

FIG. 2 is a flowchart showing an operation.

[Explanation of symbols]

 1 Control Device 2 Parts Checking Device 3 Parameter Input Device 4 Parameter Checking Device 5 Data Editing Device

Claims (1)

[Claims] 1. A control device for managing activation / control of another device as a core part of the tool, a component checking device for checking existence of a component called from a screen, and an input parameter item according to the called component. External routine format characterized by having a parameter input device for sequentially displaying the parameters on the screen, a parameter check device for checking whether or not those parameters have been input normally, and a data editing device for editing the input data. Parts test tool.