JP4395761B2 - Program test support apparatus and method - Google Patents

Description

  The present invention relates to an apparatus for supporting a test for detecting a bug in an interactive program having a GUI (Graphical User Interface), and more particularly to an apparatus for supporting an automatic test.

  Patent document 1 and patent document 2 describe a program test support device using a method of automatically inputting a large amount of data as a device for automatically testing a GUI program. In these program test support devices, operations performed by the user are recorded, input items are extracted from the operations, and the user sets one or more data to be tested for the extracted input items. This is automatically combined by the program test support device, and the test is automatically performed based on the data combined with the recorded operation. In the program test support device of Patent Document 1, an error check is automatically performed based on the error check conditions registered in advance by the user, the result of the error is analyzed, and the cause of the error is determined. It is possible to automatically extract the input items that have become. Furthermore, the program test support apparatus of Patent Document 2 can automatically generate a condition for error check based on higher-level design information created using a CASE tool or the like.

  Further, Patent Document 3 discloses a program test support apparatus that uses a method for automatically extracting GUI program operation parts and exhaustively performing GUI screen transitions. In this program test support device, GUI operation component identifiers are stored in a table stack, predetermined operations are sequentially performed on each operation component, GUI screen transitions by each operation are saved, and the state of the GUI screen is changed. If there is, the GUI program design is performed by recursively storing the GUI operation component identifiers in the table stack, scanning the properties of all GUI operation components, and comparing the properties of each GUI operation component. Can automatically check the sense of unity.

Furthermore, Patent Document 4 describes that as a method for creating test data for program test execution, test data that matches the type of data item and the number of digits is generated based on a program specification or a record specification. Has been.
JP2000-112784 JP2003-228493 JP 10-198586 JP-A-6-110733

  In the program test support apparatus described in Patent Document 1 or Patent Document 2, a user needs to input test data one by one. For this reason, it is necessary for the user himself / herself to consider useful test data for each input item, and the user's work becomes complicated, and appropriate test data may not be prepared. In addition, it is necessary to first perform an operation by a human hand, and the operation path itself cannot be automatically determined.

  Patent Document 3 describes a method for exhaustively performing GUI screen transitions by extracting and manipulating operation parts of a GUI program, and the technology is described in Patent Document 1 or Patent Document 2 If it is applied to a test support device, it is not necessary to first perform a manual operation. However, the operation components extracted in Patent Document 3 are limited to operation components that generate screen transitions such as menus, submenus, option buttons, and push buttons (paragraph 0037), and operation components that do not generate screen transitions such as text boxes. Is not considered. Depending on the GUI program, since the transition to the next state may not occur unless the push button is operated after a predetermined value is entered in the text box, such a GUI program cannot be sufficiently tested.

  Further, since a technique for automatically generating test data is described in Patent Document 4, if the technique is applied to the program test support apparatus described in Patent Document 1 or Patent Document 2, a user inputs test data. There is no need. However, Patent Document 4 only generates normal test data that matches the data item type and the number of digits. The program test also requires a test with an invalid value, and when executing a test using such an invalid value, the user still needs to input it.

  An object of the present invention is to automatically perform a test for detecting a bug in a GUI program while automatically operating an operation component that does not generate a screen transition such as a text box in addition to an operation component that generates a screen transition of a program to be tested. An object of the present invention is to provide a program test support apparatus and method that can be executed.

  Another object of the present invention is to provide a program test support device capable of automatically executing a test for detecting a bug in a GUI program while automatically generating abnormal test data in addition to normal test data. It is to provide a method.

