JP2005115582A - System and method for generating test script component automatically - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the following problems: all the transitional patterns with respect to each object of a picture can not be grasped and that a bug cannot be detected in the case of a rare operating pattern in generation of the conventional test script. <P>SOLUTION: The system is provided with a function to create picture information for every picture by using standard action pattern, picture definition information for every picture and event information. The picture information for every picture represents, in the form of a table, definition information for every object, order of focus acquisition, and state transition related to other objects in performing the action related to the respective objects. The system is provided with a means for creating a test script which covers all the input patterns in a program picture to be tested based on a combination of input patterns with respect to the respective objects by using the information. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an automatic test system and test method for software programs.

Automatic testing of software programs The prior art is divided into the following six areas. 1. 1. Automatic test item generation technology 2. Automatic test procedure generation technology 3. Automatic test data generation technology 4. Test script automatic generation technology Automatic test execution technology, 6. Automatic output of test results.
The software program automatic test system and test method of the present invention relate to the automatic test script generation technique described above. The test script is a program for simulating the operation of the program under test from the outside, separately from the program under test.

  Examples of the automatic generation method using the conventional automatic test script generation technique include the methods shown in Patent Literature 1, Patent Literature 2, Patent Literature 3, Patent Literature 4, and the like.

JP 2002-14845

JP-A-8-212291 JP-A-9-2223040 JP-A-10-301809

The prior art has the following two problems.
One problem is that all transition patterns for each object on the screen cannot be grasped. In conventional script component generation, events such as “change of screen input range by pressing a radio button on the screen” are not grasped. For example, in the example of Patent Document 1, a test script can be automatically generated. Because event information for each object on the screen is not acquired, even if the input range of the screen is limited by the action, it is not possible to grasp, and numerical values etc. are input to protected objects was there. Further, in the example of Patent Document 4, each object information of the screen is acquired by directly referring to the resource code of the screen, but the branch information of the object input range restriction by executing the action is not acquired. There was a problem.
The other is a problem related to the generation of test script patterns for screens. Conventional test script generation does not cover all input patterns on the screen, so bug detection in the case of rare operation patterns is not possible. There was a problem that it was possible. For example, in the examples of Patent Document 1 and Patent Document 3, there is a problem in that all input patterns are not covered only by generating test scripts that always execute all input events at least once.

  An object of the present invention is to provide a system and test script component automatic generation method that solves the above problems and automatically generates test script components that cover all transition patterns and screen input patterns for each object on the screen. is there.

In order to solve the above problems, the present invention uses the following system and method.
First, standard action patterns corresponding to products used for each development are prepared in advance and stored in the system. The standard action pattern describes an operation command peculiar to an object such as selecting one of a button group or inputting a text for each object such as a radio button, a combo box, and a text input field.
In addition, the screen definition information and event information of the program under test are obtained by directly referring to the screen source and stored. The acquisition method is triggered by the user inputting and specifying the screen ID of the program under test. The screen definition information includes a focus acquisition order corresponding to each object in the screen, an arrangement on the screen, a size, an action type, an inputable range, and the like. The event information includes information on branching of state transitions such as selectable state and non-selectable state for other objects when an action such as selecting one of the radio buttons is executed for each object. .

This system has a function of creating screen information for each screen using standard action patterns, screen definition information for each screen, and event information. The screen information for each screen represents the definition information for each object, the focus acquisition order, and state transitions related to other objects when an action is performed on each object in a tabular format.
In addition, this system has a function of creating a test script that covers all input patterns on the test target program screen from combinations of input patterns for each object using these pieces of information. At this time, a test script is created that takes into consideration the selectable and impossible states of other objects, such as by selecting one radio button. Also, by combining the screens, it is possible to create a test script for each paperwork that spans multiple screens.

A test script is automatically generated based on these information and functions of this system.
The created test script is executed by the automatic execution program, and the test result is stored in the test result storage device. If an error occurs, the error information is stored in the error information storage device.
As a result, the test executor can automatically generate test script parts that cover all the transition patterns and screen input patterns for the screen simply by specifying the ID of the screen to be tested.・ Tests can be executed. In addition, even when one business process spans multiple screens, it is possible to execute a test for each business process. Also, by covering all input patterns, it is possible to efficiently extract bugs of rare patterns.
By mounting the test script storage system of the present invention on a user terminal, it is possible to store input information of each user and use it as input information for a reproduction test when a failure occurs.

