WO2012042560A1 - Dispositif d'acquisition d'image, procédé d'acquisition d'image et programme d'ordinateur - Google Patents

Dispositif d'acquisition d'image, procédé d'acquisition d'image et programme d'ordinateur Download PDF

Info

Publication number
WO2012042560A1
WO2012042560A1 PCT/JP2010/005827 JP2010005827W WO2012042560A1 WO 2012042560 A1 WO2012042560 A1 WO 2012042560A1 JP 2010005827 W JP2010005827 W JP 2010005827W WO 2012042560 A1 WO2012042560 A1 WO 2012042560A1
Authority
WO
WIPO (PCT)
Prior art keywords
unit
browser
test
screen
browser window
Prior art date
Application number
PCT/JP2010/005827
Other languages
English (en)
Japanese (ja)
Inventor
高畠勇人
溝口拓治
石橋琢磨
阪上紗里
伊藤俊廷
Original Assignee
株式会社野村総合研究所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社野村総合研究所 filed Critical 株式会社野村総合研究所
Priority to JP2012506253A priority Critical patent/JP5303680B2/ja
Priority to PCT/JP2010/005827 priority patent/WO2012042560A1/fr
Priority to CN201080043089.XA priority patent/CN102549556B/zh
Publication of WO2012042560A1 publication Critical patent/WO2012042560A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/875—Monitoring of systems including the internet

