The EveryStep Scripting Tool is an application that automates the recording of a browser’s interactions with a website or web application. You can use web-based or Windows desktop version  of the browser recording tool. To install the desktop version, see Using EveryStep Scripting Tool Desktop.

Note that if you are going to monitor web applications that are not available from outside a company network, use a desktop version of the EveryStep Recorder to record a monitoring script and Dotcom-Monitor Private Agent to execute monitoring from within the local network. Due to its nature, a web-based EveryStep Recorder will not be able to access this type of web application.

EveryStep Scripting Tool Overview Video

How to Run Web-Based EveryStep Scripting Tool

To use web-based EveryStep Scripting Tool, login to your Dotcom-Monitor account, then on the left sidebar menu select EveryStep Recorder > Web-based Application.

You can also start recording during the monitoring device configuring:

  1. On the Device Manager page, click Add Device at the upper-right corner to add a new monitoring device.
  2. Under Web Applications, select Record Browser Interactions.
  3. In the Record New Script pop-up, enter a starting URL.
  4. Specify User Device Type, Browser, Resolution To Record.
  5. Click Record Now.

Scope of Usage

EveryStep Scripting Tool is used to record scripts for:

  • Web application monitoring: web application monitoring using a browser.
  • Rich Internet Application (RIA) monitoring: web application monitoring that includes a need for image verification or dynamic web page elements, such as Silverlight, Flex, Flash, etc.
  • Server uptime monitoring: web application monitoring using an HTTP/S (GET/POST) request process (HTTP-scripting mode is available only via EveryStep Scripting Tool Desktop).
  • Load Testing: testing web applications from worldwide monitoring agent locations.

Web Applications

This is the default selection and the most commonly used function of EveryStep. Web application monitoring creates a robust script that can perform complex actions including filling out forms, interacting with multimedia, clicking on different elements of a page, checking to make sure specific text and images have loaded on the page, and much more. Read more about how web application monitoring scripting works.

Server Uptime

Click through multiple pages, quickly creating multiple server uptime HTTP/S tasks that run, in sequence, under a single monitoring device. There are several key differences between how server uptime monitoring and web application monitoring scripts work. Download EveryStep Scripting Tool Desktop to implement this monitoring task.

Load and Stress Testing

Record the actions you would expect an average user of your website to perform. Run that script on several different machines to simulate heavy loads on your website. Load testing is unique among the Dotcom-Monitor platforms in that once you record a script, you must schedule one-time tests, while other platforms perform ongoing monitoring.

EveryStep Browser Recording

Next, you perform “every step” of the web application path that a user would normally take, or that you specifically wish to verify with clicks, posts, hovers etc. The EveryStep Recorder records each browser interaction.

Once you are done recording the script, select the Stop button from the left-hand navigation tools.

Once you have stopped recording, you will be prompted to replay the newly recorded script within the EveryStep Recorder to confirm the script recorded properly.

The recording is then replayed within the EveryStep Recorder to confirm that the script works.

Content Validation

Validation is a set of the functions of EveryStep Scripting Tool specific to web application monitoring tasks. Keywords are available in several different kinds of monitoring tasks, including server uptime, web performance, and web application monitoring tasks.

Keyword (text) validation is used to help verify that not only is the server responding to a request but that it is serving up the proper data. Keyword validation allows you to specify keywords to be verified on a page each time the page is loaded. You can specify one keyword phrase per line. A keyword phrase consists of one or more words in the same format as they appear on the page. You cannot include multiple keywords from different locations on a website in a keyword phrase. For more information, see Using Keyword Validation.

Checking for a keyword is not a necessary component of creating a script, however, it is highly recommended that you check for at least one keyword to verify that the content on your page has loaded and rendered successfully.

Image Validation technology is used to take a snapshot of a reference image or area to make a per-pixel comparison. For more information, see Image Validation.

The result is a coefficient of a coincidence that is used to determine the existence of the image during monitoring.

RIA Recorder

Rich Internet Application (RIA) monitoring is an add-on module of the EveryStep Scripting Tool that provides an unparalleled level of rich application monitoring capabilities. Combining our powerful Image matching technology with EveryStep Scripting Tool allows for easy creation of complex transactional analysis scripts that can actually “see” and interact with RIA technologies such as Flash, Silverlight, Java, Flex, Ajax, Shockwave, QuickTime, ActiveX, and others.

To work with dynamic RIA sites, use RIA Image and RIA Keyboard + Mouse functions.

A video demonstration of RIA capabilities and the recording process is available in the How To: Recording an RIA Script video.

Filtering Errors

If any errors are detected in the script, you will be presented with the list of errors and prompted to choose whether you wish to filter out those errors when the script runs by selecting Ignore.

If you choose to filter out an error, EveryStep Scripting Tool will add a filter to the beginning of the script similar to the following:

NetworkFilter.Deny (““);

If at any time the script runs into an error with this element, the error will be ignored, and the script will continue to run without reporting the error.

Saving the Script

After creating your first script, save it to the Dotcom-Monitor site by pressing the Save button.

The EveryStep script is uploaded to your Dotcom-Monitor account where alerting and reporting options are configured. Here you will set the final details for your monitoring script including: