JPH06250883A - Method for preparing test command - Google Patents

Abstract

PURPOSE:To lighten manhour for a test by generating a test data editing window relating to a specific data item in a program to be tested and generating test data and a test command for a debugging tool. CONSTITUTION:A menu of a program name 201 is selected from a file menu on a program display window 205 and a program to be test object is read in a displayed window 202. After designating an extraction option to the read program, a remarkable data item in the program and its high-order data item are inversely displayed, an instruction sentence for using these items is extracted from the program and displayed on the display window 202 as a table. After editing the test data and setting up an interruption point, a test command for a test debugging tool use is generated. Since an important spot for the test can be specified and test data for efficiently testing the specified spot can easily be prepared, the manhour of the test can be lightened.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a support method for creating a test command when a test data and a test debugger are used in the unit test stage of a program in software development, and particularly, an instruction to use a focused data item. And a test command generation method by extracting related data items.

[0002]

2. Description of the Related Art Conventionally, in the case of performing a unit test of a program in software development, for example, as a method of test debugging, a human being first determines which item in the program and which item is to be checked, and then the program under test. Human beings chased the source with their eyes and checked the place and items. On the other hand, regarding the test command generation function, for example, a test command generation method for test debugging is used as a manual by each company. In one of the test command automatic generation methods, a breakpoint is set at the entry / exit of the subroutine and the IF statement, or data items are set at the entry / exit of the file and arguments, and the test items are set at the time of interruption. The test commands were edited by referencing subroutines and files in the data items.
In this case, the breakpoints, data item settings, and file references are limited to the input / output parts and arguments of subroutines and files. There is a problem that it is necessary to edit, and since it is done manually by a human, an error due to manual work is likely to occur. Further, there is a support tool for supporting the creation of test data, and this support tool creates a test data creation screen based on the record specifications. However, even with this tool, humans were required to judge the setting location of the test data.

[0003]

As described above, in the conventional test debugging method, the human being has confirmed the contents of the program and the information about the passing of the data. In addition, although there was a test data creation support tool, since the entire record was created, humans had to determine which data item needed to be edited. . Further, in the test command generation function of the conventional test debugger tool, since the automatically generated break point information is limited to the IF statement, it may be necessary to set an unnecessary break point or a new setting. It was A first object of the present invention is to solve these conventional problems, to eliminate the need for a human hand, and to easily specify a test priority point and test data for efficiently testing the specified point. It is to provide a test command creation method that can be created in. A second object of the present invention is to provide a test command creating method capable of automatically creating a test command for a test debug tool and reducing the number of test steps.

[0004]

In order to achieve the above object, a test command creating method according to the present invention comprises: (a) designating a program to be tested and reading the program;
By designating a data item by paying attention to a specific data item in the program under test, a test data edit window for the data item is generated, and the data item and Instructions that use related data items are extracted, test data is created using the data items, and test commands for the test debug tool are automatically generated from the information displayed in the program under test and the window. It is characterized by generating. Also,
(B) When specifying related data items, select "Extract option" from the option menu of the program display window where the program under test is loaded to display the extract option window, then select "Reference data" from the window. It is also characterized in that either or both of "data item" and "data item in branch instruction" are selected. (C) To automatically generate a test command, select "Test command" generation from the File menu of the program display window, set the command to specify the test target program, and then specify the data specified in the test data editor. Values are set as test data, break points are set, and each break point is given a test command that refers to the values of the data item of interest and related data items. It is also characterized by setting an execution command.

[0005]

In the present invention, attention is paid to specific data in the source program, and data items and instructions related to the data item are extracted to specify the test location and its Create test data for efficient testing of locations. That is, by paying attention to the specific data in the program source list or the graphic editor, the instruction using the data item and its upper data item is extracted in a separate window, and at the same time, the focused data is extracted. Items, their upper-level data items, and related data items are each tested.
By extracting the data in a window for editing data, the test location and test items are specified to support the creation of appropriate test data. Then, a test command of the test debug tool is generated from the created test data and the extracted instruction information. As described above, according to the present invention, the instructions that use the data items and the instructions that use the other data items used for those instructions are extracted, and these data items are set to the upper data. Extract the test data including the item name into the test data editing window. As a result, the instruction in which the data item is used can be referred to, and the necessary test data can be easily edited. In addition, by extracting the instruction using the focused data item or the related data item,
You can determine valid breakpoints during test debugging. Furthermore, since the test command for the test debugger is automatically generated from the set test data and break point,
The test and its preparatory work can be reduced.

