JP2011164788A - Device, method and program for verifying operation - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently execute an operation test of an application which is installed in an ERP (Enterprise Resource Planning) package and operates. <P>SOLUTION: An operation verification device 100 in one embodiment obtains a log indicating contents of a series of operation executed to the application operating on a SAP server 402. The operation verification device 100 selects a function corresponding to the operation recorded in the log of a plurality of kinds of functions installed with logic for achieving various kinds of operation to generate a program for the operation test for reproducing the series of operation. The operation verification device 100 executes the program for the operation test, and operates a SAP Gui (Graphical User Interface) client 406 through an add-in 410 for SAP of QTP (Quick Test Professional) 408 in the execution. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for testing the operation of a product.

  In order to guarantee product quality, operational tests before product shipment are indispensable. In general, a test engineer often performs an operation test by manually operating a product and confirming the operation result. However, manual operation tests are limited in the case of multi-function products with abundant operation variations.

  Therefore, it is often the case that the operation test is automatically executed by a test program to save labor of the operation test. For example, an automatic function test tool “QTP (Quick Test Professional)” provided by HP (Hewlett-Packard) Co., Ltd. automates an operation test by executing a test program created by the user.

JP 2004-227396 A

  The present inventor considered that there is a need to efficiently execute an operation test of an application that is embedded in an ERP package and is operating in an enterprise that introduces an ERP (Enterprise Resource Planning) package to improve management efficiency. . However, a specific method for efficiently executing an operation test of an application embedded in an ERP package has not been sufficiently proposed so far.

  The present invention has been completed based on recognition of the above problems of the present inventor, and a main object of the present invention is to provide a technique for efficiently executing an operation test of an application that is incorporated in an ERP package and operates. There is.

  In order to solve the above-described problem, an operation verification apparatus according to an aspect of the present invention is an apparatus for executing a test program for confirming an operation of an application embedded in an ERP package. Select the function corresponding to the operation recorded in the log from the multiple types of functions that incorporate the logic to implement various operations and the log acquisition unit that acquires the log showing the contents of the series of operations executed For a data input operation to the application, by selecting an input function having an interface for acquiring input data to the application, a program generation unit that generates a test program for reproducing a series of operations, Input data acquisition unit that acquires input data to be passed to the input function, and the acquired For on the basis of the force data of the operation check when executing the series of operations comprises a program execution unit for executing a test program passes the acquired input data into the input function, a.

  Another aspect of the present invention is an operation verification method. This method is a method that is executed by a device that executes a test program for confirming the operation of an application that is incorporated in an ERP package, and the contents of a series of operations executed on the application are displayed. Select the function corresponding to the operation recorded in the log from the multiple types of functions that incorporate the steps to obtain the log to be displayed and the logic to implement various operations, and for the data input operation to the application to the application Generating a test program for reproducing a series of operations by selecting an input function having an interface for acquiring input data, acquiring input data to be passed to the input function, and acquiring When a series of operations are executed based on the input data For work confirmation, it comprises the steps of executing the test program passes the acquired input data into the input function, a.

  It should be noted that any combination of the above-described constituent elements and a representation of the present invention converted between an apparatus, method, system, program, recording medium storing the program, etc. are also effective as an aspect of the present invention.

  According to the present invention, it is possible to efficiently perform an operation test of an application that operates by being incorporated in an ERP package.

It is a screen figure of a portal site 1st screen. It is a screen figure of a portal site 2nd screen. It is a figure which shows the log when a dictionary test is performed. It is a figure which shows the program for performing a dictionary test. It is a functional block diagram of an operation verification device. It is an outline figure until it acquires a log and performs an operation test. It is a screen figure of a log screen. It is a screen figure of a function setting screen. It is a screen figure of a program screen. It is a screen figure of an input setting screen. It is a screen figure of a case setting screen. It is a figure which shows the outline | summary of a structure in each of the operation verification apparatus of the reference technique 1, and the operation verification apparatus of the reference technique 2. It is a figure which shows the outline | summary of operation | movement in each of the operation verification apparatus of the reference technique 1, and the operation verification apparatus of the reference technique 2. It is a block diagram which shows the function structure of the operation verification apparatus of the reference technique 2. FIG. In the reference technique 2, it is a schematic diagram until it detects a user's data input operation and performs an operation test. It is a screen figure of the function setting screen in the reference technique 2. It is a screen figure of the function setting screen in the reference technique 2. It is a screen figure of the input setting screen in the reference technique 2. It is a screen figure of the case setting screen in the reference technique 2. It is a figure which shows the system architecture in the operation | movement test of embodiment. It is a figure which shows FIG. 19 in detail. It is a block diagram which shows the function structure of the program execution part of embodiment. It is a figure which shows the example of the function which a user can set in the operation verification apparatus of embodiment. It is a figure which shows the display screen of a GUI component. It is a figure which shows the display screen of a GUI component. It is a figure which shows the collation result of a status message.

  Before describing the operation verification system according to the present embodiment, reference techniques 1 and 2 related to the operation verification apparatus as a premise thereof will be described.

(Reference technology 1)
FIG. 1A is a screen view of the portal site first screen 300.
In Reference Technique 1, an operation test for the portal site “XYZ!” Will be described. The portal site first screen 300 includes an edit box 302 and a search link 304. The search link 304 includes four links of “web”, “blog”, “image”, and “dictionary”. When the user inputs a character string into the edit box 302 and clicks one of the search links 304 with the mouse, the search for the input character string is started. For example, when the character string “liquid crystal” is input to the edit box 302 and the link “web” is clicked with the mouse, a website including the character string “liquid crystal” is searched. When the character string “LCD” is entered in the edit box 302 and the link “blog” is clicked with the mouse, the blog including the character string “LCD” among the blogs (Weblogs) established on this portal site. The page becomes the search target.
Here, it is assumed that the character string “test” is input to the edit box 302 and the link “dictionary” is clicked with the mouse.

FIG. 1B is a screen view of the portal site second screen 310.
When “test” is input on the portal site first screen 300 and “dictionary” is clicked with the mouse, a portal site second screen 310 shown in FIG. 1B is displayed. In the search result column 306, items related to the character string “test” are listed by the “dictionary” service provided by the portal site.
Here, it is assumed that the link “test” at the top of the search result column 306 is clicked with the mouse.

In the above process, the following three operations are performed.
A1. An operation of inputting the character string “test” in the edit box 302 of the portal site first screen 300.
A2. An operation of clicking the link “dictionary” in the search link 304 of the portal site first screen 300 with a mouse.
A3. An operation of clicking the link “test” in the search result column 306 of the portal site second screen 310 with a mouse.
Hereinafter, the operation process realized by the operations of A1 to A3 is referred to as “dictionary test”.

FIG. 2 is a diagram showing the log 320 when the dictionary test is executed.
When a client terminal in which HP QTP is installed is operated to access the portal site and the operations A1 to A3 are executed, QTP generates a log 320 shown in FIG. In the log 320, operations A1 to A3 are recorded as code sentences in a predetermined format.
For example, the operation A1 is
Browser ("XYZ!"). Page ("XYZ!"). WebEdit ("p"). Set "Test"
It is expressed by the code sentence. This corresponds to a web site “XYZ!”, A web page named “XYZ!”, And an edit box named p (corresponding to the edit box 302 shown in FIGS. 1A and 1B). On the other hand, the character string “test” is input.
Similarly, the operation A2 is
Browser ("XYZ!"). Page ("XYZ!"). Link ("Dictionary"). Click
Operation A3 is
Browser ("XYZ!"). Page ("XYZ! -All dictionaries-Test"). Link ("Test"). Click
It is displayed with the code sentence. Reference technology 1 will be described based on the grammar of QTP, but the format of the code sentence is not limited to this.

QTP can reproduce and execute the operation expressed by the code sentence while interpreting the code sentence of the log 320. For this reason, once the log 320 is generated, the dictionary test with the same contents can be repeatedly executed. Further, if a part of the log 320 is rewritten, the dictionary test can be executed with contents different from those at the time of manual operation. For example,
Browser ("XYZ!"). Page ("XYZ!"). WebEdit ("p"). Set "Test"
Change the string "test" contained in to another string "taste"
Browser ("XYZ!"). Page ("XYZ!"). WebEdit ("p"). Set "Taste"
And re-input to QTP, it is possible to automatically execute a dictionary test of the same content in which only the input character string in the edit box 302 is changed.
However, in order to execute the operation test while rewriting the log 320, a certain degree of knowledge about the grammar of the log 320 is required. Further, when the log 320 is rewritten, a human error may occur.

FIG. 3 is a diagram showing a program 330 for executing the dictionary test.
Instead of executing the operation test using the log 320, a test program may be created by describing the content equivalent to the log 320 in a VB (Visual Basic) script or the like. A program 330 shown in FIG. 3 is a test program created with reference to the log 320 of FIG.
For example, the operation A1 is
WebEditSet (Browser ("XYZ!"). Page ("XYZ!"). WebEdit ("p"), DataTable ("p1, dtGlobalSheet")
It is expressed by the VB function. The specific logic of the WebEditSet function is as described in the middle of the figure.

  The program 330 is different from the log 320 in that input data such as the character string “test” is not included in the program 330. Instead, the WebEditSet function receives input data from a file expressed as dtGlobalSheet (hereinafter referred to as “input data file”). That is, logic and input data are separated. By rewriting or replacing input data files, dictionary tests with the same logic can be executed based on various input data. Compared to the operation test by manual operation and the operation test by log 320, the operation test by program 330 has an advantage that it is easy to increase variations of input data.

However, the operation test by the program 330 has the following problems.
d1. There is a new effort to create a program.
d2. The content of the program changes depending on the program creator. For example, the WebEditSet function created by the programmer P1 corresponding to the operation A1 and the WebEditSet function created by the programmer P2 corresponding to the operation A1 do not necessarily have the same logic even though the function names are the same. In addition, bugs may be mixed in the program itself. For this reason, it is necessary to make efforts to ensure the reliability of the program 330 itself. The program 330 also requires logic that is not directly related to the operation test, such as exception processing, but not all programmers implement logic that considers even exception processing. For example, in the case of the WebEditSet function shown in FIG. 3, the logic is set up so that it can cope with the case where the input data is an empty character, but such consideration is lacking when another programmer implements the WebEditSet function. Might do.
As a result, programmer skills are likely to affect the content and results of behavior tests.

FIG. 4 is a functional block diagram of the operation verification apparatus 100.
Each functional block shown in the block diagram of the present specification can be realized in hardware by an element or a mechanical device such as a CPU of a computer, and in software by a computer program or the like. Here, The functional block realized by those cooperation is drawn. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software. For example, each functional block may be stored in a recording medium as a computer program, installed in a hard disk of an information processing device, read into a main memory as appropriate, and executed by a processor.
The operation verification apparatus 100 may be formed as dedicated hardware, or may be formed as a software module that cooperates with a user interface such as a web browser.
The operation verification apparatus 100 of the reference technique 1 will be described as a software module formed as an add-on of QTP.

The operation verification apparatus 100 includes an IF (interface) unit 110, a data processing unit 130, and a data holding unit 140.
The IF unit 110 is in charge of an interface with a user or QTP. The data processing unit 130 executes various data processing based on data acquired from the IF unit 110 and the data holding unit 140. The data processing unit 130 also serves as an interface between the IF unit 110 and the data holding unit 140. The data holding unit 140 is a storage area for holding various data.

IF unit 110:
The IF unit 110 includes an input unit 112 and an output unit 118. The input unit 112 is in charge of input processing from the user and QTP, and the output unit 118 is in charge of output processing for the user and QTP. The input unit 112 includes a log acquisition unit 114 and an input data acquisition unit 116. The log acquisition unit 114 acquires a log from QTP. The input data acquisition unit 116 acquires an input data file and acquires input data to be provided to the program from the input data file. Details of the input data file will be described in detail with reference to FIGS.

  The output unit 118 includes a function setting screen display unit 120, an input setting screen display unit 122, a program screen display unit 124, and a case setting screen display unit 126. The function setting screen display unit 120 displays a function setting screen 210 shown in FIG. The input setting screen display unit 122 displays an input setting screen 230 shown in FIG. The program screen display unit 124 displays a program screen 220 shown in FIG. The case setting screen display unit 126 displays a case setting screen 240 shown in FIG.

Data processing unit 130:
The data processing unit 130 includes a program generation unit 132, a program execution unit 134, and a test case registration unit 136. The program generation unit 132 automatically generates an operation test program. The program execution unit 134 executes the generated program. In the reference technique 1, QTP is caused to execute a program. The test case registration unit 136 registers the execution set in the case file. The execution set and the case file will be described in detail with reference to FIG.

Data holding unit 140:
The data holding unit 140 includes a log holding unit 142, a program holding unit 144, an input data file holding unit 146, a case file holding unit 148, a function holding unit 150, and a result holding unit 152. The log holding unit 142 holds a log. The program holding unit 144 holds a program. The input data file holding unit 146 holds an input data file. The case file holding unit 148 holds a case file. The function holding unit 150 holds a function library for the functions registered in the operation test program. The result holding unit 152 holds the result of the operation test.

FIG. 5 is a schematic diagram from obtaining a log to executing an operation test in Reference Technology 1.
First, manually operate the device to be tested. In Reference Technology 1, the portal site “XYZ!” Is accessed by operating the web browser of the client terminal. QTP generates a log, and the log acquisition unit 114 acquires a log from QTP. A function is associated with each code sentence in advance. The function setting screen display unit 120 reads the function library of the function holding unit 150 and displays a list of functions corresponding to each code sentence included in the log (S1). In the function setting screen display unit 120, the user can add, change, and delete functions as appropriate. In this way, functions to be included in the program are specified. S1 will be described in detail later with reference to FIG.

  Next, input data to be supplied to this program is set (S2). The setting contents are registered as an input data file. S2 will be described in detail later with reference to FIG. A program is automatically generated from the function group set in S1 (S3). S3 will be described later in detail with reference to FIG.

Next, a combination of a program and an input data file is registered as an “execution set” from a plurality of types of programs and a plurality of types of input data files. A plurality of execution sets can be registered (S4). The setting contents are registered as a case file. For example, when the program P1 is executed based on the input data file F2 and then the program P2 is executed based on the input data file F6,
Execution set 1: Program P1 + Input data file F2
Execution set 2: Program P2 + input data file F6
Is registered in the case file. S4 will be described in detail with reference to FIG.
Finally, the program is executed according to the case file. In the case of the above example, the program execution unit 134 continuously executes the execution set 1 and the execution set 2. The program execution unit 134 registers the execution result of the program, in other words, the test result in the result holding unit 152.

FIG. 6 is a screen diagram of the log screen 200.
When the log acquisition unit 114 acquires the log, the output unit 118 displays the log on the log display area 202 in the log screen 200. The user may copy and paste the QTP log into the log display area 202. Alternatively, the output unit 118 may acquire a log (file) generated by QTP when the log screen 200 is displayed and display the log in the log display area 202. When the user clicks the execution button 204 with the mouse, a function setting screen 210 shown in FIG. 7 is displayed.

FIG. 7 is a screen diagram of the function setting screen 210.
The program generation unit 132 specifies a function for the code sentence included in the log, and displays the specified function in a list in the function column 214 of the function setting screen 210. The number column 212 indicates the execution order, the description column 216 indicates the outline of the function, the object column 218 indicates the operation target object, the parameter column 219 indicates the parameter name, and the input value column 217 indicates the input data.
A sign statement indicating the above-mentioned operation A1,
Browser ("XYZ!"). Page ("XYZ!"). WebEdit ("p"). Set "Test"
The WebEditSet function is associated with the function library in advance. When the program generating unit 132 reads the first code sentence of the log 320, the program generating unit 132 refers to the function library of the function holding unit 150 and identifies the WebEditSet function. Since the object to be operated by the operation A1 is the page “Browser (“ XYZ! ”). Page (“ XYZ! ”)”, The object column 218 displays “Browser (“ XYZ! ”). Page ( "XYZ!") "Is set. The WebEditSet function is a function that takes input data set in the edit box p (edit box 302) as an argument. Although it is possible to set input data to be set in the edit box p in the input value column 217, it is assumed that no input data is registered in the function setting screen 210. Input data to be set in the edit box p is set on the input setting screen 230 described in detail with reference to FIG.

  Since the log 320 includes three code sentences corresponding to the operations A1 to A3, the program generation unit 132 identifies three functions. The user may add, delete, or change a function on the function setting screen 210. The fourth TextCheck function and the fifth WebScreenCapture function in FIG. 7 are functions additionally selected by the user.

  The TextCheck function is a function for determining whether or not a character string to be substituted for the variable q is included in the displayed web page. The WebScreenCapture function is a function that captures a screen of the web page being displayed. The WebScreenCapture function is a convenient function for trail management of the results of operation tests. As described above, the function library includes not only functions corresponding to user operations such as the WebEditSet function but also functions for assisting and supporting the operation test such as the TestCheck function. The user can set logic to be included in the operation test simply by selecting a desired function from the function library.

  When the test case setting button 215 is clicked, a case setting screen 240 in FIG. 10 is displayed. When the input data file creation button 213 is clicked, the input setting screen 230 of FIG. 9 is displayed. When the program creation button 211 is clicked, the program screen 220 of FIG. 8 is displayed.

The operation verification apparatus 100 of the reference technique 1 has the following merits.
m1. The logic to be included in the program can be selected simply by selecting a function based on GUI (Graphical User Interface). There is little effort to create a program.
m2. Since the functions included in the program are functions registered as a function library, the quality of the program hardly varies depending on the creator. Necessary logic such as exception handling is also incorporated in each function in advance.

FIG. 8 is a screen diagram of the program screen 220.
When the program creation button 211 is clicked with the mouse on the function setting screen 210, the program generation unit 132 generates a program, and the program screen display unit 124 displays the source code in the program display area 222 in the program screen 220. The program is held in the program holding unit 144.

FIG. 9 is a screen diagram of the input setting screen 230.
When the input data file creation button 213 is clicked on the function setting screen 210, the input setting screen display unit 122 displays the input setting screen 230. In the function setting screen 210, parameters p and q are defined. The number column 232 indicates the input order, the variable column 234 indicates the input data to the parameter p, and the variable column 236 indicates the input data to the parameter q. On the input setting screen 230, input data to be substituted for the parameters p and q is set. Each input data is held in the input data file holding unit 146 as an input data file.

For example, when an input data file in the format shown in FIG.
1. 1. A test for inputting a character string “test” into the edit box 302 to search the dictionary and determining whether the character string “test” is included in the screen showing the execution result. 2. A test for inputting a character string “test” into the edit box 302 and searching the dictionary to determine whether the character string “test” is included in the screen showing the execution result. Enter the character string “test case” in the edit box 302, search the dictionary, and determine whether the character string “test” is included in the screen showing the execution result. Multiple dictionary tests based on can be executed continuously.

FIG. 10 is a screen diagram of the case setting screen 240.
When the test case setting button 215 is clicked with the mouse on the function setting screen 210, the case setting screen display unit 126 displays the case setting screen 240. The number column 244 indicates the execution order, the execution set column 245 indicates the outline of the execution set, the program column 246 indicates the program to be executed, and the input data file column 247 indicates the input data file from which the input data is to be extracted.
Here, the website of the Internet securities will be described as an operation test target.

  In FIG. Login, 2. 2. News check, Stock sales, 4. Bond sales, 5. Address change, 6. Six execution sets called logout are registered. First, QTP generates a “login” project from the program “login.vbs”. Here, the “project” is a directory including a group of QTP execution format files. QTP executes the process defined in login.vbs and login.xls with the “login” project as input. When the user clicks the execute button 248 with a mouse, the “login” project of the execution set “login” is first executed. When the first execution set “login” is completed, the “ncheck” project is executed as the execution set “news check”.

  Thus, when the execution button 248 is clicked with the mouse, Login, 2. 2. News check, Stock sales, 4. Bond sales, 5. Address change, 6. Six execution sets called logout are executed continuously. As a result, it is possible to automate an operation test based on a test scenario of “login, check news, instruct to sell hand shares and bonds, change address, and log out”.

The user can freely create a test scenario on the case setting screen 240. For example, instead of the execution set “Stock Sell”, you can register the execution set “Stock Purchase”, or register another input data file instead of “stock1.xls” as the input data file for the execution set “Stock Sell”. May be. The test scenario registered on the case setting screen 240 is recorded as a case file and held in the case file holding unit 148.
By changing the test scenario configuration and the input data file little by little, it becomes easier to expand the variation of the operation test.

The operation verification device 100 of the reference technique 1 has been described above.
According to the operation verification apparatus 100, a program and input data, that is, a process and a parameter can be separated. And the program for it can be automatically generated based on the setting of the GUI base. This makes it possible to easily generate a stable quality program while ensuring the diversity of logic included in the program. In addition, since the contents of the operation test can be changed simply by changing the contents of the input data file, it is easy to expand the variations of the operation test.

  Furthermore, by registering an execution set in a case file and creating a test scenario, operation tests in various situations can be realized while combining existing programs. In addition to functions for operating the test target device such as the WebEditSet function, functions such as the WebScreenCapture function for supporting the operation test are prepared to further improve the efficiency and reliability of the operation test. It becomes easy to improve.

(Reference technology 2)
The reference technique 2 proposes an operation verification apparatus 100 obtained by improving the reference technique 1.
First, an outline of the operation verification apparatus 100 of the reference technique 2 will be described while comparing the operation verification apparatus 100 of the reference technique 1 and the operation verification apparatus 100 of the reference technique 2.

  FIG. 11 shows an outline of the configuration of each of the operation verification apparatus 100 of the reference technique 1 and the operation verification apparatus 100 of the reference technique 2. As shown in FIG. 11A, the operation verification apparatus 100 of the reference technique 1 is used to improve the efficiency of the operation test of the QTP module 102 which is an execution engine of the operation test and the web server 400 using the QTP module 102. And a wrapper module 104. The wrapper module 104 includes the functional blocks shown in FIG.

  In FIG. 11A, the user operates the web server 400, which is a target device for operation confirmation, via the QTP module 102 (S100). The wrapper module 104 obtains a log in which the operation content is recorded from the QTP module 102 and provides the function setting screen 210 to the user (S102). When performing the operation test, the user causes the wrapper module 104 to generate an operation test program that can be read by the QTP module, and causes the QTP module 102 to execute the program (S104).

  On the other hand, as illustrated in FIG. 11B, the operation verification apparatus 100 according to the reference technique 2 includes an integrated verification module 106 in which the function of the operation test execution engine and the function of the wrapper module 104 are integrated. When the user operates the web server 400 via the integrated verification module 106 (S200), the integrated verification module 106 sequentially detects the operation contents, sets the data of the function setting screen 210, and provides the function setting screen 210 to the user. (S202). When executing the operation test, the user causes the integrated verification module 106 to generate and execute an operation test program (S204).

  FIG. 12 shows an outline of operations in each of the operation verification apparatus 100 of the reference technique 1 and the operation verification apparatus 100 of the reference technique 2. FIG. 12A shows an outline of the operation in the operation verification apparatus 100 of the reference technique 1. The user executes a data input operation on the web server 400 (S110), and the QTP module 102 outputs a log in which the operation content is recorded (S112). The user copies the log data to a predetermined input area of the QTP module 102 (S114). The wrapper module 104 sets and displays a function setting screen based on the log data set in the predetermined input area (S116), and the user adds the function / input data to be added / changed via the function setting screen. Set (S118).

  The wrapper module 104 generates a QTP program for an operation test based on the function setting screen data (S120). The user copies the QTP program to a predetermined input area of the QTP module 102 (S122). On the case setting screen, the user sets an operation test scenario that specifies the QTP program and the input data file as a set (S124). Based on the scenario, the wrapper module 104 passes a set of the QTP program and the input data file to the QTP module 102, and executes an operation test for each set (S126).

  FIG. 12B shows an outline of the operation in the operation verification apparatus 100 of Reference Technique 2. The user executes a data input operation on the web server 400 (S210). The integrated verification module 106 sequentially detects the data input operation, records the function corresponding to the data input operation in the operation content file, and displays the recorded data of the operation content file on the function setting screen (S212). The user sets the function / input data to be added / changed in the operation content file via the function setting screen (S214). Then, on the case setting screen, the user sets an operation test scenario specifying the operation content file and the input data file as a set (S216). Based on the scenario, the integrated verification module 106 generates and executes an operation test program in which one or more sets in the scenario are aggregated (S218).

  As described above, in the operation verification apparatus 100 of the reference technique 1, the QTP module 102 and the wrapper module 104 are separated. Therefore, in order to link the two modules, the user himself / herself has to execute a mediation operation. Further, the wrapper module 104 needs to call the QTP module 102 for each set in the scenario and execute the test program for each set.

  On the other hand, in the operation verification apparatus 100 of the reference technique 2, the execution engine of the operation test and the wrapper that realizes its efficient use are seamlessly integrated without being separated. Therefore, compared with the operation verification apparatus 100 of the reference technique 1, the user's work required for linking the separated modules becomes unnecessary, and the user's work amount for the operation test is reduced. In addition, since an operation test program in which a plurality of sets in a scenario are aggregated is generated and a series of scenarios is executed by executing the program, a quick operation test is realized.

  FIG. 13 is a block diagram illustrating a functional configuration of the operation verification apparatus 100 of the reference technique 2. The functional blocks shown in the figure are included in the integrated verification module 106 shown in FIG. Among the functional blocks of the reference technique 2, the functional blocks corresponding to the functional blocks of the reference technique 1 are denoted by the same reference numerals. Functional blocks with the same reference numerals as those of the reference technique 1 are described when the functions are different from the contents described in the reference technique 1, and description of similar functions is omitted.

  The data holding unit 140 includes an operation content file holding unit 143, a program holding unit 144, an input data file holding unit 146, a case file holding unit 148, and a function holding unit 150. The operation content file holding unit 143 stores an operation content file in which a function to be set in the operation test program is recorded. The program holding unit 144 stores an operation test program generated according to the operation content file.

  The input unit 112 of the IF unit 110 includes an operation detection unit 115 and a user setting reception unit 117. The operation detection unit 115 sequentially detects user data input operations on the web server 400. The user setting reception unit 117 detects setting information by the user for the function setting screen 210, the input setting screen 230, and the case setting screen 240.

  The output unit 118 of the IF unit 110 includes a function setting screen display unit 120, an input setting screen display unit 122, and a case setting screen display unit 126. The function setting screen display unit 120 displays a function setting screen 210 that displays the contents of the operation content file recorded in the operation content file holding unit 143 on a predetermined display device.

  The data processing unit 130 includes a program generation unit 132, a program execution unit 134, a test case registration unit 136, an operation recording unit 137, and an input data recording unit 138. The operation recording unit 137 refers to the function holding unit 150, specifies a function corresponding to the data input operation detected by the operation detection unit 115, and records the function in the operation content file. The operation recording unit 137 records user setting information for the function setting screen 210 in an operation content file. The input data recording unit 138 records input data input by the user via the input setting screen 230 in an input data file. The program generation unit 132 generates an operation test program according to the function recorded in the operation content file. The program execution unit 134 executes an operation test program as an operation test execution engine, and records the result in the result holding unit 152.

  FIG. 14 is a schematic diagram from when the user's data input operation is detected to when the operation test is executed in Reference Technology 2. First, the user operates the web browser of the client terminal to access the web server 400, and executes various operations on the web server 400, typically data input operations on web pages provided by the web server 400. The operation detection unit 115 sequentially detects data input operations by the user, and the operation recording unit 137 reads the function library of the function holding unit 150 and sequentially records the functions corresponding to the data input operations in the operation content file (S220).

  Next, the function setting screen display unit 120 reads the operation content file in the operation content file holding unit 143 and displays a function setting screen that displays a list of functions corresponding to the operation by the user. On the function setting screen, the user can add, change, and delete functions as appropriate, and can set input data to be statically set in the operation test program. In this way, a function to be included in the operation test program is specified. The function setting screen will be described later with reference to FIGS. 15 and 16.

  Next, the input setting screen display unit 122 displays the input setting screen 230. The user sets input data to be dynamically supplied to the operation test program when the operation test is executed via the input setting screen 230. The input data set by the user is recorded in the input data file (S222). The input setting screen 230 will be described later with reference to FIG.

Next, the case setting screen display unit 126 displays the case setting screen 240. The user registers a combination of an operation content file and an input data file as an execution set from a plurality of types of operation content files and a plurality of types of input data files. The test case registration unit 136 records one or more execution sets in the case file (S224). For example, in the test case 1, after the setting content of the operation content file F01 is executed based on the input data file F12, the setting content of the operation content file F02 is executed based on the input data file F16.
Test case 1:
Execution set 1: operation content file F01 + input data file F12
Execution set 2: operation content file F02 + input data file F16
Is registered in the case file. The case setting screen 240 will be described later with reference to FIG.

  Next, the program generation unit 132 generates an operation test program based on the case file and the operation content file (S226). Specifically, the functions sequentially recorded in the operation content file set in the execution set may be sequentially set in the program code of the operation test program. Further, when a plurality of execution sets are set in one test case, the program generation unit 132 collects and sets the functions recorded in the operation content file of each execution set in one operation test program.

  In addition, when the input data itself is set for the function of the operation content file, the program generation unit 132 statically sets the input data in the operation test program. For example, when generating an operation test program, input data is set in advance as a function argument in the program code. If an input data file is specified for the function of the operation content file, the data of the input data file is set to be read when the program is executed.

  Finally, the program execution unit 134 executes the operation test program to reproduce a series of operations performed by the user on the web server 400 (S228). For functions that require data in the input data file, the data of the input data file read when the operation test program is executed is passed as an argument. That is, the function is executed based on the input data dynamically acquired from the input data file.

  FIG. 15 is a screen diagram of the function setting screen 210. This figure shows a function setting screen 210 that displays “search entry.xls” described later in FIG. The data file column name column 250 is an area in which the column name of the input data file in which the input data set in the parameter is recorded is designated. The user may describe the input data itself in the input value field 217, or instead, may specify the column name of the input data file in the data file column name field 250. When the column name of the input data file is specified in the data file column name field 250, when the operation test program is executed, one or more input data set in the column of the input data file is read and passed to the function. .

  FIG. 16 is a screen diagram of the function setting screen 210 in the reference technique 2. In the input value field 217 of the “search part signature” parameter in FIG. 9, input data candidates are listed in a drop-down list 252. The input data candidates displayed in the drop-down list 252 are input data candidates displayed in the drop-down list of the web page when the user inputs data to the web page. The user can select input data from the drop-down list 252 and the burden on the user in setting the input data is reduced.

  In order to set the drop-down list 252, the operation detection unit 115 acquires input data candidates displayed in the drop-down list of the web page when the user performs a data input operation on the web page. For example, a candidate for input data in the drop-down list is acquired from web page data acquired from the web server 400, for example, HTML data. The operation recording unit 137 records the input data candidates in the input value field 217 of the operation content file. When the input value field 217 is input, the function setting screen display unit 120 displays a list of input data candidates recorded in the operation content file in the form of a drop-down list.

  FIG. 17 is a screen diagram of the input setting screen 230 in the reference technique 2. FIG. 17A shows an input setting screen 230 that displays the input data file “search entry data.xls” in which the column name is specified in the function setting screen 210 of FIGS. 15 and 16. 15 and FIG. 16, the “name kanji” column and the “name kana” column in FIG. 17A are designated. FIG. 16B shows an input setting screen 230 that displays another input data file “login data 2.xls”. The input data file shown in the figure will be described later with reference to FIG.

  FIG. 18 is a screen diagram of the case setting screen 240 in the reference technique 2. A basic execution order of each execution set is set in the execution number column 253, and test case identification information is set in the test case ID column 254. In the group ID column 256, identification information indicating a group of execution set repetition processing is set, and in the line number column 258, a reference range of the input data file in the operation test is set. The operation content file column 260 is set with an operation content file for each execution set, and the input data file column 262 is set with an input data file for each execution set. The setting content on the case setting screen 240 is stored as a case file in the case file holding unit 148.

  When the test execution button 264 is pressed on the case setting screen 240, the program generation unit 132 generates an operation test program according to the case file and the operation content file. Specifically, based on one or more operation content files in which the same test case ID is set in the case file, one operation test program in which the function recorded in each operation content file is set in the program code Generate. For example, the program generation unit 132 performs one operation test program for executing a registered case and one for executing a search case in accordance with a case file in which the contents of the case setting screen 240 of FIG. 18 are recorded. An operation test program is generated. Note that “one operation test program” means a program executed as one execution unit, in other words, a program executed at one execution opportunity, and the number of physical programs is not limited.

  When the program execution unit 134 executes one function recorded in each operation content file, the program execution unit 134 associates the function with the function in the operation content file among the data of the input data file associated with the operation content file. Pass column data to the function.

  Further, the program execution unit 134 handles a plurality of execution sets assigned the same group ID in the same test case as the same group that should execute the same repeated process. Specifically, each execution set with the same group ID is repeatedly executed, and each time it is repeated, the function recorded in the operation content file of each execution set is recorded in the input data file. Pass a certain number of records. In the reference technique 2, one record recorded in the input data file is passed to the function every time it is repeated. Note that the program generation unit 132 may generate an operation test program in which a repetition instruction for executing the above-described processing is set in the program code.

  Further, the program execution unit 134 passes the input data specified by the line number in the input data file to the function recorded in the operation content file for the execution set for which the line number is specified. Therefore, when the repetition process by the group ID is designated and the line number is further designated, the repetition is executed by the designated number of line numbers. For example, in the registration case of FIG. 18, there is no group setting across execution sets, and processing for one input data is executed in each execution set. On the other hand, in the search case of FIG. 18, the process for one input data in each execution set is repeated three times.

Specifically, in the first iteration, login2. 1. Login data for the function recorded in xls Data “t_yamada” on the 35th line of xls is passed. And search entry. Search entry data for the function recorded in xls, specifically, the function No. 1 in FIG. The data “Taro Yamada” in the first line of the xls and full name kanji is passed. For the function No. 2 in FIG. The data “Yamada Taro” in the first line of the xls and the name Kana is passed.
In the second iteration, login 2. 1. Login data for the function recorded in xls The data “h_yamada” on the 36th line of xls is passed. And search entry. Search entry data for the function No. 1 in FIG. Data “Kana Yamada” in the second line of xls and full name kanji is passed. In addition, the search entry data for the function No. 2 in FIG. The data “Yamada Hanako” in the second line of xls and the name Kana is passed.
Similarly, in the third iteration, the input data in the incremented line number is passed to each function.

  The operation verification apparatus 100 of the reference technique 2 also has the effects described in the reference technique 1. Specifically, since separation of processing and parameters and GUI-based setting are realized, it is possible to easily generate a stable quality program while ensuring the diversity of logic included in the operation test program. Moreover, it becomes easy to expand the variation of the operation test by setting the input data file. Furthermore, operation tests in various scenarios can be realized by setting case files.

  In the operation verification apparatus 100 of Reference Technology 2, the execution engine function that executes the operation test program and the wrapper function that realizes efficient use of the execution engine are seamlessly linked without requiring user intervention. To do. Thereby, the burden on the user for executing the operation test can be reduced. Unlike the case of the operation verification apparatus 100 of the reference technique 1, the user does not need to be aware of the environment for program execution such as a QTP project. That is, an operation content file and an input data file in a format that can be easily understood and operated by the user may be set. As a result, the user can easily perform the operation test.

  In the operation verification apparatus 100 of the reference technique 2, one operation test program in which a plurality of execution sets of the same test case are aggregated is generated, and the one operation test program is executed. Compared with execution for each execution set in the operation verification apparatus 100 of the reference technology 1, that is, for each project of QTP generated based on the execution set, overhead when executing a series of operation tests in one test case is reduced. A quick operation test can be realized.

  In the operation verification apparatus 100 of the reference technique 2, it is possible to set a repeated group over a plurality of execution sets. As a result, the execution set can be flexibly divided, and an operation test scenario can be flexibly set. Furthermore, the reference range of the input data file can be set. Thereby, even if the input data file is the same, the reference range can be flexibly changed according to the scenario, and various variations of the operation test can be easily realized.

  In the reference technique 2 described above, the drop-down list 252 is shown as an example of supporting the value setting on the function setting screen 210. In the modified example, candidates for input data displayed so as to be selectable by a radio button, a check box, a list box, etc. on the web page are displayed so as to be selectable on the function setting screen 210 in a drop-down list 252 or other formats. Also good. That is, input data candidates that are displayed so as to be selectable in various formats for the user when performing a data input operation on the operation confirmation target device are displayed so as to be selectable when setting values on the function setting screen 210. Also good.

  In the reference technique 1 described above, the operation verification apparatus 100 creates an operation test program on the condition that a user operation on the web server 400 is accepted by the QTP and a log is generated. In the reference technique 2 described above, the operation verification apparatus 100 detects a user operation on the web server 400 and creates an operation test program. As a modification, an operation test program may be generated when the operation verification apparatus 100 acquires an HTML file from the web server 400. In this case, the operation verification apparatus 100 searches for a form tag included in the HTML file and specifies what input interface is included in the HTML file. If a function for inputting data to each input interface is selected and these functions are arranged in various orders, an operation test program can be generated without an explicit web operation by the user.

(Embodiment)
Hereinafter, embodiments of the present invention will be described. First, an outline thereof will be described.
In the present embodiment, a technique for efficiently executing an operation test of an application that operates by being incorporated in an ERP package is proposed. Hereinafter, as an example of the ERP package, an ERP package provided by SAP (SAP R / 3, SAP ERP, etc., hereinafter simply referred to as “SAP software”) (“SAP” is a registered trademark) is shown. Those skilled in the art will appreciate that similar techniques can be applied to other ERP packages.

  As shown in Reference Technique 1, QTP, which is an automated operation test tool, provides a standard test engine for web page operation tests. This test engine executes a web page operation test by causing a web browser to execute various operations set in the operation test program.

  QTP can also add in a test engine for an operation test of an application (hereinafter, also referred to as “AP for SAP”) operating on an SAP server in which SAP software is installed. Hereinafter, this test engine is also referred to as “SAP add-in”. The SAP add-in allows the client program (hereinafter also referred to as “SAPPGi client”) that provides a GUI environment for operating the SAP AP to execute various operations set in the operation test program. An AP operation test is executed.

  By the way, GUI components provided by the SAPPGui client include a window object, a table object, and a grid object. Hereinafter, these objects will be referred to as “SAPPGiWindow”, “SAPPGiTable”, and “SAPPGiGrid”. SAPGuiWindow forms an outer frame of a display area for displaying data related to the AP for SAP. SAPGuiTable and SAPGuiGrid are GUI components similar to a spreadsheet, and are displayed on the SAPGuiWindow, and input data is set for cells specified by rows and columns.

  In the operation test of the AP for SAP, it is necessary to scroll these GUI components. For example, data set in the lower part of the GUI component may not be displayed on the initial screen. When this data should be secured as data for certifying the result of the operation test (hereinafter also referred to as “evidence”), after performing a scrolling operation on the GUI component, in other words, on the screen After making it visible with, you need to perform screen capture.

  However, the SAP add-in provides a function for scrolling the SAPPGuiWindow, but does not provide a function for scrolling the SAPPGuiTable and SAPPGiGrid. Therefore, in order to secure a proof, the user has to manually perform a scroll operation, which hinders the realization of an efficient operation test.

  Therefore, in the present embodiment, an operation verification device is proposed that uses QTP in which an SAP add-in is incorporated, complements the insufficient functions thereof, and mechanically executes a scroll operation on SAPGuiTable and SAPGuiGrid. As a result, an exhaustive scrolling operation for the SAP GUI component is realized, and an efficient operation test is realized.

  Note that the SAP AP of the present embodiment provides an input function for inputting test data to the SAP GUI component. For example, an SAP input function corresponding to the “WebEdit Set” function of FIG. 7 is provided. Similarly to the operation recording for the web page described in the reference technique 1, the user operation for the SAP AP is recorded. However, the AP for SAP does not record the scroll operation for the GUI component. Therefore, when a scroll operation is required in the operation test, the user needs to newly register a scroll operation function in the operation test program.

  Another feature of the operation verification apparatus according to the present embodiment will be described. The SAP AP displays the operation status of the SAP AP in the status bar area below the GUI component. For example, whether or not the input data is set appropriately is displayed in the status bar area. Accordingly, in the operation test of the SAP AP, it is necessary to confirm whether or not the message displayed in the status bar area of the GUI component is appropriate. However, the SAP add-in does not provide a function for acquiring a message displayed in the status bar area. For this reason, until now, it has been necessary for the user to visually check messages in the status bar area, which has hindered the realization of an efficient operation test.

  Therefore, the operation verification apparatus according to the present embodiment acquires a message displayed in the status bar area of the GUI component, and mechanically confirms whether a message as expected before the test is output. This automates the confirmation work that has been performed manually by the user so far and realizes an efficient operation test.

  FIG. 19 shows a system architecture in the operation test of the embodiment. The operation verification system 1000 includes an operation verification apparatus 100, a web server 400, and an SAP server 402. Each of these devices is connected by a known communication means such as LAN / WAN / Internet.

  The test engine IF 412 collectively detects an operation test function set in the operation test program, specifically, a function for operating the web browser 404 and a function for operating the SAPGui client 406. When a function for operating the web browser 404 is detected, the browser driver 414 operates the web browser 404 by calling an API of QTP 408 corresponding to the function. When a function for operating the SAPGui client 406 is detected, the SAP driver 416 operates the SAPGui client 406 by calling the API of the SAP add-in 410 corresponding to the function. Note that the test engine IF 412, the browser driver 414, and the SAP driver 416 function as the wrapper module 104 illustrated in FIG. 11A and are installed in the program execution unit 134 described later.

  FIG. 20 shows in detail the portion related to the SAP operation of FIG. The SAPGui client 406 includes an AP display screen 420 and a SAPPS scripting API 428. The AP display screen 420 is a function for controlling the display of a GUI component for operating the SAP AP, and in the figure, a screen image displayed on a predetermined display is shown. The AP display screen 420 includes a SAPGuiWindow 422, a SAPGuiTable 424, and a SAPGuiGrid 426. Each GUI component has a vertical scroll bar for vertical scrolling and a horizontal scroll bar for horizontal scrolling.

  The SAPScript scripting API 428 is a native method group of the SAPPGui client 406 for operating the SAPPGui client 406. In other words, it is an API group for directly calling the library of the SAPPGui client 406 from the outside. An external process of the SAPGui client 406 can execute various operations for each GUI component by calling the SAPPSscripting API 428 corresponding to the various GUI components.

  The SAP add-in 410 includes a scroll-only function 430 and a native reference object 432. The scroll dedicated function 430 is a dedicated function for executing a scroll operation on the SAPGuiWindow 422. The native reference object 432 is a client module for accessing the SAPGui client 406. For example, an external process of the SAPPGui client 406 can call the SAPSscripting API 428 via the native reference object 432 as a pointer.

  The SAP driver 416 moves the scroll bar of the SAPGuiWindow 422 by calling a scroll-dedicated function 430 when a scroll operation on the SAPGuiWindow 422 is to be executed. On the other hand, when a scroll operation on the SAPPGiTable 424 or the SAPPGiGrid 426 is to be executed, the SAPPSTable API 428 is called via the native reference object 432 to move the scroll bar of the SAPPGiTable 424 or the SAPPGiGrid 426.

  FIG. 21 is a block diagram illustrating a functional configuration of the program execution unit 134 according to the embodiment. The program execution unit 134 operates the SAPGui client 406 according to the operation test program in order to reproduce the operation for the SAP AP executed in the SAPGui client 406. The program execution unit 134 includes a GUI operation unit 160, a witness setting unit 162, a collation unit 164, and a verification result presentation unit 166.

  The functional configuration of the entire operation verification apparatus 100 is the same as that of the reference technique 1, that is, the same as the block diagram of FIG. Specifically, the operation content for the SAP AP recorded in the SAP add-in 410 is acquired as a log by the log acquisition unit 114. The program generation unit 132 sets the function recorded in the log and the function set by the user on the function setting screen 210 in the program code of the operation test program. The acquisition of the input data from the input data file and the setting of the execution set are the same as in the reference technique 1. That is, the operation test execution process in the present embodiment is the same as in FIG.

  The GUI operation unit 160 corresponds to the SAP driver 416 of FIGS. 19 and 20 and executes an operation on the GUI component of the SAPGui client 406 via the SAP add-in 410. When the scroll operation of the GUI component is to be executed, the scroll dedicated function 430 of the SAP add-in 410 is called or the SAPSscripting API 428 is called via the native reference object 432 according to the type of the GUI component.

  The proof object setting unit 162 sets a proof object of the operation test for the SAP AP. Specifically, the image data of the GUI component displayed on the AP display screen 420 in the operation test is captured. The evidence object setting unit 162 stores the captured image data, that is, the screen snap of the GUI component in the result holding unit 152 as a evidence object.

  Further, the left object setting unit 162 acquires a message (hereinafter also referred to as “status message”) displayed in the status bar area at the bottom of the SAPGuiWindow 422. Specifically, the status message is acquired by calling the status message acquisition method of the SAPSscripting API 428 via the native reference object 432 as a pointer. The proof object setting unit 162 stores the status message data in the result holding unit 152 as a proof object.

  The collation unit 164 compares and collates the expected value of the status message set in advance by the user with the data actually displayed as the status message (hereinafter also referred to as “actual value”), and the collation result is proved. And stored in the result holding unit 152. This collation result is information indicating consistency / inconsistency between the expected value and the actual value of the status message in the operation test. For example, when the expected value and actual value of the status message do not match, the collation unit 164 stores an error report indicating that the status message is abnormal in the result holding unit 152.

  The verification result presentation unit 166 presents the proof obtained in the operation test of the SAP AP to the user. Specifically, in response to a request from the user, the screen snap of the GUI component of the SAP and the result of checking the status message are acquired from the result holding unit 152 and displayed on a predetermined display.

  FIG. 22 illustrates examples of functions that can be set by the user in the operation verification apparatus 100 according to the embodiment. This figure shows a test function for executing a scroll operation for the GUI component of the SAP, a test function for acquiring a screen snap of the GUI component, and a test function for executing a status message matching process. The setting format in the figure corresponds to the function setting screen 210 in FIG.

  The test function 170 is a function for horizontally scrolling the SAPGuiWindow 422 by the number of pixels specified by the parameter. The test function 172 is a function for vertically scrolling the SAPGuiWindow 422 by the number of pixels specified by the parameter. The test function 174 is a function for acquiring a screen snap of the SAPGuiWindow 422 while calling the test functions 170 and 172 therein. Specifically, the display screen is captured while repeating the horizontal scrolling of the number of pixels specified by the horizontal scrolling amount by the number of horizontal scrolling. Then, after performing vertical scrolling for the number of pixels specified by the vertical scrolling amount, horizontal scrolling and screen capture are executed again. That is, a screen capture of the entire SAPGuiWindow 422 is acquired by appropriately combining horizontal scroll and vertical scroll.

  The test functions 170 and 172 are functions provided as scroll-only functions 430. When the GUI operation unit 160 detects these functions from the operation test program, it calls the scroll dedicated function 430. The test function 174 is a function provided by the evidence object setting unit 162. When this function is detected from the operation test program, the proof object setting unit 162 calls the scroll dedicated function 430 via the GUI operation unit 160 and executes screen capture. For example, a screen capture function of an OS (Operating System) may be called to obtain screen snap data recorded on the clipboard.

  The test function 176 is a function for horizontally scrolling the SAPPGiTable 424 by the number of columns specified by the parameter. The test function 178 is a function for vertically scrolling the SAPPGiTable 424 by the number of lines specified by the parameter. The test function 180 is a function for acquiring a screen snap of the SAPPGiTable 424 while calling the test functions 176 and 178 therein. Specifically, the display screen is captured while repeating the horizontal scrolling of the number of columns specified by the horizontal scrolling amount to the final column. Then, after performing vertical scrolling for the number of lines specified by the vertical scrolling amount, horizontal scrolling and screen capture are executed again. That is, a screen capture of the entire SAPPGuiTable 424 is recorded by appropriately combining horizontal scroll and vertical scroll.

  The test function 182 is a function for horizontally scrolling the SAPGuiGrid 426 by the number of columns specified by the parameter. The test function 184 is a function for vertically scrolling the SAPPGiGrid 426 by the number of lines specified by the parameter. The test function 186 is a function for acquiring a screen snap of the SAPPGiGrid 426 while calling the test functions 182 and 184 therein. Specifically, the display screen is captured while repeating the horizontal scrolling of the number of columns specified by the horizontal scrolling amount to the final column. Then, after performing vertical scrolling for the number of lines specified by the vertical scrolling amount, horizontal scrolling and screen capture are executed again. That is, a screen capture of the entire SAPGuiGrid 426 is acquired by appropriately combining horizontal scroll and vertical scroll.

  The test functions 176, 178, 182, and 184 are functions provided as the SAPSscripting API 428. When the GUI operation unit 160 detects these functions from the operation test program, it calls the SAPSscripting API 428 via the native reference object 432. The test functions 180 and 186 are functions provided by the evidence object setting unit 162. When the evidence setting unit 162 detects these functions from the operation test program, it calls the SAPSscripting API 428 via the GUI operation unit 160 and executes screen capture.

  As shown in FIG. 22, regardless of whether the GUI component to be scrolled is SAPPGiWindow 422, SAPGuiTable 424, or SAPGiGrid 426, the user is not aware of the difference in internal processing, and the test function is displayed on the function setting screen 210. May be specified in the same manner. In other words, whether the scroll operation of the GUI component is executed via the scroll dedicated function 430 or the native reference object 432 to the SAPSscripting API 428 is hidden from the user. Therefore, if the user appropriately selects and sets predetermined test functions 176 to 186 on the function setting screen 210, the user can comprehensively execute scroll operation and screen capture operation of the GUI component.

  Note that the vertical scrolling of the SAPGuiTable 424 does not require designation by the user, and the number of lines displayed on the AP display screen 420 of the SAPGui client 406 may be automatically scrolled. Specifically, the VisibleRowCount property value of the GuiTableControl object in the SAPSscripting API 428 may be acquired as the vertical scroll amount. Similarly, for the vertical scrolling of the SAPGuiGrid 426, the number of lines displayed on the AP display screen 420 of the SAPGui client 406 may be automatically scrolled. Specifically, the VisibleRowCount property value of the GuiGridControl object in the SAPSscripting API 428 may be acquired as the vertical scroll amount. Necessary and sufficient screen snaps can be recorded while reducing the burden on the user by reducing parameters to be specified by the user.

  The test function 188 is a function for collating the status message displayed on the status bar with its expected value, and the expected value of the status message as a parameter, in this embodiment, S (normal), W (warning), E (error) ) Can be specified. The test function 188 is a function provided by the matching unit 164. When the verification unit 164 detects this function from the operation test program, the verification unit 164 calls the SAPSscripting API 428 via the native reference object 432 and acquires the actual value of the status message. Then, the actual value is compared with the expected value, and the comparison result is recorded.

  Hereinafter, an example of status message verification will be described. FIG. 23 shows a display screen of the SAP GUI component. This figure shows a situation in which the user manually inputs the order information on the SAPGuiWindow screen 190 at the preparation stage of the operation test. In the figure, since the customer order number has not been entered even though the customer order date has been entered, a status message indicating a warning is displayed in the status bar area 192.

  FIG. 24 shows a display screen of the SAP GUI component. This figure shows a situation in which order information is automatically input in an operation test for the SAPGuiWindow screen 190. In the figure, although the customer order number is not entered and the customer order date is entered, a status message indicating normality is displayed in the status bar area 192.

  FIG. 25 shows the collation result of the status message. This figure shows an error report display screen 194 when the test function 188 of FIG. 22 is set in the operation test program. Specifically, since the expected value of the status message is W (warning) as shown in FIG. 23, the actual value is S (normal) as shown in FIG. 164 detected as an error. An error report indicating that fact is presented to the user by the verification result presentation unit 166.

  According to the operation verification apparatus 100 of the present embodiment, even when the target of the operation test is an AP for SAP, the effects described above in Reference Technology 1 can be obtained, and an efficient operation test can be realized. For example, it becomes easy to expand the variation of the operation test by separating the processing and the parameter. In addition, functions for operating the SAP AP and various functions for screen capture are provided in a manner that can be selected by the user on the unified function setting screen 210, thereby improving the efficiency and reliability of the operation test. It becomes easy.

  Further, according to the operation verification apparatus 100, a scrolling operation of GUI components that cannot be automated by the QTP 408 and a status message collation process are automated, thereby realizing a more efficient operation test. In general, a large number of SAP APs are built in the SAP server 402, and the large number of SAP APs are subjected to an operation test. Therefore, the number of screen snaps and the number of status messages of the GUI component to be acquired as evidence is also large. By automating the acquisition and verification of these evidences, the man-hours required for operation tests can be greatly reduced.

  The present invention has been described based on the embodiments. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there.

  Any combination of the above-described reference techniques, embodiments, and modifications is also useful as an embodiment of the present invention. The new embodiment resulting from the combination has the effects of the combined reference technology, embodiment, and modification.

  It should be understood by those skilled in the art that the functions to be fulfilled by the constituent elements described in the claims are realized by a single element or a combination of the constituent elements shown in the reference technique, the embodiment, and the modification. is there.

  DESCRIPTION OF SYMBOLS 100 Operation verification apparatus, 114 Log acquisition part, 116 Input data acquisition part, 132 Program generation part, 134 Program execution part, 160 GUI operation part, 162 Evidence setting part, 164 Collation part, 166 Verification result presentation part, 402 SAP server 406 SAPPGui client, 408 QTP, 410 add-in for SAP, 412 test engine IF, 416 driver for SAP, 1000 operation verification system.

