JP2008040537A - Gui test support system and application program for test support - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a GUI test support system which is mounted with two systems of operation recording/reproducing functions of a Windows GUI and a Web GUI, and fully exhibits user-friendliness by switching the recording/reproducing state of both functions depending on an operation object. <P>SOLUTION: The GUI test support system is provided with: an OS1; a test execution tool 3 for executing an application program 2 having a Windows GUI and a Web GUI to be tested and executing the test of the application program in an object description system; and a storage device 4 for storing test scripts acquired by the test execution tool 3. The test execution tool 3 is provided with: GUI operation recording parts 10a and 11a for respectively storing the Windows GUI and the Web GUI operation progress as scripts; a script merge processing part 12b for merging and storing the respective scripts; and GUI operation reproduction parts 10b and 11b for reproducing each of the Windows GUI and the Web operation progress by using the merged and stored scripts. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a GUI (Graphical User Interface) test support system and a test support application program used in the system, and in particular, a mixture of a Windows (registered trademark) GUI and a web GUI without impairing the maintainability of a script. The present invention relates to a GUI test support system and a test support application program for realizing script recording and reproduction.

  With recent advances in computer technology, the scale of system development using computers has become enormous, and as a result, application development has become more complex. For this reason, in order to keep the quality of the application to be used high, the number of man-hours required for the test process increases and becomes complicated, and the importance of the test tends to increase without stopping. It is in.

  In such a background where the application is placed, automating application testing reduces human error and, as a result, is highly reliable and compared to manual operation. Therefore, applying an execution tool based on an automated test is an extremely effective means even when testing an application having a GUI. In particular, when testing an application having a GUI, once the history of the test operation performed by the user previously is recorded in the recording unit, and the recorded content is filed in the form of a test script, the application is subsequently used. Even when remodeling, by automatically replaying the test script filed in the past, it is possible to confirm that there is no defect in the existing part even if remodeling is performed without increasing the number of test steps. Have advantages.

  Recently, a program test support apparatus disclosed in Japanese Patent Laid-Open No. 2000-112784 has been proposed as means for applying an automatic test execution tool when testing an application having a GUI.

  The program test support apparatus disclosed in Japanese Patent Application Laid-Open No. 2000-112784 is based on an operation recording unit 20 that records user input operations on a program under test as operation procedure data, and operation procedure data recorded in the operation recording unit 20. A test data editing unit 30 that extracts input items of input operations and sets one or more input values for each input item, and a test case generation unit 40 that automatically generates a plurality of test cases by combining the set input values. Then, the input value of the input item of the operation procedure data recorded in the operation recording unit 20 is replaced with the input value of each test case to generate new operation procedure data for each test case, and the generated new operation procedure An operation playback unit 60 for testing a program under test based on data, and an input value for each test case after the test of the program under test A test result analysis / evaluation unit 70 that performs evaluation, and various test patterns are easily generated by appropriately changing one or more input values for each input item by script editing. Is used to automatically execute the test of the program under test.

  In general, it is known that a GUI test automatic execution program can be roughly classified into two types, an object description method and a coordinate axis description method, as scripts for describing operations for automatically executing tests. In this case, as the object description method, for example, when the button A whose center coordinates are located at (100, 200) is represented as a click operation, an expression based on the object “click button A” is used. In the coordinate axis description method, when the button A whose center coordinates are located at (100, 200) is represented as a click operation, an expression based on the coordinates “click (100, 200)” is used.

