JP2013037580A - Information processor - Google Patents

Abstract

An object of the present invention is to improve the efficiency of automated testing of structured documents.
An operation verification apparatus 100 acquires a structured document that defines display content of a screen (S302), and triggers a process of changing the display content of the screen among elements described in the structured document. Are extracted (S304), and an operation description document for allowing the user to describe an operation on the extracted element is output (S306). The element described in the operation description document according to the correspondence between the function defined in the verification device that executes the test program for confirming the display content of the screen and the operation to the element described in the operation description document A test program in which a program code for calling a function corresponding to the operation of the program is set is generated (S312).
[Selection] Figure 28

Description

  The present invention relates to a data processing technique, and more particularly, to an information processing apparatus that supports a test of a structured document.

  In recent years, test tools for automating tests on web pages and the like have been provided. The present applicant has proposed an operation verification apparatus that efficiently realizes an automatic test of a web page or the like in Patent Document 1 below.

JP 2010-237841 A

  In the operation verification apparatus of Patent Document 1, a user performs an operation once on a test object such as a web page and records the operation, and then the user interprets the contents of the recorded operation. It was necessary to edit the above appropriately and create the test execution code. That is, the user needs to understand how operations are recorded in the motion verification device and how they can be edited to perform the desired test, in other words, understand the rules of the motion verification device. It was necessary to have. The inventor considered that there was room for improvement so that users could more easily perform automated testing of structured documents.

  The present invention has been made in view of these problems, and a main object of the present invention is to provide a technology that supports efficient automatic testing of structured documents.

  In order to solve the above-described problem, an information processing apparatus according to an aspect of the present invention includes an acquisition unit that acquires a structured document that defines display content of a screen, and among elements described in the acquired structured document, An extraction unit that extracts, as a display change element, an element that triggers a process that changes the display content of the screen, and an output unit that outputs a document for allowing the user to describe an operation on the extracted display change element as an operation description document Between a function for operating a predetermined element in a verification device that executes a test program for confirming the display content of the screen and an operation to a display change element described in the operation description document And a program code for calling a function defined by the verification device corresponding to the operation on the display change element described in the operation description document according to the correspondence. It comprises a program generating section for generating a test program by the.

  Another embodiment of the present invention is also an information processing apparatus. This apparatus includes an acquisition unit that acquires a structured document that defines display content of a screen, and an extraction unit that extracts, as input elements, elements that receive data input from a user among elements described in the acquired structured document And an output unit for outputting a document for allowing the user to describe the operation to the extracted input element as an operation description document, and a verification device for executing a test program for confirming the display content of the screen. To the input element described in the operation description document according to the correspondence relationship, and the correspondence holding unit that holds the correspondence relation between the function for operating the element and the operation to the input element described in the operation description document A program generation unit that generates a test program by setting a program code for calling a function defined by the verification device corresponding to the operation of

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

  According to the present invention, it is possible to support the efficiency of automatic testing of structured documents.

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 web page of the object of an operation test. FIG. 20 is a diagram showing an operation content file in which operations for the web page in FIG. 19 are recorded. It is a figure which shows the operation description document. It is a block diagram which shows the detail of IF part of an operation verification apparatus. It is a block diagram which shows the detail of the data holding part of an operation verification apparatus. It is a block diagram which shows the detail of the data processing part of an operation verification apparatus. It is a figure which shows the example of the input element described in the structured document. It is a figure which shows the example of the display change element described in the structured document. It is a figure which shows typically the example of conversion by the operation information conversion part. It is a flowchart which shows operation | movement of an operation verification apparatus.

  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 (S5). 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. 1. Login 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, 1. Login 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. 17B 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 row 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)
