JP5324375B2 - Capture system - Google Patents

Description

  The present invention relates to a capture system that captures only items (confirmation items) necessary for visual confirmation at the time of test execution among screens provided by a web application to a web browser and stores them as image files.

2. Description of the Related Art Conventionally, there is a tool (hereinafter referred to as a test automation tool) that automatically executes a test in order to improve the test work efficiency, as disclosed in Patent Document 1 below, in the Web application development action.
However, although the test automation tool can perform operations automatically, it cannot automatically acquire evidence such as screen capture and HTML (Hyper Text Markup Language) source.

  In the following Patent Document 1, in addition to automation of operation, a method of saving display contents of each screen in an image file is disclosed.

JP 2005-266554 A

In the case of Patent Document 1, a capture of the entire screen provided by the Web application is acquired, but it is difficult to determine where to check on the screen from the contents described in the check list defining the confirmation items. It is.
In addition, when the entire screen is captured, a scroll bar is added to the confirmation item, and there is a problem that the entire content of the item cannot be confirmed when display control is performed.

  The object of the present invention is to capture only the display contents of items necessary for visual confirmation from the operation contents and confirmation contents defined in the checklist when acquiring a capture during automatic execution of the test, and the captured image and confirmation contents It is to provide a capture system that makes it possible to visually check the image on the linking screen.

  In order to solve the problems in the previous period, the present invention is a capture system that captures display contents of items that require visual confirmation on a screen among screens provided by a web application to a web browser. Analyzing means for analyzing a checklist defining items to be confirmed and confirmation contents, and capturing only specific items defined in the checklist according to the analysis result of the analyzing means among the screens provided by the Web application, Capture acquisition means for storing in an image file, capture acquisition result generation means for generating a confirmation screen file by associating the acquired image file and confirmation contents, and contents of the confirmation screen file generated by the capture acquisition result generation means A capture acquisition result display means for displaying is provided.

The screen item capture system of the present invention has the following effects.
Capturing only the desired confirmation items without searching the screen to be tested can increase the efficiency of confirmation work.

It is a system configuration figure showing an example of an embodiment of the present invention. It is a flowchart which shows the outline | summary of operation | movement of embodiment of FIG. It is a figure which shows the example of the screen which receives the request | requirement of operation reproduction. It is a figure which shows the example of the data structure of a check list. It is a figure which shows the example of the data structure of a screen item definition document. It is a figure which shows the example of the data structure of matching with a screen name and a screen item definition document storage path. It is a figure which shows the example of the display screen of an operation target application. It is a flowchart which shows the process of an operation control means. It is a flowchart which shows the process of a check list analysis means. It is a flowchart which shows the whole item capture acquisition process. It is a flowchart which shows the process of an item capture process part. It is a figure which shows the example of the display screen of capture object. It is a figure which shows the example of the capture image of the item which is not controlled by the scroll bar. It is a figure which shows the example of the capture image of the item controlled by the scroll bar. It is a figure which shows the example of the data structure of a log file. It is a flowchart which shows the process of a capture acquisition result production | generation means. It is a figure which shows the example of the display screen of a capture acquisition result.

Hereinafter, an embodiment of a capture system to which the present invention is applied will be described.
FIG. 1 is a system configuration diagram showing an example of an embodiment of the present invention.
First, an overview of processing for accessing a Web server by a Web browser and displaying a Web page will be described.
When the input device of the client machine 112 is operated by the end user, the Web browser 112 is activated, and the server machine 130 is accessed via the network 120 such as the Internet or an intranet.

On the other hand, the server machine 130 accessed by the Web browser 113 includes a Web server 131 and an application server 135.
The Web server 131 is provided with static contents such as an HTML file 132 written in the HTML language, an image file 133, and a layout control file 134 such as a CSS (Cascading Style Sheet) defined by extracting a layout portion from an HTML document. Has been.
By describing the HTML document so as to refer to an external image file, the image is displayed on the Web browser 113, and by describing so as to refer to the layout control file 134, the layout can also be controlled.
The application server 135 executes a web application 136 to perform a process of accessing the database 137 in response to a request transmitted from the web browser 113, and returns a processing result to the web browser 113.
For example, when a search condition is input by the Web browser 113, the Web application 136 searches the database 137 based on the input search condition and dynamically generates HTML for displaying the search result.

The capture system according to the present embodiment will be described on the premise of the processing of each machine and each application as described above.
The capture system 100 according to the present embodiment includes processing units such as an operation reproduction unit 101 and an evidence recording unit 102.
The operation reproduction unit 101 includes an operation reproduction accepting unit 103, an operation control unit 104, and a check list analysis unit 105.
The operation reproduction accepting unit 103 accepts a test execution request for the operation target screen from the end user.
The operation control unit 104 transmits a request for acquiring an automatic execution of an operation and a capture of each confirmation item toward the operation target screen to the capture acquisition unit 106.
The check list analysis 105 analyzes the contents of the check list created by the end user, and extracts operation contents and confirmation contents.
The evidence recording unit 102 includes a capture acquisition unit 106, a capture acquisition result generation unit 107, and a capture acquisition result display unit 108.
The capture acquisition means 106 captures only the target item portion based on the confirmation item extracted by the check list analysis 105 and stores it as an image file 110. In addition, a log file 109 is generated in order to leave a record of obtaining evidence at the time of capture.
The capture acquisition result generation unit 107 generates one result file 111 by associating the content of the image file 110 acquired from the content of the log file 109 with the confirmation content described in the check list.
The capture acquisition result display means 108 displays the contents of the result file 111 to the end user.

FIG. 2 is a flowchart showing an outline of processing of the capture system of the present embodiment.
First, on the client machine 112 side, the end user transmits a test execution request to the operation reproduction accepting means 103 (step 201).
The client machine 112 automatically operates the screen of the application to be operated based on the operation contents of the test case, and acquires a screen capture of necessary confirmation items and saves it in a file (step 202).
A capture acquisition result file is generated by associating the contents of the image file acquired in step 202 with the confirmation contents described in the check list created by the end user (step 203).
Finally, the contents of the capture acquisition result file are displayed to the end user (step 204).

FIG. 3 shows an operation reproduction acceptance screen 300 for the end user to send a test execution request.
On the operation reproduction acceptance screen 300, a test case list for displaying a list of test cases to be automatically executed is displayed. The test case list includes a “test case name” column 301 that displays the name of each test case, a “check list” column 302 that describes in which file the check list of the corresponding test case is written, and a test “Test execution” in which a “status” column 303 indicating the test execution status of the case, an “execution date / time” column 304 indicating the test execution date / time, and a button for transmitting a test execution request to the operation reproduction reception 103 are displayed. It consists of a column 305.
In the “situation” column 303, a character string “running” indicating that the test is being executed and “waiting” indicating that the test execution request is waiting are displayed.

FIG. 4 is a description screen of the check list 400.
The check list 400 includes a “test case name” row 401 that defines the name of the test case, and an “operation definition” column 402 that describes the contents of the operation.
In the “test case name” line 401, the names of test cases are described one by one in one column.
The “operation definition” column 402 includes a “screen name” column 403 that describes a name for uniquely identifying a screen, and an “item name” column 404 that describes a name for uniquely identifying an item in the screen. , An “operation type” column 405 describing a specific operation and confirmation for the item name, and an “operation content / confirmation content” column 406 describing an outline of the operation and an outline of confirmation.
The checklist 400 indicates that if a test case name and an operation definition intersect with each other and a “◯” is described and defined, the test case at the defined location executes the operation.
For example, when it is desired to execute the operation content “input login ID“ User001 ”” with the test case name “TC0001”, it is only necessary to describe “◯” at the intersection of each row and column. In addition, the execution order of operations and confirmations is executed in order from the top.

FIG. 5 is a diagram illustrating an example of a description screen of the screen item definition document 500.
The screen item definition document 500 includes a screen ID field 501 describing an ID for uniquely identifying a screen, a screen name field 502 describing a Japanese name of the screen, and a title displayed on the upper left of the screen such as a browser. A screen title column 503 to be described and a screen item list 504 describing the definition of items in the screen are included.
The screen item list 504 includes an “item number” column 505 that describes an item number, an “item name” column 506 that describes a name for uniquely identifying the item, and a “type” that describes the control type of the item. ”Column 507,“ size ”column 508 defining the maximum number of input bytes of items whose values are input to the field by the end user, and“ initial value ”describing a value to be displayed immediately after the end user makes a screen transition ”Column 509, when an event occurs when an operation is performed on an item and a screen transition occurs, a“ transition destination screen ID ”column 510 describing a screen ID of the transition destination, and a value uniquely identifying the item An “attribute name” column 511 describing a set attribute and an “attribute value” column 512 describing a value set in the attribute name are included.
For example, when <Input Type = “button” ID = “AttrButton 1”> is described in HTML, and the ID value is uniquely defined in the screen, “ID” is used for the attribute name, and “ID” is used for the attribute value. It is described as “AttrButton 1”.

FIG. 6 is a diagram showing an example of a correspondence table 600 that shows the association between screen names and screen item definition documents.
In the correspondence table 600, an “item number” column 601 indicating a correspondence number, a “screen name” column 602 describing a screen name, and a storage location of a file in which item definitions for the screen name are described are described. The “screen item definition document storage path” column 603 includes:
The contents described in the correspondence table 600 are used to acquire item information described in the screen item definition document 500 from the screen names described in the check list 400.

FIG. 7 is a diagram showing an example of the display screen of the Web application to be operated. Here, a login screen 700 when the contents described in the screen item definition document 500 are displayed on the Web browser 113 is shown.
The login screen 700 has a user ID input field 701, a password input field 702, and a login button 703, and “Login” is displayed as the title 704 of the Web page.

FIG. 8 is a flowchart showing the processing of the operation control unit 104.
First, the file path input in the check list field of the operation reproduction acceptance screen 300 is accessed, and the check list is analyzed (step 801).
The screen is activated before the item operation or confirmation is executed (step 802).
Next, it is determined whether an operation is performed on the item (step 803). When performing an operation on an item, the operation of the item is executed (step 804). If no operation is performed on the item, a capture of the item is acquired (step 805).
Next, it is determined whether all operations and item captures to be executed in the test case have been executed (step 806). If capture of all operations and items has not been acquired, it is determined whether a screen transition has occurred by performing the previous operation or capture processing (step 807).
If a screen transition occurs, the process starts again from step 802.
If no screen transition occurs, the process starts again from step 803.
When captures of all operations and items are acquired, a capture acquisition result file is generated (step 808).

FIG. 9 is a flowchart showing the processing of the check list analysis means.
First, the checklist file path entered in the checklist field of the operation reproduction acceptance screen 300 is accessed to open the checklist (step 901).
Next, screen transition information when the test case is executed is extracted (step 902).
Next, the extracted operation information and confirmation information of each screen are extracted (step 903).
The operation information and confirmation information extracted in step 903 include the screen name, item name, operation type, operation content / confirmation content described in the check list 400, and the screen title, type, and attribute described in the screen item definition document 500. Name and attribute value information is included. The screen transition information and operation information (operation type and operation content) extracted during the checklist analysis are used when the operation control unit 104 measures the timing for transmitting an item capture request to the screen capture acquisition unit 106. The confirmation information (operation type, confirmation content, type, attribute name, attribute value) is used when a capture request is transmitted to the screen capture acquisition means 106.

