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 Selector (what to do it on)
an optional Value (what to type or select, if needed)
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).
Selector: Paste a CSS selector or full XPath for the element to target.
Value: Provide a value if the action needs one (for example, the text to type).
How to get a selector
Using browser developer tools
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.
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.