JPH09330248A - Event test system for gui control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten the time required for the program test of a graphical user interface(GUI) control program and to provide test comprehension for test items to be automatically generated by automatically outputting the test items and test program of events provided for GUI parts. SOLUTION: The events provided in GUI components are inputted 20, the components for a screen are stuck 21 and the discrimination conditions of events are inputted 22 at a main storage device 1 so that an event table 30, picture file 31 and discrimination condition file 32 can be outputted through respective processes 10-12. The test items are prepared 13 while using these files, a test item file is outputted 33, and a test program file 34 is automatically generated by test program preparing processing 14.

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD The present invention relates to a GUI (Graphical).
User Interface) control program,
It is for creating a dialog screen, and is composed of GUI parts such as menus and buttons, and an event for notifying that the operation has occurred when the GUI part is operated by an input device such as a mouse or a keyboard. ing.

[0002] The present invention relates to automatic generation of test items and test programs that do not depend on the processing method of the GUI control program in the event test of the GUI control program.

[0003]

2. Description of the Related Art An event of a GUI control program is an input operation (press, enter a value, etc.) for the GUI component.
This is information generated in association with the above, and each GUI component holds a plurality of events.

Various processes can be performed by combining individual events of these GUI parts. When creating test items, test programs, executing programs, and confirming events for this GUI component,
It is necessary to artificially create test items that consider the positional relationship of individual parts and the combination of events, and create a test program based on the test items.

Further, in order to confirm the execution result, it is necessary to make an input from an input device such as a mouse or a keyboard and visually confirm it in accordance with the judgment criteria of the test item.

Test items artificially created in this way,
In the case of the test method by the test program, there is a possibility that combination item omission may occur, and the possibility increases remarkably as the number of GUI parts and events increases. Further, in the confirmation operation, there are drawbacks in input operation / visual confirmation such as an input error from the input device and a result confirmation error.

The second and subsequent executions of the test program executed once can be compared with the previous execution history, and this method is generally known.

[0008]

In the above-mentioned conventional test method, it is necessary to artificially set the test item and the test program for the event of each GUI component in units of GUI components.

Further, it is necessary to predefine the execution order of the created test items and test programs, execute them according to the definitions, and confirm the execution results.

In general GUI parts, since the contents of the event are limited, test items for individual parts,
Although it is possible to create a test program, it is very difficult to create a test item and a test program that consider the combination of parts.

Furthermore, if a system-specific component, an event that the component has, and the like are combined in addition to general GUI components, the number of combinations of test items becomes enormous, and it is artificially created to create a test program. It is impossible to confirm the execution.

According to the present invention, by automatically outputting the test items and the test program of the event that the GUI part has,
The purpose is to reduce the time required for the program test of the GUI control program and to make the test items automatically generated have test coverage.

[0013]

According to the present invention, in order to achieve the above object, by inputting an event name of an event possessed by each GUI component and an output data type of the event in an event test of a GUI control program. , When the event of the relevant part is registered in the event table, the event registration process, the screen layout creation process that sets the screen configuration of the test program and the placement of the parts, and the judgment condition file is created from the created screen and the judgment condition of the event. It is provided with a judgment condition setting process for outputting, a test item creating process for automatically generating a test item from a configured screen and a judgment condition file, a judgment condition file, and a test program generating process for automatically generating a test program from an event table.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described with reference to the drawings.

FIG. 1 is a system configuration diagram of the present invention.
Stores a main storage device, 10 event registration process, 11 screen layout creation process, 12 determination condition setting process, 13 test item creation process, and 14 test program creation process.

Reference numeral 20 is an event input device for inputting event information, 21 is a parts pasting device for sticking parts on the screen to determine the screen layout, and 22 is a judgment condition input device for inputting judgment conditions of the input event.

Reference numeral 30 is an event table for storing the input event information, 31 is a screen file for storing the created screen, 32 is a judgment condition file for storing the judgment conditions for the event, and 33 is a created test item. A test item file, 34 is a test program file that stores a test program created from an event table and a judgment condition file.

FIG. 2 shows an example of a data file in which the correspondence between the input GUI part name and the event name corresponding to the part is stored in the event table by the event registration process. The events of the registered parts are stored in a matrix table format.

FIG. 3 shows an example of a data file in which the correspondence of the type of data output by executing the event of the input GUI part is stored in the event table by the event registration process.

The data files shown in FIGS. 2 and 3 are stored in the event table.

FIG. 4 shows an example of a judgment condition file in which the judgment conditions of the event to be confirmed in the parts attached to the screen created in the screen layout creation process are set and stored in the judgment condition setting process.

FIG. 5 is an event registration process, FIG. 6 is a screen layout creation process, FIG. 7 is a judgment condition setting process, FIG. 8 is a test item creation process, and FIG. 9 is a test program creation process. , 20
0-212, 300-307, 400-408, 500
Reference numerals 510 to 510 show respective processing steps in the respective flowcharts.

FIG. 10 shows an example of the generated test items and test program.

The operation of the embodiment of the present invention will be described below with reference to the drawings.

The event registration process will be described with reference to FIGS. 1 and 5.