FIG. 10 is a flowchart showing the overall processing of item capture acquisition.
First, a screen on which an item to be captured is displayed is searched from various screens displayed (step 1001).
When searching the screen, the search is performed using the title displayed at the upper left of the screen as a key. Then, an HTML document is acquired from the screen to be captured (step 1002).
In the case of a Web page having a frame configuration, an HTML document in an area where an item to be captured is displayed is acquired. Specifically, the content of the <Frame> tag in the <Frameset> tag in the HTML document is acquired using an API (Application Program Interface) of DOM (Document Object Model).
In this process and the subsequent processes, when using the information of each element, the DOM API is also used.

Next, the vertical width and horizontal width of the display area of the Web page are acquired (step 1003). In this process, the height of the Web page is acquired from the information of “ClientHeight” included in the “Body” element, and the width of the Web page is acquired from the information of “ClientWidth”.
Next, an item to be captured is searched in the Web page (step 1004). When searching for an item, the search is performed based on the type, attribute name, and attribute value settings described in the screen item definition document. For example, if the item to be captured is defined with the type “EditBox”, the attribute name “ID”, and the attribute value “attrUser”, the attribute of the <Input Type = “Text”> tag is “ID” in this system. = Search for an element set as “attrUser”.

Thereafter, the display position of the element searched in step 1004 is acquired (step 1005). In this process, the display position is acquired from the information of “OffsetLeft” and “OffsetTop” from the element to be captured to the “Body” element.
Next, the display area of the item to be captured is acquired (step 1006). The height of the item is acquired from the information of “ClientHeight” included in the element searched in step 1004, and the width of the item is acquired from the information of “ClientWidth”. The vertical width and horizontal width of the entire item to be captured are acquired (step 1007). In this process, the height of the item is acquired from the information of “ScrollHeight” included in the element searched in step 1004, and the width of the item is acquired from the information of “ScrollWidth”.

Next, the scroll bar of the Web page is moved so that the item to be captured is displayed as the display content of the Web page (step 1008). As for the operation of the scroll bar, the position of the item to be captured acquired in step 1005 is set to the values of “ScrollLeft” and “ScrollTop” of the “Body” element, thereby moving the scroll bar.
Next, the display position of the item from the upper left of the Web page is acquired (step 1009). This process is obtained by subtracting the values of “ScrollLeft” and “ScrollTop” of the “Body” element from the display position information of the item to be captured. If the Web page has a frame configuration, it is necessary to add the value of the display position of the frame in which the confirmation item is displayed.
Capture processing is performed based on the item information obtained in steps 1001 to 1009 (step 1010). Details of step 1010 will be described with reference to FIG.

FIG. 11 is a flowchart showing details of the item capture processing portion.
First, when the item to be captured is controllable with a scroll bar, the scroll bar attached to the item is moved to the lowest position and the right end (step 1101). The scroll bar can be controlled by setting the values of “ScrollWidth” and “ScrollHeight” to “ScrollLeft” and “ScrollTop” of the element.
Next, capture processing of items displayed on the Web browser 113 is performed to acquire an image (step 1102), and the acquired image data is stored in a temporary area such as a memory or a temporary file (step 1103). In the image acquisition in this case, an OS (Operating System) capture function is used as an example.

If the width of the display area of the Web page is larger than the width of the item display area, it is determined whether the entire width of the item display area has been captured (step 1104).
When the entire width of the item is captured, only the horizontal scroll bar of the Web page is moved to the item display position (step 1105).
If the entire width of the item has not been captured, the horizontal scroll bar of the Web page is moved to the right by the display area of the Web page (step 1106).
If the vertical width of the display area of the Web page is larger than the vertical width of the item display area, it is determined whether the entire vertical width of the item display area has been captured (step 1107).

When all the vertical widths of the items are captured, only the vertical scroll bar of the Web page is moved to the item display position (step 1108).
If all the vertical widths of the items have not been captured, the vertical scroll bar of the Web page is moved downward by the display area of the Web page (step 1109).
It is determined whether all the display contents in the horizontal direction have been captured among all items to be captured (step 1110).
When all the display contents in the horizontal direction of the item are captured, the horizontal scroll bar attached to the item is moved to the right end (step 1111).
If not all the display contents in the horizontal direction of the item are captured, the horizontal scroll bar attached to the item is moved leftward by the display area of the item (step 1112).

