JP2001356936A - Test support device and supporting method of gui system program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make a test of a screen program to use a graphic user interface automatic and efficient. SOLUTION: This test support device is provided with a means 2 to receive screen definition information of the screen program to be tested as input, to be a sub-class in relation of succession of object orientation to a class of the screen program to be tested and to generate a test support class to test the screen program and a means 3 to perform the test of the screen program to be tested by using the generated test support class.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program test method, and more particularly, to a GUI program test support device for realizing the efficiency and automation of a screen program test operation using a graphic user interface. And support methods.

[0002]

2. Description of the Related Art When performing a test on a screen program using a graphic user interface (GUI), it is necessary to create a test driver used for testing a general program. Was difficult and the testing was done mainly by the program creators manually. In general, there are test support tools that script keyboard (mouse) operations (character description), but such test support tools cannot be used because the position of the screen or the arrangement of parts on the screen changes. There were inconveniences.

In a unit test of a screen program,
Conventionally, test specifications are not often created and tested, and the screen program creator or the person in charge of unit testing often creates an appropriate pattern and tests the program. The problem remains. Also, when creating test specifications and performing tests, humans often refer to screen definitions visually to create specifications, for example, misunderstanding the maximum and minimum values, or creating test data. Mistakes could occur.

[0004] Even when data is input based on the specification at the time of execution of a test, there is always a possibility that an input error may occur when a human performs data input. If the input data does not remain, verification after the test execution cannot be performed. Furthermore, it is often difficult to determine whether the processing of the input data has passed through the normal processing on the screen program or has passed abnormal processing such as an error, and it is difficult to grasp the movement of the screen program during the test execution. Met.

[0005] Many screen programs have many input items, and even one input item has a wide range of change, so that the test pattern becomes very large, and it is difficult for a human to manually execute all the patterns. is there. Further, when the retest is performed, no input data remains for the previous test, and as a result, the same operation is repeated, resulting in inefficiency. With commercially available test support tools that record and script the operation of the mouse cursor and keyboard, if the screen position and the layout of screen components change, the tool cannot be used. Had a problem that it could not be used for retesting.

When measuring the execution performance of a program, such as the startup time of a screen or the response time when a button on the screen is pressed, a person in charge often measures the time using a stopwatch or the like. In addition, it is generally necessary to perform measurement a plurality of times and perform tallying, which increases the workload of the person in charge. It is not impossible to modify the screen program for the test and display the processing time, but it is necessary to restore the corrected part after the measurement is completed, and the program source must be changed after the test is completed. Due to mistakes in correction, the quality of the program after the test is completed remains uneasy. Further, in preparing a test report after the test is executed, there is a problem that a mistake may occur due to manual entry by a tester.

SUMMARY OF THE INVENTION The object of the present invention is to provide a G
To provide a test support device and a test support method for efficiently and automating a whole test operation of a screen program using a UI, and to provide a test specification, a test execution, and a test report in general. It is to solve various problems in three stages of the test operation.

[0008]

FIG. 1 is a block diagram showing the principle configuration of the present invention. FIG. 1 is a block diagram showing the principle configuration of a GUI program test support apparatus for supporting a screen program test using a graphic user interface (GUI).

In FIG. 1, a test support apparatus 1 includes a test support class generating means 2 and a test executing means 3.
The test support class generation means 2 is, for example, a test support class generation device, receives screen definition information of a test target program as input, and inherits object-oriented inheritance for the class (super class, parent class) of the test target screen program. Is a subclass (child class) in the relationship of (1), and generates a test support class for testing a screen program.

The test execution means 3 executes a test of the screen program to be tested using the test support class generated by the test support class generation means 2.

In the embodiment of the present invention, the test support device 1 further includes a test specification generation unit. The test specification generation means generates a test specification for the test target screen program from the screen definition information. In addition, the test support device 1 can further include a test report generation unit. The test report generation unit generates a test report using the test specification generated by the test specification generation unit and the test execution result of the test target screen program by the test execution unit 3.

In the embodiment of the present invention, the test support class has a function of supporting input of input test data, a function of recording a test result at the time of executing a test manually or automatically, and Provide a function to visually display the location of test execution on the screen, and a function to manually or automatically execute a test using new input test data or input data for the previous test execution result Can also. At this time, a function of displaying a warning when a test execution result using input data for the previous test execution result is different from the previous execution result may be provided. Further, the test support class may have a function of supporting measurement of the execution performance of the test target screen program.

In the GUI program test support method according to the present invention, as a method of supporting a screen program test using a graphic user interface, screen definition information is received as an input, and an object is defined for a class of a screen program to be tested. A method for generating a test support class for testing a screen program, which is a subclass (child class) in an orientation-oriented inheritance relationship, and executing a test of a test target screen program using the generated test support class Is used.

Further, as a computer-readable portable storage medium of the present invention, a storage medium used in a computer for supporting a test of a screen program using a graphic user interface receives screen definition information of a screen program to be tested. A program for causing a computer to execute a step and a step of generating a test support class for testing a screen program, which is a subclass in an object-oriented inheritance relationship with respect to the class of the screen program to be tested. Storage medium is used.

