Skip to main content

Multi‑Tab Workflows

Written by Ines

Prerequisites

Your test opens more than one browser tab during execution (for example, a link that opens in a new tab).


Browser Tab Bar

The Browser Tab Bar shows you all the browser tabs that are open during your test. It appears in the browser panel, making it easy to see which tabs are active and navigate between them when reviewing your test results.

Where You'll See It

The tab bar appears at the top of the browser panel in both:

  • Test Case Editor: while your test is running

  • Test Run Report: when reviewing completed test results

What the Tabs Show

Each tab in the bar represents a browser tab that was open during your test. You'll see different types of tabs:

  • Browser tabs: Show the page icon (favicon) when available, with the page title or website name

  • API Call: Appears when viewing an API call step

  • Assertion: Appears when viewing an assertion step

  • Extraction: Appears when viewing an extraction step

Tab Labels

Each tab displays a label to help you identify it:

  1. Page title: If the page has a title, it shows the most relevant part

  2. Website name: If there's no page title, it shows the website domain

  3. Tab number: If neither is available, it shows "Tab 1", "Tab 2", etc.

How It Works

  • Active tab: The tab you're currently viewing is highlighted

  • Hover for URL: Hover over a browser tab or API tab to see the full URL

  • Scrolling: If you have many tabs, scroll horizontally to see them all

  • Updates automatically: The tab bar updates as you click through different steps in your test

Empty State

If no tabs are available (for example, when no step is selected), you'll see "No active tab yet" instead of tabs.


Switch To Tab

Switch To Tab lets you change the active browser tab during a test run.

Instead of being limited to the tab that is currently in focus, you can tell Thunders to switch to another open tab by its Tab Number.

Why Use Switch To Tab?

Switch To Tab makes multi‑tab scenarios reliable and easy to debug:

  • Handle real user flows like "Open invoice in a new tab", "Continue checkout in another tab", or "Open Terms & Conditions"

  • Control which tab the test is interacting with

  • Keep your run readable by making tab changes explicit in your steps

How to Use Switch To Tab

1. Run your scenario and confirm multiple tabs are open

During execution, your flow may open additional tabs. When a new tab is opened, Thunders will automatically switch to it.

2. Add a Browser step

In your test steps, add a Browser step.

3. Select the action Switch To Tab

Choose Switch To Tab from the action list.

4. Enter the Tab Number

In the value field, enter the Tab Number of the tab you want to switch to.

  • The label is Tab Number

  • The placeholder is Enter tab number (e.g., 1, 2, 3)

  • Tab numbers start at 1. Example: use 2 to switch to the second open tab

5. Continue your steps in the new tab

Once you switch, all following steps run in that tab until another tab change happens or a new tab is opened.


Open New Tab

Open New Tab lets you open a brand-new browser tab, navigate it to a specific URL, and automatically switch context to it, all in a single step.

While Switch To Tab moves focus to an already-open tab, Open New Tab creates one. After the step executes, every subsequent step runs inside the new tab until another tab action is used.

How to use it

  1. Add a Browser Step

  2. Select the action Open New Tab

  3. In the Value field, enter the full URL (must start with http:// or https://)

  4. The Selector field is not required and is automatically hidden for this action


Troubleshooting / FAQ

I entered a tab number and the step fails — why?

The most common cause is: The tab you're trying to switch to does not exist (for example, you asked for tab 3 but only 2 tabs are open).

Do I need to specify a URL or title to switch tabs?

No. Switch To Tab switches by Tab Number.

What does "Tab Number" refer to?

It is the position of the tab among the currently open tabs in the run (starting at 1).

What if my flow opens tabs unexpectedly?

If your application opens new tabs unexpectedly, your test may still continue, but it can become harder to predict which tab is active. Adding an explicit Switch To Tab step keeps the context clear.

When I have 2 tabs (tab1 and tab2), then I switch to tab 1, and perform an action that opens a new tab, what will be the number of the new tab?

New tabs are always opened at the end. If you perform a click that opens a new tab while on tab 1, the new tab will be tab 3.

Why don't I see all my tabs in the browser tab bar?

The browser tab bar only shows tabs that represent actual page interactions. It filters out system events that don't correspond to real browser tabs you can interact with.

Why does the tab bar show "No page selected"?

This appears when:

  • No test steps have been selected yet

  • The selected step has no actions to display

Click on a step with actions to populate the tab bar.

Did this answer your question?