As described above, according to the system and the automatic generation method for automatically generating test script parts of the present invention, test script parts covering all transition patterns and screen input patterns for each object on the screen are automatically generated and automatically generated. Tests can be performed.
Further, even when there is a branch of the input range on the program under test screen, a test script including the branch can be created, and efficient bug extraction can be performed.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a configuration diagram of a test script component automatic generation system according to the present invention.
The automatic generation system for test script parts of the present invention includes a screen definition information storage function 111 for each product, a screen information storage function 112 for storing screen definition information 102 and event information 103, tabular object information, and focus. Screen information generation function 121 that outputs screen information including order and event information, test script generation function 122, generated test script storage function 114, test script automatic execution function 123, and test result storage function 116 And an error information storage function 117, and a screen ID to be tested is input from the input device 101.
The screen definition information 111 is definition information of each object of a product used for development, and includes a focus acquisition order, an arrangement on the screen, a size, an action type, and an inputable range corresponding to each object in the screen.
The screen definition information 102 is the screen definition information that is directly referred to in text form from the program under test screen and includes the focus acquisition order. Like the screen definition information 102, the event information 103 is event information when an action is executed on each object, which is directly referred to in a text format from the program under test screen.

The screen information generation function 121 executes the action for each object input from the screen ID information input from the input device 101, definition information and focus acquisition order for each object input from the screen definition information 102, and event information 103 This is a function for outputting the input range branching information as screen information 113 composed of tabular object information, focus order, and event information.
The test script generation function 122 uses the screen information 113 as input information, creates all input patterns on each screen as a test script 115, and stores the test script 115 in the test script storage function 114. When one paperwork spans multiple screens, a test script is created by designating a plurality of screen IDs forming one paperwork from the input device 101.
The test script automatic execution function 123 uses the test script 115 as input information and automatically executes the test script. When the executed result is normally completed, the test result is output to the test result storage function 116. When the executed result is not normally completed, the error information is output to the error information storage function 117.

  FIG. 2 shows a processing flow of the present invention. A screen ID is designated by the input device 101 (process 201), and a screen definition that matches the screen ID of the designated program to be tested is referred to in a text format (process 202). Next, the screen source that matches the screen ID of the designated program under test is referred to in text format (process 203). Next, the format of the product used is read from the screen definition storage device for each product, and the screen definition and the screen source are decoded (process 204). Branches such as the decrypted screen definition and the input range restriction from the screen source to the object are discriminated, and screen information is created (process 205). Branching of the input range restriction to the object will be described later with reference to FIG. The screen information will be described later with reference to FIG.

  A test script for the screen of the program to be tested is created from the combination of screen information created in processing 205 (processing 206). Next, it is determined whether or not one business process extends over a plurality of screens (process 207), and when it extends over a plurality of screens, a test script is created from a combination of screen IDs constituting one business process specified by the input terminal 101 ( Process 208).

  A test is automatically executed for the created test script (process 209). It is determined whether the test execution result is an error (process 210). If the test execution result is an error, a process of storing in the error information storage device is performed (process 211). If there is no error, a process of storing the test result in the test result storage device is performed (process 212). Finally, it is determined whether or not the test script is the end of all patterns (process 213). If all patterns are not ended, the script execution process of process 209 is performed.

  FIG. 3 shows a processing flow when event information exists on the program under test screen. First, based on the designated screen ID, event information is directly referred to in text form from the program screen to be tested (process 301). The presence / absence of event information is determined (process 302). If event information exists, event information is read (process 303). If it does not exist, the process ends. For the read event information, it is determined whether or not the input range branch information based on the protection of the object is described in the event information (processing 304). If there is a description, another object when the action is executed on each object is determined. A process for creating a table in which branches in the selectable state and the unselectable state in FIG. If there is no description, the process ends.