The program test support apparatus of the present invention is a program to be tested, which is an interactive program for performing input / output operations using a GUI, and an operation component that generates a screen transition after a value is input to the operation component that does not generate a screen transition In a program test support apparatus that supports the test of the program under test so that the screen does not transition to the next state unless the button is operated, the types and inputs of the effective operations for the operation components included in the output screen of the program under test Design information storage means for storing design information describing information on value conditions, test pattern storage means for storing test patterns describing test data generation rules, and an output screen as a test target of the test target program Operation component detection means for detecting an existing operation component, and the operation component detection means Operation component storage means for storing information of the detected operation component, and for the operation components stored in the operation component storage means, valid operation types and input values for the operation components stored in the design information storage means The test data generation means for generating test data based on the information on the conditions of the test data and the test data generation rules stored in the test pattern storage means, and the screen transition among the operation parts stored in the operation component storage means The test data generated by the test data generation unit for the operation component that does not generate the screen and the test data generated by the test data generation unit for the operation component that generates the screen transition to the operation component that does not generate the screen transition Combined so that operations are performed earlier in time than operations on operation components that cause screen transitions A test case generating means for generating only test case, the test case storage means for storing the test cases generated by the test case generating means, by using the function of the execution environment of the test program, the test program A means for performing operation on an operation component existing on an output screen of the test target program, starting and ending, reading a test case from the test case storage means, and testing each of the read test cases A program control unit that resets the test target program before starting execution of the case and then executes an operation on the operation component of the test target program based on the test case; and the operation component by the program control unit The test target for which the operation on was performed Test result storage means for storing a test result including a new output screen output from the program.

