JPS62133539A - Execution controlling system for test program - Google Patents

Abstract

PURPOSE:To avoid an execution of a meaningless sub-test by making each sub-test itself have a function for generating a return code and determining the subsequent schedule, in a computer system. CONSTITUTION:When an execution managing part M starts a sub-test Ti, the sub-test Ti performs a test, and when it is ended, a result of execution is generated, and stores in a return code store area Ri. Subsequently, the execution managing part M checks the return code store area Ri and judges whether the subsequent sub-test Ti+1 can be executed or not. In case the subsequent sub-test Ti+1 cannot be executed, a schedule of the subsequent sub-test is suspended.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Application in Industry 1-] The present invention relates to a computer system, and particularly to a test program execution control method.

[Conventional technology]

The purpose of the test program is to test whether the functions of each device making up the computer system operate correctly. Since the functions of a device are divided into a plurality of smaller functions, a test program for this device typically consists of subtests that test these smaller functions.

Conventionally, the execution of these subtests has been controlled by a method in which when one subtest ends, control is automatically passed to the next subtest regardless of the test result.

[Problem that the invention seeks to solve]

The conventional execution control method described above has the disadvantage that when one subtest ends, control is automatically passed to the next subtest regardless of the test result, so a subtest that is meaningless to execute is activated. There is.

For example, assume that there are function A and function B, and subtest hA and subtest B are prepared correspondingly.

If function A and function B are functionally interrelated, an error detected by subtest A will also be detected by subtest I-B. The 1-1 objective of the test program is
Considering that the purpose of this test is to check whether the functions of the device under test η operate normally, the error messages output by subtest B cannot be said to be of interest to maintenance personnel.

[Means for solving problems]

The test program execution control method of the present invention determines whether the test result is normal or abnormal for each subtest that makes up the test program, and if it is abnormal, the error will affect subsequent subtests. The present invention is characterized in that it has a function of generating a return code indicating whether the subtest is affected, and the execution management unit of each subtest determines whether to schedule the next subtest depending on the content of the return code.

This avoids running meaningless subtests.

〔Example〕

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

FIG. 1 is an explanatory diagram of an embodiment of a test program execution control method according to the present invention.

The test program T has n subtests Ti (i=1.
2. ..., n), and a return code indicating whether the test result of each subtest TI is normal or abnormal, and if abnormal, whether the error affects subsequent subtests. A return code storage area J (i=1.2° . . . , n) in which the return code is stored is provided in the main memory. The execution management unit M controls the execution of these subtests TI. When each subtest T+ completes the test, it passes the test result R1 along with the control to the execution management section M.

The execution management unit M determines the schedule for subsequent subtests based on the content of the test results.

Figure ff5Z is a flowchart showing this control procedure.

The execution management unit M starts the subtest) T+ (step 10). This causes subtest TI to perform the test (step 5). When the test is completed, the subtest Ti generates an execution result and stores it in the return code storage area R (step 15). Next, the execution management unit M checks the contents of the return code storage area R1 (step 20) and determines whether the subsequent subtest 1" T1+1 is executable. If the subsequent subtest) T+++ is executable, then For example, increment i by 1 and schedule subtest TI (step 40). On the other hand, if the contents of the return code storage area R indicate that the subsequent subtest h TI++ cannot be executed, then subtests TI++, T
The schedule of I+z+... is moved up by one (step 50).

〔Effect of the invention〕

As explained above, the uninvented method is to provide each subtest that makes up the test program with a function to generate a test result, and to decide whether to schedule a subsequent subtest based on the content of the test result. , None, Q, I
This has the effect of avoiding the execution of unnecessary subtests.

[Brief explanation of drawings]

FIG. 1 is an explanatory diagram of an embodiment of the execution control system of the test programger 1 of the present invention, and FIG. 2 is a diagram showing the processing flow of the embodiment of FIG. 1. T...Test program, "I," 2+..., Tn...Subtest, R,,R
2,...+Rn...Return code storage area,
・Execution management department.

Claims (1)

[Claims] In a computer system, each subtest that makes up the test program checks whether the test results are normal or not.
A function is provided to generate a return code indicating whether the error is abnormal and, if so, whether the error will affect subsequent subtests. A method for controlling execution of a test program, characterized in that it is determined whether or not to schedule the next subtest.