Web Transaction Scout

The Web Transactions Scout simulates a user's interaction with a SaaS application (or any website). While performing the predefined interactions, the Scout checks if the website is working as expected and can detect errors such as slow loading times.

A test is made up of steps that define what the Scout does on the web page. You can choose from many different types of steps, and use element locators to control where the step is performed.

For example:

• Load the web page
• Step 1: Wait until the username and password fields appear
• Step 2: Enter the username
• Step 3: Enter the password
• Step 4: Click Sign In
• Step 5: Perform some action on the web page

Step types

 This table describes the types of steps you can use to perform different actions on a website.

Create a Web Transactions Scout

1. Go to Create Scout > Applications and select Web Transactions as the Scout type.
2. In the Hives field, select one or more locations from which you want to initiate the test.
3. Enter the URL of the website to begin the web transaction. The Scout loads this website at the beginning of each test. After the page is loaded, the Scout performs the steps that you define.
4. Enter a Name for the Scout.
5. With the Run Every slider, choose how often you want the Scout to perform the test.
6. Define the workflow to perform on the website. You can either:
   • Click Record Steps and use our browser extension to interactively record a workflow. This is the recommended method. Click here to learn how to record your steps.
   • Manually add steps and configure the parameters for each step type. Click here to learn how to get element locators. Read Step Types above to learn how to configure each step.
     Note

     You can rearrange the order of steps, delete steps, and insert steps using these buttons:
7. Optionally, add labels to the Scout. Labels are used to help organize and filter Scouts.
8. Click Show additional parameters to configure the following:
   • SSL Verify. Sets whether to check for a trusted SSL certificate on the website. If you select Yes and the certificate isn't trusted, then the test fails.
   • Success Codes. Sets which HTTP status codes the Scout considers a successful response. If the status code of the website is not one of the selected options, then the test fails.
   • Screen size. Sets the resolution used when testing the website.
   • Overall transaction timeout. Sets the timeout duration for the entire test, including the initial page load and all steps. if this duration is reached before all steps are completed, then the test fails.
9. Click Test to test the current Scout configuration. You should test the Scout frequently when you are adding steps to make sure that the step logic and element locators are working correctly.
10. Click Save and optionally configure an alert policy before saving the Scout. Learn more about alert policies.

Record your steps interactively

Instead of configuring each step manually, you can use our transaction recorder to record your steps on a website interactively. The transaction recorder automatically adds your steps to the Scout configuration page.

The transaction recorder can record Click, Insert text, iframe step in/out, and Press key steps. If you need to add other steps, you can edit the Scout configuration after you record your steps.

Note the following requirements before you use the transaction recorder:

• Supported only on Google Chrome.
• Before starting the recording on a website, make sure your cache is cleared and that you disable any form of auto-completion for usernames, passwords, etc.
• Don't use an incognito window.

To record your steps:

1. Click here to download the browser extension from the Google Chrome web store.
2. In the Scout configuration page, enter a URL and click Record Steps.A new browser tab opens the URL you entered. 
3. Perform a workflow on the website, and the transaction recorder automatically records each step that you perform.
4. When you are finished performing the steps, click Submit. The steps are automatically added to the Scout configuration page.

Manually configure steps using element locators

If you manually configure steps (instead of using the transaction recorder), you need to specify where to perform the interaction using one of the following types of element locators:

• CSS selector
• XPath
• JS path

We recommend that you use CSS selectors. Web developers often add automation IDs to elements so that they can be easily located using a CSS selector. If you're having trouble testing an internal site, you can ask your web developer to add unique automation IDs.

Some websites dynamically change the names of element classes each time the page loads (for example, div.treeButton__MYZeT might change to div.treeButton__B4yZ4 when the page refreshes). In these cases, XPath might be the better option to locate the element.

JS path should be used when the name of the element is not dynamically changing and it is located under the shadow root. In these cases, CSS selectors won't include the path to the element, but JS path will.

To get element locators:

1. Click here to download our browser extension from the Google Chrome web store. The extension is supported only on Google Chrome.
2. Go to a website and Start the browser extension. We recommend that you use an incognito window to ensure that the website is not cached on your browser.
3. Click on the element on the website that you want to get the locator for. As you hover your cursor around the website, a red box highlights the elements on the page.
4. After clicking on the element, copy the locator for the element. You can paste the element locator into the Scout configuration page.

How to sign in to SaaS applications

Most SaaS web applications start with a login screen. This Scout can enter a username and password, but does not support multi-factor authentication (MFA). If the application you want to test uses MFA, then there are a few ways to get around this requirement:

• Bypass MFA in your application. In the application you want to test, configure a service account that doesn't require MFA.
• Bypass MFA in your identity provider. In your identity provider, configure a service account that doesn't require MFA. When the Scout attempts to sign in to the application, it is redirected to your identity provider for authentication. The Scout enters the username and password and is returned to the application after authentication.

You might want to bypass MFA only if the sign in attempt comes from a specific IP address. If you are using a Custom Hive, then the IP address comes from the machine where the Custom Hive is installed. To see the IP addresses of Cloud Hives, visit Cloud Locations Used by Scoutbees.

Test results

When you view a test result, you can see details about the initial page load and all steps performed. You can also see a screenshot taken during each step. Click on a screenshot to enlarge it.

Metrics

The metrics in the table below are collected for each test result. You can create an alert policy based on some of these metrics so that you are notified when something goes wrong.

Tips and troubleshooting

• Most step types do not have a timeout. For example, a Click step will click on an element when it appears, even if it takes 30 seconds for the element to appear. If you want the test to fail based on the time it takes for an element to for an element to appear, add a Wait step and set the timeout duration.