Thunders News Center

When a test opens multiple tabs, you now have full visibility into what's happening.

• Tabs appear in the test preview header with page title and favicon.
• Works during live execution and in the test run view.
• Always know which tab you're looking at in multi-tab scenarios.

Sprint #25

Debugging a flaky test is much easier when you can see exactly where two runs diverged.

• Step-by-step diff to pinpoint the first point of divergence.
• Action-level diff for a deeper look inside a single step.
• Compare side by side across screenshots, page HTML, logs, and execution settings.

Sprint #25

Test sets used to be a simple list nested inside your project. Each one now has a dedicated workspace: a single place to organize, run, and iterate on a set as it evolves.

• See pass rate, set runs, and every test case in one view.
• Search, filter, add, or remove tests from the same page.
• Work with a set end to end without jumping between screens.
• In sets runs list, you can bulk re-execute and bulk stop

Sprint #25

Previously, asking Thunders Copilot meant waiting behind a loading spinner with no visibility into what was happening. That black box is gone. Thunders Copilot now streams its thinking and actions to you in real time:

• Ask it to pull in an existing test case while you're authoring a new one, and watch it find and weave it in.
• See it fetch context from Jira or Linear as it drafts your tests.
• Watch it browse the web to build test cases grounded in real product flows.

Sprint #25

API steps are no longer opaque:

• After execution, open the full response in an interactive inspector and navigate the JSON.
• Extract any value as a reusable variable in one click, with context-aware naming.
• Define assertions directly on the response, on status codes, headers, or body values.

Sprint #25

A project can now contain multiple applications, each with its own type and environment URLs.

• Add Web and API apps to the same project from the new Apps tab.
• Set a separate URL per environment for each app, so the same test project can cover staging, production, and more.
• Write test cases that cross app boundaries with a single test can navigate from your admin panel to your frontend and verify changes end to end.
• Thunders Copilot understands your apps when you say "go to the Admin app", it resolves it to the right URL automatically.

Sprint #25

Bugs reported from a failing test step are now saved and surfaced everywhere: on the test case detail, in the test run view, and in list views via a bug count column.

You can see the full history of bugs already reported for any test case and navigate to it in one click.

💡 This prevents duplicate bug reports and makes it easy to know whether a known issue is already being tracked.

Each test step now includes a short explanation of how the AI identified and selected the element it interacted with.

Click the icon on any step to see the reasoning: why the AI chose a specific button, field, or link.

💡 This makes it much faster to catch cases where the AI picked the wrong element, without digging through screenshots or logs.

Tests can now extract data from downloaded files (PDFs, Excel, CSV, and more) during execution, and store the extracted value in a variable for use in subsequent steps.

This enables automation of workflows that depend on the content of a downloaded document, such as reading a confirmation number from a receipt or extracting an ID from a generated report.

❗ You need to execute your test with “Firefox” to be able to use File Extraction

You can now create custom labels with colors, assign them to test cases, and filter by label across the test case list and test run list.

A full label management page is available for creating, editing, and deleting labels at the project level.

💡 Use labels like "Smoke", "Regression", or "Critical" to quickly find and run the right subset of tests as your suite grows.