"Action"
In the present invention, the design information storage means stores design information describing information related to the effective operation range of the operation component included in the output screen of the test target program, and the test pattern storage means generates test data. Test patterns describing rules are stored, and when testing a program to be tested, the operation component detection means detects an operation component present on the output screen to be tested by the test target program and stores it in the operation component storage means The operation data stored in the operation component storage means is stored in the design information storage means, and the test data stored in the test pattern storage means is stored in the design information storage means. Test data is generated based on the generation rule of the test component, and the test pattern generation means The test data generated by the test data generation means for the operation parts that do not cause screen transition and the test data generated by the test data generation means for the operation parts that generate screen transition among the operation parts stored in The test case is generated and stored in the test case storage means, and the program control means reads the test case from the test case storage means, and executes an operation on the operation component of the test target program based on the read test case. Then, a test result including a new output screen output from the test target program is stored in the test result storage means.

  According to the present invention, in a program to be tested in which a screen does not transition to the next state unless an operation component that causes screen transition such as a push button is operated after a value is input to the operation component that does not cause screen transition such as a text box. Even so, the test can be performed automatically. The reason for this is that test data for each operation component, including operation components that do not cause screen transitions, is automatically generated based on the design information and test pattern of each operation component, and tests that are generated for operation components that do not cause screen transition. This is because a test case is generated by combining the data and the test data generated for the operation component that generates screen transition, and an operation on the operation component of the test target program is executed based on the generated test case.

  Next, the best mode for carrying out the present invention will be described in detail with reference to the drawings.

  Referring to FIG. 1, a GUI program test support device 10 according to an embodiment of the present invention includes a program control unit 11, an operation component detection unit 12, an operation component storage device 13, a design information storage device 14, and a test pattern. A storage device 15, a test data generation unit 16, a test case generation unit 17, a test case storage device 18, a test result storage device 19, a design information input device 20, and a test pattern input device 21 are provided. Are connected to the interactive program under test 1 and the output means 2 for performing input / output operations.

  The program under test 1 is a program controlled by an OS (operating system) that operates on a hardware computing resource such as a PC (personal computer) or WS (workstation). The output means 2 is a display device such as an LCD for outputting a display screen such as a window output from the test target program 1.

  Among the components of the GUI program test support apparatus 10, the program control unit 11, the operation component detection unit 12, the test data generation unit 16, and the test case generation unit 17 operate on hardware calculation resources such as a PC and WS, for example. Realized by a program controlled by the operating system. The operation component storage device 13, the design information storage device 14, the test pattern storage device 15, the test case storage device 18, and the test result storage device 19 are configured by storage means represented by a memory, a hard disk, and the like. The design information input device 20 and the test pattern input device 21 are programs that receive and process input information from an input device (not shown) such as a mouse or a keyboard. An outline of these operations is shown below.

  The program control unit 11 can use the function of the execution environment (such as an OS) of the program under test 1 to start and end the program under test 1 and perform operations that are present on the output screen (window) of the program under test 1 It controls the program under test 1 such as operations on various operation parts (menus, push buttons, etc.) and controls the entire GUI program test support apparatus 10.

  The operation component detection unit 12 detects an operation component that can be an operation target from the output screen of the test target program 1 controlled by the program control unit 11. The screen output from the test target program 1 is stored in the test result storage device 19, and the operation component detection unit 12 detects the operation component from the output screen stored in the test result storage device 19. Is also possible.

  The operation component storage device 13 stores information related to the operation components of the test target program 1 detected by the operation component detector 12 in the form of a file or the like. The stored information includes information indicating on which screen (window) the operation component detected by the operation component detection unit 12 exists, and information such as the type, position, size, and caption of the operation component. .

  The design information input device 20 is a device for inputting design information created by a developer when developing the program under test 1. The design information to be input includes, for each operation component displayed on the output screen by the program under test 1, information indicating on which screen (window) the operation component exists, the type of the operation component, and the valid Contains information about the type and range of operations. The input design information is converted into an internal format and stored in the design information storage device 14.

  The test pattern input device 21 is a device for a user to input a test pattern (test data generation rule) employed in a general test method such as a limit value test. The input information is stored in the test pattern storage device 15.

  The test data generation unit 16 takes out information on the operation component, design information, and test pattern from the operation component storage device 13, the design information storage device 14, and the test pattern storage device 15, respectively, and provides one test data for each operation component. Or create more than one. The test data for the operation component includes, for example, a click operation when the operation component is a menu and a numerical value input operation when the operation component is a text box. As the test data, both normal data that matches the design information and data that does not match the design information are generated. The former is called normal test data, and the latter is called abnormal test data. For example, when the design information indicates that the condition of the input value of a certain text box is an integer from 0 to 100, the test data in which an arbitrary integer from 0 to 100 is input to the text box is normal. The test data for which a value other than an integer from 0 to 100 is input to the text box is an abnormal system.

  The test case generation unit 17 generates test data for each operation component generated by the test data generation unit 16, information on the operation component stored in the operation component storage device 13, and a test case generated by itself before. From the existing test cases stored in the storage device 18, test cases including screen transitions are comprehensively generated. The operation of the test case generation unit 17 will be described with reference to FIG.

  FIG. 2 shows an example of transition of the output screen of the program under test 1. In this example, when the test target program 1 is started, a window W1 is first output. Next, when the value a is input to the operation component B12 existing in the window W1 and the operation component B11 is clicked, a new window W2 is output. Further, when the value b is input to the operation component B22 existing in the window W2 and the operation component B21 is clicked, a new window W3 is output. Further, when the value c is input to the operation component B22 existing in the window W2 and the operation component B21 is clicked, an error E1 is generated. The test cases generated by the test case generation unit 17 are test data (B12 = a, B11 = click) for causing screen transition from the window W1 to the window W2 in FIG. 2 and screen transition from the window W1 to the window W3. Test data sequence {(B12 = a, B11 = click)}, (B22 = b, B21 = click)}, or test data sequence {(B12 = a, B11 = click), (B22 = c, B21 = click)}.

  A test case T11 based on test data (B12 = a, B11 = click) causes the next screen transition to start from the window W1 displayed immediately after the program control unit 11 starts the program under test 1. Yes, it is first generated together with other test cases T12 to T1m using different test data for the operation parts B11 and B12, stored in the test case storage device 18, and executed by the program control unit 11. Other test cases T22 to T2n using the test case T21 by the test data sequence {(B12 = a, B11 = click), (B22 = b, B21 = click)} and other test data for the operation parts B21, B22 are: The test case (B22 = b, B21 = click) generated by combining the test data (b, c, etc.) of the operation component B21 generated by the test data generator 16 and the test data (click, etc.) of the operation component B22 And (B22 = c, B21 = click) and the like and the existing test case T11 (B12 = a, B11 = click) stored in the test case storage device 18 are combined.

  When combining the test data of the operation components B21 and B22 generated by the test data generation unit 16, the operation on the operation component B22 that does not cause a transition is performed first in time, and the operation on the operation component B21 that causes the transition Are combined to be performed later in time. Whether or not the operation component causes a transition is determined by the type of the operation component stored in the operation component storage unit 13.

  Referring to FIG. 1 again, the test case storage device 18 stores the test cases generated by the test case generation unit 17. The test cases stored in the test case storage device 18 are transferred to the program control unit 11, and when the automatic test is executed, the program under test 1 is automatically operated in order based on the test cases, and the result is output to the output means 2. .

  In the test result storage device 19, the program control unit 11 automatically tests the program under test 1 based on the test cases stored in the test case storage device 18, and stores the test results including the output screen.

  Next, the overall operation of the present embodiment will be described in detail with reference to the flowcharts of FIGS. 1 and 2 and FIG.

  First, the program control unit 11 starts the test target program 1 (step ST1 in FIG. 3). The activated program under test 1 displays a GUI screen on the output means 2. Next, the operation component detection unit 12 detects an active window, that is, a window that is in a state of receiving an input from the user, from the GUI screen of the started program under test 1, and the operation component storage device 13 (step ST2). In the example of FIG. 2, the window W1 is detected. The information registered at this time includes, for example, information for identifying the window on the GUI screen, such as a window name, and an ID for identifying the relationship between the windows in the program test support apparatus 10. There is. Even in the same window, if there is a difference in the operation parts on it, the information is given.

  Next, the operation component detection unit 12 detects all operation components from the active window and registers them in the operation component storage device 13 (steps ST3 to ST6). Specifically, for each detected operation component, the operation component detection unit 12 checks whether or not the operation component is already registered in the operation component storage device 13. It is registered in the operation component storage device 13. The information registered at this time is the program control unit on the GUI screen including information on the operation component itself, such as the type and size of each operation component, the content of the caption, and information on which window it is placed on. 11 is information for identifying the operation component to be registered. In the example of FIG. 2, the operation components B11 and B12 are registered.

  Next, the test data generation unit 16 tests the test pattern registered in advance by the test pattern input device 21, the design information registered in advance by the developer using the design information input device 20, and the operations registered in steps ST2 to ST6. The component information is extracted from the design information storage device 14, the test pattern storage device 15, and the operation component storage device 13, respectively, and a test pattern is applied to each operation component based on the design information, and test data for each operation component is obtained. Is generated (step ST7).

  Next, the test case generation unit 17 extracts information indicating which window is currently targeted from the operation component storage device 13, and an existing test case that has undergone a transition until the window becomes active from the test case storage device 18. As a next test step for the extracted test case, a combination of test data generated by the test data generating unit 16 is added to generate a plurality of new test cases and store them in the test case storage device 18. (Step ST8).

  Next, the program control unit 11 takes out the generated new test cases one by one from the test case storage device 18, and automatically performs a test according to the test cases (step ST9). Specifically, if the taken out test case is, for example, the test case T11 of FIG. 2, the program under test 1 is restarted, and the user performs an operation of inputting the value a to the operation component B12 on the GUI screen. The same event that occurs when the user clicks on the operation component B11 on the GUI screen is generated, and the same event that occurs when the user clicks the operation component B11 on the GUI screen is generated. Then, the output screen of the program under test 1 at this time is stored in the test result storage device 19 as a part of the test result of the test case. In step ST9, the test using all the test cases generated in step ST8 is repeated.

  Depending on the type of operation performed on the operation component performed in the test based on the above test case, a new window may be generated like the window W3 in FIG. In the next step ST10, it is determined whether or not there is a window that is not yet a test target among windows included in the test result corresponding to the already executed test case stored in the test result storage device 19. If there is a window that has not been tested yet, that one window is set as the active window (step ST2), and the same test as described above is repeated. If there are multiple windows to be tested, priority is given to the window closer to the root on the transition hierarchy. For example, when window W2 in FIG. 2 is the test target, window W3 is generated at the end of the test, but when window W1 is the test target, another window (not shown) of the same hierarchy as window W2 was generated. Then, so-called width priority selection is performed in which it is selected with priority over the window W2. If all the generated windows are to be tested, the test of the program under test 1 is terminated (step ST11).

  Next, the effect of this embodiment will be described.

  According to the present embodiment, the test data generation unit 16 automatically generates test data for each operation component including operation components that do not cause screen transition based on the design information and test pattern of each operation component, and performs the test. The case generation unit 17 generates a test case that combines the test data generated for the operation component that does not cause the screen transition and the test data that is generated for the operation component that causes the screen transition, and the program control unit 11 Since an operation is performed on the operation component of the program under test 1 based on the generated test case, the operation component that generates a screen transition must be operated after a value is input to the operation component that does not generate a screen transition. Even the program under test 1 whose screen does not transition to the state can be automatically tested .

  In addition, according to the present embodiment, the test data generation unit 16 generates both normal test data and abnormal test data, so that a test using an incorrect value as well as a normal value is automatically performed. Can be executed.

  Further, according to the present embodiment, a new output screen stored in the test result storage device 19 is set as the output screen to be tested, and the test is recursively repeated, so that a comprehensive test can be performed.

  Next, the operation of this embodiment will be described using specific examples.

  FIG. 4 shows an image example of the initial screen of the program under test 1 activated by the program control unit 11. In FIG. 4, reference numeral 100 denotes a window of the program under test 1 that has been started, and a character string (here “Main”) in the title bar 101 is the title of the window 100. Reference numerals 102 and 103 denote menus, each of which is an operation component.

  The operation component detection unit 12 detects an active window 100 on the screen and registers the information in the operation component storage device 13. FIG. 5 shows registered window information. In addition, the operation component detection unit 12 detects the operation components 102 and 103 on the window 100 that is active on the screen, and registers them in the operation component storage device 13. FIG. 6 shows information on registered operation components. The ID for identifying the operation component, the ID of the window in which the operation component exists, the type of operation component, the caption, and the layout information are registered. Here, information based on the arrangement of menus is registered as layout information, but depending on the type of operation component, it is also useful to identify it by information such as position and size, so store this information. Is also possible. Further, FIG. 6 shows an example of registration as minimum information, but if there is information other than these that is useful for identification or testing of the operation component, it is also automatically registered.