[0006]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a flowchart of a test command creating method showing an embodiment of the present invention. First, a program to be tested is designated (step 101). Next, the program to be tested is loaded into the window (step 102). Next, the extraction option for the program read in the window is set (step 103). After designating the extraction option, attention is paid to the data item in the program (step 104). Next, the noticed data item and its upper data item are highlighted so that the test data can be easily set, and the command statement that uses the noticed data item and its upper data item is displayed. It is extracted from the program and displayed as a list in the display window (step 105). It is judged whether or not the related data item is to be extracted (step 106), and if it is necessary to extract it, the reference data item is also extracted similarly to the focused data item (step 107). . Edit test data (step 108) and set break point (step 10)
After 9), if there is a further data item to be focused on (step 110), steps 103 to 109 are repeated. Next, an instruction for generating a test command for the test debug tool is given (step 1
11). A test command is generated by selecting the test command generation from the file menu (step 112). When it is necessary to create another test command (step 113), the process returns to step 102 and the same processing is repeated.

FIG. 2 is a diagram showing an example of program name designation in the present invention. In FIG. 1, when a program to be tested is designated (step 101), a program display window as shown in FIG. 2 is displayed. When designating a program, if the menu of “program name” 201 is selected from the file menu of the “program display window” 205 for reading the program, a window 202 for designating the program name is displayed. In the designation field 203 of this window 202, for example, the program name "/ users / test / SAMPLE1"
By inputting and selecting “OK” 204, the program to be tested is loaded into this window. By moving the mouse to the file (F) in the window 202, all the read file menus are displayed, and one of them can be selected. Also, by moving the mouse to option (O), all the option menus that can be extracted are displayed, and one of them can be selected.
In Option (O), the "Extraction Option" window for determining the extraction target is selected by selecting "Extraction Option" as a menu. Select the extraction option in that window. Multiple items can be specified at the same time (select with the square button on the left). FIG. 3 is a diagram showing an example of a program display window according to the present invention. FIG. 3 shows an example in which the program is loaded in the program display window 301. Here, the program is displayed in the form of a graphic editor, but it is also possible to display it directly in the program source.

FIG. 4 is a diagram showing an example of designation of extraction options in the present invention. FIG. 4 shows an example of setting the extraction option for the program read in the program display window. Here, whether or not to extract the related data item in addition to the focused data item is designated. Related data items include "reference data item" and "data item in branch instruction". When the "extraction option" 401 is designated from the option menu of the program display window, the "extraction option" window 402 is displayed. As the "reference data item use instruction" 403 and the "branch instruction" 404 are displayed as options, the selection button of the one to be extracted is selected, and "execute" 405 is selected. Here, the "reference data item" is a data item referred to by the focused data item in the program, and by specifying this option, the reference data item Also performs the same extraction work as the focused data item. Also, "branch instruction"
The option 404 is to extract the data item used by the branch instruction and the branch condition when the instruction focused on the data item is dependent on the branch instruction (Fig. 1 step 107).