Claims (8)

An apparatus that executes a test program for confirming the operation of an application that is incorporated into an ERP (Enterprise Resource Planning) package and operates.
A log acquisition unit for acquiring a log indicating the contents of a series of operations performed on the application;
Selects a function corresponding to the operation recorded in the log from a plurality of types of functions in which logic for realizing various operations is incorporated, and obtains input data to the application for the data input operation to the application A program generation unit for generating a test program for reproducing the series of operations by selecting an input function having an interface for
An input data acquisition unit for acquiring input data to be passed to the input function;
A program execution unit for passing the acquired input data to the input function and executing the test program for operation confirmation when the series of operations is executed based on the acquired input data;
An operation verification apparatus comprising: In the test program, a function for scrolling a table object or a grid object which is a GUI object provided by the ERP package displayed on the display screen of the application can be registered.
The program execution unit scrolls the table object or the grid object by calling a native method of the ERP package via a native reference object for the ERP package when the function for scrolling is to be executed. The operation verification apparatus according to claim 1, wherein: In the test program, a function for scrolling the window object provided by the ERP package displayed on the display screen of the application is registered in the same format as the function for scrolling the table object or grid object. Is possible,
The program execution unit scrolls the window object by calling a dedicated function for scrolling the window object provided by a predetermined test engine when a function for scrolling the window object is to be executed. The operation verification apparatus according to claim 2. In the test program, a screen capture function for recording the display screen of the table object or grid object can be registered,
4. The operation verification device according to claim 2, wherein the program execution unit records the display screen while scrolling the table object or the grid object when the screen capture function is to be executed. .   5. The operation verification according to claim 1, wherein the program execution unit records information displayed on a status bar on the display screen of the application as a proof in the operation check of the application. apparatus.   The information processing apparatus according to claim 5, further comprising: a collation unit that collates information preset as information expected to be displayed on the status bar and information actually displayed on the status bar. Operation verification device. A computer program for executing a test program for confirming the operation of an application installed in an ERP package,
A function of acquiring a log indicating the contents of a series of operations executed on the application;
Selects a function corresponding to the operation recorded in the log from a plurality of types of functions in which logic for realizing various operations is incorporated, and obtains input data to the application for the data input operation to the application A function for generating a test program for reproducing the series of operations by selecting an input function having an interface for
A function of acquiring input data to be passed to the input function;
A function for executing the test program by passing the acquired input data to the input function for operation confirmation when the series of operations is executed based on the acquired input data;
An operation verification program for realizing a computer. A method that is executed by a device that executes a test program for confirming the operation of an application embedded in an ERP package,
Obtaining a log indicating the contents of a series of operations performed on the application;
Selects a function corresponding to the operation recorded in the log from a plurality of types of functions in which logic for realizing various operations is incorporated, and obtains input data to the application for the data input operation to the application Generating a test program for reproducing the series of operations by selecting an input function having an interface for
Obtaining input data to be passed to the input function;
Passing the acquired input data to the input function to execute the test program for operation confirmation when the series of operations is executed based on the acquired input data;
An operation verification method comprising:

Images