Browse Prior Art Database

Automated tool for Web based application browser testing

IP.com Disclosure Number: IPCOM000020239D
Original Publication Date: 2003-Nov-05
Included in the Prior Art Database: 2003-Nov-05
Document File: 3 page(s) / 93K

Publishing Venue

IBM

Abstract

As per today, web based application testing is required to be performed in different browsers in order to support heterogeneous client environments. The cost of testing will increase tremendously along with the new release of various browsers. There are no tools in the market which target at testing in different browsers and most of them only emphasis on performance testing. Disclosed is an automated tool to reduce browser testing effort, hence increase overall testing productivity.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 48% of the total text.

Page 1 of 3

Automated tool for Web based application browser testing

In general, there are two aspects a tester will validate when performing browser testing: Supporting of specific scripting language: Each browser of specific release supports a set of   scripting languages and different versions of standard. If a particular syntax of the scripting language is not supported, an error message or garbage output will be displayed. Rendering of HTML or other output type : The look and feel may differ from browser to browser when HTML is displayed. This is important for some web applications which have to comply to a specific web design guideline or specification. For all cases, visual inspection of the browser input is necessary in any browser testing. This has lead to the main design of the automated tool which has the screen capture capabilities when performing browser testing. In general, there are two aspects a tester will validate when performing browser testing: Supporting of specific scripting language: Each browser of specific release supports a set of scripting languages and different versions of standard. If a particular syntax of the scripting language is not supported, an error message or garbage output will be displayed. Rendering of HTML or other output type : The look and feel may differ from browser to browser when HTML is displayed. This is important for some web applications which have to comply to a specific web design guideline or specification. For all cases, visual inspection of the browser input is necessary in any browser testing. This has lead to the main design of the automated tool which has the screen capture capabilities when performing browser testing.

The application architecture of the automated tool is as follows:

Recording

User Input

Test Engine

Screen Capture

Response Editor

System configuration Test cases Screen captures

Rule base: parsing/JavaScript generator

Figure 1: Application Architecture: There are 3 main components in the application architecture. Databases are used to stored application information.

Recording component

Recording component is responsible for recording steps in a test case. This can be achieved by capturing all the HTTP request messages sent to the Web server. In particular, one HTTP request

1

[This page contains 2 pictures or other non-text objects]

Page 2 of 3

message represents one of the steps in the test case. By parsing the HTTP request message, recording component will be able to determine:
a) The triggering source, either directly go through HTTP reference or by clicking on input button.
b) If input button is used, record all the parameter value pairs sent in the request message. The rules to parse the HTTP message can be stored in the database to allow changes in the future. User Input component User Input component represents a GUI based interface to display all the required information after recording. User can modify the value of the input parameter in any...