The computer-readable portable storage medium according to the present invention is a storage medium used in a computer for executing a screen program test using a graphic user interface. A step of receiving input data for the execution result, and using the received input data, a subclass in an object-oriented inheritance relationship with respect to the class of the test target screen program,
Using a test support class for testing a screen program, a storage medium storing a program for causing a computer to execute a step of executing a test of the test target screen program is used.

Further, as a program of the present invention, in a program used in a computer for supporting a test of a screen program using a graphic user interface, a procedure for receiving screen definition information of a screen program to be tested, A program for causing a computer to execute a procedure for generating a test support class for testing a screen program, which is a subclass in an object-oriented inheritance relationship with respect to a screen program class, is used.

Also, in the program used in the computer for executing the test of the screen program using the graphic user interface as the program according to the present invention, new input test data or input data for a previous test execution result is received. Using the procedure and the received input data, a subclass in an object-oriented inheritance relationship to the class of the screen program to be tested, using the test support class for testing the screen program, the screen to be tested A program for causing a computer to execute a procedure for executing a test of the program is used.

As described above, in the present invention, a test support class for testing a screen program, which is a subclass in an object-oriented inheritance relationship with respect to a class of a screen program to be tested, is generated, and the test is performed. The test of the test target screen program is executed using the support class.

[0019]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Regarding the basic concept of the present invention,
This will be described with reference to FIGS. FIG. 2 and FIG. 3 are explanatory diagrams of the use of a test support class that uses the concept of inheritance in object-oriented programming to execute a test of a screen program using a graphic user interface (GUI).

As shown in FIG. 2, the present invention does not use a conventional general-purpose support tool or generates a test driver to support the test execution work. The test of the test target screen program 10 is executed by using the target test support class 11 that has an inheritance relationship in the directional programming.

FIG. 3 is an explanatory diagram of the configuration of the test support class by extending the screen program. The test support class 11 is configured by extending the test target screen program 10 and adding a test support function.

In the embodiment of the present invention, a test specification is created, a test is executed using the test support class described above, and a test report for the result is generated. FIG. 4 is an explanatory diagram of test specification generation. In the figure, the test specification generating device 16
Test pattern and its input data file 17
Is generated, and the input data file is edited / imported to generate the test specification 18. As the test specification 18, the output of the test specification generation device 16 may be used as it is.

As a test pattern, a pattern expected to obtain a normal result and a test pattern expected to detect an abnormal result, that is, an error or the like are used. Format is generated, but in order to actually execute the test, the format must be specified as a file separated by commas for each data item.
It is necessary to convert the file into a V-format file and convert the file into a file format that can be read by a computer executing the test.

FIG. 5 is a conceptual illustration of test support class generation. A test support class, that is, a screen program to which a test support function is added as described in FIG. 3 is generated based on the definition of the screen program. That is, from the screen definition information 15, the test support class generation device 20
As a result, a test support class 21 is generated. The class name (parent class name) of the screen program 10 to be tested is described in the screen definition information 15, and a test support class 21 as a child class is generated by inheriting this class.

When a test is executed, the screen program 10 to be tested is also started by executing the generated test support class 21, and a screen with a test support function is displayed. The test support functions added to the screen program are the following six functions.

The first function is a function for supporting input of test patterns and input test data. By using this function, the test specification or the generated input data file is read, a list of input data is displayed corresponding to the input items on the screen, and the test operator can select any of those input data. Provide support so that you can select and enter.

The second function is a function of recording an execution result.
Date and time of test execution, test case number, input data,
This function allows you to record execution results and other information in a file.

The third function is a function for automatically executing a test. Using input data files based on test specifications or input data from previous test execution results,
This is a function that allows input data to be automatically and sequentially input to the screen program to be tested and records the execution results.

The fourth function is a function of comparing the result with the previous result when the test is re-executed. In the automatic execution function of the third function described above, when a test is automatically or manually executed using input data for a previous test execution result, if a result different from the previous execution result is obtained, a test operation is performed. This function allows a warning to be displayed to the user.

The fifth function is a visual representation function of a passage portion in the program processing at the time of test execution. In this function, the color of the control (part on the screen) corresponding to the passing point in the program processing on the screen is displayed when the normal processing is performed and when the error processing such as an error is performed. For example, this function is to change the display to blue and yellow so that the test operator can be notified of whether or not normal processing has been performed.

The sixth function is a function for supporting performance measurement during program execution. For example, it is a function of measuring a startup time of a screen, a response time when a button in the screen is pressed, and displaying or recording the result. In order to measure the time from when the program is started to when the screen is displayed, the time until the corresponding processing is completed when the button is pressed, etc., the measurement start / end processing of the time matched with the start / end of the processing is performed. In addition, it is a function that enables the performance of a program to be measured, and a function that displays the measurement results on a screen or saves it in a file.

When the test is completed, a test report is prepared. As shown in FIG. 6, a test report generation device 24 generates a test report 25 using the test specification 18 and the execution result information 23.

FIG. 7 is an overall configuration diagram of the test support apparatus. 4 is basically a summary of FIGS. 4 to 6, and further includes a screen class generation device 27 that generates a test target screen class 28 corresponding to a test target screen program from the screen definition information 15. ing. Since the generation of the screen class 28 from the screen definition information 15 has no direct relation to the present invention, the description is omitted.