FIG. 5 is a diagram showing an example of focusing on data items according to the present invention, FIG. 6 is a diagram showing a display example of a test data editor according to the present invention, and FIG. 7 is the same as the program source. It is a figure which shows the example of a display of an extraction window.
In the flow chart of FIG. 1, after the extraction option is designated (step 103), the data item in the program is focused and designated (step 104). In this case, as shown in FIG. 5, the data item 501 of interest is designated by the mouse, and "extract" 502 in the file menu is selected to select "test data editor" (see FIG. 6) and "program". Source extraction window ”(see FIG. 7) is generated and displayed. In this embodiment, since both the "reference data item use instruction" and the "branch instruction" are specified as the extraction options, the "test data editor" window (Fig. 6) is generated and displayed, and related instructions are extracted in the “Data item use instruction list” window (FIG. 7). The "test data editor" window shown in FIG. 6 has an item level number 601, a data item name 602, an attribute 603, and a data length 6.
04, each field of the data value 605 which is a test data edit area. Reference numerals 601 to 604 are parts generated from the data definition which constitutes the test target program,
Reference numeral 605 is an area for setting an appropriate data value with reference to the "data item use instruction list" (FIG. 7). When a value is set here (step 108 in FIG. 1), a test command for data value setting is generated at the time of generating the test command (step 112 in FIG. 1). When the "branch instruction" is extracted, the data that satisfies the branch condition for the point of interest is
Data values are automatically set in the field 605 in FIG. Figure 7
Data item use command list ”window, from the left, the breakpoint release button 701, the line number 702 of the extraction command, the extraction command 70
3 and the section / label name 7 to which the extraction instruction belongs
04 areas.

As is apparent from the flow chart of FIG. 1, in this embodiment, the extraction target can be selected by the option, so that it is possible to flexibly deal with the test. Especially, if no option is specified, the data
By focusing on the data item, a multi-window of "test data editor" as shown in FIG. 6 is generated and displayed from the data definition in which the focused data item is defined. In FIG. 6, the data item of interest and its upper data item are highlighted so that the test data can be set easily, and the command data item using the data item of interest and its upper data item is displayed. Are extracted from the program and displayed in a list in the "data item use command list" display window as shown in FIG. 7 (see step 105 in FIG. 1). Also, refer to
Data item use instruction ”option is specified,
As shown in, the "test data editor" is created from the data definition for the reference data item in a window separate from the data item of interest, and the reference data item and its upper data items are highlighted. To do. In addition, the instructions for using the reference data item are extracted together with the instruction for using the focused data item, and the list is displayed. When the "branch instruction" option is specified, a "test data editor" is generated for the data item used as the branch condition from the branch instruction for the point of interest, and the data item and upper data item are set. In addition to being highlighted, the data value that matches the branching condition for the point of interest is automatically set in the "test data editor" (Fig. 6).
reference). In addition, the line of the branch instruction / branch condition is focused on
Data items are extracted together with the data item usage instruction and displayed in a list. The above is the extraction result when the option is specified in the "extraction option" window. These three types of option contents can be designated redundantly.

In this embodiment, both the focused data item and the related data item are highlighted, but it is also possible to display only the extracted data item. Also,
In this embodiment, the set test data is used for the test command, but it is also possible to output it to a file and use it as an input file for the test. The instruction group extracted in the "Data item used instruction list" window of FIG. 7 is the target of the interruption point of the test debug tool. 70
1 is picked when the setting of this interruption point is unnecessary (step 109 in FIG. 1). When this cancellation designation is not made, all the extracted instructions are set as the interruption points. After the test data editing (step 108) and the unnecessary break point cancellation (step 109) in FIG. 1 are performed, if there is a further data item to be focused on (step 1
10), the processes of steps 103 to 109 are repeated. After the extraction process of steps 103-109 is completed,
An instruction for generating a test command for the test debug tool is given (step 111). FIG. 8 is a diagram showing an operation example of test command generation in the present invention, and FIG. 9 is a diagram of a screen on which the test command is similarly generated. The test command is generated by selecting "test command generation" 801 from the file menu of the "program display window" as shown in FIG. 8 (step 112 in FIG. 1).

FIG. 9 shows an example of the generated test command. First, a command designating a test target program is set (901) (for example, as SAMPLE1, simulation of the main program and setting of reception data).
Next, the data specified in the "test data editor" of FIG.
The data value is set as test data (902) (A2 = 1, A
3 = SPACE, ...). Next, an interruption point is set just before the instruction and the section name for which the interruption point cancellation is not designated in the “data item use instruction list” in FIG. 7 (903). Break point (903-905
At the interruption point), a test command that refers to the value of the focused data item or the related data item is added (904), and a re-execution command up to the next interruption point is set (905).
If the test command generated by the above procedure is used for the test debug tool, it is possible to save labor in a series of test processes.