By the way, as an automatic test execution tool for performing a GUI test, it is not affected by the change in the control arrangement coordinates of the target application, and it is easy to understand what operation was performed when the user saw the script. It is preferable to use an object description method. In this case, the object description method is classified into two types, a Windows system and a web system. The reason is that the concept of object recognition is fundamentally different between the Windows system and the Web system, and the automatic execution tool for performing the GUI test is generally intended for the Windows system or the Web system. Each one is used exclusively.
JP 2000-112784 A

  In the object description method classified into two types, the Windows system and the web system, as in the program test support apparatus disclosed in Japanese Patent Application Laid-Open No. 2000-112784, a dedicated system for either the Windows system or the web system is used. GUI test automatic execution tools exist, but in reality, many web applications also use dialogs and Windows applications. When a series of operations are performed, the Windows system and the web system However, it cannot handle the operation.

  In other words, if the object description method is used, the readability and maintainability of the script are high. Therefore, even if an attempt is made to realize an automatic test execution script using the object description method, the operation part dedicated to the Windows GUI operation and the Web GUI operation are used. Since dedicated operation parts are mixed and their operations are restricted by operations of other systems, the convenience of the GUI test automatic execution tool cannot be fully exhibited.

  The present invention has been made in view of such a technical background, and an object of the present invention is to implement two systems of an operation recording / reproducing function for a Windows GUI and an operation recording / reproducing function for a web GUI. It is an object of the present invention to provide a GUI test support system that can fully exhibit convenience by switching the recording / reproducing state of both functions while monitoring whether the GUI is the same.

  In order to achieve the above object, a GUI test support system according to the present invention includes an OS, an input operation unit controlled by the OS, an OS-based GUI to be tested, and an application program having a web GUI, and a test of the application program. Is executed according to the object description method, and a storage device having a test script file for storing the test script obtained by the test execution tool. OS-based GUI operation recording / reproducing function having an OS-based GUI operation recording unit stored as a script in the test script file, an OS-based GUI operation reproducing unit reproducing the OS-based GUI operation history stored in the test script file, and an input operation Web GUI operation recording / playback function having a web GUI operation playback section for reproducing the web GUI operation history stored in the test script file and a web GUI operation playback section for storing the web GUI operation history by the test script file as a script, and an OS system GUI A test management unit that manages the operation recording / reproducing function and the web GUI operation / reproducing function, and a test merge unit that merges the OS GUI operation history and the web GUI operation history stored in the test script file and stores them in the test script file It has an automatic execution manager function.

  A test support application program having an OS GUI and a web GUI for executing a GUI test support system for achieving the above object according to an object description method, wherein the OS system GUI operation history based on an input operation unit is scripted. As a first means for storing in the test script file, a second means for storing the web GUI operation history based on the input operation unit as a script in the test script file, and recorded in the OS GUI operation recording unit under the control of the test management unit Test based on the third means for reproducing the OS system GUI operation history, the fourth means for reproducing the web GUI operation history recorded in the web GUI operation recording section under the control of the test management processing section, and the control of the script merge processing section Each stored in a script file It was merged and OS-based GUI operation history and web GUI operating history are those selectively executing a fifth means for storing the test script file.

  As described above, according to the GUI test support system of the present invention and the test support application program having the Windows (OS system) GUI and the web GUI for executing the GUI test support system according to the object description method, the Windows GUI, the web Regardless of the type of GUI, it is possible to automatically execute a script test using the object description method. By using the object description method, the layout of the test target GUI is changed compared to the case where the coordinate axis description method is used. There is no need to re-edit scripts previously recorded or re-record GUI operation procedures every time, and it is possible to handle both Windows and web systems, so it has excellent maintainability. Target of test automation Can be enlarged, there is an effect that it is possible to improve the quality of productivity improvement and application in the development of applications.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 relates to an embodiment of a GUI test support system according to the present invention, and is a block diagram showing the configuration of the main part thereof. This GUI test support system is realized by using hardware resources in a computer system. It is what is done.

  As shown in FIG. 1, the GUI test support system includes a Windows OS (operating system) 1, a test target GUI group 2 in which a GUI application program to be tested is stored, and a GUI application program to be tested. The GUI test automatic execution tool 3 for executing the above test, the storage device 4 containing the test script file, the keyboard 5 and the mouse 6 which are input operation devices, and the display 7 which is a display device. Here, the Windows OS 1 is coupled to the test target GUI group 2, the GUI test automatic execution tool 3, the keyboard 5, the mouse 6, and the display 7, and the GUI test automatic execution tool 3 is coupled to the storage device 4.

  The test target GUI group 2 includes a Windows form 8 that includes a Windows GUI 8a and a web browser 9 that includes a web GUI 9a. The GUI test automatic execution tool 3 includes a Windows GUI operation recording / reproducing function 10 having a Windows GUI operation recording unit 10a and a Windows GUI operation reproducing unit 10b, a web GUI operation recording unit 11a, and a web GUI operation reproducing unit 11b. And a test automatic execution manager function 12 having a test management unit 12a and a script merge processing unit 12b. Further, the storage device 4 includes a Windows GUI test script file 13a, a web GUI test script file 13b, and a test script file 13c.

  In this case, the outline of the test operation executed by the GUI test automatic execution tool 3 and the storage device 4 will be described. When the input operation to the Windows GUI is performed, the Windows GUI operation recording unit 10a records the input operation content. The recorded input operation contents are temporarily stored as a test script in the order in which they are operated in the Windows GUI test script file 13a. The Windows GUI operation / playback unit 10b operates so as to reproduce the input operation for the Windows GUI recorded in the Windows GUI test script file 13a when a playback operation for the Windows GUI is instructed.

  The web GUI operation recording unit 11a records the input operation content when an input operation is performed on the web GUI, and the operation order of the recorded input operation content as a test script on the web GUI test script file 13b. According to the temporary storage. The web GUI operation playback unit 11b operates to reproduce the input operation for the Windows GUI recorded in the Windows GUI test script file 13b when a playback operation for the Windows GUI is instructed.

  Further, the test management unit 12a manages input operation reproduction processing performed by the web GUI operation reproduction unit 10b and the web GUI operation reproduction unit 11b, and the script merge processing unit 12b includes a test script file for Windows GUI. 13a and the web GUI test script file 13b are combined, and the combined script is operated to be stored in the test script file 13c.

  The operation of the GUI test support system configured as described above is as follows.

  First, when the user performs activation processing of a GUI application program stored in the test target GUI group 2, the GUI application program is activated under the control of the Windows OS 1 and an input operation screen is displayed on the display 7.

  FIG. 2 is an example showing an input operation screen displayed on the display 7 at this time and an event operation that occurs inside the OS when operated.

  When such an input operation screen is displayed, when the user clicks the button A according to the operation instruction on the input operation screen, the Windows OS 1 generates an event message (a) corresponding to the operation performed by the user inside the OS. To do. At this time, in the GUI test automatic execution tool 3, the Windows GUI operation recording unit 10a reads the event message (a) at the time of this operation, and temporarily stores it in the Windows GUI test script file 13a in the form of a script.

  FIG. 3 is an example showing an operation concept in which the GUI test automatic execution tool 3 automatically executes the GUI application program using the recorded script file.

  The GUI test automatic execution tool 3 reproduces the operation in which the button A is clicked by reading the saved script file and generating the corresponding event message (b).

  FIG. 4 is a flowchart showing a processing procedure when the user performs operations in the order of the Web GUI 9a → Windows GUI 8a → Web GUI 9a in accordance with an instruction on the input operation screen in the GUI test automatic execution tool 3 thereafter.

  The operation recording operation performed by the GUI test automatic execution tool 3 will be described below according to this flowchart.

  First, in step S1, upon receiving a recording start operation from the user, the automatic test execution manager function 12 activates the Windows GUI operation recording / reproducing function 10 and the web GUI operation recording / reproducing function 11 through the test management unit 12a.

  Next, in step S2, when the user operates the GUI application program stored in the test target GUI group 2, the automatic test execution manager function 12 performs the Windows GUI operation of the activated Windows GUI operation recording / playback function 10. The recording GUI 10a and the web GUI operation recording processing unit 11a of the activated web GUI operation recording / reproducing function 11 correspond to the user's operation history in the form of a script, respectively, a Windows GUI test script file 13a or a web GUI test script file 13b. To store.

  Next, in step S3, it is determined whether or not the user has completed a series of operations on the GUI application program and the user has pressed a hot key for stopping operation recording. When it is determined that the hot key has been pressed (Y), the process proceeds to the next step S4. On the other hand, when it is determined that the hot key has not been pressed (N), the processing of step S2 and step S3 is repeatedly executed in the recording stop command waiting loop.

  Subsequently, in step S4, the test automatic execution manager function 12 stops the operations of the Windows GUI operation recording / reproducing function 10 and the web GUI operation recording / reproducing function 11.

  Thereafter, in step S5, the automatic test execution manager function 12 merges the script stored in the Windows GUI test script file 13a and the script stored in the web GUI test script file 13b, and the merged script is used as a test script file. 13c. When this process ends, this series of operation recording processes ends.

  Next, FIG. 5 is a flowchart showing details of the operation executed by the Windows GUI operation recording unit 10a of the Windows GUI operation recording / reproducing function 10 during operation history recording, and corresponds to step S2 shown in FIG. Is.

  First, in step S10, when the user starts an operation on the GUI application program, the Windows GUI operation recording unit 10a determines whether the source of the Windows message generated internally by the operation is the web GUI 9a. To do. When it is determined that the source of the Windows message is not the web GUI 9a but the Windows GUI 8a (N), the process proceeds to the next step S11. On the other hand, when the source of the Windows message is determined to be the Web GUI 9a (Y) Shifts to another step S13.

  Next, in step S11, since the source of the Windows message is the Windows GUI 8a, the obtained Windows message is stored in a memory buffer which is a temporary work area (not shown). This process corresponds to recording the operation history of the Windows GUI.

  Next, in step S <b> 12, the Windows GUI operation recording unit 10 a determines whether or not an end command indicating the end of the user operation is received from the test automatic execution manager function 12. When it is determined that the reception end command has not been received (N), the processing of steps S10 to S12 for monitoring the arrival of the Windows message is repeatedly executed. On the other hand, when it is determined that a reception end command has been received (Y), the process proceeds to another step S18.

  On the other hand, in step S13, since the source of the Windows message is the web GUI 9a, the Windows GUI → Web GUI switching command is stored in the memory buffer.

  Next, in step S <b> 14, the Windows GUI operation recording unit 10 a determines whether or not an end command indicating the end of the user operation is received from the test automatic execution manager function 12. When it is determined that a reception end command has not been received (N), the process proceeds to the next step S15, and when it is determined that a reception end command has been received (Y), the process proceeds to another step S18.

  Next, in step S15, the Windows GUI operation recording unit 10a determines whether or not the transmission source of the Windows message is the web GUI 9a. When it is determined that the source of the Windows message is not the web GUI 9a but the Windows GUI 8a (N), in step S16, a web GUI → Windows GUI switching command is transmitted to the web GUI operation recording / reproducing function 11. On the other hand, when it is determined that the source of the Windows message is the web GUI 9a (Y), the processes in steps S14 to S15 are repeatedly executed in the Windows message reception loop.

  Subsequently, in step S17, since the source of the Windows message is the Windows GUI 8a, the Windows GUI operation recording unit 10a stores the web GUI → Windows GUI switching instruction in the memory buffer, and proceeds to the process of step S10.

  Finally, in step S18, the Windows GUI operation recording unit 10a has received an end command from the test automatic execution manager function 12, so that the operation information stored in the memory buffer so far is stored in the form of a script as a test script file for Windows GUI. When the data is stored in 13a and this process ends, the series of processes ends.

  FIG. 6 is a flowchart showing details of the operation executed by the web GUI operation recording unit 11a of the web GUI operation recording / reproducing function 11 during operation history recording, and corresponds to step S2 shown in FIG. is there. This operation is executed in parallel with the operation illustrated in FIG.

  First, in step S20, when an operation for the GUI application program by the user is started, the web GUI operation recording unit 11a accumulates the web browser event generated inside in the memory buffer. This process corresponds to recording the operation history of the web GUI.

  Next, in step S <b> 21, the web GUI operation recording unit 11 a determines whether or not an end command indicating the end of the user operation is received from the test automatic execution manager function 12. When it is determined that the end instruction has not been received (N), the process proceeds to the next step S22, whereas when it is determined that the end instruction has been received (Y), the process proceeds to another step S24.

  Next, in step S22, the web GUI operation recording unit 11a determines whether or not a web GUI → Windows GUI switching command from the Windows GUI operation recording / reproducing function 10 has been received. When it is determined that the web GUI → Windows GUI switching command has been received (Y), the process proceeds to the next step S23, and when it is determined that the web GUI → Windows GUI switching command has not been received (N). The processing of step S20 to step S22 for monitoring the reception of the end command or the web GUI → Windows GUI switching command is repeatedly executed.

  Subsequently, in step S23, the web GUI operation recording unit 11a accumulates the transition switch command from the web GUI to the Windows GUI in the memory buffer. When the accumulation is performed, the web GUI operation recording unit 11a receives the transition switch command from the web GUI to the Windows GUI. The processing of step S20 to step S22 for monitoring is repeatedly executed.

  Finally, in step S24, the web GUI operation recording unit 11a receives an end command from the automatic test execution manager function 12, and thus the operation information accumulated in the memory buffer so far is stored in the form of a script in the web GUI test script. Store in file 13b. When this storage process ends, this series of processes ends.

  Next, it is output from the Windows GUI operation recording unit 10a and the web GUI operation recording unit 11a described with reference to the flowcharts shown in FIGS. 5 and 6, and is output to the Windows GUI test script file 13a and the Web GUI test script file 13b, respectively. A merge process executed by the script merge processing unit 12b based on the stored test script file will be described.

  FIG. 7 shows an example of an image of the test script file stored in the Windows GUI test script file 13a in step S18 of the flowchart shown in FIG. 5, and this image is transferred from the web GUI 9a to the Windows GUI 8a to the web GUI 9a. An example when each switching is performed by a user operation is shown.

  The main operation flow executed by the Windows GUI operation recording unit 10a when the test script file is output by this user operation is as follows: Step S10 → Step S13 (form script data 13a01) → Step of the flowchart shown in FIG. Step S14 → Step S15 → Step S16 → Step S17 (form script data 13a02) → Step S10 → Step S11 (form script data 13a03) → Step S12 → Step S10 → Step S13 (form script data 13a04) → From step S14 to step S18, the operation history at this time is described in the test script file 13a for Windows GUI.

  FIG. 8 shows an example of an image of the test script file stored in the web GUI test script file 13b in step S24 of the flowchart shown in FIG. 6. This image is the web GUI 9a → Windows GUI 8a → Web. The example when each switch to GUI9a is performed by user operation is shown.

  The main operation flow executed by the web GUI operation recording unit 11a when the test script file is output by this user operation is step S20 (forms script data 13b01) in the flowchart shown in FIG. 6 → step S21 → step Step S22 → Step S23 (form script data 13b02) → Step S20 (form script data 13b03) → Step S21 → Step S24, and the operation history at this time is described in the web GUI test script file 13b.

  Next, FIG. 9 is a flowchart showing the operation history of the script merge processing unit 12b included in the test automatic execution manager function 12 at the time of operation recording, and corresponds to the process of step S5 shown in FIG. . These operations are executed by the script merge processing unit 12b.

  First, in step S30, the script merge processing unit 12b opens the Windows GUI test script file 13a and the web GUI test script file 13b.

  In step S31, the script merge processing unit 12b reads only one line of the script file of the Windows GUI test script file 13a.

  In step S32, the script merge processing unit 12b determines whether the read script file is the end of the file. When it is determined that it is not the end of the file (N), the process proceeds to the next step S33, and when it is determined that it is the end of the file (Y), the process proceeds to another step S39.

  In step S33, the script merge processing unit 12b adds the contents of the read file to the memory buffer.

  In step S34, the script merge processing unit 12b determines whether the read one line is a Windows GUI → Web GUI switching instruction. When it is determined that the instruction is a Windows GUI → Web GUI switching instruction (Y), the process proceeds to a reading loop of the Web GUI test script file 12b, while when it is determined that the instruction is not a Windows GUI → Web GUI switching instruction (N). Repeats the processing from step S31 to step S34.

  In step S35, the script merge processing unit 12b reads only one line of the script file of the web GUI test script file 13b this time because the operation object has moved to the web GUI 9a.

  Next, in step S36, the script merge processing unit 12b determines whether or not the read script file is the end of the file. When it is determined that it is not the end of the file (N), the process proceeds to the next step S37, and when it is determined that it is the end of the file (Y), the process proceeds to a reading loop for the Windows GUI test script file 12a.

  Next, in step S37, the script merge processing unit 12b determines whether the read one line is a web GUI → Windows GUI switching instruction. When it is determined that the instruction is a Web GUI → Windows GUI switching instruction (Y), the process proceeds to a reading loop of the Windows GUI test script file 12a, while when it is determined that the instruction is not a Web GUI → Windows GUI switching instruction (N). Shifts to the next Step S38.

  In step S38, the script merge processing unit 12b adds the contents of the read file to the memory buffer. When this process is completed, the processes from step S35 to step S37 are repeatedly executed.

  Finally, in step S39, the script merge processing unit 12b has finished reading through the script files of the Windows GUI test script file 12a and the GUI test script file 12b, and has detected that each is the end of the script file. The contents of the memory buffer are output to and stored in the test script file 13c, and when this process is performed, this series of processes ends.

  FIG. 10 shows an example of an image of a test script file stored in the test script file 13c formed in the script merge processing unit 12b according to the flowchart shown in FIG. 9, and this image is a web GUI 9a → Windows GUI 8a → An example when each switching to the web GUI 9a is performed by a user operation is shown.

  The main operation flow executed by the script merge processing unit 12b when the test script file 13c is output is step S30 → step S31 → step S32 → step S33 (forms script data 13c01) in the flowchart shown in FIG. ) → Step S34 → Step S35 → Step S36 → Step S37 → Step S38 (form script data 13c02) → Step S35 → Step S36 → Step S37 → Step S31 → Step S32 → Step S33 (form script data 13c03) → Step S34 → Step S31 → Step S32 → Step S33 (form script data 13c04) → Step S34 → Step S31 → Step S32 → Step S3 (Form script data 13c05) → step S34 → step S35 → step S36 → step S37 → step S38 (form script data 13c06) step S35 → step S36 → step S31 → step S32 → step S39. The operation history is described in the test script file 13c.

  Next, the operation history of the test automatic execution manager function 12, the Windows GUI operation recording / playback function 10, and the web GUI operation recording / playback function 11 during GUI operation playback will be described with reference to flowcharts.

  FIG. 11 is a flowchart showing the operation history during the operation reproduction of the test management unit 12a in the automatic test execution manager function 12. The operation at the time of operation reproduction of the test management unit 12a will be described using this flowchart.

  First, when the GUI test automatic execution tool 3 receives an instruction for a reproduction start operation from the user, the automatic test execution manager function 12 controls the Windows GUI operation recording / reproducing function 10 and the web GUI operation recording / reproducing function in step S40. 11 is activated.

  Next, in step S41, the test automatic execution manager function 12 determines whether the started Windows GUI operation playback unit 10b and the web GUI operation playback unit 11b are based on the GUI operation by the user stored in the test script file 13c. Reproduce the GUI operation history.

  Next, in step S42, the test automatic execution manager function 12 determines whether or not reproduction of a series of GUI operation details by the Windows GUI operation reproduction unit 10b and the web GUI operation reproduction unit 11b has been completed. When it is determined that reproduction of a series of GUI operation details has not been completed (N), reproduction of the same GUI operation details is executed until reproduction of a series of GUI operation details is completed, while a series of GUI operation details is reproduced. When it is determined that the reproduction of the GUI has been completed (Y), the reproduction of the GUI operation history is terminated.

  FIG. 12 is a flowchart showing the operation history of the Windows GUI operation / playback unit 10b during operation / playback in the Windows GUI operation recording / playback function 10, and the operation history of the Windows GUI operation / playback unit 10b during operation / playback according to this flowchart. explain.

  This flowchart shows an example in which the user operation is switched in the order of the web GUI 9a → Windows GUI 8a → web GUI 9a in the script file of the test script file 13c. And is executed by the Windows GUI operation / playback unit 10b.

  First, in step S50, the Windows GUI operation / playback unit 10b determines whether or not the first line of the content of the script file read from the test script file 13c is a Windows GUI → Web GUI switching command. When it is determined that it is not a Windows GUI → Web GUI switching instruction (N), the process proceeds to step S51 in the Windows GUI operation playback loop, while when it is determined that it is a Windows GUI → Web GUI switching instruction (Y), etc. The process proceeds to step S54.

  Next, in step S51, the Windows GUI operation playback unit 10b executes playback of the operation on the Windows GUI 8a according to the contents of the script file in the test script file 13c.

  Next, in step S52, the Windows GUI operation / playback unit 10b determines whether there is a Windows GUI → Web GUI switching command in the contents of the script file. When it is determined that there is a Windows GUI → Web GUI switching command (Y), the process proceeds to the next step S54. On the other hand, when it is determined that there is no Windows GUI → Web GUI switching command (N), other steps are performed. The process proceeds to S53.

  Subsequently, in step S53, the Windows GUI operation / playback unit 10b determines whether the content of the script file in the test script file 13c has reached the end. When it is determined that the terminal has not been reached (N), the process returns to step S51. On the other hand, when it is determined that the terminal has been reached (Y), this series of operation reproduction operations is terminated.

  In step S54, the Windows GUI operation / playback unit 10b skips the contents of the script file of the test script file 13c until the Windows GUI → Web GUI switching command is read.

  Next, in step S55, the Windows GUI operation / playback unit 10b transmits a Windows GUI → Web GUI switching command to the web GUI operation recording / playback function 11.

  Next, in step S56, the Windows GUI operation / playback unit 10b determines whether the content of the script file in the test script file 13c has reached the end. When it is determined that the terminal has not been reached (N), the process proceeds to a Web GUI → Windows GUI switching command reception loop. On the other hand, when it is determined that the terminal has been reached (Y), this series of operation reproduction operations is performed. Terminate.

  Thereafter, in step S57, the Windows GUI operation / playback unit 10b determines whether or not a web GUI → windows GUI switching command is received from the web GUI operation recording / playback function 11. When it is determined that the Web GUI → Windows GUI switching command has been received (Y), the process proceeds to the Windows GUI operation playback loop, while when it is determined that the Web GUI → Windows GUI switching command has not been received (N). Repeats the same operation until a web GUI → Windows GUI switching command is received.

  Further, FIG. 13 is a flowchart showing the operation history of the web GUI operation / playback unit 11b during operation / playback in the web GUI operation recording / playback function 11. According to this flowchart, the operation history of the web GUI operation / playback unit 10b during operation / playback explain.

  This flowchart shows an example in which the user operation is switched in the order of the web GUI 9a → Windows GUI 8a → web GUI 9a in the script file of the test script file 13c. Is executed in parallel with the operation of the Windows GUI operation / playback unit 10b in the web GUI operation / playback unit 11b.

  First, in step S60, the web GUI operation / playback unit 11b skips the contents of the script file of the test script file 13c until it reads the Windows GUI → Web GUI switching command.

  Next, in step S61, the web GUI operation reproducing unit 11b determines whether or not the content of the script file in the test script file 13c has reached the end. When it is determined that the terminal has not been reached (N), the process proceeds to the Windows GUI → Web GUI switching command reception loop. On the other hand, when it is determined that the terminal has been reached (Y), this series of operation reproduction operations is performed. Terminate.

  Thereafter, in step S62, the web GUI operation / playback unit 11b determines whether a Windows GUI → web GUI switching command is received from the Windows GUI operation recording / playback function 10. When it is determined that a Windows GUI → Web GUI switching command has been received (Y), the process proceeds to a Web GUI operation playback loop, while when it is determined that a Windows GUI → Web GUI switching command has not been received (N). Repeats the same operation until a Windows GUI → Web GUI switching command is received.

  In step S63, the web GUI operation reproduction unit 11b reproduces the operation for the web GUI 9a according to the contents of the script file in the test script file 13c.

  Next, in step S64, the web GUI operation reproduction unit 11b determines whether or not a web GUI → Windows GUI switching instruction exists in the contents of the script file. When it is determined that there is no web GUI → Windows GUI switching instruction (N), the process proceeds to the next step S65. On the other hand, when it is determined that there is a Web GUI → Windows GUI switching instruction (Y), other steps are performed. The process proceeds to S66.

  Next, in step S65, the web GUI operation reproducing unit 11b determines whether or not the content of the script file in the test script file 13c has reached the end. When it is determined that the end has not been reached (N), the process returns to step S63 to repeatedly execute the web GUI operation playback loop. On the other hand, when it is determined that the end has been reached (Y), this series of operation playback operations. End.

  In step S 66, the web GUI operation / playback unit 11 b finds a web GUI → Windows GUI switching command, and transmits a web GUI → Windows GUI switching command to the Windows GUI operation recording / playback function 10. After this processing is performed, the process returns to step S60, and the operations after step S60 are executed again.

  As described above in detail, the GUI test support system according to the present invention has two GUI operation recording / playback functions 10 and 11 specializing in these processes for the Windows GUI 8a and the Web GUI 9a, and controls messages from each other. By transmitting each other, the Windows GUI 8a and the Web GUI 9a can realize a practical level GUI test operation recording / reproducing process using an object description method script.

  Although the embodiment according to the present invention has been described based on the configuration means shown in FIGS. 1 to 13, the GUI test support system according to the present invention is limited to the one expressed in the embodiment. Instead, other equivalent configuration means, for example, a configuration means in which any GUI operation recording / reproducing function also serves as a test automatic execution manager function may be used.