Definitions

  • This invention relates to a technique for acquiring an image of web content displayed on a screen.
  • the operation test is automatically executed by the test program to save labor of the operation test.
  • an automatic function test tool “QTP (Quick Test Professional)” provided by HP (Hewlett-Packard) automates an operation test by executing a test program created by a user.
  • an image of the web content displayed on the external device may be captured. Then, the normality of the operation may be confirmed by a test engineer confirming the captured image.
  • the display format of the window (hereinafter also referred to as “browser window”) in which the web browser is started differs depending on the web browser. For this reason, when the same web content is displayed on different web browsers, the present inventor has thought that the appearance of the entire browser window may be different, which may reduce the efficiency of the operation test.
  • the present invention has been completed based on the above-mentioned problem recognition of the present inventor, and its main purpose is to provide a technique for acquiring a display image of web content that is highly convenient in an operation test. .
  • an image acquisition device provides a browser window display on a screen for a browser window including a client area in which a web page is displayed and an additional area different from the client area. Specifies the display position of the client area on the screen according to the window position acquisition unit that acquires the position, the display position of the browser window on the screen, the size of the additional area of the browser window, and the size of the status bar of the browser window And an image acquisition unit that captures a display image of the client area in accordance with the display position on the screen specified by the image position specification unit.
  • Another aspect of the present invention is an image acquisition method.
  • This method is a method executed by the image acquisition device, and acquires the display position of the browser window on the screen for a browser window including a client area in which a web page is displayed and an additional area different from the client area. And specifying the display position of the client area on the screen according to the step of displaying, the display position of the browser window on the screen, the size of the additional area of the browser window, and the size of the status bar of the browser window Capturing a display image of the client area according to the display position on the screen specified in the step.
  • FIG. 1 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.
  • FIG. 10 It is a figure which shows the characteristic of two operation methods with respect to a web browser. It is a figure which shows typically the calling relationship between functions about two operation methods with respect to a web browser. It is a block diagram which shows the function structure of the operation verification apparatus of the reference technique 3. It is a block diagram which shows the detail of the program execution part of FIG. 10 is a flowchart showing the operation of the operation verification device of Reference Technique 3. It is a figure which shows typically the calling relationship between the functions in the operation
  • FIG. 31 is a flowchart showing in detail a test program reading process in S402 of FIG. 30.
  • FIG. It is a flowchart which shows the web browser starting process of S419 of FIG. 30 in detail.
  • FIG. 34 is a flowchart showing in detail an IE operation process in S458 of FIG. 33.
  • FIG. 1A is a screen view of the portal site first screen 300.
  • 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”.
  • 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.
  • FIG. 1B is a screen view of the portal site second screen 310.
  • “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.
  • items related to the character string “test” are listed by the “dictionary” service provided by the portal site.
  • the link “test” at the top of the search result column 306 is clicked with the mouse.
  • FIG. 2 is a diagram showing the log 320 when the dictionary test is executed.
  • QTP 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.
  • operations A1 to A3 are recorded as code sentences in a predetermined format.
  • 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).
  • the character string “test” is input.
  • FIG. 3 is a diagram showing a program 330 for executing the dictionary test.
  • 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.
  • the operation A1 is WebEditSet (Browser ("XYZ!). Page ("XYZ!).
  • 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.
  • 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.
  • 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.
  • 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.
  • the logic is set up so that it can cope with the case where the input data is an empty character. 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • the portal site “XYZ!” Is accessed by operating the web browser of the client terminal.
  • QTP generates a log
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • the program generating unit 132 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.
  • the program generation unit 132 specifies 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 that determines whether or not the character string to be assigned to 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.
  • 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.
  • test case setting button 215 When the test case setting button 215 is clicked, a case setting screen 240 of FIG. 10 is displayed.
  • the input data file creation button 213 When the input data file creation button 213 is clicked, the input setting screen 230 of FIG. 9 is displayed.
  • the program creation button 211 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.
  • FIG. 8 is a screen diagram of the program screen 220.
  • the program generation unit 132 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.
  • the input setting screen display unit 122 displays the input setting screen 230.
  • 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
  • the variable column 236 indicates the input data to the parameter q.
  • 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.
  • FIG. 10 is a screen diagram of the case setting screen 240.
  • 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
  • the input data file column 247 indicates the input data file from which the input data is to be extracted.
  • the website of the Internet securities will be described as an operation test target.
  • 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.
  • a program and input data that is, a process and a parameter can be separated.
  • 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.
  • 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.
  • 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.
  • 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.
  • a wrapper module 104 includes the functional blocks shown in FIG.
  • 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).
  • 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).
  • the operation verification apparatus 100 of 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.
  • 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).
  • 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 data on the function setting screen (S120).
  • the user copies the QTP program to a predetermined input area of the QTP module 102 (S122).
  • the user sets an operation test scenario that specifies the QTP program and the input data file as a set (S124).
  • 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 the 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).
  • the user sets an operation test scenario specifying the operation content file and the input data file as a set (S216).
  • the integrated verification module 106 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).
  • 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.
  • the execution engine for the operation test and the wrapper for realizing 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 showing 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.
  • 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 reference data 2 is detected until a user data input operation is detected and an operation test is executed.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the program execution unit 134 executes the operation test program to reproduce a series of operations executed by the user on the web server 400 (S228).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the program generation unit 132 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.
  • 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.
  • 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 repetition 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.
  • 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.
  • 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. 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.
  • login2. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the drop-down list 252 is shown as an example of supporting the value setting on the function setting screen 210.
  • 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.
  • 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.
  • the operation verification apparatus 100 detects a user operation on the web server 400 and creates an operation test program.
  • an operation test program may be generated when the operation verification apparatus 100 acquires an HTML file from the web server 400.
  • 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.
  • Method 1 External operation: By calling an API (Application Programming Interface) published by the web browser to the outside, that is, an interface that accepts an input operation to the test target page being displayed on the web browser (hereinafter also referred to as “operation IF”), Operate from.
  • the operation IF of the reference technique 3 is a function for inputting data to the test target page, executing the form of the test target page, and transmitting a GET request or a POST request to the web server. is there.
  • Method 2 Operation from inside: A script document (hereinafter also referred to as “control code”) that accepts an input operation to the test target page and causes the web browser to execute the input operation is added to the program code (ie, HTML document) of the test target page. . Then, the web browser is operated from the inside by calling the control code. In other words, the web browser is operated by a script document embedded in advance in a web page displayed on the web browser.
  • control code ie, HTML document
  • the control code of Reference Technology 3 is a program code in which a function including an interface function that accepts an input operation to the test target page from the outside is described. Further, the program code describes a function including a function for updating the display contents of the test target page by operating the DOM tree of the test target page and a function for transmitting a GET request or a POST request to the web server.
  • the control code may be described in a predetermined script language (for example, JAVA script (“JAVA” is a registered trademark)).
  • FIG. 19 shows the characteristics of the two operation methods for the web browser.
  • the figure compares the operation method from the outside with the operation method from the inside.
  • the reliability of the operation test itself which is assumed to be the most important, it can be said that the operation method from the outside is superior because the operation method from the inside rewrites the test target page.
  • the operation method from the outside depends on the operation IF in the web browser, so the operation method from the inside is superior.
  • the operation verification device operates the web browser from the inside. Propose. As a result, it is possible to support operation tests using various types of web browsers while ensuring reliability of the operation tests at best effort.
  • FIG. 20 schematically shows a calling relationship between functions for two operation methods for the web browser.
  • the web server 400 is an information processing apparatus that provides a test target page.
  • Browser A 402a, browser B 402b, browser C 402c, and browser D 402d, which are collectively referred to as browser 402, are web browsers that function as HTTP user agents, and execute display processing / operation processing of a test target page.
  • the browser A 402a and the browser B 402b shown in the figure disclose the operation IF to the outside, and the browser C 402c and the browser D 402d make the operation IF private.
  • the browser A engine 404a and the browser B engine 404b which are collectively referred to as the individual browser engine 404, are program codes that call the operation IFs of the browser A 402a and the browser B 402b, respectively.
  • the common IF 406 is an interface for calling the operation IF of each of the plurality of types of browsers 402, and is a program code having a common format interface that does not depend on the operation IFs that are different for each of the plurality of types of browsers 402.
  • the browser A engine driver 408a and the browser B engine driver 408b which are collectively referred to as the individual browser engine driver 408, convert the data in the common IF 406 format independent of the type of the browser 402 into data in the operation IF format different for each browser 402. By performing the conversion, the operation test program and the individual browser engine 404 are bridged.
  • the proxy server 410 functions as a reverse proxy that acquires a test target page from a web server as a proxy of the browser 402. After adding the control code to the test target page, the proxy server 410 provides the test target page to the browser C402c and the browser D402d.
  • the internal operation engine 412 calls the control code added to the test target page via the proxy server 410.
  • the internal operation engine driver 414 bridges the operation test program and the internal operation engine 412 by converting data in the common IF 406 format into data in a predetermined format for calling a control code.
  • the operation test program calls the common IF 406. Accordingly, the web browser operation IF is called via the individual browser engine driver 408 and the individual browser engine 404, whereby the web browser is operated, and the input operation to the test target page is realized.
  • the proxy server 410 adds a control code to the test target page and causes the test browser to display the test target page.
  • the operation test program calls the common IF 406, and the control code added to the test target page is called through the internal operation engine driver 414, the internal operation engine 412, and the proxy server 410.
  • the operation test program can always operate the test execution browser by calling the common IF 406 regardless of the type of web browser (hereinafter also referred to as “test execution browser”) used in the operation test of the web page.
  • test execution browser a type of web browser
  • FIG. 21 is a block diagram showing a functional configuration of the operation verification apparatus of Reference Technique 3.
  • the functional blocks corresponding to the functional blocks of the operation verification apparatus 100 shown in the reference techniques 1 and 2 are denoted by the same reference numerals.
  • Functional blocks with the same reference numerals are described when the functions are different from those already described in Reference Techniques 1 and 2, and similar functions are already described, and thus description thereof is omitted as appropriate.
  • the operation verification apparatus 100 further includes a browser processing unit 160 in addition to the functional blocks shown in FIG.
  • the browser processing unit 160 corresponds to the browser 402 in FIG. 20 and functions as a web browser.
  • a single operation verification apparatus 100 may include a plurality of types of browser processing units 160.
  • the program execution unit 134 selects an external operation method or an internal operation method according to the type of the test execution browser, in other words, the mode of the browser processing unit 160 when executing the operation test program.
  • the unit 160 is operated.
  • FIG. 22 is a block diagram showing details of the program execution unit 134 of FIG.
  • the program execution unit 134 includes a test subject selection unit 162, an external operation execution unit 164, a proxy processing unit 166, an internal operation execution unit 168, and a witness setting unit 170.
  • the test subject selection unit 162 acquires information indicating the type of the test execution browser, in other words, information indicating the disclosure status of the operation IF in the browser processing unit 160 from a predetermined setting file or an operation test program, and according to the information Determine the execution subject of the operation test. For example, with reference to a table in which various web browsers are associated with the disclosure status of each operation IF, the disclosure status of the operation IF in the test execution browser may be specified.
  • the test subject selection unit 162 selects an external operation execution unit 164 described later as an execution subject of the operation test.
  • a proxy processing unit 166 and an internal operation execution unit 168 described later are selected as execution subjects of the operation test.
  • the external operation execution unit 164 corresponds to the individual browser engine 404 in FIG. 20 and detects the call to the common IF 406 by the operation test program when the operation test program is executed. Then, the browser processing unit 160 is operated by calling an operation IF disclosed by the browser processing unit 160 to execute an input operation on the test target page.
  • the proxy processing unit 166 corresponds to the proxy server 410 in FIG. 20, obtains the test target page requested from the browser processing unit 160 by proxy from the web server 400, and inserts a control code into the HTML code of the test target page. Then, the HTML code of the modified test target page is sent to the browser processing unit 160 for display.
  • the proxy processing unit 166 receives a control code call from an internal operation execution unit 168, which will be described later, and calls the control code added to the test target page. Communication between the proxy processing unit 166 and the test target page may be implemented as asynchronous communication using XMLHttpRequest.
  • the internal operation execution unit 168 corresponds to the internal operation engine 412 in FIG. 20, and detects the call to the common IF 406 by the operation test program when the operation test program is executed. Then, by calling the control code added to the test target page via the proxy processing unit 166, the browser processing unit 160 is operated to perform an input operation on the test target page.
  • the proxy processing unit 166 and the internal operation execution unit 168 may be implemented using a Selenium (http://seleniumhq.org/) library published as a test automation tool.
  • the testimony object setting unit 170 sets data (hereinafter also referred to as “testimony object”) that proves the result of the operation test. Is stored in the result holding unit 152.
  • a screen snap of the test target page displayed on the display by the browser processing unit 160 may be acquired, and data transmitted and received by HTTP communication with the web server 400 may be acquired.
  • the screen snap acquisition function may be provided by the operating system (hereinafter also referred to as “OS”) of the operation verification apparatus 100, and the HTTP communication data acquisition function is a packet installed in the operation verification apparatus 100. It may be provided by capture software.
  • FIG. 23 is a flowchart showing the operation of the operation verification apparatus 100.
  • This figure shows an operation when an operation test program is executed in the operation verification apparatus 100. For example, it shows details of S218 in FIG. 12, and also shows details of S228 in FIG.
  • the test subject selection unit 162 selects an operation test execution engine according to the disclosure status of the operation IF in the browser processing unit 160 (S300).
  • the browser processing unit 160 requests the web server 400 to provide a test target page (S302).
  • the proxy processing unit 166 obtains the test target page by proxy, adds the control code to the HTML code, and then transmits the test target page to the browser.
  • the data is sent to the processing unit 160 (S306). If the operation IF is disclosed (Y in S304), S306 is skipped.
  • the browser processing unit 160 displays the test target page on a predetermined display (S308).
  • the proof object setting unit 170 sets a proof object of the operation test, such as obtaining a screen snap of the test target page, and stores it in the result holding unit 152 (S310).
  • the operation verification apparatus 100 of the reference technique 3 is obtained by adding a configuration for supporting a web page operation test in a plurality of types of web browsers on the premise of the configuration of the operation verification apparatus 100 described in the reference techniques 1 and 2. is there. Therefore, the configuration of the operation verification apparatus 100 of the reference technique 3 has the effects described in the reference techniques 1 and 2 as they are, and further has the following effects.
  • the operation verification apparatus 100 can execute an operation test of web pages in a plurality of types of web browsers regardless of whether or not the operation IF is disclosed in the web browser by implementing an internal operation method as the web browser operation method. .
  • the operation verification apparatus 100 also implements an external operation method as a web browser operation method. When the web browser publishes an operation IF, an operation test is performed by an external operation method. It becomes easy to ensure the reliability of the operation test.
  • the operation verification device 100 of the reference technique 3 has been described above.
  • the proxy processing unit 166 corresponding to the proxy server 410 is included in the operation verification apparatus 100.
  • the proxy processing unit 166 may be provided in another information processing apparatus different from the operation verification apparatus 100.
  • a plurality of types of web browsers may be installed in the single operation verification device 100, and the operation verification device 100 may include a plurality of browser processing units 160 corresponding to the plurality of types of web browsers.
  • the program execution unit 134 may execute an operation test on the test target page in each web browser. That is, the processing shown in FIG. 23 may be executed in parallel for each web browser. Since an operation test in a plurality of types of web browsers can be performed in the single operation verification apparatus 100, an operation test can be realized efficiently and at low cost.
  • either the internal operation method or the external operation method was selected for each type of web browser.
  • both formulas may be combined in an operational test with a single web browser.
  • an operation that can be executed using the published operation IF applies an external operation method, that is, the external operation execution unit 164 calls the operation IF.
  • the operation method from the inside is applied to an operation that cannot be executed by the published operation IF, that is, the internal operation execution unit 168 calls a control code. Since script code written in a web page generally allows a wide range of operations, constraints from external operation methods that occur depending on the operation IF specifications are complemented by internal operation methods. can do.
  • the reference technique 4 is related to the reference technique 3 and proposes an operation verification apparatus 100 that supports a web page operation test by various types of web browsers.
  • “Windows”, “Internet Explorer”, “Firefox”, “Mac”, “Mac OS”, “Safari” (Safari) ) ",” JAVA ", etc. are trademarks or registered trademarks of the respective companies.
  • FIG. 24 schematically shows a call relationship between functions in the web page operation test.
  • the operation verification engine 500 in FIG. 5 shows a core function for an operation test of a web page in the operation verification apparatus 100.
  • a Windows environment 540 indicates an environment in the Windows OS
  • a Mac environment 560 indicates an environment in the MacOS.
  • the operation verification apparatus 100 in which Windows is installed in the OS may be configured by a combination of the operation verification engine 500 and the Windows environment 540.
  • the operation verification apparatus 100 in which MacOS is installed in the OS may be configured by a combination of the operation verification engine 500 and the Mac environment 560.
  • the IE (Internet Explorer) browser 542 in FIG. 24 discloses COM550, which is an operation IF that can be called from an external application. Therefore, the operation method from the outside in the reference technique 3 is adopted for the operation of the web page displayed on the IE browser 542.
  • the FF (Firefox) browser 546 and the Safari browser 562 do not disclose an operation IF that can be called from an external application. Therefore, the operation method from the inside in the reference technique 3 is adopted for the operation on the web page displayed on these browsers.
  • FIG. 24 shows a selenium module 530 for an operation method from the inside.
  • the selenium module 530 is a server program of Selenium (http://seleniumhq.org/) that corresponds to the internal operation engine 412 and the proxy server 410 of FIG. 20 and is published as a test automation tool.
  • the selenium module 530 assigns a unique identifier to a web browser window (hereinafter also referred to as “browser window”) that displays a web page. Then, by specifying the identifier from the client, the browser window (in other words, the web page) to be operated is uniquely identified.
  • the common IF 406 corresponds to the common IF 406 in FIG.
  • the IE driver 502 corresponds to the individual browser engine driver 408 of FIG.
  • the IE driver 502 functions as a bridge between an operation test program (hereinafter also referred to as “test program”) and the IE browser 542 in a web page operation test using the IE browser 542.
  • the IE driver 502 includes an IE window manager 504, an IE browser operation unit 506, and an IE dialog operation unit 508.
  • the IE window manager 504 has an identifier assigned by the user in the test program (hereinafter also referred to as “user assigned ID”) and an identifier assigned by the OS (hereinafter “ The correspondence relationship with the “OS allocation ID”) is managed.
  • the IE browser operation unit 506 specifies an OS allocation ID corresponding to the user allocation ID specified by the test program for a browser window (hereinafter also referred to as “operation target window”) on which a web page should be operated.
  • the COM 550 function corresponding to the operation content specified by the test program is specified.
  • the IE browser 542 is operated from the outside, and the IE browser 542 is caused to execute the web page operation in the operation target window.
  • the IE browser 542 may display a dialog box by directly using the resources of the Windows OS.
  • this dialog box is also referred to as an “OS dialog”.
  • the IE dialog operation unit 508 operates the OS dialog 544 displayed by the IE browser 542. Specifically, when the OS dialog 544 is detected, an operation for the OS dialog 544 is executed by calling a Win32 API 552 function corresponding to the dialog operation specified by the test program. Note that typical operation contents for the OS dialog 544 include input of a character string, selection of a display item, and pressing of a button. The same applies to the operation contents for the FF dialog 548 and the Safari dialog 564 described later.
  • the FF driver 510 corresponds to the internal operation engine driver 414 in FIG. 20 and functions as a bridge between the test program and the FF browser 546 in the web page operation test using the FF browser 546.
  • the FF driver 510 includes an FF window manager 512, an FF browser operation unit 514, and an FF dialog operation unit 516.
  • the FF window manager 512 assigns an identifier (hereinafter also referred to as “selenium assignment ID”) assigned by the selenium module 530 to the browser window displaying the web page, and a user assignment ID and an OS assignment ID for the window. Manage the correspondence of.
  • an identifier hereinafter also referred to as “selenium assignment ID”
  • the FF browser operation unit 514 specifies a selenium assignment ID corresponding to the user assignment ID specified by the test program for the operation target window.
  • the function of the selenium module 530 corresponding to the operation content specified by the test program is specified.
  • the function of the selenium module 530 is called by specifying the selenium allocation ID.
  • the selenium module 530 specifies an operation target window based on the selenium assignment ID, and calls a control code corresponding to the called function among the control codes of the web page displayed in the operation target window.
  • a specific JAVA script is operated on the operation target web page, and the FF browser 546 is operated from the inside, and the operation of the web page specified by the test program is realized.
  • the FF browser operation unit 514 suppresses calling of the selenium module 530 when a predetermined operation to be operated without going through the selenium module 530, typically, a browser window closing process is designated by the test program. Instead, similar to the IE dialog operation unit 508, the operation is executed by calling the Win32 API 552.
  • the FF browser 546 may display the OS dialog 544 or a dialog box (hereinafter, also referred to as “FF dialog”) using a unique resource of the FF browser 546. is there.
  • the OS dialog 544 is displayed in cooperation with the OS, such as saving a file, and the FF dialog 548 is displayed as an alert dialog by JAVA script.
  • the FF dialog operation unit 516 operates the OS dialog 544 and the FF dialog 548. Specifically, when the display of the OS dialog 544 is detected, an operation for the OS dialog 544 is executed by calling a Win32 API 552 function corresponding to the dialog operation specified by the test program. When the display of the FF dialog 548 is detected, an operation for the FF dialog 548 is executed by calling the FF plug-in 554 which is an extension function set in advance in the FF browser 546 and instructing the dialog operation. Details of this will be described later with reference to FIG.
  • the Safari driver 520 corresponds to the internal operation engine driver 414 in FIG. 20 and functions as a bridge between the test program and the Safari browser 562 in the web page operation test using the Safari browser 562.
  • the Safari driver 520 includes a Safari window manager 522, a Safari browser operation unit 524, and a Safari dialog operation unit 526.
  • the Safari window manager 522 manages the correspondence between the user allocation ID, the OS allocation ID, and the selenium allocation ID for the window in which the web page is displayed. In MacOS, it is the Safari browser 562 that assigns an ID to a browser window, but for simplicity of description, the name is unified with the OS assignment ID.
  • the Safari browser operation unit 524 specifies a selenium allocation ID corresponding to the user allocation ID specified by the test program for the operation target window.
  • the function of the selenium module 530 corresponding to the operation content specified by the test program is specified.
  • the function of the selenium module 530 is called by specifying the selenium allocation ID.
  • an operation on the operation target web page is executed via the selenium module 530.
  • the Safari browser operation unit 524 suppresses calling of the selenium module 530 when a predetermined operation to be operated without going through the selenium module 530, typically, a window closing process is designated by the test program. Instead, the operation is executed by calling an API provided by MacOS. Specifically, an accessibility API 566 which is an API group provided for use by an application for a disabled person is called. Details of this will be described later with reference to FIG.
  • the Safari browser 562 may display a dialog (hereinafter also referred to as “Safari dialog”).
  • Sesi dialog a dialog
  • the Safari dialog operation unit 526 detects the display of the Safari dialog 564
  • the Safari dialog operation unit 526 calls the MacOS API corresponding to the dialog operation specified by the test program to execute the operation on the Safari dialog 564. Also at this time, the above-described accessibility API 566 is called. Details of this will be described later with reference to FIG.
  • FIG. 25 shows an example of data stored in the selenium window manager 532.
  • the selenium window manager 532 holds the user assignment ID, selenium assignment ID, and OS assignment ID assigned to each browser window in the web page operation test in association with each other.
  • the operation of the IE browser 542 is not performed through the selenium module 530. Therefore, the IE window manager 504 holds only the user allocation ID and the OS allocation ID in association with each other.
  • the FF browser operation unit 514 and the Safari browser operation unit 524 are collectively referred to as a selenium browser operation unit 534 that operates a web browser via the selenium module 530.
  • FIG. 26 shows an operation mechanism for the FF dialog 548 shown in FIG.
  • a window handler 572 implemented by a JAVA script is preset in the FF profile 570 read by the FF browser 546.
  • the function of the window handler 572 is additionally incorporated by reading the window handler 572 into the storage area of the FF plug-in 554.
  • the listener object for detecting window generation by the FF browser 546 is registered in the window watcher 582 via the XPConnect 578 and the XPCOM 580.
  • the window handler 572 detects that the FF dialog 548 has been generated via the registered listener object, the window handler 572 performs socket communication with the socket server 574 of the FF dialog operation unit 516 and notifies that the FF dialog 548 has been generated. To do.
  • the notification information includes a display character string in the FF dialog 548 and display mode information indicating a display object such as a button.
  • the FF dialog operation unit 516 When notified that the FF dialog 548 has been generated, the FF dialog operation unit 516 is a function corresponding to the dialog operation specified by the test program, and notifies the window handler 572 of the identification information of the XPCOM 580 function. .
  • the window handler 572 operates the FF dialog 548 by calling the XPCOM 580 function designated by the FF dialog operation unit 516.
  • the FF dialog operation unit 516 may appropriately adjust the operation content for the FF dialog 548 in accordance with the display mode of the FF dialog 548. For example, for the button pressing operation specified by the test program, the ID of the button to be pressed may be added and the operation instruction may be notified to the window handler 572.
  • the FF browser 546 displays the FF dialog 548 as an alert dialog of JAVA script. Since the FF dialog 548 is displayed using resources unique to the FF browser 546, the contents of the dialog cannot be determined from the OS side. For example, display character strings and display objects such as buttons in the FF dialog 548 cannot be determined. For this reason, an operation via the Win32 API 552 cannot be performed like an operation on the OS dialog 544. For example, the pressing operation on the button displayed in the FF dialog 548 cannot be performed.
  • the display contents of the FF dialog 548 can be acquired, and an operation for the FF dialog 548 is realized.
  • a function for dialog operation (for example, a program code similar to the window handler 572) is set in the program code of the web page.
  • the FF dialog 548 is a modal dialog (an application modal dialog or a system modal dialog)
  • the window handler 572 incorporated as the FF plug-in 554 can continue the operation to the modal dialog. From this viewpoint, it can be said that the window handler 572 is desirably set as an extended function of the FF browser 546.
  • FIG. 27 shows an operation mechanism for the Safari dialog 564 shown in FIG.
  • An Apple script 584 in the figure is a script for calling an Apple event, which is an inter-application communication technique in MacOS.
  • a system event 586 is an application provided by MacOS, and implements the calling of the accessibility API 566 by the Apple script 584 through the Apple script 584 and the accessibility API 566.
  • FIG. 27 shows MacOS in four layers, and an upper layer provides an API having a higher abstraction level than a lower layer, in other words, provides a high level API.
  • the accessibility API 566 belongs to the highest hierarchy “user experience”. As described above, the accessibility API 566 is an API group related to a UI automation function for ensuring usability for persons with disabilities.
  • the operation contents to be automated include various user interface (screen) operations such as opening a window and pressing a button.
  • the Safari dialog operation unit 526 specifies the function of the accessibility API 566 corresponding to the dialog operation specified by the test program, and transmits the Apple script 584 specifying the function to the system event 586. Thus, a dialog operation function prepared as the accessibility API 566 is called through the system event 586.
  • the operation on the Safari dialog 564 can be realized using a lower level API group in MacOS.
  • the Safari dialog operation unit 526 can execute the operation on the Safari dialog 564 by calling the “Quartz” API of the graphics and media hierarchy.
  • the accessibility API 566 provides a high-level function corresponding to the UI operation by the user, the accessibility API 566 can be used to reduce the code amount of the Safari dialog operation unit 526 and to improve the maintainability thereof. Can do.
  • the Safari browser operation unit 524 calls the accessibility API 566 for a predetermined operation to be performed without going through the selenium module 530 among the operations on the web page, as in the Safari dialog operation unit 526. This causes the MacOS or Safari browser 562 to execute the operation.
  • FIG. 28 is a block diagram illustrating a functional configuration of the operation verification apparatus 100 of the reference technique 4.
  • functional blocks that are the same as or correspond to the functional blocks of the operation verification apparatus 100 shown in the reference techniques 1 to 3 are denoted by the same reference numerals.
  • Functional blocks with the same reference numerals are described when their functions are different from those already described in Reference Techniques 1 to 3, and descriptions of similar functions are omitted as appropriate.
  • the operation verification apparatus 100 further includes a window ID holding unit 154 and an ID acquisition unit 139.
  • the window ID holding unit 154 and the ID acquisition unit 139 correspond to the IE window manager 504 and the selenium window manager 532 in FIG. That is, the window ID holding unit 154 holds the correspondence relationship between the user assignment ID, selenium assignment ID, and OS assignment ID assigned to the browser window that displays the web page.
  • the ID acquisition unit 139 acquires an OS allocation ID for the browser window from the OS (Windows OS or MacOS).
  • the ID acquisition unit 139 acquires a window handle obtained by calling Win32 API.
  • the HWND value returned by the function “FindWindow” is acquired as a long integer and stored in the OS allocation ID field of the window ID holding unit 154.
  • those not stored in the window ID holding unit 154 may be added as new records in the window ID holding unit 154.
  • the ID acquisition unit 139 acquires a long value obtained from the Safari browser 562 using the Apple script, and stores it in the OS allocation ID field of the window ID holding unit 154.
  • the following script tell application "Safari" return id of windows end tell To obtain a list of long values assigned by the Safari browser 562 to each browser window.
  • the ID acquisition unit 139 acquires “seleniumWindowName” which is a window attribute value assigned to each browser window by the selenium module 530 (Selenium-CORE). Then, the window attribute value is stored as a selenium allocation ID in the selenium allocation ID field of the window ID holding unit 154. For example, a list of window attribute values managed by the selenium module 530 is acquired by calling the function “getAttributeFromAllWindows (“ seleniumwindowName ”)” of the selenium module 530.
  • the ID acquisition unit 139 acquires a user allocation ID allocated to the browser window by an ID allocation unit 174 and an ID allocation unit 180, which will be described later, and stores them in the user allocation ID field of the window ID holding unit 154.
  • the ID acquisition unit 139 sequentially stores the user allocation ID, the selenium allocation ID, and the OS allocation ID in the window ID holding unit 154 in the allocation order on the time axis (the acquisition order in the ID acquisition unit 139). Also good.
  • the ID for example, selenium allocation ID
  • the ID previously allocated on the time axis is similarly associated with another ID (for example, user allocation ID) previously allocated on the time axis.
  • FIG. 29 is a block diagram showing details of the program execution unit 134 of FIG.
  • the program execution unit 134 includes a test environment determination unit 171, an external operation execution unit 164, a proxy processing unit 166, an internal operation execution unit 168, and a witness setting unit 170.
  • functional blocks in the figure functional blocks that are the same as or correspond to the functional blocks of the program execution unit 134 shown in the reference technique 3 are denoted by the same reference numerals. Functional blocks with the same reference numerals are described when their functions are different from those already described in Reference Technology 3, and descriptions of similar functions are omitted as appropriate.
  • the test environment determination unit 171 corresponds to the test subject selection unit 162 in the reference technique 3 (FIG. 21), and is based on the environment for the operation test of the web page, specifically based on the combination of the OS and the web browser. Determine the operation test method. For example, a web browser operation method and a dialog operation method are determined.
  • the external operation execution unit 164 corresponds to the IE browser operation unit 506 in FIG.
  • the external operation execution unit 164 includes an ID assignment unit 174 and a dialog operation unit 176.
  • the ID allocation unit 174 detects that a function (command) for generating a new browser window is specified in the test program during execution of the test program, the ID allocation unit 174 uses the ID specified as an argument of the command as the user allocation ID. Determine as.
  • a new ID that is unique in the external operation execution unit 164 and the internal operation execution unit 168 may be assigned as a user allocation ID.
  • the dialog operation unit 176 corresponds to the IE dialog operation unit 508 in FIG. 24 and periodically monitors the dialog settings by the IE browser 542. For example, the above-described FindWindow function of Win32 API 552 may be periodically called to detect that a dialog window has been generated.
  • the dialog operation unit 176 operates the OS dialog 544 displayed on the IE browser 542 via the Win32 API 552.
  • the external operation execution unit 164 includes a web page operation function that can be specified by the test program, a function defined as the web browser operation IF, a function defined in COM550 or Win32 API 552 in Reference Technique 4. Holds a table that stores the correspondence relationship.
  • the external operation execution unit 164 refers to the table and calls a COM550 or Win32 API 552 function corresponding to the function specified by the test program.
  • the proxy processing unit 166 corresponds to the selenium module 530 in FIG. As already described in the reference technique 3, the proxy processing unit 166 acquires the operation target web page by proxy.
  • the program code of the web page is a program code implemented by a JAVA script, and a function group ("control code" in Reference Technology 3) prepared in advance for executing various operations on the web page is added. To do. Then, the web page after the addition of the control code is displayed on the browser processing unit 160. Further, in response to an operation instruction from the internal operation execution unit 168, a function of a control code corresponding to the operation instruction is called to execute the web page operation in an intermediary manner.
  • the proxy processing unit 166 includes an ID issuing unit 178 and an add-on setting unit 179.
  • the ID issuing unit 178 issues identification information for uniquely identifying the browser window in the proxy processing unit 166 when the browser processing unit 160 displays the web page after the addition of the control code. This identification information is acquired as a selenium allocation ID by the ID acquisition unit 139.
  • the add-on setting unit 179 specifies the FF profile 570 including the window handler 572 in FIG. 26 when the FF browser 546 is to be activated in order to display the web page after the addition of the control code on the browser processing unit 160. Start up. As a result, the window handler 572 is incorporated as an extended function of the FF browser 546.
  • the internal operation execution unit 168 corresponds to the selenium browser operation unit 534 in FIG.
  • the internal operation execution unit 168 includes an ID assignment unit 180 and a dialog operation unit 182.
  • the ID allocation unit 180 has the same configuration as the ID allocation unit 174 of the external operation execution unit 164.
  • the internal operation execution unit 168 holds a table that stores the correspondence between web page operation functions that can be specified by the test program and web page operation functions defined in the selenium module 530.
  • the external operation execution unit 164 refers to the table and calls a function of the selenium module 530 corresponding to the function specified by the test program as an operation instruction to the selenium module 530.
  • the dialog operation unit 182 corresponds to the FF dialog operation unit 516 and the Safari dialog operation unit 526 in FIG.
  • the dialog operation unit 182 periodically monitors the dialog settings by the FF browser 546. For example, the above-described FindWindow function of Win32 API 552 may be periodically called to detect that a dialog window has been generated.
  • the dialog operation unit 182 operates the OS dialog 544 displayed on the FF browser 546 via the Win32 API 552. Further, the dialog operation unit 182 detects the FF dialog 548 displayed by the FF browser 546 via the FF plug-in 554 and operates it via the FF plug-in 554.
  • the dialog operation unit 182 periodically monitors the dialog settings by the Safari browser 562.
  • the above-mentioned Apple script may be periodically executed to detect a dialog window setting in the Safari browser 562.
  • the dialog operation unit 182 operates the Safari dialog 564 displayed on the Safari browser 562 via the accessibility API 566.
  • FIG. 30 is a flowchart showing the operation of the operation verification apparatus 100.
  • This figure shows an operation when an operation test program is executed in the operation verification apparatus 100. For example, it shows details of S218 in FIG. 12, and also shows details of S228 in FIG. That is, as illustrated in FIG. 14, the operation verification apparatus 100 supports the operation check of the web page by reproducing a series of input operations performed by the user in advance on the web page.
  • 30 can be said to be a more detailed version of the flowchart of FIG.
  • the test environment determination unit 171 determines the type of the OS and web browser that are the execution environment of the operation test. Then, according to the determination result, the external operation execution unit 164 or the internal operation execution unit 168 is selected as the operation subject of the web page (S400).
  • the program execution unit 134 in other words, the external operation execution unit 164 or the internal operation execution unit 168 selected as the operation subject executes a test program reading process to be described later (S402).
  • This test program is an operation test program set by the series of processes shown in FIG.
  • “waitForNewWindow” is specified as a function for specifying operation 1 and operation 2
  • the URL of the web page and the user-specified ID are set as arguments.
  • “selectWindow” is designated as a function for designating operations 3 and 7, and an ID designated by the user is set as an argument thereof.
  • functions for specifying the operation 4 the operation 5, and the operation 8
  • functions for various operations such as WebEditSet and WebElementClick are specified.
  • a predetermined function for dialog operation is designated as a function for designating the operation 6.
  • the operation commands described in the test program are executed sequentially.
  • an unexecuted operation command remains in the test program (N in S404)
  • the display of a new web page is requested in the test program, that is, when the above operation 1 and operation 2 are to be executed
  • the external operation execution unit 164 or the ID assignment unit of the internal operation execution unit 168 selected as the operation subject assigns the ID specified by the operation command as the user assignment ID.
  • the ID acquisition unit 139 acquires the user assignment ID and stores it in the window ID holding unit 154 (S408).
  • the external operation execution unit 164 causes the web browser to acquire the data of the operation target web page by calling the operation IF (S412). Then, the browser window displaying the operation target web page is displayed on the display (S420).
  • Y in S410 is when the web browser is the IE browser 542, and the COM 550 corresponds to the operation IF at this time.
  • N in S410 When the operation IF of the web browser is not disclosed (N in S410), the internal operation execution unit 168 instructs the proxy processing unit 166 to acquire the operation target web page.
  • the ID issuing unit 178 of the proxy processing unit 166 issues a selenium allocation ID (S414).
  • the proxy processing unit 166 acquires data of the operation target web page (S416), and adds a control code to the data of the web page (S418).
  • the proxy processing unit 166 after executing a web browser activation process described later (S419), passes the web page data to which the control code is added to the web browser, and displays a browser window for displaying the operation target web page on the display. (S420).
  • N in S410 is when the web browser is the FF browser 546 or the Safari browser 562.
  • the ID acquisition unit 139 calls an API provided by the OS, acquires the OS assignment ID assigned by the OS to the browser window, and stores the acquired OS assignment ID in the window ID holding unit 154.
  • the API provided by the selenium module 530 is called to acquire the selenium assignment ID assigned by the selenium module 530 to the browser window and store it in the window ID holding unit 154. To do.
  • the user allocation ID, the OS allocation ID, and the selenium allocation ID allocated to the browser window A and the browser window B are associated with each other (S422).
  • the program execution unit 134 executes a web page operation process described later (S426). If no web page operation is specified in the test program (N in S424), S426 is skipped. After the operation on the web page, the proof object setting unit 170 stores the proof object data such as the screen snapshot in the result holding unit 152 (S428), and the process returns to S404.
  • the proof object setting unit 170 records the proof object such as a screen snap related to the browser window as the proof object in association with the user assignment ID assigned to the browser window.
  • the user who confirms the result of the operation test on the web page can confirm the proof corresponding to the ID designated by the user, and the convenience of the user in the confirmation of the proof can be improved.
  • FIG. 31 is a flowchart showing in detail the test program reading process in S402 of FIG.
  • the program execution unit 134 reads an operation test program (S430). When a predetermined function indicating a dialog operation is specified in the program (Y in S432), the program execution unit 134 stores the content of the dialog operation (the above operation 6) in a predetermined dialog operation holding table (S434). ). If no dialog operation is specified (N in S432), S434 is skipped.
  • FIG. 32 is a flowchart showing in detail the web browser activation process in S419 of FIG.
  • the proxy processing unit 166 activates a web browser for the operation test (S440).
  • the web browser for the operation test is the FF browser 546 (Y in S442)
  • the add-on setting unit 179 adds on the window handler 572 as an extended function of the FF browser 546 (S444).
  • the window handler 572 registers a listener for detecting the FF dialog 548 in the FF browser 546 (S446). If the web browser for the operation test is not the FF browser 546 (N in S442), S444 and S446 are skipped.
  • FIG. 33 is a flowchart showing in detail the web page operation process of S426 of FIG.
  • the internal operation execution unit 168 executes a Mac operation process described later (S452). If the OS is not MacOS (N in S450), S452 is skipped.
  • the OS is Windows (Y in S454) and the web browser is the IE browser 542 (Y in S456)
  • the external operation execution unit 164 executes an IE operation process described later (S458).
  • the web browser is not the IE browser 542 (N in S456) and is the FF browser 546 (Y in S460)
  • the internal operation execution unit 168 executes an FF operation process described later (S462). If the web browser is not the FF browser 546 (N in S460), S462 is skipped, and if the OS is not Windows (N in S454), S456 and subsequent steps are skipped.
  • FIG. 34 is a flowchart showing in detail the Mac operation process in S452 of FIG.
  • a window selection operation (the above operations 3 and 7) is specified in the test program (Y in S470)
  • the ID allocation unit 180 of the internal operation execution unit 168 identifies the ID received as an argument as the user allocation ID. (S472).
  • a predetermined operation to be executed via the Safari browser 562 (the above-described operations 4, 5, and 8, hereinafter also referred to as “browser operation”) is designated instead of the window selection operation (N in S470) (Y in S474)
  • the internal operation execution unit 168 specifies the selenium allocation ID associated with the user allocation ID (S476).
  • the selenium module 530 of an operation instruction designating the selenium allocation ID the function corresponding to the operation instruction among the control codes added to the web page is called by the selenium module 530 (S478).
  • OS operation When not a browser operation (N in S474) but a predetermined operation to be executed via MacOS (the above operations 9 and 10, hereinafter also referred to as “OS operation”) is designated (Y in S480), an internal operation is executed.
  • the unit 168 identifies the OS assignment ID associated with the user assignment ID (S482). Then, by designating the OS allocation ID and calling a function of the accessibility API 566 corresponding to the operation content, Mac OS is caused to execute the OS operation on the browser window (S484). If it is not an OS operation (N in S480), S482 and S484 are skipped.
  • the dialog operation unit 182 of the internal operation execution unit 168 detects the display of the Safari dialog 564 (Y in S486)
  • the operation content for the dialog (the above operation 6) is acquired from the dialog operation holding table (S488).
  • an operation for the Safari dialog 564 is executed by calling a function of the accessibility API 566 corresponding to the operation content (S490). If the display of the Safari dialog 564 is not detected (N in S486), S488 and S490 are skipped.
  • FIG. 35 is a flowchart showing in detail the IE operation process in S458 of FIG.
  • a window selection operation (the above operations 3 and 7) is specified in the test program (Y in S500)
  • the ID assignment unit 174 of the external operation execution unit 164 specifies the ID received as an argument as the user assignment ID. (S502).
  • an operation to be executed via the IE browser 542 (the above-described operations 4, 5, and 8, hereinafter also referred to as “browser operation”) is specified instead of the window selection operation (N in S500) (Y in S504)
  • the external operation execution unit 164 identifies the OS assignment ID associated with the user assignment ID (S506). Then, by designating the OS allocation ID and calling a function of the COM 550 corresponding to the content of the browser operation, the IE browser 542 is caused to execute the operation (S508).
  • the external operation execution unit 164 Specifies the OS allocation ID associated with the user allocation ID (S512). Then, by designating the OS assignment ID and calling a function of the Win32 API 552 corresponding to the operation content, the OS operation on the browser window is executed by the Windows OS (S514). If it is not an OS operation (N in S510), S512 and S514 are skipped.
  • the dialog operation unit 176 of the external operation execution unit 164 detects the display of the OS dialog 544 (Y in S516)
  • the operation content for the dialog (the above operation 6) is acquired from the dialog operation holding table (S518).
  • an operation for the OS dialog 544 is executed by calling a function of the Win32 API 552 corresponding to the operation content (S520). If the display of the OS dialog 544 is not detected (N in S516), S518 and S520 are skipped.
  • FIG. 36 is a flowchart showing in detail the FF operation process in S462 of FIG.
  • a window selection operation (the above operations 3 and 7) is specified in the test program (Y in S530)
  • the ID allocation unit 180 of the internal operation execution unit 168 identifies the ID received as an argument as the user allocation ID. (S532).
  • a predetermined operation to be executed via the FF browser 546 (the above-described operations 4, 5, and 8, hereinafter also referred to as “browser operation”) is designated instead of the window selection operation (N in S530) (Y in S534)
  • the internal operation execution unit 168 identifies the selenium allocation ID associated with the user allocation ID (S536).
  • the selenium module 530 is called a function corresponding to the operation instruction among the control codes added to the web page (S538).
  • OS operation When not a browser operation (N in S534) but a predetermined operation to be executed via Windows OS (the above operations 9 and 10, hereinafter also referred to as "OS operation") is designated (Y in S540), an internal operation is executed.
  • the unit 168 identifies the OS assignment ID associated with the user assignment ID (S542). Then, by designating the OS allocation ID and calling a function of the Win32 API 552 corresponding to the operation content, the OS operation on the browser window is executed by the Windows OS (S544). If it is not an OS operation (N in S540), S542 and S544 are skipped.
  • the dialog displayed by the operation 5 is the FF dialog 548.
  • the dialog operation unit 182 of the internal operation execution unit 168 detects the display of the FF dialog 548 based on the notification from the window handler 572 (Y in S546)
  • the dialog operation holding table displays the operation content (the above operation 6) for the dialog. (S548).
  • the window handler 572 is caused to call a function of the FF browser 546 corresponding to the operation content (S550).
  • an operation according to the test program is executed for the FF dialog 548. If the display of the FF dialog 548 is not detected (N of S546), S548 and S550 are skipped.
  • the dialog displayed by the operation 5 is the OS dialog 544.
  • the dialog operation unit 182 of the internal operation execution unit 168 detects that the OS dialog 544 is displayed (Y in S552)
  • the operation content for the dialog (the above operation 6) is acquired from the dialog operation holding table (S554).
  • an operation on the OS dialog 544 is executed by calling a Win32 API 552 function corresponding to the operation content (S556). If the display of the OS dialog 544 is not detected (N in S552), S554 and S556 are skipped.
  • the selenium module 530 According to the operation verification apparatus 100 of the reference technique 4, as already described in the reference technique 3, by using the selenium module 530, web pages on various web browsers can be displayed regardless of whether or not the operation IF is disclosed. Operation check is possible. Further, the user can assign an arbitrary ID to the browser window in the test program and the operation content file or function setting screen that is the generation source of the test program. In other words, the user can appropriately set the browser window ID according to the convenience of the test, while the selenium module 530 does not need to be aware of the selenium allocation ID necessary for identifying the browser window, thereby improving the user convenience. It can be improved.
  • the operation verification apparatus 100 can support an operation on a browser window that should be performed without using the selenium module 530.
  • the user can arbitrarily set the ID of the browser window according to the convenience of the test, but the user does not need to be aware of the ID assigned to the browser window by the OS or the web browser. Can be improved.
  • a dialog detection function is added on as an extended function of the web browser (FF browser 546).
  • the function of the OS cannot acquire the contents of the dialog because the web browser uses its own resource to display the dialog
  • the contents of the dialog are acquired via the dialog detection function that is added, and the dialog Can be operated.
  • the operation for either dialog can be performed by appropriately switching the dialog operation method. Also make it possible.
  • the first dialog is operated through the add-on dialog detection function
  • the second dialog is operated through the OS native function, thereby supporting a series of operations on the web page. Can be reproduced.
  • the selenium module 530 is used in many operations on the browser window, and the OS API is directly called or a dialog operation module is used in exceptional operations.
  • the OS API is directly called or a dialog operation module is used in exceptional operations.
  • FIG. 37 shows a display example of web content in the browser window. This figure shows a situation in which a web page (typically a test target page) provided from a web server is displayed on a browser window 632 on a display screen 630.
  • the web browser activated in the browser window is the Safari browser 562.
  • the browser window 632 includes a client area 634 and a header area 636.
  • the header area 636 is an area in which information related to the Safari browser 562 is mainly displayed, and various menus and icons for operating the Safari browser 562 are displayed. Also, meta information of the web page such as URL and title is displayed instead of the content of the web page itself.
  • the client area 634 is an area where the content of the web page itself is displayed.
  • the client area 634 includes a plurality of frames each displaying a different web page.
  • a frame a638, a frame b640, and a frame c642 are included.
  • the header area 636 is arranged above the client area 634.
  • the vertical scroll bar 646 is arranged in the frame a638 because the entire vertical length including the non-display portion exceeds the vertical length of the visible range.
  • the frame a638 includes an element 644.
  • the “element” in the first embodiment is a GUI component that is arranged in a frame and can be set with a scroll bar, and includes, for example, a text box and a list box.
  • the vertical scroll bar 645 is disposed in the element 644 in the drawing because the entire vertical length including the non-display portion exceeds the vertical length of the visible range.
  • the horizontal width including the non-display portion exceeds the horizontal length of the visible range, so the horizontal scroll bar 650 is arranged.
  • the frame b640 includes a table 648.
  • the operation verification apparatus 100 stores a display image of the browser window 632 as one piece of image data for each frame. That is, in a screen capture of a web page composed of a plurality of frames, in other words, a web page that displays a plurality of web pages divided into frames (hereinafter also referred to as “top page” for convenience), for each frame. Save captured images. Further, when the contents of the entire frame cannot be displayed at a time in the browser window 632 and scrolling is necessary, a plurality of pieces of image data each including a part of the frame are acquired, and the image data obtained by connecting them is obtained as a final captured image. Save as.
  • FIG. 38 shows a captured image of the browser window of FIG.
  • FIG. 38A shows a captured image of the frame a638.
  • the entire frame a638 including the area not displayed in FIG. 37 is stored as one image.
  • FIG. 38B shows a captured image of the element 644 in the frame a638.
  • the entire element 644 including the area not displayed in FIG. 37 is stored as one image.
  • FIG. 38C shows a captured image of the frame b640.
  • the entire frame b640 including the non-displayed area is stored as one image.
  • a captured image of the frame c642 is also acquired. Since no scroll bar is arranged in the frame c642, a captured image indicating the display content in FIG. 37 is acquired.
  • a browser window that should capture a display image is called a “capture target window”
  • a frame included in the capture target window is referred to as a “capture target frame”
  • an element included in the capture target frame is referred to as a “capture target element”.
  • a web page displayed in each frame on the top page is referred to as a “frame page”.
  • the main functional configuration of the operation verification apparatus 100 in the first embodiment is the same as the functional configuration of the operation verification apparatus 100 in the reference technique 4 shown in FIGS.
  • the description of the configurations already described in the reference techniques 1 to 4 will be omitted as appropriate, and the configuration for screen capture processing of web content will be described in detail.
  • FIG. 39 is a block diagram showing a functional configuration related to screen capture processing in the first embodiment.
  • the operation verification apparatus 100 includes the evidence setting unit 170, the proxy processing unit 166, and the browser processing unit 160.
  • the witness setting unit 170 calls various functions described later provided by the proxy processing unit 166.
  • the proxy processing unit 166 appropriately communicates with the control code added to the program code of the web page, and causes the browser processing unit 160 to execute the JAVA script corresponding to the function called by the evidence setting unit 170.
  • the witness setting unit 170 operates the web page using various functions provided by the proxy processing unit 166, and acquires information necessary for image capture of the web page from the browser processing unit 160 and the proxy processing unit 166. To do.
  • FIG. 40 shows functions provided by the proxy processing unit 166 to the witness setting unit 170.
  • these functions are functions that the selenium module 530 in FIG. 24 exposes to the outside.
  • the functions other than “getOffsetPositionOfWindow” in the figure may be functions provided by the proxy processing unit 166, that is, the selenium module 530 as standard.
  • the proxy processing unit 166 of the first embodiment acquires the top page to be displayed on the Safari browser 562 as a proxy, and adds a control code to the top page.
  • a frame page to be displayed in the frame of the top page is obtained by proxy, and a control code is added to each frame page.
  • a unique ID is assigned to the browser window displaying the web page, and an ID is also assigned to each frame displayed on the web page. Then, the ID assigned to the window and the ID assigned to the frame are managed in association with each other.
  • the proxy processing unit 166 includes an image position specifying unit 600.
  • the witness setting unit 170 includes an object specifying unit 612, a frame processing unit 614, an element processing unit 619, an image acquisition unit 625, and an image composition unit 627.
  • Each function block in the figure can also be collectively referred to as a screen capture processing unit 629 as a function block for executing a screen capture process of web content.
  • Each functional block of the screen capture processing unit 629 may be arranged in the proxy processing unit 166 according to the function of the function provided by the proxy processing unit 166 to the witness object setting unit 170. It may be arranged.
  • Proxy processing unit 166 The image position specifying unit 600 realizes the function of the function “getOffsetPositionOfWindow” in FIG. That is, the display position on the screen 630 is derived for the frame (capture target frame) specified by the argument of the function, and information indicating the display position is notified to the evidence object setting unit 170.
  • the image position specifying unit 600 includes a window display position acquiring unit 602, a header area specifying unit 604, a client area specifying unit 606, a frame relative position acquiring unit 608, and a frame display position specifying unit 610.
  • the window display position acquisition unit 602 acquires the display position on the screen 630 of the browser window 632 in which the capture target frame is displayed.
  • the coordinates in the Cartesian coordinate system with the upper left corner of the screen 630 as the origin and the coordinates of the upper left corner of the browser window (point 659 in FIG. 37) are acquired.
  • the window display position acquisition unit 602 communicates with the control code of the top page including the capture target frame, and causes “window.screenX” to be executed on the top page. Then, as a return value, the abscissa value of the point 659 (abscissa 652 in FIG. 37) is acquired. Similarly, “window.screenY” is executed on the top page, and the ordinate value of the point 659 (ordinate 654 in FIG. 37) is acquired as a return value.
  • the header area specifying unit 604 specifies the size of the header area 636 in the browser window 632. In the first embodiment, since the header area 636 is disposed above the client area 634, the header area specifying unit 604 specifies the vertical length of the header area 636.
  • the header area specifying unit 604 communicates with the control code of the top page including the capture target frame, and causes “window.outerHeight” to be executed on the top page. Then, the vertical length of the browser window 632 (vertical width 656 in FIG. 37) is acquired as a return value. Similarly, “window.innerHeight” is executed on the top page, and the vertical length of the client area 634 (vertical width 658 in FIG. 37) is acquired as a return value.
  • the header area specifying unit 604 derives the vertical length of the header area 636 by subtracting the vertical length of the client area 634 from the vertical length of the browser window 632.
  • the client area specifying unit 606 specifies the display position of the client area 634 on the screen 630 according to the display position of the browser window 632 on the screen 630 and the size of the header area 636. Specifically, the vertical length of the header area 636 is added to the ordinate value of the coordinates of the upper left corner (point 659) of the browser window 632, while the abscissa value of the coordinates of the point 659 is used as it is. The coordinates of the upper left corner (point 660) of the area 634 are derived.
  • the frame relative position acquisition unit 608 acquires the position of the capture target frame in the client area 634.
  • the coordinates are in an orthogonal coordinate system with the upper left corner of the client area 634 (point 660 in FIG. 37) as the origin, and the coordinates of the upper left corner of the capture target frame (hereinafter also referred to as “coordinate within the client area”). .)
  • the capture target frame is the frame b640
  • the coordinates in the client area of the point 662 in FIG. 37 are acquired.
  • the frame relative position acquisition unit 608 communicates with the control code of the top page including the capture target frame, and causes “frame name.frameElement.offsetLeft” to be executed on the top page. Then, as a return value, the abscissa value of the coordinates in the client area of the capture target frame is acquired. Similarly, “frame name.frameElement.offsetTop” is executed on the top page, and the ordinate value of the coordinates in the client area of the capture target frame is acquired as a return value.
  • the frame display position specifying unit 610 determines the capture target frame on the screen 630 according to the display position of the client area 634 on the screen 630 derived by the client area specifying unit 606 and the position of the capture target frame on the client area 634. Specify the display position. Specifically, by adding the ordinate value and the abscissa value of the coordinates in the client region of the capture target frame to the ordinate value and the abscissa value of the upper left coordinate of the client region 634, the upper left end of the capture target frame The coordinates (coordinates on the screen 630) are derived.
  • the target specifying unit 612 determines target content to be image-captured from the web content displayed on the screen 630. Specifically, the capture target window, the capture target frame, and the capture target element are sequentially specified.
  • a user sets a screen capture function (for example, “WebScreen Capture” in FIG. 7) on the function setting screen 210, and sets a user allocation ID of a browser window to be captured as an argument thereof.
  • the target specifying unit 612 identifies the browser window corresponding to the user assignment ID specified by the argument of the screen capture function as the capture target window.
  • the target specifying unit 612 calls the function “getAllFrame” by specifying the selenium allocation ID corresponding to the user allocation ID specified by the argument of the screen capture function. Then, the proxy processing unit 166 obtains frame list information (hereinafter also referred to as “frame list”) included in the capture target window. This frame list includes the ID of each frame (hereinafter also referred to as “frame ID”) assigned by the selenium module 530 to each frame included in the capture target window. The target specifying unit 612 identifies each frame included in the frame list as a capture target frame.
  • the target identifying unit 612 calls the function “getScrollableElement” by designating each ID of the capture target frame. Then, scrollable element list information (hereinafter also referred to as “element list”) included in the capture target frame is acquired from the proxy processing unit 166. This element list includes the ID of each scrollable element included in the capture target frame (hereinafter also referred to as “element ID”). The target specifying unit 612 specifies each element included in the element list as a capture target element.
  • the frame processing unit 614 executes a preparation process for capturing a capture target frame.
  • the frame processing unit 614 includes a frame display position acquisition unit 615, a frame range acquisition unit 616, and a frame scroll processing unit 617.
  • the frame display position acquisition unit 615 calls the function “getOffsetPositionOfWindow” by specifying the frame ID of the capture target frame.
  • the image position specifying unit 600 of the proxy processing unit 166 specifies the coordinates indicating the display position of the capture target frame on the screen 630, and the coordinate value is acquired from the proxy processing unit 166.
  • the frame range acquisition unit 616 specifies the frame ID of the capture target frame and calls the function “getScrollRectangleOfElement”. Then, the invisible portion of the capture target frame, in other words, the entire size including the portion displayed on the screen 630 for the first time by scrolling, here the horizontal length (horizontal width) and the vertical length of the entire capture target frame. (Vertical width) is acquired from the proxy processing unit 166.
  • the proxy processing unit 166 may execute different JAVA scripts on the top page depending on the type of the browser processing unit 160. That is, in the case of the Safari browser 562 as in the first embodiment, the execution result of “frame name. Document. Width” may be specified as the horizontal width of the entire capture target frame. Similarly, the execution result of “frame name. Document. Height” may be specified as the vertical width of the entire capture target frame.
  • the execution result of “frame name.window.innerWidth” + the execution result of “frame name.window.scrollMaxX” is specified as the horizontal width of the entire capture target frame. Also good.
  • the execution result of “frame name.window.innerHeight” + the execution result of “frame name.window.scrollMaxY” may be specified as the vertical width of the entire capture target frame.
  • the frame range acquisition unit 616 specifies the frame ID of the capture target frame and calls the function “getClientRectangle”.
  • the visible portion of the capture target frame in other words, the size of the portion displayed on the screen 630 without scrolling, that is, the horizontal width and the vertical width of the visible portion in the capture target frame are acquired from the proxy processing unit 166.
  • the proxy processing unit 166 executes a JAVA script corresponding to the function on the top page.
  • the execution result of “frame name. Document. DocumentElement. ClientWidth” may be specified as the horizontal width of the visible portion in the capture target frame.
  • the execution result of “frame name. Document. DocumentElement. ClientHeight” may be specified as the vertical width of the visible portion in the capture target frame.
  • the frame scroll processing unit 617 divides the horizontal width of the entire capture target frame by the horizontal width of the visible portion (the remainder is rounded up), and determines the result as the maximum number of horizontal scrolls. Further, the vertical width of the entire capture target frame is divided by the vertical width of the visible portion (the remainder is rounded up), and the result is determined as the upper limit number of vertical scrolls.
  • the frame scroll processing unit 617 vertically scrolls the frame or vertically scrolls and horizontally scrolls before acquiring the next image.
  • the frame ID of the capture target frame the horizontal scroll amount is 0
  • the vertical width of the visible portion of the capture target frame is specified as the vertical scroll amount
  • the function “doScrollFrameTo” is set. call.
  • the function “doScrollFrameTo” is called by specifying the frame ID of the capture target frame, the horizontal width of the visible portion of the capture target frame as the horizontal scroll amount, and 0 as the vertical scroll amount.
  • scrolling is executed in a so-called inverted N type. That is, for each image acquisition process, the frame scroll processing unit 617 first repeats the vertical scroll once for the upper limit number of times while fixing the horizontal position. Next, the vertical position is returned to the initial position and horizontal scrolling is executed once. Then, the vertical scrolling is repeated once each up to the upper limit number while the horizontal position is fixed again. When both the vertical scroll count and horizontal scroll count reach the upper limit count, the scroll process for the capture target frame is terminated.
  • the element processing unit 619 executes a preparation process for capturing the capture target element.
  • the element processing unit 619 includes an element relative position acquisition unit 620, an element display position specification unit 621, an element range acquisition unit 622, and an element scroll processing unit 623.
  • the element relative position acquisition unit 620 calls the function “getOffsetPositionOfElement” by specifying the element ID of the capture target element. Then, the coordinates in the Cartesian coordinate system having the origin at the upper left corner of the frame including the capture target element and the coordinates of the upper left corner of the capture target element (hereinafter also referred to as “in-frame coordinates”) are acquired. For example, for the element 644 included in the frame a638, the upper left corner coordinate of the element 644 with the point 662 as the origin is acquired.
  • the proxy processing unit 166 When the proxy processing unit 166 receives a call to the function “getOffsetPositionOfElement”, the proxy processing unit 166 causes the JAVA script corresponding to the function to be executed on the frame page. For example, “element name.getBoundingClientRect.left” may be executed, and the abscissa value of the in-frame coordinates of the capture target element may be acquired as the return value. Similarly, “element name.getBoundingClientRect.top” may be executed, and the ordinate value of the in-frame coordinates of the capture target element may be acquired as the return value.
  • the element display position specifying unit 621 acquires coordinates of the display position of the capture target frame on the screen 630 acquired by the frame display position acquisition unit 615, and the frame of the capture target element acquired by the element relative position acquisition unit 620.
  • the display position of the capture target element on the screen 630 is specified according to the internal coordinates. Specifically, by adding the ordinate and abscissa values of the in-frame coordinates of the capture target element to the ordinate and abscissa values of the upper-left corner coordinates of the capture target frame, the upper-left corner of the capture target element Coordinates (coordinates on the screen 630) are derived.
  • the element range acquisition unit 622 specifies the element ID of the capture target element and calls the function “getScrollRectangleOfElement”. Then, the entire size including the invisible part of the capture target frame, here, the horizontal width and the vertical width of the entire capture target frame are acquired from the proxy processing unit 166.
  • the proxy processing unit 166 when the proxy processing unit 166 receives a call to the function “getScrollRectangleOfElement”, the proxy processing unit 166 causes the JAVA script corresponding to the function to be executed on the frame page. For example, “element name. ScrollWidth” may be executed, and the horizontal width of the entire capture target element may be acquired as the return value. Similarly, “element name. ScrollHeight” may be executed, and the vertical width of the in-frame coordinates of the capture target element may be acquired as the return value.
  • the element range acquisition unit 622 calls the function “getClientRectangleOfElement” by specifying the element ID of the capture target element. Then, the size of the visible portion of the capture target element, here, the horizontal width and vertical width of the visible portion in the capture target frame is acquired from the proxy processing unit 166.
  • the proxy processing unit 166 executes a JAVA script corresponding to the function on the frame page.
  • the execution result of “element name. ClientWidth” may be acquired as the width of the visible portion of the capture target element.
  • the execution result of “element name. ClientHeight” may be acquired as the vertical width of the visible portion of the capture target element.
  • the element scroll processing unit 623 divides the horizontal width of the entire capture target element by the horizontal width of the visible portion (rounds up the remainder), and determines the result as the maximum number of horizontal scrolls. Further, the vertical width of the entire capture target element is divided by the vertical width of the visible portion (the remainder is rounded up), and the result is determined as the upper limit number of vertical scrolls.
  • the element scroll processing unit 623 vertically scrolls the element or vertically scrolls and horizontally scrolls before acquiring the next image.
  • the element ID of the capture target element the horizontal scroll amount is 0
  • the vertical width of the visible portion of the capture target element is specified as the vertical scroll amount
  • the function “doScrollElementTo” is executed. call.
  • the function “doScrollElementTo” is called by specifying 0 as the element ID of the capture target element, the horizontal width of the visible portion of the capture target element, and the vertical scroll amount as the horizontal scroll amount.
  • the scroll mode of the element is the same as the scroll mode of the frame described above.
  • the image acquisition unit 625 captures the display image of the capture target frame according to the display position of the capture target frame on the screen 630. Further, the display image of the capture target element is captured according to the display position of the capture target element on the screen 630.
  • the image acquisition unit 625 of the first embodiment excludes the header area 636 of the browser window 632 from the capture target. In other words, the display image of the capture target frame is obtained purely from which the display image of the header area 636 is excluded.
  • the image acquisition unit 625 specifies the coordinate value of the upper left corner of the capture target frame on the screen 630 as the start point, specifies the horizontal width and vertical width of the visible portion of the capture target element as the capture range, and performs screen capture of the OS.
  • a function API may be called. Then, the image data of the visible portion of the capture target element may be stored in the memory (clipboard).
  • the image acquisition unit 625 repeats the capture processing of the capture target frame until the number of vertical and horizontal scrolls determined by the frame scroll processing unit 617 reaches the upper limit. Similarly, the capture processing of the capture target element is repeated until the number of vertical and horizontal scrolls determined by the element scroll processing unit 623 reaches the upper limit. Therefore, for a frame or element in which a scroll bar is set, data of a plurality of captured images is taken into the memory.
  • the image composition unit 627 synthesizes the data of a plurality of captured images acquired by a plurality of image acquisition processes for one capture target frame into one image data.
  • one piece of image data is stored in the result holding unit 152 as a proof of the operation test.
  • the element For one capture target frame, one piece of image data is stored in the result holding unit 152 as a proof of the operation test. If there is an overlapping portion between a plurality of captured images, the overlapping portion is trimmed from one captured image and then combined into a single image.
  • FIG. 41 is a flowchart showing the operation of image capture processing in the operation verification apparatus 100.
  • the target specifying unit 612 acquires a list of frames included in the capture target window specified by the request from the proxy processing unit 166. (S602).
  • the target specifying unit 612 specifies one of the frames included in the frame list as a capture target frame (S604).
  • the frame display position acquisition unit 615 designates a capture target frame and causes the proxy processing unit 166 to execute a frame display position specifying process described later (S606).
  • the frame range acquisition unit 616 acquires the size of the entire capture target frame and the size of the visible portion (S608).
  • the frame scroll processing unit 617 determines the maximum number of horizontal and vertical scrolls to be performed on the capture target frame according to the size of the entire capture target frame and the size of the visible portion (S610).
  • the image acquisition unit 625 temporarily stores the image of the visible portion of the capture target frame in the memory (S612). If the upper limit number of scrolls has not been reached (N in S614), the frame scroll processing unit 617 changes the display content (that is, the visible portion) of the capture target frame by scrolling the capture target frame by one unit. , The process returns to S612 (S616).
  • the image composition unit 627 acquires a plurality of capture images temporarily stored for the capture target frame, and sets one image data obtained by composing them. Then, the combined image data is stored in the result holding unit 152 as a proof of the operation test (S618). If there is one captured image, the image is stored in the result holding unit 152 as a proof as it is.
  • the target specifying unit 612 acquires a list of elements included in the capture target frame from the proxy processing unit 166.
  • the element relative position acquisition unit 620 acquires the position of the capture target element in the capture target frame (S622).
  • the element display position specifying unit 621 derives the display position of the capture target element on the screen according to the display position of the capture target frame on the screen and the position of the capture target element in the capture target frame (S624). ). Then, the process returns to S608.
  • the element range acquisition unit 622 acquires the size of the entire capture target element and the size of the visible portion (S608).
  • the element scroll processing unit 623 determines the maximum number of vertical and horizontal scrolls to be performed on the capture target element according to the size of the entire capture target element and the size of the visible portion (S610).
  • the image acquisition unit 625 temporarily stores the image of the visible portion of the capture target element in the memory (S612). If the upper limit number of scrolls has not been reached (N in S614), the element scroll processing unit 623 scrolls the capture target element by one unit and returns to S612 (S616).
  • the image composition unit 627 acquires a plurality of captured images temporarily stored for the capture target element, and sets one image data obtained by composing them. S618).
  • FIG. 42 is a flowchart showing in detail the frame display position specifying process in S606 of FIG.
  • the window display position acquisition unit 602 acquires the display position on the screen of the capture target window including the capture target frame (S630).
  • the header area specifying unit 604 derives the size of the header area 636 by calculating the difference between the size of the entire capture target window and the size of the client area 634 (S632).
  • the client area specifying unit 606 derives the display position of the client area 634 on the screen according to the display position of the capture target window on the screen and the size of the header area 636 (S634).
  • the frame relative position acquisition unit 608 acquires the position of the capture target frame in the client area 634 (S636).
  • the frame display position specifying unit 610 derives the display position of the capture target frame on the screen according to the display position of the client area 634 on the screen and the position of the capture target frame on the client area 634 (S638).
  • the operation verification apparatus 100 of the first embodiment only the display image of the web page necessary for confirming the success or failure of the operation test is stored as a proof. Specifically, it is the content of the web page displayed in the frame itself, and presents the captured image to the user, excluding the extra part such as the header area, in other words, the part that would rather get in the way of confirming the result of the operation test. it can. Thereby, an efficient operation test can be supported.
  • the second embodiment of the present invention differs from the first embodiment in that the web browser activated in the browser window 632 is the FF browser 546.
  • FIG. 43 shows a display example of web content in the browser window.
  • the browser window 632 of the second embodiment includes a fixed-length (for example, 26 pixels) status bar at the bottom of the client area 634.
  • the browser window 632 of the second embodiment includes a frame line 666 in which a certain amount of width (for example, a fixed length of 4 pixels) is set as a boundary with an object outside the browser window (another window, background, etc.). .
  • the main functional configuration of the operation verification apparatus 100 in the second embodiment is the same as that of the first embodiment, and the main operation is also the same as that of the first embodiment.
  • the operation verification device 100 according to the second embodiment will be described while referring to differences from the first embodiment.
  • the header area specifying unit 604 of the image position specifying unit 600 specifies the size of the header area 636 in consideration of the size (width) of the status bar 664. Specifically, by subtracting the vertical width of the client area 634 from the vertical width of the browser window 632 and subtracting the vertical length of the status bar 664, which is a predetermined 26 pixels in this case, the header area 636 is subtracted. The vertical length of is derived. Strictly speaking, the fixed value of 26 pixels can be said to be the total value of the vertical length of the status bar 664 and the width of the frame line 666.
  • the client area specifying unit 606 of the image position specifying unit 600 specifies the display position of the client area 634 on the screen 630 in consideration of the size (width) of the frame line 666. Specifically, the vertical length of the header area 636 is added to the ordinate value of the upper left coordinate of the browser window 632, while the width of the frame line 666, which is predetermined here, is added to the abscissa value of the coordinate.
  • the coordinates of the upper left corner of the client area 634 are derived by adding the four pixels.
  • the operation test using the web browser in which the status bar 664 and the frame line 666 having a certain width are arranged in the browser window 632 is the same as in the first embodiment.
  • the effect of can be realized.
  • a captured image that excludes a portion that hinders confirmation of the result of the operation test, such as a status bar and a frame line can be presented to the user.
  • the header area 636 is arranged above the client area 634, but the mode of the browser window 632 is not limited to this.
  • the header area 636 may be disposed on the left side of the client area 634.
  • the header area specifying unit 604 specifies the horizontal length of the header area 636 by acquiring the horizontal length of the browser window 632 and the horizontal length of the client area 634 and calculating the difference between them. May be.
  • the client area specifying unit 606 adds the horizontal length of the header area 636 to the abscissa value of the upper left corner of the browser window 632, while using the ordinate value as it is, the upper left corner of the client area 634. Coordinates may be derived.
  • the first embodiment and the second embodiment may be combined and realized in the same operation verification apparatus 100.
  • the proxy processing unit 166 captures the display image of the browser window in which the FF browser 546 is activated and the first image position specifying unit that is called when capturing the display image of the browser window in which the Safari browser 562 is activated. May include a second image position specifying unit to be called. Then, the proxy processing unit 166 may operate one of them depending on the type of browser window to be captured.
  • the header area specifying unit 604 and the client area specifying unit 606 of the image position specifying unit 600 perform the operation described in the first embodiment or the second embodiment according to the type of browser window to be captured. Any of the operations described may be performed.
  • the browser window type may be specified by the user in an argument at the start of the operation test or in various setting files, or may be dynamically read from the OS or the browser processing unit 160.
  • the client area 634 is divided into a plurality of frames.
  • the client area 634 is not necessarily divided into a plurality of frames.
  • the frame processing unit 614 may operate in the same manner as in the embodiment, regarding the entire client area as one frame.
  • the element processing unit 619 may operate in the same manner as in the embodiment, regarding elements included in the entire client area as elements included in one frame.
  • the Safari browser 562 and the FF browser 546 are illustrated as web browsers.
  • the scope of application of the technical idea of the present invention is not limited to these types of web browsers.
  • the technology of the first embodiment can be applied to a web browser in which the status bar 664 is not arranged in the browser window 632 and the width of the frame line 666 is less than a predetermined value.
  • the technology of the second embodiment can be applied to a web browser in which the status bar 664 is arranged and the width of the frame line 666 is a predetermined value or more.
  • the width of the frame line 666 is less than a predetermined value when the status bar 664 is disposed, or conversely, when the width of the frame line 666 is not greater than the predetermined value when the status bar 664 is not disposed, Those skilled in the art will understand that the configurations of the first embodiment and the second embodiment may be appropriately selected and combined.
  • the operation verification apparatus 100 further includes a verification image holding unit that holds a verification image for verifying whether the captured images acquired in the operation test match. Also good.
  • This collation image is image data set in units of frames and elements, as in the capture image of the embodiment.
  • the operation verification apparatus 100 may further include a verification unit that determines whether the captured image as the evidence and the verification image match.
  • the captured image as the evidence is a captured image in the operation test, in other words, an image synthesized by the image synthesizing unit 627, and in other words, a captured image stored in the result holding unit 152.
  • the collation unit may store the determination result as to whether the captured image and the collation image match in a predetermined storage area (file, DB, etc.) and notify the user. According to this modification, it is possible to support the efficient operation test by automating the determination of the normality of the operation. Further, in the above embodiment, pure web content contents with the header area excluded are captured, so that the exclusion setting of the verification area (so-called mask processing) becomes unnecessary, and the captured image matches the verification image. It can be easily determined whether or not to do so.
  • 100 operation verification device 160 browser processing unit, 166 proxy processing unit, 170 evidence object setting unit, 600 image position specifying unit, 602 window display position acquisition unit, 604 header area specifying unit, 606 client area specifying unit, 608 frame relative position Acquisition unit, 610 frame display position specifying unit, 612 target specifying unit, 625 image acquiring unit, 627 image compositing unit, 630 screen, 632 browser window, 634 client area, 636 header area, 664 status bar, 666 frame line.
  • This invention can be used for an apparatus for testing the operation of a product.

Abstract

L'invention porte sur un dispositif de vérification d'opération (100) qui comprend : une unité d'acquisition de position d'affichage de fenêtre (602) qui acquiert la position d'affichage à l'écran d'une fenêtre de navigateur contenant une région de client dans laquelle une page web est affichée et une région supplémentaire différente de la région de client ; une unité de détermination de région de client (606) qui détermine la position d'affichage à l'écran de la région de client conformément à la position d'affichage à l'écran de la fenêtre de navigateur, à la taille de la région supplémentaire dans la fenêtre de navigateur et à la taille de la barre d'état dans la fenêtre de navigateur ; et une unité d'acquisition d'image (625) qui capture une image d'affichage dans la région de client conformément à la position d'affichage à l'écran déterminée.
PCT/JP2010/005827 2010-09-28 2010-09-28 Dispositif d'acquisition d'image, procédé d'acquisition d'image et programme d'ordinateur WO2012042560A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2012506253A JP5303680B2 (ja) 2010-09-28 2010-09-28 画像取得装置、画像取得方法およびコンピュータプログラム
PCT/JP2010/005827 WO2012042560A1 (fr) 2010-09-28 2010-09-28 Dispositif d'acquisition d'image, procédé d'acquisition d'image et programme d'ordinateur
CN201080043089.XA CN102549556B (zh) 2010-09-28 2010-09-28 图像取得装置、图像取得方法及计算机程序

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2010/005827 WO2012042560A1 (fr) 2010-09-28 2010-09-28 Dispositif d'acquisition d'image, procédé d'acquisition d'image et programme d'ordinateur

Publications (1)

Publication Number Publication Date
WO2012042560A1 true WO2012042560A1 (fr) 2012-04-05

Family

ID=45892071

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/005827 WO2012042560A1 (fr) 2010-09-28 2010-09-28 Dispositif d'acquisition d'image, procédé d'acquisition d'image et programme d'ordinateur

Country Status (3)

Country Link
JP (1) JP5303680B2 (fr)
CN (1) CN102549556B (fr)
WO (1) WO2012042560A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015138479A (ja) * 2014-01-24 2015-07-30 レノボ・シンガポール・プライベート・リミテッド Ｗｅｂサイトを共有する方法、電子機器およびコンピュータ・プログラム
JP2016066227A (ja) * 2014-09-24 2016-04-28 富士通株式会社 非互換検出装置、非互換検出方法、及びプログラム

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110909739B (zh) * 2019-11-19 2021-01-08 广东润联信息技术有限公司 图片识别并操作的方法、装置、计算机设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005266954A (ja) * 2004-03-16 2005-09-29 Hitachi Software Eng Co Ltd 操作情報記録・再生装置
JP2010039901A (ja) * 2008-08-07 2010-02-18 Nomura Research Institute Ltd 動作検証装置および動作検証プログラム

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6456305B1 (en) * 1999-03-18 2002-09-24 Microsoft Corporation Method and system for automatically fitting a graphical display of objects to the dimensions of a display window
CN100517332C (zh) * 2007-01-11 2009-07-22 深圳市光芒科技有限公司 网页内容块智能截取方法
CN100592292C (zh) * 2007-04-09 2010-02-24 腾讯科技（深圳）有限公司 一种网页截屏系统及其实现方法
JP5324375B2 (ja) * 2009-09-29 2013-10-23 株式会社日立ソリューションズ キャプチャシステム
CN101727495B (zh) * 2009-12-31 2012-03-28 优视科技有限公司 一种用于移动通讯设备终端的网页页面缩放管理系统及其应用方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005266954A (ja) * 2004-03-16 2005-09-29 Hitachi Software Eng Co Ltd 操作情報記録・再生装置
JP2010039901A (ja) * 2008-08-07 2010-02-18 Nomura Research Institute Ltd 動作検証装置および動作検証プログラム

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Window Capture", 27 August 2007 (2007-08-27), Retrieved from the Internet <URL:http://yokohama.cool.ne.jp/chokuto/advanced/capturewindow.html> [retrieved on 20101209] *
MICROSOFT CORP.: "CWnd::RedrawWindow", November 2007 (2007-11-01), Retrieved from the Internet <URL:http://msdn.microsoft.com/ja-jp/library/Ofdz8ey6(VS.90).aspx> [retrieved on 20101209] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015138479A (ja) * 2014-01-24 2015-07-30 レノボ・シンガポール・プライベート・リミテッド Ｗｅｂサイトを共有する方法、電子機器およびコンピュータ・プログラム
JP2016066227A (ja) * 2014-09-24 2016-04-28 富士通株式会社 非互換検出装置、非互換検出方法、及びプログラム

Also Published As

Publication number Publication date
JPWO2012042560A1 (ja) 2014-02-03
JP5303680B2 (ja) 2013-10-02
CN102549556B (zh) 2016-09-28
CN102549556A (zh) 2012-07-04

Similar Documents

Publication Publication Date Title
US6301592B1 (en) Method of and an apparatus for displaying version information and configuration information and a computer-readable recording medium on which a version and configuration information display program is recorded
US7421683B2 (en) Method for the use of information in an auxiliary data system in relation to automated testing of graphical user interface based applications
WO2010116586A1 (fr) Dispositif de vérification d&#39;opération, procédé de vérification d&#39;opération et système de vérification d&#39;opération
US20090031227A1 (en) Intelligent screen capture and interactive display tool
US20130097484A1 (en) Method and system of operation retrieval for web application
US20170147480A1 (en) Test script generation
EP3309695A1 (fr) Appareil de traitement d&#39;informations, procédé d&#39;affichage de document, système d&#39;affichage de document et programme
JP7248067B2 (ja) 情報処理装置及びプログラム
JP2015219890A (ja) 管理装置、その制御方法およびプログラム
JP2010061334A (ja) ファイル管理システム、ファイル管理方法、およびプログラム
JP5303680B2 (ja) 画像取得装置、画像取得方法およびコンピュータプログラム
WO2012042561A1 (fr) Dispositif d&#39;acquisition d&#39;image, procédé d&#39;acquisition d&#39;image et programme d&#39;ordinateur
CN114489625A (zh) 将json格式文本转换为可视化配置工具的方法和装置
JP5379911B2 (ja) 動作検証装置、動作検証方法および動作検証プログラム
JP2010237841A (ja) 動作検証装置および動作検証プログラム
JP4681673B1 (ja) 動作検証装置、動作検証方法および動作検証プログラム
US10884711B2 (en) Code management system and code management method using a visual programming tool
JP4846029B2 (ja) 動作検証装置、動作検証方法および動作検証プログラム
JP4846030B2 (ja) 動作検証装置、動作検証方法および動作検証プログラム
CN105739717B (zh) 信息输入方法和装置
JP4795404B2 (ja) 動作検証装置および動作検証プログラム
JP2009025977A (ja) ミドルウェアにおける操作履歴機能
JP2009223568A (ja) シナリオ生成装置及びプログラム
JP5379910B2 (ja) 動作検証装置、動作検証方法および動作検証プログラム
JP4903279B2 (ja) 動作検証装置、動作検証方法、および動作検証プログラム

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080043089.X

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2012506253

Country of ref document: JP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10857778

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10857778

Country of ref document: EP

Kind code of ref document: A1