A new Execution Diagnostics section has been added to the Test Case Editor's Properties panel, giving you deeper insight into what happened during a test run.

• Debug Analysis: after a test run completes or fails, trigger an AI-powered analysis that automatically identifies root causes of failing steps and provides a summary of what went wrong
• Download Console Logs: download the browser's console output captured during the test run as a .txt file, making it easy to inspect JavaScript errors, warnings, and network issues
• Both tools become available in the Properties side panel once a test execution reaches a completed or failed state

Sprint #25

More granular control over accessibility checks.

• A new "Always" severity level is available in the Accessibility Persona configuration.
• Use it to confirm accessibility is respected on every new page your test visits, even when no standard is violated.

Sprint #25

The test case editor now moves at the speed of your keyboard.

• Run a test with **⌘**/Ctrl+E, stop it with Esc.
• Open Thunders Copilot with **⌘**/Ctrl+J.
• Open the properties panel with **⌘**/Ctrl+I
• And more... Tooltips show the shortcut next to every action.

Sprint #25

Thunders now flags test execution issues (like console errors), even when the UI still looks fine.

• Thunders automatically detects Browser Console Errors during execution.
• See exactly which console errors fired in any step.
• Turn the setting on or off from the QA Persona profile.

Sprint #25

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