It is a block diagram which concerns on embodiment of the GUI test assistance system by this invention, and shows the principal part structure. It is an example which showed the event operation | movement which generate | occur | produces inside OS when it is operated with the input operation screen displayed on a display. It is an example showing an operation concept in which a GUI test execution tool automatically executes a GUI application program using a recorded script file. It is a flowchart which shows the process sequence when operation is performed in order of Web GUI-> Windows GUI-> Web GUI by the instruction | indication of an input operation screen in a GUI test automatic execution tool. It is a flowchart which shows the detail of the operation | movement performed by the Windows GUI operation recording part of the Windows GUI operation recording / reproducing function at the time of operation history recording. It is a flowchart which shows the detail of the operation | movement performed by the web GUI operation recording part of a web GUI operation recording / reproducing function at the time of operation history recording. 2 shows an example of an image of a test script file stored in a Windows GUI test script file. 2 shows an example of an image of a test script file stored in a web GUI test script file. It is a flowchart which shows the operation | movement history of the script merge process part contained in the test automatic execution manager function at the time of operation recording. An example of an image of a test script file stored in a test script file formed in the script merge processing unit is shown. It is a flowchart which shows the operation | movement history at the time of operation reproduction | regeneration of the test management part in a test automatic execution manager function. It is a flowchart which shows the operation | movement history at the time of operation reproduction | regeneration of the Windows GUI operation reproduction | regeneration part in a Windows GUI operation recording / reproduction function. It is a flowchart which shows the operation | movement history at the time of operation reproduction of the web GUI operation reproduction | regeneration part in a web GUI operation recording / reproduction | regeneration function.