First, the event registration process on the main storage device (1) shown in FIG. 1 is started, and each of the component group name, the component name, the event name, and the output data type at the time of event execution to which the newly registered event belongs. Give parameters. At this time, if there is no component or event to be newly added, this process is skipped and the process proceeds to the screen layout creation process (11).

In the activated event registration process,
As shown in FIG. 5, individual parameters such as a part name and an event name are input (100), and when it is determined that the part to be registered and the content of the event are valid (103),
The duplication with the already registered parts and the contents of the event is determined (104). If it is determined that the part to be registered, the part that has already registered the event, and the part do not overlap with the event, enter the output data type of the event (10
6), the event table is updated (107), and the process ends.

The respective processes of 102 to 107 are repeated for the number of parts and events to be registered.

The screen layout creating process will be described with reference to FIGS. 1 and 6.

In order to create a screen as a test program, a screen creating process is started (200). Attach the parts to be tested on this screen (202-203),
This process is repeated the required number of times.

Select the attached parts (204 to 20)
By doing 5), the event table (30) created by the event registration process can be called (206).

In the event group in the event table corresponding to the part selected on the screen, the target event is selected (207 to 208), and this process is repeated for the required number of events.

When the selection of the event is completed, the created screen, parts and event information are output as an intermediate file.

When the event setting for each component on the screen is completed in the processing of 202 to 209 (20
1), a screen file is generated (211), the intermediate file is deleted at the end of the process (212), and the process ends.

The determination condition setting process will be described with reference to FIGS. 1 and 7.

When the screen layout creating process (11) is completed, the determination condition setting (12) is activated. The screen file created in the screen layout creating process (11) is read (300), and the determination condition setting screen in which this screen is imported is displayed (301).

On the displayed judgment condition setting screen, the component for which the judgment condition is set is selected (303), the judgment condition is set (304), and it is judged whether the set judgment condition is valid or not. (305). This 304 ~
The processing step 306 is repeated for the number of conditions to be set. When the setting of the judgment condition is completed for the component on the judgment condition setting screen, the judgment condition file is output (307) and the process is ended.

The test item creation process will be described with reference to FIGS. 1 and 8.

When the judgment condition setting process (12) is completed,
The test item creation process (13) is started. The determination condition file (32) created in the determination condition setting process is read (400), and the component name of each component is read from this file,
The event name, the output data type when the event is executed, the part position, and the determination condition are read (402 to 406).

When one record has been read, test items for the relevant parts are generated using the read items (4
07), and output the test item file (408).

This process is repeated up to the last record of the file (401), the test items for all records are output, and the process ends.

The test program creation process will be described with reference to FIGS. 1 and 9.

The judgment condition file created in the judgment condition setting process (12) is read (500), and the read judgment condition file is analyzed (501). Based on the analysis information of this judgment condition file, the corresponding parts and event information is read from the event table (50
2), the event information corresponding to the event set in each component is analyzed (503). When the analysis is completed, the number of parts on the screen is assigned to the loop counter (504),
Enter a loop that combines the information of each part.

The analysis information of the event table and the judgment condition file are combined (505), and an intermediate file is generated for each part (506). Repeat this for the number of parts attached to the screen. After generating the intermediate files for all parts, combine the intermediate files (50
After 8), a test program is generated (509), a test program file is output (510), and the process is terminated.

[0045]

As described above, according to the present invention, in the event test in the GUI control program, by visually defining the screen configuration and the test condition of the test program, the test items from the basic items to the combination items of the test, A test program can be generated automatically.

Also, 2 for the event registered once
Registration after the first time can be omitted, which has the effect of improving the test efficiency in event testing.

[Brief description of drawings]

FIG. 1 is a system configuration diagram of the present invention.

FIG. 2 is a diagram showing correspondence between GUI parts and events held by the parts.

FIG. 3 is a diagram showing a correspondence between an event of each component and an output data type when the event is executed.

FIG. 4 is a diagram showing correspondence between components to be tested, events, and determination conditions.

FIG. 5 is a flowchart of event registration processing.

FIG. 6 is a flowchart of a screen layout creation process.

FIG. 7 is a flowchart of determination condition setting processing.

FIG. 8 is a flowchart of a test item creation process.

FIG. 9 is a flowchart of a test program creation process.

FIG. 10 is an example of generated test items and a test program corresponding to the items.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Main memory device, 10 ... Event registration process, 11 ... Screen layout creation process, 12 ... Judgment condition setting process, 13 ... Test item creation process, 14 ... Test program creation process, 20 ... Event input,
21 ... Adhesion of parts, 22 ... Input of judgment conditions,
30 ... event table, 31 ... screen file,
32 ... Judgment condition file, 33 ... Test item file, 34 ... Test program file, 100-1
07 ... Processing, 200-212 ... Processing, 300-
307 ... Processing, 400-408 ... Processing, 500
~ 510 ... Processing.

Claims (1)

[Claims] Claims: 1. In the event test method of a GUI control program, a matrix table showing correspondence between GUI part names and event names of parts, event processing contents,
GUI based on the table showing the correspondence between the judgment conditions and the judgment values
An event test method for a GUI control program, comprising test items for events of parts and a test program generation process for automatically generating a test program.