FIG. 4 shows an example of the screen information 113 created by the screen information generation function 121. FIG. 4A shows a table in which information such as position, font, numerical input range, etc. in each object on the test target program screen is decoded based on the screen definition information 111. FIG. 4B shows the focus acquisition order for each object on the test program screen. FIG. 4C shows the event information created in the flow of FIG.
FIG. 4 shows that, for example, when the radio button 2 of the object 3 (OBJ3) is pressed, the text box of the object 4 (OBJ4) becomes unselectable.

  FIG. 5 shows an example of the test script 115 created by the test script generation function 122. For example, “script 1” in FIG. 5 indicates a script that inputs “ah” in the text box of object 1, then presses the radio button of object 2, and then inputs “0” in object 4. Yes. There are as many scripts as the number of combinations shown in FIG.

  FIG. 6 shows an example of a test script for each paperwork when one paperwork spans multiple screens. For example, in the “test script 1” of FIG. 6, the script 1 of the screen 1 is executed on the screen 1, the script 1 of the screen 2 is then executed on the screen 2, and then the script 1 of the screen 3 is displayed on the screen 3. , And finally the script for executing the script 1 of the screen 4 on the screen 4 is shown.

It is a figure which shows an example of the hardware apparatus structure of a computer for implement | achieving this invention. It is a figure which shows an example of the flow of the whole process for implement | achieving this invention. It is a figure which shows an example of the process for grasping | ascertaining the branch information by event information. It is a figure which shows an example of the screen information produced from the screen definition and the screen source. It is a figure which shows an example of the test script for every to-be-tested program screen. It is a figure which shows an example of a test script in case a paperwork spans multiple screens.

Explanation of symbols

101... Input device for specifying screen ID, 102... Screen definition information, 103 .. event information, 104... Input device for specifying screen ID, 111. ... screen information generation processing device, 113 ... created screen information, 114 ... test script storage device, 115 ... test script, 116 ... device for storing normal test results, 117: Device for storing error results, 121: Screen information generation processing, 122: Test script generation processing, 123: Test script automatic execution processing, 201: Designates screen ID Processing 202: Processing for referencing the screen definition in text format 203: Processing for referencing the screen source in text format 204: Screen definition, image Process for decoding source, 205 ... Process for creating screen information, 206 ... Process for creating test script, 207 ... Process for determining whether one business process spans multiple screens, 208 ... A process for creating a test script from a combination of screen IDs constituting one business process, 209... Test script automatic execution process, 210... A process for determining whether the test execution result is an error, 211. Processing to store in error information storage device, 212 to store normal test results in test result storage device, 213 to determine whether test script is complete, 301 to Processing to directly refer to event information in text format, 302 ... Processing to determine whether event information exists, 303 ... Reading event information 305... Processing for determining whether input range branch information by object protection is described, 305... Selectable state in other objects when action is performed on each object, unselectable Processing for creating a table in which branching of states is classified, 401... Table describing information such as position, font, numerical value input range, etc., in each object on the test target program screen, 402. Table indicating the focus acquisition order for each object, 403... Event information table for each object on the test target program screen, 501... Test script table, 601. Test script for crossing multiple screens

Claims (3)

Screen definition information describing each object attribute of the screen of the program under test, event information in other objects when actions are performed on each object, and standard action patterns for each product corresponding to each object type And, based on these information, a focus order acquisition means for each object on the screen and a branch information generation means for the object input order by executing an action for each object are provided for the screen used in the test. Automatic generation system for test script parts. All input patterns for each screen based on definition information for each object on the screen of the program under test, focus acquisition order for each object, and branch information for object input order by executing actions for each object 2. The test script component automatic generation system according to claim 1, further comprising generation means. 3. The test script component automatic generation system according to claim 1 or 2, wherein the screen definition information and event information of the program under test are directly referenced from the screen source, and the user inputs and specifies the screen ID of the program under test. Is created as a trigger, and screen information for each screen is created using the standard action pattern, screen definition information and event information for each screen, and all inputs on the program under test screen are combined from combinations of input patterns for each object. The test script component automatic generation method using the test script component automatic generation system according to claim 1 or 2, wherein a test script that covers patterns is created.

Images