Click here to Skip to main content
Click here to Skip to main content

WebReplay - an automated software testing tool for Web applications

, 16 Jun 2005
Rate this:
Please Sign up or sign in to vote.
This article presents an automated software testing tool for Web applications (Internet/Intranet) based on Internet Explorer.

Click to enlarge

Introduction

Web Replay is an automated software testing tool for Web applications. It helps in detecting bugs and regressions in Web applications by replaying scenarios to test the application.

Using WebReplay, you can automatically navigate to a Web page, fill in form fields, click on the submit (OK) button, and then continue to another Web page.

To use Web Replay, build an XML Scenario File (see below), type the name of the file in the edit box and click on the Replay button.

Background (optional)

Web Replay is based on Microsoft's WebBrowser control (Microsoft® ActiveX® control). It embeds the control into a very simple dialog-based application which loads an XML scenario file and programmatically drives the WebBrowser control (via its COM Interface IWebBrowser2) to execute the scenario.

Using the code

Web Replay provides the following features:

  • Replay scenarios from an XML file.
  • Supports every feature supported by Microsoft Internet Explorer (includes Windows Integrated Authentication).
  • Supports HTML forms, HTML input elements, HTML hyperlinks (anchors).
  • Supports two actions on HTML elements: set_value and click:
    • set_value simulates a change in the HTML element's value (input, select, etc...).
    • click simulates a mouse click on the HTML element (any element).
  • Supports unnamed HTML elements: Elements can be found with their associated value and/or innerText and/or Href.
  • Stores and reloads the last scenario file name (it uses a good old WebReplay.ini file).
  • Supports dynamically-generated Web Sites (client-side): If your web site generates HTML within the browser (using JavaScript's commands like "document.write"), Web Replay can still play back a given scenario - it uses a timeout mechanism to find the dynamically-generated controls.

Sample XML Scenario

An XML scenario file looks like this:

<?xml version="1.0" encoding="Windows-1252"?>
<web_replay>
  <scenario>
    <!--<span class="code-comment"> Search something in codeproject --></span>
    <!--<span class="code-comment"> Scenarios are divided into steps (one step per page download) --></span>
    <step>
      <!--<span class="code-comment"> Every step can contain one or more actions --></span>
      <!--<span class="code-comment"> Action can be of type "navigate" = 
             Web Replay will navigate to the given URL --></span>
      <action type="navigate" url="http://www.codeproject.com" />
    </step>
    <step>
      <!--<span class="code-comment"> Action can be of type "control" = 
             Web Replay will interact with an HTML element --></span>
      <action type="control" 
             name="target" event="set_value" value="WebReplay" />
      <!--<span class="code-comment"> This field is unnamed; but it has a specific value attribute --></span>
      <action type="control" name="" value="Go" event="click" />
    </step>
  </scenario>
</web_replay>

To build a scenario file, you need to basically know the names (or ids) of HTML elements within your Web Application. Alternatively, you can use an empty name and use the HTML element's value (for unnamed items).

Points of Interest

How do you test code? Well, just write a test program! Web Replay helps you with this by providing a simple way of testing you Web apps. But it's still a brand new program; the TODO list is long...

Web Replay TODO List

  • Play scenarios multiple times (even infinite loops to stress-test your Web application).
  • Use of variables/expression in scenario files (to replay scenarios that are always different).
  • Batch playback of scenario files.
  • Enhanced error detection (e.g. a scenario should fail if a given HTML pattern is not found in the HTML page).
  • Automated recording of scenario files (implement an event sink for IWebBrowser2 and record HTML elements names/id and associated event).

History

V1.0 - $Date: 2005-06-16 11:50:08 +0200 (Thu, 16 Jun 2005) $

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

Emmanuel Kartmann
Web Developer
France France
Fell into computer software at the age of 11, founder of 3 startups, and now manager of an independent software vendor (ISV) labelled proSDK (www.prosdk.com)... And still a freeware writer and technical article author!

Comments and Discussions

 
Generalnice PinmemberDonsw22-May-09 7:46 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web01 | 2.8.140709.1 | Last Updated 16 Jun 2005
Article Copyright 2005 by Emmanuel Kartmann
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid