How to add and use a Browser Step

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

Complete List of Browser Step Actions

Below is a comprehensive reference of every available browser step action, organized by category.

Navigation & Tab Management

These actions control page navigation and tab behavior. No selector required.

Action	Code	Description
Go Back	`goback`	Navigate to the previous page in the browser history.
Go Forward	`goforward`	Navigate to the next page in the browser history.
Reload	`reload`	Reload the current page.
Switch To Tab	`switchtotab`	Switch to an already-open browser tab. Requires a value (tab index or identifier).
Open New Tab	`opennewtab`	Open a new browser tab. Optionally provide a URL as the value.

Waiting

These actions pause execution until a condition is met. Useful for dynamic pages.

Action	Code	Description
Wait For Timeout	`wait`	Pause execution for a specified duration (in ms). Requires a value (timeout in milliseconds). No selector needed.
Wait For Selector	`waitforselector`	Wait until an element matching the selector appears in the DOM. Requires a selector.
Wait For Load State	`waitforloadstate`	Wait until the page reaches a specific load state (e.g., `load`, `domcontentloaded`, `networkidle`). Requires a value. No selector needed.
Wait For URL	`waitforurl`	Wait until the page URL matches a specified pattern. Requires a value (URL or URL pattern). No selector needed.

Element Interaction

These actions interact with elements on the page. All require a selector unless otherwise noted.

Action	Code	Description
Click	`click`	Click on an element. Requires a selector.
Double Click	`dblclick`	Double-click on an element. Requires a selector.
Right Click	`rightclick`	Right-click (context menu) on an element. Requires a selector.
Middle Click	`middleclick`	Middle-click on an element (typically opens link in new tab). Requires a selector.
Click At	`clickat`	Click at specific page coordinates. Requires x and y coordinate values instead of a selector.
Hover	`hover`	Hover the mouse over an element. Requires a selector.
Drag	`drag_drop`	Drag an element and drop it on another. Requires a source selector and a target selector/coordinates as value.

Input & Selection

These actions fill in or modify form fields. All require a selector and typically a value.

Action	Code	Description
Fill	`input`	Type text into an input field (clears existing content first). Requires a selector and a value (text to enter).
Clear	`clear`	Clear the content of an input field. Requires a selector.
Press	`press`	Press a keyboard key or key combination (e.g., `Enter`, `Tab`, `Control+A`). Requires a value (key name). Selector is optional (targets focused element if omitted).
Select	`select`	Select an option from a dropdown. Requires a selector and a value (option value or label).
Open Dropdown	`open_dropdown`	Open a dropdown element without selecting. Requires a selector.
Check	`check`	Check a checkbox or radio button. Requires a selector.
Uncheck	`uncheck`	Uncheck a checkbox. Requires a selector.
Select Text	`selecttext`	Select/highlight text within an element. Requires a selector.

Focus & State

These actions manage element focus and visibility.

Action	Code	Description
Focus	`focus`	Set focus on an element. Requires a selector.
Blur	`blur`	Remove focus from an element. Requires a selector.
Scroll Into View	`scroll`	Scroll the page until the element is visible in the viewport. Requires a selector.

Screenshot & Export (NEW)

These are recently added features that allow you to capture visual snapshots and export page content directly from a browser step.

Action	Code	Description
Screenshot (Viewport)	`screenshot_viewport`	Capture a screenshot of the current browser viewport. No selector required.
Screenshot (Full Page)	`screenshot_full`	Capture a full-page screenshot (includes content below the fold). No selector required.
PDF Export	`pdf_export`	Export the current page as a PDF file. Chrome/Chromium only. No selector required.
Extract File	`extract_file_from_page`	Extract structured data (e.g., CSV) from the page content. Supports options like removing empty columns. No selector required.

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.

If your Selector type is ARIA Label or Text:

ARIA Label: Enter the value of the element’s aria-label attribute (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.