In the design information storage device 14, design information of the program under test is stored in advance as shown in FIG. This information is obtained by inputting information designed by the developer during development using the design information input device 20. In addition to direct input by human hands, it is also possible to input from a data file when designing with a CASE tool. The stored design information describes the operation contents and restrictions to be performed on each operation component. For example, “Click ()” specified in FIG. 7 indicates a single click with a pointer device such as a mouse for the operation component, and “Input (regexp (”. ^* “))” Is specified with a regular expression. Input the target character string.

  Further, the logic of a general test method is registered in the test pattern storage device 15 in advance. For example, the limit value test logic describes a rule that when a certain value is determined as the limit value, the value before and after the limit value is also used as the input value. An example is shown in FIG. In the example of FIG. 8, when only a single integer N is a valid input value, three types of data N-1, N, and N + 1 are generated as test data, and a certain range of integers When (M to N) is an effective input value, a rule is described that four types of data M-1, M, N, and N + 1 are generated as test data.

  The test data generation unit 16 generates appropriate test data for each operation component registered in the operation component storage device 13 based on the information registered in the design information storage device 14 and the test pattern storage device 15. Generate (step ST7). Details of step ST7 are shown in FIG. Referring to FIG. 9, the test data generation unit 16 sequentially takes out the operation components from the operation component storage device 13 (steps ST7-1 and ST7-2), and the corresponding design from the design information storage device 14 for each operation component. Information (operation contents and restrictions) is extracted (step ST7-3). Then, test pattern information is sequentially extracted from the test pattern storage device 15 (steps ST7-4 and ST7-5), and test data is generated according to the design information extracted in step ST7-3 (step ST7-6). For example, when an operation component (text box) having an ID of 3 in an operation component registered in the operation component storage device 13 as shown in FIG. 18 described later is selected, the design information storage device 14 is used as design information of the operation component. "Input (integer (1-100)" is extracted from the design information registered in FIG. 7, and this design information indicates that "an integer value of 0 to 100 is a valid input value". Therefore, based on the test pattern of the limit value test of FIG. 8 registered in the test pattern storage device 15, as shown in FIG. 10 as test data, “−1”, “0”, “100”, “101” Is generated.

  Next, the test case generation unit 17 generates a test case based on the test data generated by the test data generation unit 16 (step ST8). Details of step ST8 are shown in FIG. Referring to FIG. 11, the operation components are sequentially extracted from the operation component storage device 13 (ST8-1, ST8-2), and the test data generated by the test data generation unit 16 is combined with each operation component (ST8). -3, ST8-4), generate a test case (ST8-5). FIG. 12 is a test case generated for the window of FIG. In the window of FIG. 4, since there are only two operation components and each effective operation is only a single click, a test case for performing a single click operation on each menu is generated. Further, for example, when a test pattern registered in the test pattern storage device 15 is registered with a logic of a pattern for testing an operation method such as “drag and drop” such as “test by a different operation method using a pointing device”, FIG. A test case like 13 is generated. In the test case ID, a value for identifying different operations on the same operation component is set. The validity in FIGS. 12 and 13 is a flag indicating whether or not the test item is a test item for setting a valid value for each operation component. Indicates an abnormal test. The transition destination window ID field is a column for setting the transition destination window ID when the execution result of the test case is a transition to a new window screen, etc., and all are null at this point. . The generated test case is stored in the test case storage device 18.

  The program control unit 11 resets the test target program 1 once, reads out the test cases stored in the test case storage device 18 one by one, and loads the test target program 1 every time one test case is finished. Run multiple test cases in sequence while resetting. The execution result of each test case is output to the output means 2 and stored in the test result storage device 19 together with the test case information. The user can find a bug in the program by outputting the test result stored in the test result storage device 19 from the output means 2 and referring to it. In other words, a bug in the program under test 1 was found by confirming that an error was recorded as an output result even though it was a normal test, or that an error was not recorded even though it was an abnormal test can do.

  Also, when the execution result of each test case is a transition to a new window screen, or when an operation component is added or deleted in the same window, or the size or position is changed, it is stored in the test case storage device 19 The window ID serving as a flag indicating that is set in the transition destination window ID field in the test case information of FIG. 12 and FIG. The state where the flag is raised is shown in FIG. In the case of the window of FIG. 4, as a result of executing the operations on the menus 102 and 103, new windows are generated as shown in FIGS. 15 and 16, respectively. Accordingly, these results are stored in the test result storage device 19, and after the test cases stored in the test case storage device 18 are completely executed, a new transition is made from the information stored in the test result storage device 19. Or a test case in which there is a change to the operation component is called and the operation component detector 12 detects the test case. That is, the program control unit 11 once resets the test target program 1 and then makes an existing test in which a transition is made until the new window screen becomes active so that the new window screen becomes the test target. The case is extracted and executed, and the processing from step ST2 is recursively repeated for this active window screen.

  The window information, operation component information, and test case information generated when the test case execution for the window of FIG. 15 is completed are as shown in FIGS. 17, 18, and 19, respectively. When the program control unit 11 performs a program test based on the test case information shown in FIG. 19, first, the operation of Click () is performed on the menu 102 for the window 100 having the window ID of 1, and as a result, the window ID Each operation is performed on the operation components 201 to 206 with respect to the second window 200. The operation is performed by combining test cases for each operation component. At this time, all the operations on the operation components (201 to 204) where no transition occurs are performed first, and the operation is performed on the operation components (205 or 206) where the transition occurs thereafter. When the operation component ID is 7 and the test case ID is a, a new window 300 is generated in which a table is added to the window 100 as shown in FIG. Stored as window information and operation component information. At this time, since the base window is the same for the window 100 and the window 300, the ID is given a branch number. FIG. 21 and FIG. 22 show the updated window information and operation component information.

  Thereafter, the test ends when the user gives an instruction to stop the test, reaches a stage determined by the user in advance, or when all test cases have been executed.

