JPH0784830A - Software test execution support system - Google Patents

Abstract

(57) [Summary] [Purpose] To avoid having to re-enter the test command string to test the rebuilt load module. [Structure] When the input command recognition unit 51 determines that a new execution mode command has been input from the keyboard 1, it accepts a test command input from the keyboard 1 thereafter and inputs it to the test execution unit 53. The test of the load module specified by the test command is executed according to the option specification of the command, and the command is recorded in the execution command recording file 41.
When the input command recognition unit 51 determines that the re-execution mode command is input from the keyboard 1,
This is notified to the test execution unit 53, and the load module is tested in accordance with the test command sequence recorded in the execution command recording file 41.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software test execution support system for supporting a load module to be tested by giving various test commands in a test phase of software development.

[0002]

2. Description of the Related Art Generally, in a test phase of software development, various test commands are given to a compiled and linked load module to perform a test (test / debug). In this test, it is necessary to give a test command for every possible case and to pass all parts of the source code.

For that purpose, various options (functions) are specified by a test command when the load module is activated, and various test data are required.

The test is repeated each time the source code is modified, the source code is recompiled, and the load module is recreated. At this time, it is necessary to check not only the test corresponding to the modified part but also the test performed previously to check whether the modified part has the influence.

Therefore, conventionally, every time the load module is recreated, the software developer inputs the test command sequence again from the outside in order to perform the previously performed test again.

[0006]

As described above, in the past, every time the source code was modified and the load module was recreated, the software developer again executed the test command string in order to re-execute the previously performed test. It was necessary to input from the outside.

The present invention has been made in view of the above circumstances, and an object thereof is to use a sequence of test commands once input for test execution of a load module for test re-execution, and to execute test re-execution. It is to provide a software test execution support system that eliminates the need to re-enter test command strings.

Another object of the present invention is to provide a software test execution support system capable of modifying and reusing a test command once used for test execution of a load module.

[0009]

According to the present invention, an execution command recording file for recording a series of test commands for testing a load module and a test command input from the outside when a test execution of the load module is executed. In the re-execution mode in which a command recording unit for sequentially recording in the command recording file is provided and the test is re-executed, the test commands are read from the execution command recording file in the recording order and the load module is tested using the command. It is characterized by that.

Further, according to the present invention, in the correction execution mode in which the test command is corrected and the test is re-executed, the list display means for displaying a list of columns of the test command recorded in the command recording file is displayed. Further comprising a test command correction means for correcting any test command in the list of test commands, and a means for writing back the corrected test command to the execution command recording file,
After completing a series of test command correction processing, read the test commands from the execution command recording file in the recording order,
Another feature is that the load module is tested using this command.

[0011]

In the above structure, the test commands once input for the test execution of the load module are recorded in the execution command recording file in the order of input. Then, when the previously performed test is performed again for the modified load module created by modifying the source code, compiling and linking again, the test command recorded in the execution command recording file is The data is read in the recording order, and the load module test is performed according to the command. Therefore, it is possible to perform a test on the modified load module without re-entering the same test command sequence that was input when the test was performed previously.

Further, in the above configuration, when the correction execution mode is designated, a list of columns of test commands recorded in the execution command recording file is displayed on the screen,
It is possible to correct any test command in the list on the screen by operating the keyboard or the like. This modified test command is written back to the execution command record file. Therefore, after a series of test command correction processing is completed, the test commands are read from the execution command recording file in the recording order and the load module is tested, so that the test command sequence is not recreated and the command sequence is not input again. However, the load module test can be performed according to the modified test command sequence.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is a block diagram showing the functional configuration of a computer that realizes a software test execution support system according to an embodiment of the present invention.

The computer shown in FIG. 1 has a well-known configuration such as a keyboard 1, a display device 2, a floppy disk device 3, a magnetic disk device 4 and a CPU 5.

The keyboard 1 is used for inputting various commands including character strings.

The display device 2 is used for displaying load module test results to a computer user (here, a software developer).

The floppy disk device 3 is used as an external memory or the like which gives test data necessary for the test execution of the load module.

The magnetic disk device 4 is a group of an execution command recording file 41 for recording a test command string used for the test execution of the load module, and a file (data file) of test data given from the floppy disk device 3. It is used as an external storage for storing (data file group) 42 and the like. The magnetic disk device 4 also stores a load module file (load module file) 43 to be tested. Here, it is assumed that the load module name of the load module in the file 43 is "test.ldm".

