A Real Browser check allows us to monitor the user experience around performance for a single page or a multi-step user flow. For each page checked in a Real Browser check, Rigor captures a HAR file, or waterfall chart, that helps us see the performance of specific resources within the page.
Here are some ways to create Real Browser Checks in Rigor:
- From Scratch (single page)
- From Scratch (multi-step)
- Via Import (multi-step from Selenium IDE source code)
To create a new Real Browser Check from Scratch:
Navigate to Real Browser + New > From Scratch
From the side navigation, click + New > Real Browser > From Scratch
On the Basic tab:
- Name the check. Be sure to pick a unique, descriptive name so that we can determine the check’s function at a glance.
- Supply a starting URL. The check will begin by going to this URL and the first step in the check will be within the context of this page.
- Notify. Tell Rigor who, how, and when to alert users or groups if the check fails.
- Frequency. Define how often the check should run.
- Check Active / Inactive. Use this slider to activate or pause the check.
- Notifications Active / Muted. Use this slider to send or mute alerts.
We can easily add multiple steps to a Real Browser check. If we’d like to build a multi-step check, we should first open the initial URL (the same URL that we set on the Basic tab) in our browser.
For each step we would like to add to the user flow, we can ‘Inspect Element’ in our browser to identify an id, class, name, CSS Path, or XPATH to target each element. Once we know the correct way to target a specific element we can + Add Step in Rigor to configure the Real Browser check to interact with the element or wait for the element to be present on a page.
On the Steps tab:
- Use + Add Step to create steps for your check that simulate user flow. There are two types of steps: actions and waits.
- Use the hamburger icon to drag and re-order steps; use the trashcan icon to delete steps.
- Click the Test button to queue up a test run in the Rigor system. Tests won’t affect reporting or trigger alerts but they can help diagnose whether test steps need to be edited to successfully simulate a path or user flow.
When a test comes back with ‘Test Result: OK’ we know that we can save the Real Browser check and expect to see ‘available’ results on runs unless some performance issue prevents the check steps from executing successfully.
Download Rigor Scripting Guide for more help creating multi-step Real Browser Checks from scratch.
Selenium IDE is an extension for Firefox that helps us record and edit Selenium scripts. Selenium scripts use simple commands to target and interact with elements on your website.
Read more about using the Selenium IDE recorder here.
Once we have a Selenium script recorded, we can import the script to Rigor to quickly build a new Real Browser check:
- Save the Selenium script or copy the source code from the Selenium recorder.
- Checks > Real Browser + New > Import > and select either From File or From Source
- Select your file to import or paste source code > Import
- Rigor will automatically create the steps that correspond with the Selenium test and remove any steps that are duplicated by our system.