As described above, in this embodiment, by paying attention to a specific data item in the program, a test data editor window for the data item is generated, and the data item is selected from the program. Extract the instructions that use. As a result, when the test of the program is carried out, by focusing on the data item of the portion to be tested, the related instruction, the focused data item and the data items above it are used. The command can be comprehensively grasped. Therefore, if these are taken into consideration, the test data for performing the efficient test can be easily created. When using the test debug tool for testing, the test command for the test debugger is automatically generated from the extracted instructions and the test data edited in the test data editor to create a test command. Since the man-hours can be significantly reduced, the automation of the test can be greatly promoted. Furthermore, when extracting data item use instructions and generating a test data editor window, when paying attention to a data item, the related data item and branching conditions reaching the point of interest are also targeted. Therefore, it is possible to flexibly respond to the test.

[0014]

As described above, according to the present invention,
It becomes possible to easily specify the test priority point and easily create the test data for efficiently testing the specified point without requiring human hands. Moreover, since a test command for the test debug tool can be automatically created, it is possible to reduce the number of test steps.

[Brief description of drawings]

FIG. 1 is a processing flowchart of a test command creating method according to an embodiment of the present invention.

FIG. 2 is a diagram of a display screen showing an example of program name designation in the present invention.

FIG. 3 is a diagram of a display screen showing an example of a program display window in the present invention.

FIG. 4 is a diagram of a display screen showing an example of specifying an extraction option according to the present invention.

FIG. 5 is a diagram of a display screen showing an example of focusing on data items according to the present invention.

FIG. 6 is a screen view showing a display example of a test data editor according to the present invention.

FIG. 7 is a diagram showing a display screen of a program source extraction window according to the present invention.

FIG. 8 is a diagram showing an operation example of test command generation in the present invention.

FIG. 9 is a diagram of a display screen showing an example of test command generation according to the present invention.

[Explanation of symbols]

 201 Program name specification field 202 Program name specification window 203 Program name specification field 204 OK button 301 Program display window 401 Extraction option setting menu 402 Extraction option setting window 403 Reference data item used instruction extraction specification button 404 Branch instruction extraction specification button 405 Execution button 501 Target data item specification 502 Extraction menu 601 Level number column 602 Data item name column 603 Attribute column 604 Data length column 605 Test data edit column 701 Break point setting release button 702 Line number column 703 Extraction and use instruction display column 704 Section / label name column 801 Test command generation menu 901 Program name designation test command 902 Data value setting test command 903 Break point setting test command 04 de - data item value Display test command 905 execution start test command

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Saori Kawasaki 3-16 Omorikita, Ota-ku, Tokyo Inside Hitachi System Engineering Co., Ltd. Hitachi Software Engineering Stock Association In-house

Claims (3)

[Claims] 1. A program to be tested is specified, the program is read, and then the data item is specified by paying attention to a specific data item in the program to be tested. A test data edit window relating to a data item is generated, an instruction using the data item and the related data item is extracted from the program under test, and the test data is extracted using the data item. A method of creating a test command, characterized in that a test command for a test debug tool is automatically generated from the program under test and the information displayed in the window. 2. The test command creating method according to claim 1, wherein when the related data items are designated, "extract option" is designated from an option menu of a program display window in which the program under test is read. A method of creating a test command, characterized in that the extraction option window is displayed, and either or both of the "reference data item" and the "data item in the branch instruction" are selected from the window. 3. The test command creating method according to claim 1, wherein the test command is automatically generated,
Select "Test command" generation from the File menu of the program display window, set the command to specify the program to be tested, set the data value specified in the test data editor as test data, and set the break point. Then, at each interruption point, the focused data item and the related data are
A test command creation method characterized by adding a test command that references the value of a data item and setting a re-execution command up to the next interruption point.