The CPU 5 has functional blocks of an input command recognition section 51, a file input section 52, a test execution section 53, an execution command recording section 54, a test command list display section 55, and a test command correction section 56.

The input command recognition unit 51 is the keyboard 1
When a command is input, the input command is discriminated and each functional block in the CPU 5 is controlled according to the discrimination result.

The commands applied in this embodiment include various test commands for executing a test of the load module, a file input command for designating input of a data file from the floppy disk device 3 to the magnetic disk device 4, There is an execution mode command that specifies the execution mode (execution mode) of the load module test. This run mode command is a new run mode command that specifies a new run mode for a new run of the test, a rerun mode command that specifies a rerun mode for running the test again, and a test command modified to test There are three types of correction execution mode commands that specify the correction execution mode for re-executing.

The file input section 52, in accordance with the file input command discrimination result by the input command recognition section 51,
Data (data file) is input from the floppy disk device 3 to the magnetic disk device 4.

The test execution unit 53 receives a test command or an execution command input from the keyboard 1 and passed from the input command recognition unit 51 according to the test execution mode set by the execution mode command discrimination result by the input command recognition unit 51. The load module test according to the test command recorded in the recording file 41 is executed.

The execution command recording section 54 records the test command input from the keyboard 1 and executed in the new execution mode in the execution command recording file 41.

The test command list display section 55 reads the test command sequence recorded in the execution command recording file 41 in the correction execution mode and displays it on the display device 2 as a test command list. The test command list display section 55 is used by the test command correction section 5
The test command modified by 6 is also written back to the execution command recording file 41.

The test command modification unit 56 modifies the test command specified by the user (software developer) in the test command list according to the user operation.

Next, the operation of the configuration of FIG. 1 will be described with reference to the flowchart of FIG.

The software developer uses the load module file 43 created on the magnetic disk device 4.
When a new test is to be executed for (load module in), first set the floppy disk storing the test data file (data file) used in the test in the floppy disk device 3 and A file input command for inputting the same data file to the magnetic disk device 4 is input from the keyboard 1.

The input command recognition unit 51 is the keyboard 1
When it is determined that the command input from the file input command is a file input command, the file input unit 52 is requested to input the data file specified by the command. As a result, the file input unit 52 causes the floppy disk device 3 to
A specified data file is read from (the floppy disk set in (1)) and stored in the magnetic disk device 4 as one data file of the data file group 42.

In this way, the magnetic disk device 4 has two data files f designated by the software developer.
It is assumed that 1 and f2 are input (stored).

Next, the software developer inputs an execution mode command for designating a new execution mode, that is, a new execution mode command from the keyboard 1.

The input command recognition unit 51 is the keyboard 1
The execution mode command input from is received (step S1), and the execution mode designated by the command is determined (step S2). In the case of the new execution mode command as in this example, the input command recognition unit 51 determines the new execution mode and waits for the input of the test command.

Here, when the software developer inputs a test command from the keyboard 1, the input command recognition unit 51 receives the command (step S3), and the test execution unit 53 tests the load module according to the command. It is performed (step S4).

The test command applied in this embodiment is
As shown in the format of FIG. 3A, a load module designation field 31 that designates a load module to be tested (by its module name), an option designation field 32 that represents a function, and a data file used for the test have their filenames. The data file designation field 33 is designated by.

FIGS. 3B and 3C show specific examples of this test command.

First, the test command TC1 shown in FIG.
Specifies the load module name "test.ldm" of the load module (sort program) for data sorting in the field 31, the file name "f1" of the data file to be sorted in the field 33, and the field 32 "-A" of the module name "t
est. According to the load module of "ldm", all lines of the data file having the file name "f1" are sorted and output.

Next, the test command TC2 shown in FIG.
Is the load module name "tes" of the load module (sort program) for data sorting in the field 31.
t. "ldm" is designated, the file name "f2" of the data file to be sorted is designated in the field 33, and the module name "t" is designated by "-f var" in the field 32.
est. According to the load module of "ldm", it is specified to sort and output only the lines including the variable specified by "var" in the data file of file name "f2".