In FIG. 7, the test support class 21 includes five devices corresponding to the above-described six functions, that is, a test data input device 31, a test data setting device 32, a test automatic execution device 33, a performance measurement support device 34, and A visual expression device 35 for the passage process is provided. The operation of these devices will be described later.

FIG. 8 is an explanatory diagram of a method of realizing a test support function using inheritance in object-oriented programming. In the figure, a test target screen class 28 is a class of a screen program that the worker wants to test, and is stored in a file different from the test support class 21.
, The actual screen program can be executed only by executing the class 28.

The test support class 21 (subclass) has a relationship of inheritance with the screen class (super class) to be tested, is inherited from the screen to be tested, and is extended with a test support function. The actual test of the test target screen program is performed using the test support class 21 that inherits the test target screen class 28. From the test operator, it looks as if the test target screen class 28 has been extended. The test support class 21 has functions such as the input support function, the automatic test execution function, the performance measurement support function, and the execution result recording function as the test support functions in addition to the function of the test target screen class 28. is there.

Although it appears that the test worker is testing the test support class 21, the processing when the button is depressed is performed by calling the processing of the test target screen class 28. Screen class 28
Test. By inheriting the test target screen class 28 in this way, it is not necessary to modify the test target screen class 28 itself, and the test of the test target screen program can be executed.
In the past, to execute a test, it was necessary to modify the test target screen program source itself.
According to the present invention, there is no need to modify the test target screen class 28, and even if there is a change in controls (parts) on the screen, there is no problem in executing the test. Conventionally, even if a test target screen class and a test support class are provided, these classes are completely different from each other, and the test support class only knows the test target screen class unilaterally.

Next, the operation of the test support apparatus of the present invention will be described with reference to FIGS. 9 to 15 using a specific example of screen presentation information. FIG. 9 is an explanatory diagram of test specification generation from the screen definition information. Here, the generation of a specification for testing the registration screen of the employee will be described. In the same figure, the variable name and the type for the six items from the employee number to the cancellation are defined in the upper left employee registration screen definition, and the number of digits for the four items from the employee number to the telephone number is defined. The ranges of employee numbers and postal codes are further defined, ie, minimum and maximum values.
From such an employee registration screen definition, an employee registration screen at the lower left is generated. The description of this is omitted as described above. In addition, by the test specification generating device 16,
An employee registration screen test specification is generated.

The test specifications include item-specific specifications,
A specification for each screen is generated. The item-by-item specification generally comprises a plurality of test cases for one item of the employee registration screen definition. For example, the test case for the item of the employee number is TEST-1001-01 to T
It consists of six test cases EST-1001-06. For example, the first test case also tests the minimum value, and the test data is “000000”.
This is a normal employee number for registration, and employee registration using this data should be executed correctly. In addition to such a normal test specification, for example, test data “−1” for the third test case is an abnormal test specification, and employee registration using such data should not be performed correctly. Things.

The test specification for each screen is a set of four items to be registered, that is, four items from the employee number to the telephone number, and is set as test data for one screen. For example, TEST-G001 The test source consists of the first four digits of the test specification. When there is an item omitted in the employee registration screen definition, for example, a test specification is generated based on an instruction from a user.

FIG. 10 is a diagram for explaining the operation of the test data providing device for embedding test data in the fields of the employee registration screen. The test data providing device basically includes a test data input device 31 and a test data setting device 32. The test data input device 31 reads test specifications and creates test data input information 40 in a format that can be read by the test data setting device 32. The test data setting device 32 reads the test data input information 40 and reads the input information. A pop-up menu is displayed on the screen based on the above, and a value selected by the test operator is embedded in an input field on the screen to execute an operation.

In FIG. 10, "000000" for the employee number is selected as the first test data, and is embedded in the employee number input field on the screen. As described above, as for the employee number, only the numeral is a normal value, the valid value is from 000000 to 999999, and other than the numeral, for example, an alphabetic character or Japanese is an abnormal value.
The normal value is, of course, correctly embedded in the input field, and the fact that the correct data is embedded, that is, the setting of the test data, is recorded in the execution result information 23 that records the test data and the test result thereof. .
The test operator can input test data only by operating the mouse, thereby reducing the number of test steps. Test data for which setting has been performed can be deleted one after another so that unset test data can be checked at a glance.

FIG. 11 is an explanatory diagram of a test data setting operation for each screen by the test data providing device. In the test data setting operation for each screen, a pop-up menu generally displays a plurality of test case names each including a plurality of test items.
Four test items for the test case of EST-G001, that is, four test data from the employee number to the telephone number are correctly embedded in each input field. Also in the test data setting for each screen, it is possible to delete the data for the test cases for which the settings have been performed one after another so that the test cases for which the settings have not been performed can be checked at a glance.

FIG. 12 is an explanatory diagram of the test automatic execution operation. The automatic test execution is basically performed by the test data input device 31 and the test automatic execution device 33. The input data based on the test specification is transmitted to the test data input information 40 by the test data input device 31 as described above.
And can be provided to the automatic test execution device 33. This previous execution result information 41
It stores the result of execution performed before, and stores both the input data and the execution result at that time.

In FIG. 12, employee registration is executed as the content of the automatic test, and test case TEST-G00
The screen shows that the employee registration has been correctly performed using the test data of No. 1. That is, setting of a value in an input field for each test case, pressing of a button, and the like are automatically performed, and the execution result is stored as execution result information 23. This operation is executed for each test case one after another until the interrupt button is pressed as described later.