It is a block diagram which shows the structure of embodiment of this invention. It is a figure which shows the example of a transition of the output screen of a to-be-tested program. It is a flowchart which shows operation | movement of embodiment of this invention. It is a figure which shows the example of a screen display of a to-be-tested program. It is a figure which shows the example of the content of window information. It is a figure which shows the example of the content of operation component information. It is a figure which shows the example of the content of design information. It is a figure which shows the example of the content of a test pattern. It is a flowchart which shows the process example of a test data generation part. It is a figure which shows the example of the content of the test data produced | generated. It is a flowchart which shows the process example of a test case production | generation part. It is a figure which shows the example of the content of the test case produced | generated. It is a figure which shows the example of the content of the test case produced | generated. It is a figure which shows the example of the content of the test case produced | generated. It is a figure which shows the example of a screen display of a to-be-tested program. It is a figure which shows the example of a screen display of a to-be-tested program. It is a figure which shows the example of the content of window information. It is a figure which shows the example of the content of operation component information. It is a figure which shows the example of the content of the test case produced | generated. It is a figure which shows the example of a screen display of a to-be-tested program. It is a figure which shows the example of the content of window information. It is a figure which shows the example of the content of operation component information.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Program to be tested 2 ... Output means 10 ... GUI program test support device 11 ... Program control unit 12 ... Operation component detection unit 13 ... Operation component storage device 14 ... Design information storage device 15 ... Test pattern storage device 16 ... Test data Generation unit 17 ... Test case generation unit 18 ... Test case storage device 19 ... Test result storage device 20 ... Design information input device 21 ... Test pattern input device 100 ... Window 101 ... Window title 102 ... Menu 103 ... Menu 200 ... Window 201 ... Text box 202 ... List box 203 ... Check box 204 ... Check box 205 ... Button 206 ... Button 300 ... Window