Therefore, from the keyboard 1 to FIG.
Assuming that the test command TC1 shown in FIG. 2 is input, the test execution unit 53 loads the load module file 43 (specified by the load module specification field 31 of the test command TC1) stored in the load module file 43 on the magnetic disk device 4. Module name "test.ld
According to the load module of "m", (test command TC
The data file name in the data file group 42 (designated by the data file designation field 33 of 1) is f1.
Performs a test execution operation that sorts and outputs all the lines of the data file.

When the test execution unit 53 completes the test execution, the test execution unit 53 displays the result on the display unit 2 and passes the executed test command TC1 to the execution command recording unit 54 so that the test command TC1 can be transmitted. It is recorded in the execution command recording file 41 (step S5).

Next, the input command recognition unit 51 waits for the next key input. In this state, if it is assumed that the test command TC2 shown in FIG. 3C is input instead of the command designating the end (step S6), the input command recognition unit 51 accepts the command TC2 (step S6).
3), the test command T to the test execution unit 53
The load module is tested according to C2 (step S4).

As a result, according to the load module having the load module name "test.ldm" specified in the load module specification field 31 of the test command TC2, the data file name f2 specified in the data file specification field 33 of the command TC2 is changed. In the data file, a test execution is performed in which only the lines including the variable designated by "var" are sorted and output. The test command TC2 designating this test execution is executed by the execution command recording unit 54 by the execution command recording file 41.
It is recorded at a position subsequent to the test command TC1 in the above (step S5).

Here, assuming that a command indicating termination is input from the keyboard 1, the input command recognition unit 5
1 determines the end of a series of test executions in the new execution mode (step S6).

Next, according to the result of the test for the load module in the above new execution mode, the corresponding source code is modified, and compile / link is performed again to recreate the load module with the load module name "test.ldm". I shall.

In this case, the program developer issues an execution mode command designating a re-execution mode, that is, a re-execution mode command, to the re-created load module in order to perform the same test as that performed previously. Input from the keyboard 1.

Then, the input command recognition unit 51 receives the execution mode command input from the keyboard 1 (step S1), and in the case of the re-execution mode command as in this example, determines the re-execution mode ( Step S
2).

When the input command recognition unit 51 determines the re-execution mode, the input command recognition unit 51 notifies the test execution unit 53 of the fact and activates the test execution unit 53.