The automatic execution of the test is performed in the same manner when the test specification is in item units. When the previous execution result information 41 is used, a warning is issued for a test case in which the current execution result is different from the previous execution result, and here, the fact that the result of TEST-G003 is different is displayed.

When the registration button on the employee registration screen is depressed in this way, the entered employee number, postal code, telephone number, etc. are checked, and for example, the employee number ranges from the minimum value to the maximum value. If not, an error message is displayed. If the input data is a normal value, for example, a registration process of a server connected to a personal computer displaying an employee registration screen is called, and a database (not shown) is registered.

FIG. 13 is an operation example of a visual expression of the passage processing of the program. For example, in order to prevent test omissions, a test support logic function that visually recognizes the test results for each control (part) on the screen is embedded, for example, when the background color of the control is normal and abnormal In this case, a visual representation of the result of the passage processing of the program is realized.

For each input field, the background color of the input field is set to yellow after passing through the error processing, and the background color is set to blue if passing through the normal system. Is represented by For a button, once the button is pressed, the background color of the button is changed to, for example, blue, thereby expressing that the button is pressed.

FIG. 14 shows an operation example of the performance measurement support function. The performance measurement support device 34 measures various performances at the time of test execution using the screen definition information 15, and stores the results in the execution result information 23.

For example, when the test target screen is activated, the performance measurement support device 34 measures the time until the screen is displayed as the activation time, and displays the result. Here, it is displayed that the time until the display of the employee registration screen is 560 milliseconds.

The performance measurement support device 34 measures the time until the corresponding processing is completed by pressing down the button on the test target screen. The end of the process is detected by a change in the character string of the designated item or the call of the measurement end method, and the display of the time up to that point is performed and the time data is stored in the execution result information 23.

The performance measurement support device 34 acquires, for example, a list of each item of the employee registration screen definition from the screen definition information 15 of the test target screen, and as a candidate of an item to detect the end of the process when the button is pressed. Hold and have the tester specify it as a measurement. For example, when the registration is completed by pressing down the registration button, the status field changes from blank to “registered”, but the performance measurement support device 34 detects the change in the character string, and the processing when the registration button is pressed down is performed. Detects termination. The time measurement up to the end of the processing can be performed by calling the measurement end method as described above.

FIG. 15 is an explanatory diagram of an operation example of the test report generation device. The test report generation device 24 associates the execution result information 23 obtained by executing the test with the test specification 18 as described above, and writes the execution result and the execution date that have not been entered in the test specification 18. hand,
Generate a test report 25.

FIG. 16 is an explanatory diagram of an example of the overall operation of the test support apparatus described above. In the drawing, execution result information including a test execution result, execution date and time, and the like, and performance measurement information including a start time, a response time, and the like are stored for test data input information. The first line of the execution result information indicates the start time in milliseconds, and the second and subsequent lines indicate the value displayed as a result of inputting test data in addition to the test data input information, and the execution result is normal. Or the result of the judgment of whether or not an error
The response time (millisecond) from data input to result display is shown with an underline.

For example, the fourth line (TE
ST-I0001-03 test result) is the result for the test content of "minimum value -1" and the test data of "-1", and the first "0" in the underlined portion indicates that the input data is normal. It was not.

Next, a method for realizing the test support function according to the present invention and a processing flowchart of the test support apparatus will be described in more detail. FIG. 17 and FIG. 18 are explanatory diagrams of the conventional system and the system of the present invention when implementing the test support function. Here, the above-described employee registration screen is used as a test target screen, and the addition of a performance measurement function for measuring the time from when the registration button is pressed to when registration is completed is considered.

FIG. 17 shows a method of realizing the conventional method, in which a program is added so that the measurement start method and the measurement end method are called during the process of pressing down the registration button in the employee registration screen class. This is apparent from comparison with the employee registration screen class source program shown in FIG.

In FIG. 17, it is necessary to modify the employee registration screen class as described above. The test support A class and the employee registration screen class are different, and the screens are also different. There is only a relationship of knowing with the employee registration screen class. The measurement start method is, for example, a method for starting a stopwatch, and the measurement end method is a method for stopping the stopwatch.

In the method of the present invention shown in FIG. 18, it is not necessary to modify the employee registration screen class, but only to generate a source program for performing processing when the registration button is pressed in the test support B class. The test for the employee registration screen class is performed only by executing the test support B class, and the screen display is also performed by the test support B class.

In the test support B class, a processing method when a button is pressed, that is, torokuButton-act
The measurement start and end methods are embedded before and after calling ion () in the superclass.

FIG. 19 is a processing flowchart of the test specification creator. When the process is started in FIG.
First, the screen definition information is read in step S1,
At step S2, it is determined whether or not all the rows have been read. If not, at step S3, a test specification is generated in units of items and written to the specification, and step S1 is performed. Subsequent processing is repeated. If it is determined in step S2 that all the rows have been read, a test specification is generated for each screen in step S4, which is written in the test specification, and the process ends.