Claims (5)

A program under test, which is an interactive program that performs input / output operations using a GUI. If you do not operate an operation component that generates a screen transition after entering a value in the operation component that does not generate a screen transition, the screen is displayed in the next state. In the program test support device that supports the test of the program under test that does not transition,
Design information storage means for storing design information describing information regarding the types of effective operations and input value conditions for the operation components included in the output screen of the test target program;
Test pattern storage means for storing a test pattern describing a generation rule of test data;
Operation component detection means for detecting an operation component present on an output screen to be tested by the test target program;
Operation component storage means for storing information of the operation component detected by the operation component detection means;
For the operation component stored in the operation component storage means, information regarding the type of effective operation and input value condition for the operation component stored in the design information storage means, and test data stored in the test pattern storage means A test data generating means for generating test data based on the generation rules of
Of the operation components stored in the operation component storage unit, test data generated by the test data generation unit for operation components that do not generate screen transitions and generated by the test data generation unit for operation components that generate screen transitions That generates only test cases that are combined with the test data so that operations on operation components that do not cause screen transitions are performed earlier in time than operations on operation components that cause screen transitions Case generation means;
Test case storage means for storing the test case generated by the test case generation means;
Means for starting and ending the test target program using the function of the execution environment of the test target program, and for operating the operation component existing on the output screen of the test target program, the test case storage means For each of the read test cases, reset the test target program before starting execution of the test case, and then operate the test target program based on the test case. Program control means for performing operations on parts;
And a test result storage unit for storing a test result including a new output screen output from the test target program in which an operation on an operation component is executed by the program control unit.   2. The program test support apparatus according to claim 1, wherein the test data generation means generates both normal test data and abnormal test data.   3. The program test support apparatus according to claim 1, wherein a new output screen stored in the test result storage means is set as an output screen to be tested, and the test is recursively repeated. A program under test, which is an interactive program that performs input / output operations using a GUI. If you do not operate an operation component that generates a screen transition after entering a value in the operation component that does not generate a screen transition, the screen is displayed in the next state. Is a program test support device for supporting a test of a program under test in which no transition occurs, and describes information about the types of effective operations and conditions of input values included in the output screen of the program under test Design information storage means for storing the designed design information, test pattern storage means for storing a test pattern describing a generation rule of test data, operation component storage means for storing information of detected operation parts, and Test case storage means for storing test cases and test result storage means for storing test results A program test support method in the program test support equipment,
a) a step in which an operation component detection unit of the program test support device detects an operation component existing on an output screen to be tested by the test target program, and stores information on the detected operation component in the operation component storage unit; ,
b) The test data generation means of the program test support device, with respect to the operation parts stored in the operation part storage means, the conditions of valid operation types and input values for the operation parts stored in the design information storage means Generating test data on the basis of the information regarding and the test data generation rules stored in the test pattern storage means;
c) a test case generation unit of the program test support device, wherein test data generated by the test data generation unit for an operation component that does not cause a screen transition among the operation components stored in the operation component storage unit; For operation parts that generate transitions, the test data generated by the test data generation means is operated in time before the operation to operation parts that generate screen transitions. Generating only test cases combined to be implemented,
d) Program control means of the program test support apparatus that uses the function of the execution environment of the test target program to start and end the test target program and to operate an operation component existing on the output screen of the test target program However, the test case is read from the test case storage means, and for each of the read test cases, the test target program is temporarily reset before the execution of the test case, and then the test case is stored. A step of executing an operation on the operation component of the test target program and storing a test result including a new output screen output from the test target program in the test result storage unit;
A program test support method comprising: A program under test, which is an interactive program that performs input / output operations using a GUI. If you do not operate an operation component that generates a screen transition after entering a value in the operation component that does not generate a screen transition, the screen is displayed in the next state. Is a program test support device for supporting a test of a program under test in which no transition occurs, and describes information about the types of effective operations and conditions of input values included in the output screen of the program under test Design information storage means for storing the designed design information, test pattern storage means for storing a test pattern describing a generation rule of test data, operation component storage means for storing information of detected operation parts, and Test case storage means for storing test cases and test result storage means for storing test results The computer on which you want to configure the program test support equipment,
An operation component detection unit that detects an operation component existing on an output screen to be tested by the test target program and stores information on the detected operation component in the operation component storage unit;
For the operation component stored in the operation component storage means, information regarding the type of effective operation and input value condition for the operation component stored in the design information storage means, and test data stored in the test pattern storage means Test data generation means for generating test data based on the generation rules of
Of the operation components stored in the operation component storage unit, test data generated by the test data generation unit for operation components that do not generate screen transitions and generated by the test data generation unit for operation components that generate screen transitions That generates only test cases that are combined with the test data so that operations on operation components that do not cause screen transitions are performed earlier in time than operations on operation components that cause screen transitions Case generation means,
d) means for starting and ending the test target program using the function of the execution environment of the test target program, and for operating the operation component existing on the output screen of the test target program, the test case storage means For each of the read test cases, the test target program is reset once before starting execution of the test case, and then the test target program is based on the test case. Program control means for executing an operation on the operation part of the test part and storing a test result including a new output screen output from the test target program in the test result storage means,
Program to function as.

Images