It is determined whether all the display contents in the vertical direction among the items to be captured have been captured (step 1113).
When all the vertical display contents of the items are captured, the image data stored in the temporary area is synthesized to generate an image file indicating the entire items to be captured (step 1114).
If not all the vertical display contents of the item have been captured, the vertical scroll bar attached to the item is moved upward by the display area of the item (step 1115).

FIG. 12 is a diagram illustrating an example of a Web page 1200 that is an item capture acquisition target.
The web page 1200 displays a combo box 1201 for selecting a member type, a search result display unit 1202, and a logout button 1203.
The search result display unit 1202 displays a list of corresponding members by selecting the combo box 1201. When the list cannot be displayed in the display area, scroll bars are displayed both vertically and horizontally. Also, vertical and horizontal scroll bars are displayed depending on the display size of the Web page.

  FIG. 13 shows an image acquisition result 1300 when the combo box 1201 is captured.

  FIG. 14 shows an image acquisition result 1400 when the search result display unit 1201 is captured. The captured image is stored in a temporary file for each display content of the item based on the size and display position of the display area of the Web page and the search result display unit, the display presence / absence of the scroll bar, and position information. It is possible to capture the entire item by combining the last acquired images and generating them as one file.

FIG. 15 shows a log file 1500 for keeping the generation record of the image file 110.
In the log file 1500, a generation date and time 1501 indicating the date and time when the file was generated, an output destination folder 1502 indicating the output destination folder of the image file 110, a file name 1503 indicating the name of the generated file, and the image file 110 are stored. Confirmation contents 1504 representing the contents to be confirmed.

FIG. 16 is a flowchart showing the processing of the capture acquisition result generation unit 107.
First, the contents of the log file 1500 are analyzed, and the confirmation contents for the image file 110 and the acquired image are acquired (step 1601). The image file 110 and the confirmation content are output to a file so as to be displayed on one screen (step 1602).

FIG. 17 is a diagram showing an example of the display screen 1700 of the capture acquisition result file 111. As shown in FIG.
The capture acquisition result screen 1700 includes a “capture image” column 1701 for displaying the acquired image, a “confirmation content” column 1702 for displaying the confirmation content described in the check list 400 of FIG. A “next” button 1703 for displaying the contents and a “previous” button 1704 for displaying the previous image and the confirmation contents are configured. Images and confirmation contents are displayed in the order recorded in the log file 1500.

As described above, the capture system according to the present embodiment has the following effects.
Capturing only the desired confirmation items without searching the screen to be tested can increase the efficiency of confirmation work.

DESCRIPTION OF SYMBOLS 100 ... Capture system, 101 ... Operation reproduction | regeneration part, 103 ... Operation reproduction | regeneration reception means, 104 ... Operation control means, 105 ... Check list analysis means, 102 ... Evidence recording part, 106 ... Capture acquisition means, 107 ... Capture acquisition result Generation means 108 ... Capture acquisition result display means 109 109 log file 110 image file 111 result file 112 client machine 113 web browser 120 network 130 server machine 131 web server 132 ... HTML file, 133 ... Image file, 134 ... Layout control file, 135 ... Application server, 136 ... Web application, 137 ... Database.

Claims (1)

  A capture system that captures the display contents of items that require visual confirmation on the screen among the screens provided by the web application to the web browser, and the items that need confirmation on the screen and the confirmation contents are defined for each test case Analysis means for analyzing the checklist, capture acquisition means for capturing only the specific items defined in the checklist according to the analysis result of the analysis means in the screen provided by the Web application, and storing the captured items in an image file, and acquisition A capture acquisition result generation means for generating a confirmation screen file by associating the image file and the confirmation content, and a capture acquisition result display means for displaying the content of the confirmation screen file generated by the capture acquisition result generation means And capture system.

Images