FIG. 20 is a processing flowchart of the test support class generation device. When the process is started in the figure, first, control information, that is, information on parts on the screen is acquired in step S6, and step S7 is executed.
It is determined whether or not all the control information has been obtained in step S. If it has not been obtained yet, step S
In step 8, a test support processing function for the control, such as the processing of the time measurement function until the end of the registration processing when the registration button is pressed, is generated, and the processing from step S6 is repeated.

If it is determined in step S7 that all control information has been acquired, a test support processing function for the screen is generated in step S9, and step S10
Then, the test support processing function generated in the test support class source is written out, and the process ends. Here step S
In 9, a test data input device, a test data setting device,
An automatic test execution device, a performance measurement support device, and the like are generated as a test support processing function and provided in the test support class.

The test support class is basically generated from the screen definition information, that is, the screen definition information of the screen class to be tested, as described above. That is, information such as the maximum value and the minimum value of the attribute of the item corresponding to the control on the screen is obtained from the screen definition information, and the test support class is generated.

On the other hand, as described with reference to FIG. 7, a test support class can be generated from the test target screen class 28 generated by the screen class generation device 27. That is, for the controls on the screen, necessary information is acquired from the test target screen class 28, and the attribute information of each item, that is, information such as the maximum value and the minimum value is
For example, a test support class can be generated in response to designation from a user.

FIG. 21 shows an operation example of the test data input device.
FIG. 22 is a flowchart of the processing. In FIG. 21, a test data input device 31 reads, for example, an employee registration screen test specification (employee number) 18 and converts, for example, Excel format specification data into test data input information 40 in a format that can be read by an automatic test execution device. And output.

The test data input information 40 is composed of five items: a screen name, an input field, first-level display data, second-level display data, and a test value. The second layer display data corresponds to the test content.

When the processing is started in the processing flow chart of the test data input device of FIG. 22, first, at step S12, a test specification is read, and at step S12,
At 13 it is determined whether all rows have been read,
If it has not been read, the conversion into the test data input information and the writing thereof are performed in step S14, and the processing from step S12 is repeated, and the processing in step S13 is repeated.
The process ends at the time when it is determined that all the rows have been read.

FIG. 23 shows an operation example of the test data setting device, and FIG. 24 shows a processing flowchart thereof. FIG.
In the above, the test data setting device 32 displays a pop-up menu on the screen using the test data input information 40, embeds the test value selected by the test operator in the input field, and determines whether the data setting has been correctly performed. The execution result information 23 is output. Execution result information 2
As No. 3, an execution result other than the activation time is output from the execution result information described in FIG.

When the processing is started in the processing flowchart of the test data setting device of FIG. 24, step S1 is started.
In step 6, test data input information is read, and in step S1
In step 7, it is determined whether or not the screen name specified by the test operator exists in the data, and if not, the process ends immediately. If there is, step S1
It is determined whether or not the input field specified in step 8 exists, and if not, the processing from step S16 is repeated.

If the input field specified in step S18 exists, a pop-up menu is created and displayed on the screen in step S19.
At 0, it is determined whether or not a test value or a test case has been selected by the test operator, and if not, the processing from step S19 is repeated.

If it is determined that the test value or the test case has been selected, the test value is embedded in the input field in step S21, the pop-up menu is deleted from the screen in step S22, and for example, the test value is correctly set in step S23. The result is written out as execution result information, and it is determined in step S24 whether or not to delete the executed test value. If not, the processing from step S16 is repeated.

If the executed test value is to be deleted in step S24, the executed test value is deleted from the data to be displayed as a pop-up menu in step S25, and the processing from step S16 is repeated. By deleting the executed test value in this manner, it is possible to check the unexecuted test value or the test case at a glance as described above.

FIG. 25 shows an operation example of the automatic test execution apparatus, and FIG. 26 is a flowchart of the processing. The test automatic execution device 33 automatically executes a test using the test data input information 40 or the previous execution result information 41 as described with reference to FIG.
Output as 3. The execution result information in FIG. 25 does not include the measurement result of the startup time as compared with the execution result information in FIG. 16, and whether the execution result is normal or abnormal when the tester looks at it for automatic test execution. Is different from that in which ○ or × is not displayed as a display for judging.

When the processing is started in FIG. 26, first, test data input information or previous execution result information is read in step S30, and it is determined in step S31 whether or not the reading has been completed to the end. If so, the process ends immediately. If the data has not been read to the end yet, it is determined in step S32 whether or not the screen name specified by, for example, the worker exists in the data. If not, the process is immediately terminated.

If the designated screen name exists, it is determined in step S33 whether the designated input field exists, and if not, the processing from step S30 is repeated. If the input field exists, the test value is embedded in the input field in step S34, execution result information such as information on whether the test value has been normally embedded is written out in step S35, and the process is interrupted in step S36. It is determined whether or not the button has been pressed. If the button has not been pressed yet, the processing from step S30 is repeated. In the present embodiment, it is assumed that the test is automatically executed until the interrupt button is pressed, and the process ends when it is determined in step S36 that the interrupt button has been pressed.

FIG. 27 shows an example of the operation of the visual representation device of the passage process, and FIG. 28 is a flowchart of the process. In FIG. 27, when a value is set to an input item by, for example, a test operator in step S38, the visual expression device 35 of the passing process receives the change of the input item in step S39, that is, changes the color of the input item, ie Whether or not the input data of the range has been set is displayed to the test operator by changing the background color of the input field. FIG.
In the example of No. 7, when the normal data is input, the background color is displayed in blue and the characters are displayed in white, whereas when the abnormal data is input, the background is displayed in yellow and the characters are displayed in black.

