Configure step behaviour

Enhance your testing with Low Code Automation by customizing step behavior like locators, wait timeouts, and failure logic.

Low Code Automation by default handles finding the right unique element and waiting for a specific duration before performing the actions on the browser intelligently. It also sets appropriate failure logic for validation and action steps such that multiple validations can be executed in a single test even if one validation fails. There are use-cases where it may need these configurations to be adjusted to meet the specific requirement of the workflow automation. This document outlines how you can override the default configurations and customize the behavior of each step.

• Configure step locator
• Intelligent wait timeout
• Configure step failure logic

Configure step locator

Enhance the resilience and flexibility of your tests involving complex elements by configuring custom locators for steps. Low Code Automation now allows you to configure your own locators for recorded steps. This is usually helpful when dealing with elements that:

• Do not have any meaningful attributes
• Have dynamic class names, IDs, and other attributes
• Can only be identified in relation to other element on the page

How to configure

1. Navigate to the corresponding step for which you want to configure your own locator
2. Click on the step to open the configuration details
3. Toggle the setting Override default locator
4. Select XPath or CSS from the dropdown
5. Provide your locator corresponding to the element which uniquely identifies that element

Locator concatenation syntax

To specify locators within iframes and Shadow DOMs, we use a concatenation syntax to distinguish between different levels. The syntax includes the following separators:

• <<: Denotes the transition between iframes.
• ||: Denotes the transition between Shadow DOMs.

Locators are defined in a hierarchical manner, first identifying the iframe or Shadow DOM and then specifying the element within.

Steps to locate elements

• Iframe example
• Shadow DOM example
• Import variables in custom locators

Iframe example

In this example, we want to target an input element with the class credit-card-number within the iFrame with the ID payment-form.

• To find an element inside an iframe, we need to first find the iframe using the locator.
• The iframe element in the provided image is identified by the ID payment-form, and its corresponding CSS selector is #payment-form
• Now, find the targetted element inside this iframe
• The input element in the provided image is identified by the class credit-card-number, and its corresponding CSS selector is input.credit-card-number.
• Concatenate the two locators using separator << to form the final locator value as below

   #payment-form << input.credit-card-number
  

Shadow DOM example

In this example, we want to target an input element with id cardholder-name which is inside a shadow-root having parent element with id cart-checkout.

• To find an element inside a shadow-root, we need to first find the element which contains the shadow-root element.
• The shadow-root element in the provided image is present under element with ID cart-checkout, and its corresponding CSS selector is #cart-checkout
• Now, find the targetted element inside the shadow-root element
• The input element in the provided image is identified by the ID cardholder-name, and its corresponding CSS selector is #cardholder-name.
• Concatenate the two locators using separator || to form the final locator value as below

   #cart-checkout || #cardholder-name
  

Import variables in custom locators

• You can now also import variables in your custom locators. Click the + icon next to the locator text input box.
• Import any local or dataset variable in your custom locators.

Intelligent wait timeout

If the browser elements don’t load in time during test execution, the test might encounter incorrect results. Here’s where BrowserStack’s Low Code Automation offers a smart solution to set wait timeouts for different steps. By default, it intelligently detects the best wait time based on network requests and page navigations during the recording process. This ensures that the test is more stable even if the element sometimes takes slightly longer time to load during execution.

During test execution, Low Code Automation’s element selection algorithm finds the unique element and performs different actionability checks on the element to ensure it is actionable before executing the step. It retries multiple times if the element is not found or not actionable until the timeout of the step is reached.

By default, the intelligent wait timeout is enabled for each step. To override the setting and provide your own timeout value, you can disable the Intelligent timeout toggle for a particular step and adjust the wait timeout according to your use case.

Configure step failure logic

Low code automation provides you with options for handling test failures. You can decide what action to take when a test step fails.

Choose one of the following options to be executed:

• Fail but continue execution: Choose this option when you want to mark the step as failed but still continue with the execution. You can use this to perform the remaining validations even if current validation fails.

  

• Warn but continue execution: Choose this option when you want to ignore the step failure and continue with the execution. Failure of this step does not affect the overall test status. You can view the summary of the test execution report as shown below:

  

• Fail the test immediately: Choose this option when you want to mark the step and test as failed and halt the test execution right away.