Prerequisite
Before adding a browser step, you need to have an existing Test Case.
What is a Browser Step?
A Browser Step is an explicit browser automation command you define with:
an Action (what to do)
a Description — a natural-language explanation of the step
a Type (how to identify the element)
a Value (the actual selector or value)
Use it when you need full control on tricky pages.
When to use it
Complex targeting: Elements are hard to describe in plain text.
Unstable structure: Element text and content changes between visits.
Critical paths: You want predictable, repeatable behavior.
Add a Browser Step
Open your Test Case.
Click Add New Step.
In Step type, select Browser Step.
Configure the step
Action: Choose what to do (for example: Click, Type, Select, Check, Hover, Scroll, Wait for visible).
Description: Add a short, human-friendly explanation of what the step is doing.
Type: Select how the element is identified — CSS, XPath, ARIA Label, Text.
Value: Enter the corresponding selector/value
How to get a selector
Using browser developer tools
Use this method when your Selector type is CSS or XPath:
Right-click the element and choose Inspect.
In the Elements panel, right-click the highlighted HTML.
Choose Copy → Copy selector (CSS) or Copy → Copy full XPath.
Paste it into the Selector field of your Browser Step.
2. If your Selector type is ARIA Label or Text:
ARIA Label: Enter the value of the element’s
aria-labelattribute (you can check it in the HTML).Example: if the element has , use
Submit.
Text: Enter the visible text that appears inside the element.
Example: for a button showing “Login”, use
Login.
Tips for reliable selectors
Prefer CSS selectors over XPath when possible.
Target stable attributes (for example,
data-testid,aria-label, persistent class names).Avoid dynamic IDs or deeply nested paths that may change.
Make the selector unique to one element.