As a result, the test execution unit 53 first starts from the execution command recording file 41 to the first test command,
That is, the test command TC1 is fetched (step S7).
Next, the test execution unit 53 follows the load module (load module in the load module file 43) of the load module name “test.ldm” specified by the load module specification field 31 of the test command TC1 (test command TC1 A test execution operation of sorting and outputting all the lines of the data file having the data file name f1 in the data file group 42 (specified by the data file specification field 33) is performed (step S8).

Upon completion of step S8, the test execution section 53 checks whether or not there is a next unexecuted test command (of the previously executed test command TC1) in the execution command recording file 41 (step S9). . Here, an unexecuted test command TC2 exists at a position subsequent to the test command TC1.

In this case, the test execution section 53 takes out the test command TC2 (step S10), and the load module name "test.ldm" designated by the load module designation field 31 of the command TC2.
According to the load module (load module in the load module file 43) of (test command TC1
Of the data file group 42 designated by the data file designation field 33 of
The test execution operation is performed to sort and output only the lines including the variable designated by "var" in the data file (step S8).

As described above, in the re-execution mode, according to the test command string (TC1, TC2) used in the new execution mode and recorded in the execution command recording file 41,
The rebuilt load module is automatically tested the same way as it was done before the rebuild. Then, there is no unexecuted test command in the execution command recording file 41, and the series of test executions in the re-execution mode ends.

Next, a description will be given of the correction execution in which the contents of the test performed previously are partially changed and re-executed.

First, the program developer changes the combination of the option and the data file, for example, with respect to the test command string that defines the test contents executed before.
When it is desired to execute the test of the load module again after correcting the test command, an execution mode command for designating the correction execution mode, that is, the correction execution mode command is input from the keyboard 1.

Then, the input command recognition unit 51 receives the execution mode command input from the keyboard 1 (step S1), and in the case of the correction execution mode command as in this example, determines the correction execution mode ( Step S2).

When the input command recognition unit 51 determines the correction execution mode, it first activates the test command list display unit 55.

As a result, the test command list display section 55
Reads out the test command sequence recorded in the execution command recording file 41 and displays it on the display device 2 as a list of test commands (step S11).

The software developer designates a test command that needs to be corrected on the test command list displayed on the display device 2 and corrects the test command in the same manner as in normal document editing. Is operated using the keyboard 1.

When the input command recognition section 51 receives a key input for modifying the test command (step S
12), The test command correction unit 56 is activated. As a result, the test command modification unit 56 modifies the designated test command on the test command list displayed on the display device 2 by the test command list display unit 55 according to the key input operation of the software developer (step S13). The result of this modification is reflected in the test command list by the test command list display unit 55.

The above steps S12 and S13 are carried out each time a key input for modifying the test command is made.

When a command indicating the end is input from the keyboard 1 eventually, the input command recognition unit 51 determines the end of the series of test command corrections (step S1).
4) Notify the test command list display section 55 to that effect.

Then, the test command list display section 55 displays
The modified test command list (test command sequence) is written back to the execution command recording file 41 (step S
15) Then, the test execution unit 53 is activated.

When the test execution section 53 is activated by the test command list display section 55, the test commands are sequentially fetched from the execution command recording file 41 in the same manner as in the re-execution mode, and according to the load module designated by the command. , Performs a test execution of the option process specified by the command, targeting the data file specified by the command.

In the above-described embodiment, the case where the number of test target load module files 43 created on the magnetic disk device 4 is one has been described, but the present invention is not limited to this, and the files of a plurality of load modules are used. The same can be applied to the case. However, when recording the test command sequence in the execution command recording file 41, it is necessary to associate it with the load module name, for example. In addition, it is necessary to specify the load module name of the target load module in the re-execution mode command and the correction execution mode command.

[0063]

As described above in detail, according to the present invention,
The test command input from the outside at the time of testing the load module is recorded in the sequential execution command recording file, and in the re-execution mode, the test commands used previously are read from the same file in the order of recording to test the load module. Therefore, it is possible to automatically perform the same test as before on the rebuilt load module without inputting the test command sequence again.

Further, according to the present invention, in the correction execution mode, a list of test command columns recorded in the execution command recording file is displayed on the screen, and any test command in the list can be corrected by the user operation. According to the configuration, after the test command modified and accepted is written back to the execution command record file, the test commands used previously are read from the file in the recording order to test the load module. When performing a test with a partial change, it is not necessary to newly create and input a test command string corresponding to the changed test content.

[Brief description of drawings]

FIG. 1 is a block diagram showing a functional configuration of a computer that realizes a software test execution support system according to an embodiment of the present invention.

FIG. 2 is a flowchart showing a processing procedure of a load module test in the embodiment.

FIG. 3 is a diagram showing a format and a specific example of a test command applied in the embodiment.

[Explanation of symbols]

1 ... Keyboard, 2 ... Display device, 3 ... Floppy disk device, 4 ... Magnetic disk device, 5 ... CPU,
41 ... Execution command recording file, 42 ... Data file group, 43 ... Load module file, 51 ... Input command recognition section, 52 ... File input section, 53 ... Test execution section, 54 ... Execution command recording section, 55 ... Test command list Display unit, 56 ... Test command correction unit.

Claims (2)

[Claims] 1. In the test phase of software development,
A software test execution support system for supporting various test commands by giving various test commands to a load module to be tested, wherein an execution command recording file for recording a sequence of the test commands and the test A command recording means for sequentially recording a test command input from the outside when the test is actually executed in the execution command recording file, and in a re-execution mode for re-executing the test, the execution command recording file is read from the execution command recording file. A software test execution support system characterized in that the test commands are read in a recording order and the load module is tested using the commands. 2. A list for displaying a list of the test commands recorded in the command recording file in a correction execution mode in which the test command recorded in the command recording file is modified and the test is re-executed. Display means, a test command correction means for correcting any test command in the list of test commands displayed by the list display means, and a test command corrected by the test command correction means in the execution command recording file. Write-back means is further provided, and in the correction execution mode, after completion of a series of test command correction processing by the test command correction means,
2. The load module is tested by reading the test commands from the execution command recording file in the order of recording and using the command.
Software test execution support system described.