Table of Contents
Overview
The Synthetic Monitors page houses all of a site's synthetic monitors, including Single Page, Multi-Step, API Checks, Multi Step API, and Network Health Check monitors.
Single Page Synthetic Monitors
A single-page synthetic monitor measures the performance and availability of a single page from a site.
Multi-Step Synthetic Script
A multi-step synthetic monitors are used to track performance and availability of user journeys across a site.
There are a few more things to watch out for when creating multi-step synthetic scripts.
- When naming steps, keep in mind how you would like to segregate the data. If the step is common across multiple scripts, it is okay to use the same name across scripts. Use prefixes to be more precise, such as prefacing steps with "Ord" if a script is named "Orders". Underscores and dashed are also okay to use.
- Each step of the script should contain only one user action that changes the page, including more than one action will make debugging issues more difficult.
- After a user action that changes the page, insert a waitFor command (waitfForTextPresent or waitForElementPresent) to confirm that the action is completed. For the waitfForTextPresent command, inspect the text and copy it from the Elements tab in DevTools. (For example, the page display is "HELLO WORLD", but the element text is "Hello World").
- Pauses are only needed if a waitFor command does not fully satisfy completion of the page update. There are page updates not identifiable through waitForTextPresent or waitForElementPresent.
- There are many options when defining the "locator" of an event command, such as a click or type. If you have a recorder (like Katalon Recorder), it can give a number of locator options. Sometimes a runScript command with documentQuerySelector().click() might work better. Try using a css= or xpath=, you can find them under Copy in the Elements tab in DevTools.
Comments
0 comments
Please sign in to leave a comment.