First, the outline of the present invention will be described. FIG. 19 shows a web page to be subjected to the operation test. This web page is a web page provided by a website of an insurance company, and is a web page that allows a user to select a car insurance contract to be continued from among contracted car insurance. This web page includes a page title 500 indicating the title “abc0100” of this web page, and a radio button 502 a and a radio button 502 b that are collectively referred to as a radio button 502. Also, a first transition button 504 for transitioning the display target in the web browser to the web page of the contractor menu list, and a second transition button 506 for transitioning to the next web page after selecting the radio button 502 Is further included. Hereinafter, radio buttons, links, send buttons, text boxes, and the like that are objects included in a web page and tagged in a structured document are referred to as “elements”.

There are three cases as typical test cases for the web page of FIG.
1: Select the radio button 502a of the security number “37001” and click the second transition button 506.
2: Select the radio button 502b of the security number “38002” and click the second transition button 506.
3: Click the first transition button 504.
Actually, it is necessary to try the above test case for each user who logs in to the insurance company website, and when the user clicks the second transition button 506 without selecting the radio button 502 as an abnormal system, etc. Various test cases are assumed.

  FIG. 20 shows an operation content file in which operations for the web page of FIG. 19 are recorded, and corresponds to the contents of the function setting screen shown in FIG. 7 and FIG. The operation content file in FIG. 20 is a record of the operation of the test case 1 described above. The operation function 510 corresponds to the operation of selecting the radio button 502a of the security number “37001”, and the operation function 512 is the second. This corresponds to the operation of clicking the transition button 506.

  When performing an automatic web page test using the operation verification device described in the reference technology, the person in charge of the test (hereinafter referred to as “user”) creates an operation content file corresponding to each of a plurality of test cases. There is a need to. For example, in the case of the above three test cases, the user operates and executes a web browser for one test case, edits the operation content file created there, and creates operation content files for the remaining two test cases. There was a need.

  For this reason, the user is required to understand a function (in other words, an API) that is predetermined in the operation verification apparatus and that operates a web browser to edit a web page. For example, the name of the function that operates the radio button is “clickRadiobuttonByValue”, the object to be set as the argument is “dom = document.contentsform.element name”, and the name of the function that clicks the send button is “ The user had to understand that “clickAnchor” and the object to be set as the argument were “dom = document.getElementByTagName ('A') [element position]”. In view of this situation, the present inventor considered that there is room for further improving the efficiency of the automatic web page test by the operation verification apparatus.

  Therefore, the operation verification apparatus according to the embodiment (hereinafter, simply referred to as “operation verification apparatus 100” unless otherwise specified) is a user of the elements described in the structured document that defines the display content on the web page. The element that is the target of the operation (hereinafter also referred to as “operation target element”) is extracted.

  The operation target element of the embodiment is an element for receiving data from the user, in other words, includes an element (hereinafter, also referred to as “input element”) that is a target of data input by the user. The input elements include various form tags defined by HTML, such as radio buttons and text boxes. The operation target element further includes an element (hereinafter, also referred to as “display change element”) that triggers processing for changing the display content of the web page. The display change element includes an element that triggers a transition from a web page to another web page, such as a link tag / send button tag. In addition, the display change element includes elements other than an element that triggers switching of a display target web page. Specifically, an element that triggers updating (reloading) the display content in the web browser, for example, a general-purpose button tag or a clear button tag is included. In addition, an element that triggers execution of a processing code (for example, a program code written in JAVA script (registered trademark)) inside the web page, for example, a general-purpose button tag is included.

  It is assumed that the structured document of the embodiment is an HTML document. However, those skilled in the art will appreciate that it is applicable to other types of structured documents, such as XML and JSP documents. For example, in the case of an XML document, an operation target element may be extracted from the XML document with reference to a DTD or a style sheet. In the case of a JSP document, the operation target element may be extracted according to an HTML tag described in the JSP document.

  The operation verification apparatus 100 outputs a document (hereinafter also referred to as “operation description document”) for allowing the user to describe an operation on the operation target element extracted from the structured document. FIG. 21 shows an operation description document. The operation description document includes an element information setting field 520 in which the operation verification apparatus 100 automatically sets information on input elements and display change elements, for example, information indicating the meaning of each element, and the user performs operations on the input elements and display change elements. An operation information setting field 530 to be described is included.

  In the element information setting column 520, the input elements are displayed in association with a first input element information column 522 indicating the name in the structured document and a second input element information column 524 indicating the meaning of the element. The display change element includes a first display change element information column 526 indicating the screen contents of the change destination (for example, a file name that provides the transition destination screen), and a second display change element information column 528 indicating the meaning of the element. Are shown in association with each other.

  In the operation information setting field 530 of FIG. 21, the above three test cases are described. For example, the record of No. 1 in the figure shows that “value = 0” is selected from the options of the radio button “radRenNum” and the “Next” button is clicked. To do. The record of No. 2 indicates that “value = 1” is selected from the options of the radio button “radRenNum” and the “Next” button is clicked, and corresponds to the test case 2 described above.

  The operation verification apparatus 100 reads an operation description document in which an operation on the operation target element is described by the user, and automatically sets a plurality of operation content files corresponding to each record (for example, NO1 to 3 in FIG. 21) of the operation description document. To do. Note that, as indicated by the record No. 3, an operation of only the display change element may be set as a test case. Also, it is a structured document that contains JAVA script code, and in the structured document test in which the web browser automatically executes the script code and changes the display contents as data is input to the input element, only the input element is operated. May be set as a test case.

  According to the operation verification apparatus 100 of the embodiment, if the user knows the contents of the structured document to be tested (for example, the name of the operation target element and the value of the value attribute), the user operates the operation description document. Can be described. In other words, the operation verification apparatus 100 supports the realization of an efficient automatic test of structured documents without forcing the user to understand the function defined by the operation verification apparatus 100. Further, since the operation verification apparatus 100 transfers the name of the operation target element described in the structured document and information indicating the meaning thereof to the operation description document, it is possible to further easily describe the operation on the operation description document. Can do. Also, if a user collects and describes a plurality of types of operation contents for an operation target element in one operation description document, a plurality of operation contents files corresponding to each operation contents are created, thereby reducing the burden on the user. Efficient testing.

  Hereinafter, the functional configuration of the operation verification apparatus 100 according to the embodiment will be described in detail with reference to FIGS. 22 to 24 correspond to the block diagram of FIG. In addition, the same code | symbol is attached | subjected to the functional block same or corresponding to the functional block described in the reference technique, and the description which overlaps with the description described in the reference technique is abbreviate | omitted. Each functional block described below may be implemented as a program module added into the operation verification apparatus of the reference technology.

  FIG. 22 is a block diagram illustrating details of the IF unit 110 of the operation verification apparatus 100. The input unit 112 of the IF unit 110 further includes a document reception unit 540, and the output unit 118 further includes an operation description document output unit 542.

  When the user inputs a request for creating an operation description document specifying a structured document to the operation verification apparatus 100, the document reception unit 540 receives the request. Then, the data of the structured document designated by the request is read. For example, when the URL of the web page provided by the web server 400, that is, the URL of the structured document is designated in the operation description document creation request, the document reception unit 540 designates the URL and designates the structured document from the web server 400. May be obtained and stored in memory.

  In addition, when the user inputs a request for creating an operation content file designating an operation description document to the operation verification apparatus 100, the document reception unit 540 receives the request. Then, the operation description document data designated by the request is read. For example, when the path name of the operation description document in the operation verification apparatus 100 is specified in the operation content file creation request, the document reception unit 540 acquires the operation description document specified by the path name, stores it in the memory, and Also good.

  The operation description document output unit 542 stores the data of the operation description document set by the operation description document setting unit 550 described later in a predetermined storage area. For example, when the output directory of the document is specified in the operation description document creation request, the operation description document output unit 542 may store the operation description document in the directory.

  FIG. 23 is a block diagram illustrating details of the data holding unit 140 of the operation verification apparatus 100. The data holding unit 140 further includes an element information holding unit 544 and a correspondence relationship holding unit 546. The element information holding unit 544 is a storage area that holds attribute information related to elements set in the operation description document. For example, information indicating that a radio button is associated with the input element “radRenNum” in FIG. 21 and information indicating that the element name is “radRenNum” are stored. Information indicating that the button is a send button in association with the display change element “next” in FIG. 21 and information indicating that the anchor position in the structured document is “7” are held. The anchor position may be, for example, a numerical value that is incremented every time the description of the anchor is made after setting the position of the first anchor in the document to “0”.

  The correspondence relationship holding unit 546 is a function that is determined in advance in the operation verification apparatus 100 and held in the function holding unit 150. The function for operating the elements of the structured document and the operation target described in the operation description document This is a storage area that holds a correspondence relationship with an operation on an element. For example, the function “clickRadiobuttonByValue” and the template “dom = document.contentsform.element name” of the object serving as the argument are stored in association with information indicating the operation on the radio button in the operation description document. In addition, the function “clickAnchor” and the object model “dom = document.getElementByTagName ('A') [element position]” are stored in association with information indicating the click operation of the send button in the operation description document. To do. The correspondence held in the correspondence holding unit 546 will be described later with reference to FIG.

  FIG. 24 is a block diagram illustrating details of the data processing unit 130 of the operation verification apparatus 100. The data processing unit 130 further includes an element extraction unit 548, an operation description document setting unit 550, and an operation information conversion unit 552.

  When a structured document is read by the document reception unit 540 in response to a request for creating an operation description document, the element extraction unit 548 extracts an operation target element from the data of the structured document. Specifically, among the elements described in the structured document, data relating to the input element and data relating to the display change element are identified, and those data are stored in the memory.

  FIG. 25 shows an example of input elements described in a structured document. The radio button 560 corresponds to the radio button 502 in FIG. Upon detecting the description of the radio button 560, the element extraction unit 548 identifies “input type =“ radio ”” as the input element “radio button”. Also, name = "radRenNum" is identified as the element name. Further, the label “securities number” surrounding the radio button is identified as an element meaning. Further, when detecting the description of the text box 562, the element extracting unit 548 identifies “input type =“ text ”” as the input element “text box”. Also, name = "uid" is identified as the element name. Further, the label “user ID” associated with the text box is identified as an element meaning.

  When the element extraction unit 548 detects the description of the check box 564, the element extraction unit 548 identifies “input type =“ checkbox ”” as the input element “check box”. Also, name = "rank" is identified as the element name. Further, at least one of labels “green license”, “normal license”, and “gold license” associated with the check box is identified as an element meaning. When the element extraction unit 548 detects the description of the pull-down menu 566, the element extraction unit 548 identifies “select” as the input element “pull-down menu”. Also, name = "age" is identified as the element name. Also, the label “age” associated with the pull-down menu is identified as an element meaning.

  FIG. 26 shows an example of the display change element described in the structured document. When detecting the description of the link 570, the element extraction unit 548 identifies “a href” as a display change element. In addition, “help.html” is identified as the name of the change destination. In addition, “alt =“ help screen ”” is identified as the change destination description. Note that the character string “to help screen” enclosed by the anchor tag may be identified as the change destination description.

  26 corresponds to the first transition button 504 in FIG. When the description of the send button 572 is detected, the element extraction unit 548 identifies “form to input type =“ submit ”” as a display change element. In addition, “submit.cgi” is identified as the name of the change destination. Also, the value value “To Contractor Menu” is identified as the description of the change destination. In addition, when detecting the description of the general-purpose button 574, the element extraction unit 548 identifies “button” as a display change element. In addition, “location.reload ()” is identified as the name of the change destination. In addition, the character string “update page” surrounded by the button tags is identified as the change destination description.

  The operation description document setting unit 550 generates an operation description document by collectively setting information on operation target elements extracted by the element extraction unit 548 from one structured document as data of the same operation description document. Specifically, the character string of the element name of the input element is transferred to the first input element information column 522, and the character string of the element meaning is transferred to the second input element information column 524. In addition, the character string of the change destination name of the display change element is transferred to the first display change element information column 526, and the character string of the change destination description is transferred to the second display change element information column 528.

  The operation description document setting unit 550 also stores information on the operation target element in the element information holding unit 544 when setting the operation target element information in the operation description document. For example, the description position (for example, information indicating the column number) of the operation target element in the operation description document and the information indicating the type of the operation target element (radio button, text box, send button, etc.) are recorded in association with each other. . In the case of a display change element, information indicating the anchor position is further recorded.

  The operation information conversion unit 552 causes the operation verification apparatus 100 to store the operation contents for the operation target element described in the operation description document read by the document reception unit 540 according to the correspondence relationship held in the correspondence relationship holding unit 546 in advance. Convert to a defined function, in other words, map. As a result, the operation content file described in the reference technique is created. The operation information conversion unit 552 creates a plurality of operation content files corresponding to each operation when a plurality of types of operations for the operation target element are described in one operation description document. For example, data of three operation content files (one of which is the operation content file of FIG. 20) corresponding to the three records of the operation description document shown in FIG. 21 is set.

  When both the operation to the input element and the operation to the display change element are described in one record of the operation description document, the operation information conversion unit 552 changes the calling order of the function corresponding to the operation to the input element. , Set to be ahead of the calling order of the function corresponding to the operation to the display change element. Specifically, in the operation content file, the function corresponding to the operation on the input element is recorded in the higher order of execution than the function corresponding to the operation on the display change element. The operation information conversion unit 552 stores the operation content file created based on the operation description document in the operation content file holding unit 143.

  FIG. 27 schematically shows a conversion example by the operation information conversion unit 552. No. 1 in FIG. 27 indicates a case where 37001 (value = 0) is selected for the radio button 560 in FIG. In the correspondence holding unit 546, the input operation to the radio button is associated with the function “clickRadiobuttonByValue” and the object template “dom = document.contentsform.element name”. The operation information conversion unit 552 acquires the attribute information of the operation target element described in the operation description document from the element information holding unit 544, and when the operation target element is a radio button, “clickRadiobuttonByValue” is displayed in the function column of the operation content file. "Is set. Also, set “dom = document.contentsform.radRenNum” with the element name “radRenNum” in the object field. Then, “value = 0” described by the user in the operation description document is set in the parameter value column. This setting content corresponds to the operation function 510 in FIG.

  No. 2 in FIG. 27 indicates a case where the character string “user123” is input to the text box 562 in FIG. In the correspondence holding unit 546, the input operation to the text box is associated with the function “typeText” and the object template “dom = document.contentsform.elements ['contentsform: element name']”. The operation information conversion unit 552 acquires the attribute information of the operation target element described in the operation description document from the element information holding unit 544, and when the operation target element is a text box, “typeText” is displayed in the function column of the operation content file. "Is set. In addition, “dom = document.contentsform.elements ['contentsform: uid']” in which the element name “uid” is set is set in the object column. Then, “user123” described by the user in the operation description document is set in the parameter value column.

  No. 3 in FIG. 27 shows a case where a green license (value = green) is selected for the check box 564 in FIG. In the correspondence holding unit 546, the input operation to the check box is associated with the function “clickCheckboxByValue” and the object template “dom = document.contentsform.element name”. The operation information conversion unit 552 acquires the attribute information of the operation target element described in the operation description document from the element information holding unit 544, and when the operation target element is a check box, the operation information file displays “clickCheckboxByValue” in the function column. "Is set. In addition, “dom = document.contentsform.rank” in which the element name “rank” is set is set in the object column. Then, “value = green” described by the user in the operation description document is set in the parameter value column.

  No. 4 in FIG. 27 shows a case where the twenties (value = 20) are selected for the pull-down menu 566 in FIG. In the correspondence holding unit 546, the input operation to the pull-down menu is associated with the function “select” and the object template “dom = document.contentsform.elements ['contentsform: element name']”. The operation information conversion unit 552 acquires the attribute information of the operation target element described in the operation description document from the element information holding unit 544, and when the operation target element is a pull-down menu, “select” is displayed in the function column of the operation content file. "Is set. In addition, “dom = document.contentsform.elements ['contentsform: age']” in which the element name “age” is set is set in the object column. Then, “value = 20” described by the user in the operation description document is set in the parameter value column.

  No. 5 in FIG. 27 shows a case where the click operation of the link 570 in FIG. 26 is designated. In the correspondence holding unit 546, the hyperlink click operation is associated with the function “clickAnchor” and the object template “dom = document.getElementByTagName ('A') [element position]”. The operation information conversion unit 552 acquires the attribute information of the operation target element described in the operation description document from the element information holding unit 544, and when the operation target element is a link, “clickAnchor” is displayed in the function column of the operation content file. Set. Further, “dom = document.getElementByTagName ('A') [7]” in which the anchor position (here, “7”) held in the element information holding unit 544 is set is set in the object column.

  No. 6 in FIG. 27 shows a case where the click operation of the transmission button 572 in FIG. 26 is designated. In the correspondence relationship holding unit 546, the click operation of the send button is associated with the function “clickAnchor” and the object template “dom = document.getElementByTagName ('A') [element position]”. The operation information conversion unit 552 acquires the attribute information of the operation target element described in the operation description document from the element information holding unit 544, and when the operation target element is a send button, the operation information file displays “clickAnchor” in the function column. "Is set. Also, “dom = document.getElementByTagName ('A') [5]” in which the anchor position (here, “5”) held in the element information holding unit 544 is set is set in the object field. It should be noted that when the click operation of the general-purpose button 574 in FIG. 26 is designated, the same setting contents are obtained except that the anchor position set in the object column is different.

The operation of the above configuration will be described below.
FIG. 28 is a flowchart showing the operation of the operation verification apparatus 100. When the document accepting unit 540 accepts a request for creating an operation description document designating a structured document to be tested from a user (Y in S300), the document accepting unit 540 reads the structured document (S302). The element extraction unit 548 extracts information on the operation target element described in the read structured document (S304). The operation description document setting unit 550 is a document in which information related to the operation target element is set. The operation description document setting unit 550 sets operation description document data for allowing the user to describe the operation content of the operation target element. The operation description document output unit 542 The description document is output to the directory designated by the user (S306). If an operation description document creation request is not accepted (N in S300), S302 to S306 are skipped.

  When the document receiving unit 540 receives a request for creating an operation content file designating an operation description document from the user (Y in S308), the document reception unit 540 reads the operation description document (S310). The operation information conversion unit 552 is a function predetermined in the operation verification apparatus 100, and creates an operation content file that specifies calling a function corresponding to an operation on the operation target element described in the operation description document. The operation content is stored in the file holding unit 143 (S312). The operation information conversion unit 552 executes the processing of S312 for each record (row) indicating the operation content described by the user in the operation description document, and creates an operation content file corresponding to each record. If the operation content file creation request is not accepted (N in S308), S310 and S312 are skipped.

  When a test execution request for the structured document to be tested is received (Y in S314), the program generation unit 132 sets the object field and the function described in the operation content file held in the operation content file holding unit 143 for the functions described in the operation content file. A test program is generated by combining the steps of calling each function using the value in the parameter value column as an argument (S316). The program execution unit 134 executes operations on the web page on behalf of the user via the web browser displaying the structured document by sequentially calling the functions described in the test program (S318). If the test execution request is not accepted (N in S314), S316 and S318 are skipped.

  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.

  Although not mentioned in the above embodiment, the operation information conversion unit 552 records the display content of the web page as a proof every time a function corresponding to the operation described in the operation description document is set in the operation content file. Function may be automatically added to the operation content file. For example, when the operation content file of FIG. 20 is set based on the NO1 record of the operation description document of FIG. 21, the screen shot operation is performed before the operation function 510, next to the operation function 510, and next to the operation function 512. A corresponding function may be added.

  It should also 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 the individual constituent elements shown in the embodiments and the modification examples or by their cooperation. For example, the program generation unit described in the claims may be realized by cooperation between the operation information conversion unit 552 and the program generation unit 132. Further, since it can be said that the content of the operation content file is substantially a test execution code, it is understood by those skilled in the art that the program generation unit described in the claims can be realized by the operation information conversion unit 552. By the way.

  DESCRIPTION OF SYMBOLS 100 Operation verification apparatus, 132 Program generation part, 540 Document reception part, 542 Operation description document output part, 544 Element information holding part, 546 Correspondence relation holding part, 548 Element extraction part, 550 Operation description document setting part, 552 Operation information conversion Department.

Claims (6)

An acquisition unit that acquires a structured document that defines the display content of the screen;
An extraction unit that extracts, as a display change element, an element that triggers a process of changing the display content of the screen among the elements described in the acquired structured document;
An output unit for outputting, as an operation description document, a document for allowing a user to describe an operation on the extracted display change element;
A function for operating a predetermined element in a verification device that executes a test program for confirming the display content of the screen, and an operation for the display change element described in the operation description document A correspondence holding unit that holds the correspondence;
A program generation unit for generating the test program by setting a program code for calling a function defined by the verification device corresponding to an operation on the display change element described in the operation description document according to the correspondence relationship; ,
An information processing apparatus comprising:   The said output part is matched with the said display change element in the said structured document, The character string for showing the meaning of the said display change element is transcribe | transferred to the said operation description document. Information processing device.   The program generation unit generates a plurality of test programs corresponding to the plurality of types of operations when a plurality of types of operations with respect to the display change element are described in the operation description document. Or the information processing apparatus according to 2; The extraction unit further extracts, as an input element, an element that receives data input from a user among elements described in the structured document,
The output unit outputs, as the operation description document, a document for allowing a user to describe an operation to the input element in addition to an operation to the display change element,
The correspondence holding unit further holds a correspondence between a function for operating the element predetermined in the verification device and an operation to the input element described in the operation description document,
The program generation unit includes a program code for calling a function defined by the verification device corresponding to an operation on the display change element described in the operation description document, and an operation on the input element described in the operation description document. 4. The information processing apparatus according to claim 1, wherein the test program is generated by combining a program code that calls a function defined by the verification apparatus corresponding to the function. An acquisition unit that acquires a structured document that defines the display content of the screen;
An extraction unit for extracting, as an input element, an element that receives data input from a user among elements described in the obtained structured document;
An output unit for outputting, as an operation description document, a document for allowing a user to describe an operation on the extracted input element;
Correspondence between a function for operating the predetermined element in the verification apparatus for executing a test program for confirming the display content of the screen and an operation on the input element described in the operation description document A correspondence holding unit that holds the relationship;
A program generator for generating the test program by setting a program code that calls a function defined by the verification device corresponding to an operation on the input element described in the operation description document according to the correspondence relationship;
An information processing apparatus comprising: A function to obtain a structured document that defines the display content of the screen,
A function of extracting, as a display change element, an element that triggers a process of changing the display content of the screen among the elements described in the acquired structured document;
A function for outputting, as an operation description document, a document for allowing a user to describe an operation on the extracted display change element;
A function for operating a predetermined element in a verification device that executes a test program for confirming the display content of the screen, and an operation for the display change element described in the operation description document The ability to maintain correspondence,
A function for generating the test program by setting a program code for calling a function defined by the verification device corresponding to an operation on the display change element described in the operation description document according to the correspondence relationship;
A computer program for realizing a computer.

Images