Explanation of symbols

1 Windows OS
2 Test target GUI group 3 GUI test automatic execution tool 4 Storage device 5 Keyboard 6 Mouse 7 Display 8 Windows form 8a Windows GUI
9 Web browser 9a Web GUI
DESCRIPTION OF SYMBOLS 10 Windows GUI operation recording / reproducing function 10a Windows GUI operation recording part 10b Windows GUI operation reproducing part 11 Web GUI operation recording / reproducing function 11a Web GUI operation recording part 11b Web GUI operation reproducing part 12 Test automatic execution manager function 12a Test management part 12b Script Merge processing unit 13a Test script file for Windows GUI 13b Test script file for Web GUI 13c Test script file

Claims (2)

An OS, an input operation unit controlled by the OS, an application program having an OS GUI and a web GUI to be tested, a test execution tool for executing a test of the application program according to an object description method, and the test execution tool And a storage device having a test script file for storing the test script obtained in step (b), wherein the test execution tool stores an OS type GUI operation history by the input operation unit as a script in the test script file. An OS-based GUI operation recording / playback function having an OS-based GUI operation / playback unit for reproducing the OS-based GUI operation history stored in the recording unit and the test script file; Web GUI operation recording / playback function including a web operation recording unit stored as a script in a script file, a Web GUI operation playback unit reproducing the web GUI operation history stored in the test script file, and the OS-based GUI operation recording / playback function, Automatic test execution having a test management unit for managing the web GUI operation reproduction function, and a script merge processing unit for merging the OS GUI operation history and the web GUI operation history stored in the test script file and storing them in the test script file A GUI test support system for automatically testing an application program having an OS GUI and a web GUI, characterized by having a manager function. A test support application program having an OS GUI and a web GUI for executing the GUI test support system according to claim 1 in accordance with an object description method, wherein the OS script operation history based on the input operation unit is used as a script. A first means for storing in the file; a second means for storing the web GUI operation history based on the input operation unit as a script in the test script file; and an OS system recorded in the OS system GUI operation recording unit under the control of the test management unit The third means for reproducing the GUI operation history, the fourth means for reproducing the web GUI operation history recorded in the web GUI operation recording section under the control of the test management processing section, and the control based on the control of the script merge processing section. Store each in test script file OS-based GUI operation history and the web GUI operating history and merging to test support application programs, characterized in that it is intended to be selectively executing a fifth means for storing in said test script file.

Images