When the processing is started in the flowchart of FIG. 28, first, test data for an input item is read in step S41, and in step S42, the parent screen program, that is, the parent ( The test data is passed to the input processing of the screen program to be tested, which is a super class, and it is determined in step S43 whether or not an error, that is, an abnormality in the input data is detected. If the error does not occur after the background color of the input field and the color of the character are changed to the color of the abnormal processing expression, the processing is performed after the background color and the color of the character are changed to the color of the normal processing expression in step S45. To end.

FIG. 29 is an explanatory diagram of the operation of the performance measurement support device, and FIG. 30 is a flowchart of the process. FIG.
For example, the performance measurement support apparatus 34 measures the time until the screen is displayed when the test target screen class 28 is activated, outputs the result as the execution result information 23, and, for example, in the case of employee registration, The button processing of the test target screen class 28 is called when the registration button is pressed, and the elapsed time up to that point is output as the execution result information 23 when the button processing ends.

When the process is started in the flowchart of FIG. 30, the activation of the test target screen class and the measurement of the time until the display of the screen are started in step S50, and it is determined in step S51 whether the screen is displayed. If it has not been displayed yet, the determination is continued, and if it is determined that it has been displayed, the completion of the startup time measurement and the result are displayed in step S52, and the execution result information is written out.

Subsequently, in step S53, it is determined whether or not the monitoring item has been changed. If the monitoring item has been changed, the monitoring item is changed in step S54, and then the process proceeds to step S5.
Steps 3 and after are repeated, and if the monitoring item has not been changed, it is determined in step S55 whether a button on the target screen, for example, a registration button has been pressed, and if not, in step S56. It is determined whether or not the target screen has ended, and if not, step S
The processing after 53 is repeated, and when it is determined that the processing has been completed, the processing is completed.

The change of the monitoring item will be described with reference to FIG. FIG. 31 is an explanatory diagram of a change in a monitoring item in the performance measurement support function by detecting a change in a character string. On the employee registration screen, when the address complement button is pressed, a part of the address is complementarily input, and when the register button is pressed, information on registration success / failure is displayed in the status column as described above. Therefore, when the address complement button is pressed, the address column is monitored as a monitoring item, and when the registration button is pressed, the status column is monitored to detect a character string change.

As described above, the monitoring items differ depending on the measurement target, and therefore it is necessary to be able to change the monitoring items according to the intentions of the test operator and the user. In FIG. 31, a pop-up menu for test support customization is displayed by right-clicking the mouse at an arbitrary place other than the input field on the screen.

In addition to the change of the monitoring item, the performance measurement method change, that is, the change to the method by calling the measurement end method, and the measurement upper limit time described in steps S60 and S62 in FIG. A setting menu is displayed, and the test support function can be customized.

Referring back to FIG. 30, if it is determined in step S55 that the button on the target screen has been pressed, in step S57 the button processing time, that is, for example, employee registration is performed after the registration button is pressed, and the status field is displayed. The measurement of the time until “Registered” is displayed is started, and at the same time, the button processing in the test target screen class 28 is called. In step S58, whether the method of measuring the button processing time is character string change detection or Only the method call for measurement is determined. When a change in the character string is detected, it is determined whether or not the item specified in step S59, for example, the item in the above-described situation has a change in the character string.
At 0, for example, it is determined whether or not a predetermined upper limit time has been exceeded. If not, step S5
Steps 9 and thereafter are repeated.

If the measurement method is a method call in step S58, it is determined in step S61 whether the measurement end method has been called. If not, it is determined in step S62 whether the upper limit time has been exceeded. If not, the processing after step S61 is repeated.

When there is a change in step S59, when the time exceeds the upper limit time in steps S60 and S62,
If it is determined in step S61 that the measurement end method has been called, the processing after step S53 is repeated after the measurement is ended in step S63 and the execution result information is written out.

FIG. 32 is a processing flowchart of the test report generation device. When the process is started in FIG.
First, the test specification is read in step S65, and it is determined in step S66 whether or not all the rows have been read. If it is determined that all the rows have been read, the process ends immediately. If all the rows have not been read yet, the test result record for the test of that row is read in step S67, and it is determined in step S68 whether all the rows of the test result record have already been read. If the data has been read, the process is immediately terminated. If it has not been read yet, it is determined in step S69 whether or not the test cases match, and if not, the processing from step S65 is repeated. If they match, the execution result and the execution date are entered in step S70, and the processing from step S65 is repeated.

FIG. 33 and FIG. 34 are explanatory diagrams of separation of the test support function in the test support apparatus of the present invention. After the test of the screen program to be tested is completed, the test support function needs to be disconnected before the program is actually used in the production environment. FIG. 33 is an explanatory diagram of a display screen in a test execution environment. By executing the test support B class, a test is performed on an employee registration screen class that has a relationship of inheritance.

On the other hand, FIG. 34 shows an example of a screen display in a production environment. In a production environment in which a program is actually used, only the employee registration class is executed. Conventionally, as described with reference to FIG. 17, additions and corrections are made to the source program on the employee registration screen. Therefore, after the test is completed, it is necessary to delete the additions and corrections to provide only the original functions. . Alternatively, it is necessary to provide a test mode and a production mode, and to change the processing mode by an if statement or the like in the source program. In this way, there is always a possibility of a correction error or omission of correction, and when changing modes, the test of the logic for the determination cannot be performed by the test driver, and further testing is required for this part. .

Finally, loading of a program for realizing the present invention, that is, a program for supporting a test into a computer will be described with reference to FIG.
In order to realize the embodiment of the present invention as described above, the test support class 21 is generated by the test support class generation device 20, and the test specification and the test support class generated by the test specification generation device 16 are generated. It is necessary to execute a test using the test report generator 21 and generate a test report by the test report generator 24, but all of these operations will be performed by a general computer.

In FIG. 35, the computer 51 is
4 and a memory 55. The memory 55 is a random access memory (RAM), a hard disk,
It is a memory such as a magnetic disk, and a program for realizing the present invention is stored in such a memory, and the program is executed by the main body 54.
A test support device according to the present invention is realized.

The program corresponding to claims 10 to 12 of the present invention and the program shown in FIGS.
2. The programs and the like shown in the flowcharts of FIGS. 24, 26, 28, 30, and 32 are stored in the memory 55, and the programs are executed by the main body 54.

[0095] Such a program is supplied from the program provider side to the computer 5 via the network 53.
1 or may be stored in a commercially available and distributed portable storage medium 52, and the portable storage medium may be executed by being loaded into the computer 51. As the portable storage medium 52, various types of storage media such as a floppy disk, a CD-ROM, an optical disk, a magneto-optical disk, and an MO can be used.

Although the embodiments of the present invention have been described in detail above, the features of the present invention can be summarized as follows. First, regarding the generation of the test specification, the test specification itself or the data of the data is generated from the screen definition information. Since test specifications that can be used as input test data are generated by format conversion, the generation of test specifications is automated, or even if manual parts are included, it is easy to prepare documents for quality assurance. . In addition, since the specification is generated from the screen definition information, the test pattern can cover a wide range, and the reliability of the input test data in the consistency with the screen definition is improved.

Next, regarding the execution of the test, the test support function is added to the screen to be tested, so that the input error of the test data is eliminated and the record of the test execution result remains, so that the reliability of the test is improved. . In addition, automatic test execution and performance measurement support can improve the efficiency of test work.When a test is executed, the passing location in the screen program is reflected in the colors of input fields on the screen, so test workers It becomes easy to grasp the operation state of the screen program.

In order to record the input data and the test result instead of recording the operation of the mouse cursor and the keyboard, even if the screen is re-tested after the position of the screen or the arrangement of the controls is changed, the influence on the test execution is not affected. Does not occur. No additions are made to the screen program itself, and it is easy to disconnect the test support function after the test is completed.
Since there is no need to modify the source program,
The quality of the program after the test is completed can be guaranteed.

Further, in preparing a test report, a test result is automatically reflected in the test report, so that a mistake in entry by a test operator can be prevented, and the reliability of the test report is improved.

[0100]

As described in detail above, according to the present invention, it is possible to generate input data and support the input, automatically execute a test, record a test result and reflect it in a test report, and General unit testing work,
In other words, the work can be streamlined in three stages: test specification creation, test execution, and test result reporting. Further, even if the position of the test screen and the arrangement of the controls are changed, the test support apparatus of the present invention can be effectively used, and can be used for retesting after shifting to another OS.

There is no need to modify the screen program itself to be tested, and the test support function can be easily separated after the test, so that it is easy to shift to the production environment after the test is completed, and the quality of the program is assured. Can be guaranteed, which greatly contributes to the improvement of the reliability of the GUI program.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the principle configuration of the present invention.

FIG. 2 is a diagram illustrating a relationship between a test target screen program and a test support class according to the present invention.

FIG. 3 is a diagram illustrating addition of a test support function to a screen program.

FIG. 4 is a conceptual explanatory diagram of test specification generation.

FIG. 5 is a conceptual explanatory diagram of test support class generation.

FIG. 6 is a conceptual explanatory diagram of test report generation.

FIG. 7 is an explanatory diagram of the overall operation of the test support device of the present invention.

FIG. 8 is an explanatory diagram of a method for realizing a test support function according to the present invention.

FIG. 9 is an explanatory diagram of a specific example of generating a test specification from screen definition information.

FIG. 10 is an explanatory diagram of a specific example of test data setting in item units.

FIG. 11 is an explanatory diagram of a specific example of test data setting for each screen.

FIG. 12 is an explanatory diagram of a specific example of automatic test execution.

FIG. 13 is an explanatory diagram of a specific example of a visual expression of a passage process.

FIG. 14 is an explanatory diagram of an operation example of the performance measurement support device.

FIG. 15 is an explanatory diagram of an operation example of the test report generation device.

FIG. 16 is an overall explanatory diagram of an operation example of the test support device.

FIG. 17 is an explanatory diagram of a conventional example of a test support function realizing method.

FIG. 18 is an explanatory diagram corresponding to FIG. 17, illustrating a test support function realizing method according to the present invention.

FIG. 19 is a processing flowchart of the test specification generation device.

FIG. 20 is a processing flowchart of the test support class generation device.

FIG. 21 is a diagram illustrating an operation example of the test data input device.

FIG. 22 is a processing flowchart of the test data input device.

FIG. 23 is an explanatory diagram of an operation example of the test data setting device.

FIG. 24 is a processing flowchart of the test data setting device.

FIG. 25 is an explanatory diagram of an operation example of the automatic test execution device.

FIG. 26 is a processing flowchart of the automatic test execution device.

FIG. 27 is an explanatory diagram of an operation example of the visual expression device of the passage processing.

FIG. 28 is a processing flowchart of the visual expression device of the passage processing.

FIG. 29 is an explanatory diagram of an operation of the performance measurement support device.

FIG. 30 is a processing flowchart of the performance measurement support device.

FIG. 31 is an explanatory diagram of an operation example of the performance measurement support device when a monitoring item changes.

FIG. 32 is a processing flowchart of the test report generation device.

FIG. 33 is an explanatory diagram of test support by a test support B class in a test environment.

FIG. 34 is a diagram showing an employee registration screen in a production environment of program execution.

FIG. 35 is a diagram illustrating loading of a program for realizing an embodiment of the present invention into a computer.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Test support apparatus 2 Test support class generation means 3 Test execution means 10 Screen program 11 and 21 Test support class 15 Screen definition information 16 Test specification generation apparatus 18 Test specification 20 Test support class generation apparatus 23 Execution result information 24 Test report Document generation device 25 Test report 31 Test data input device 32 Test data setting device 33 Automatic test execution device 34 Performance measurement support device 35 Visual representation device of passage processing 40 Test data input information 41 Previous execution result information

 ────────────────────────────────────────────────── ─── Continuing on the front page (72) Inventor Yasuyuki Fujikawa 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa F-term in Fujitsu Limited (Reference) 5B042 GA08 GB02 HH17 HH19 5B076 DF08 EC05 5E501 AA02 AC10 BA05 CA02 CB02 CB09 EA05 EA10 FA25 FA42 FB28

Claims (14)

[Claims] An apparatus for supporting a screen program test using a graphic user interface receives screen definition information of a screen program to be tested as an input, and has an object-oriented inheritance relation to a class of the screen program to be tested. Test support class generation means for generating a test support class for testing a screen program, and test execution means for executing a test of a test target screen program using the generated test support class A test support apparatus for a GUI program, comprising: 2. The test support apparatus according to claim 1, further comprising: a test specification generating unit that generates a test specification for the test target screen program from the screen definition information and provides the test specification to the test execution unit. GUI program test support device. 3. The test support apparatus, further comprising: a test report generation unit that generates a test report using the test specification generated by the test specification generation unit and a test execution result by the test execution unit. 3. The test support apparatus for a GUI program according to claim 2, wherein: 4. The test support apparatus for a GUI program according to claim 1, wherein the test support class has a function of supporting input of input test data. 5. The test support class according to claim 1, wherein:
4. The GUI according to claim 1, further comprising a function of recording a test result at the time of automatic execution.
Test support system for system programs. 6. The test support apparatus for a GUI program according to claim 1, wherein the test support class has a function of visually displaying a test execution location on a screen. 7. The test support class according to claim 1, further comprising a function for manually or automatically executing a test using new input test data or input data for a previous test execution result. Or G described in 3
UI program test support device. 8. The test support class further comprises a function of displaying a warning when a test execution result using input data for the previous test execution result is different from the previous execution result. GUI of Item 7
Test support system for system programs. 9. The GU according to claim 1, wherein the test support class has a function of supporting measurement of execution performance of the test target screen program.
Test support system for I-system programs. 10. A method for supporting a test of a screen program that specifies a graphic user interface, wherein the screen definition information of the test target screen program is received as an input, and the relationship of the object-oriented inheritance to the class of the test target screen program. GU, wherein a test support class for testing a screen program is generated, and a test of a test target screen program is executed using the generated test support class.
Test support method for I-system programs. 11. A storage medium used in a computer for supporting a test of a screen program using a graphic user interface, wherein the step of receiving screen definition information of a screen program to be tested as an input; A computer-readable portable storage medium storing a program for causing a computer to execute a step of generating a test support class for testing a screen program, the subclass being in an object-oriented inheritance relationship with respect to the class. 12. A storage medium used in a computer for executing a test of a screen program using a graphic user interface, receiving new input test data or input data for a previous test execution result. Using the received input data, test the screen program under test using a test support class for testing the screen program, which is a subclass in an object-oriented inheritance relationship with the class of the screen program to be tested. And a computer-readable portable storage medium storing a program for causing a computer to execute the steps of: 13. A program used in a computer for supporting a test of a screen program using a graphic user interface, a procedure for receiving screen definition information of a screen program to be tested as an input, and a class of the screen program to be tested. A program for causing a computer to execute a procedure for generating a test support class for testing a screen program, which is a subclass in an object-oriented inheritance relationship with respect to. 14. A program used in a computer for executing a test of a screen program using a graphic user interface, a procedure for receiving new input test data or input data for a previous test execution result, A subclass in an object-oriented inheritance relationship with respect to the class of the screen program to be tested using the input data obtained, and using the test support class for testing the screen program to test the screen program to be tested. A program for causing a computer to execute a procedure to be executed.