Creating a Script with EveryStep

Glossary Definition:  EveryStep Scripting Tool

The EveryStep Web Recorder can be found under the Tools menu after logging into your Dotcom-Monitor account.

You will need to enter the URL you wish to monitor.

There are three types of monitoring scripts you can create:

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.

Stress Testing

Record the actions you would expect an average user of your website to perform and run that script on several different machines to simulate heavy loads on your website. Stress test monitoring 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.

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.  Keyword validation is available by selecting the Keyword button from the left-hand navigation area of the EveryStep Web Recorder window. This will open the Keyword Validation dialog box.

You can populate the Keyword Validation dialog box with any single word.

You may specify multiple words, but only in the exact order they appear.

If you wish to specify multiple keywords that are not in sequence, you should specify each keyword in a separate Keyword Validation dialog box. The Keyword Validation dialog box does not accept comma separated or semi-colon delimited lists of keywords.

Keyword validation adds a line to the script that asserts the specified keyword exists somewhere on the currently loaded web page.

Note: The script looks for the exact case and punctuation that you enter. If you are looking for a word that begins with a capital letter, you must be sure to use the proper case when specifying the keyword.

If you try to add a keyword and the script returns an error stating that the keyword does not exist, make sure that you have entered the text exactly as it appears on the page and that you have not accidentally added a space or pressed enter at the end.  If this occurs, a line break will be added to the end of the keyword.

You can also add a keyword for Keyword Validation by selecting a word on the page and then right-clicking (alternate click) the word. This will open the Keyword Validation dialog box and automatically populate it with the word you have selected.

For additional help with keyword validation:

EveryStep 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 Web 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.

Filter out 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 will add a filter to the beginning of the script similar to the following:

NetworkFilter.Deny (“http://www.example.com/FilteredOutElement.ttf“);

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.

Save the Script

After creating your first script, you will want to 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: