Thunders News Center

New step types expand what you can pull out of the browser during a test run.

• Extract File: pull HTML table data from the page as a downloadable CSV, with an option to remove empty columns.
• Screenshot Viewport or Full Page: capture either the visible browser area or the entire scrollable page as an image.
• PDF Export: export the current page as a PDF document.

These steps let your tests produce artifacts (data exports, visual evidence, full-page snapshots) that you can review, attach to reports, or share with your team.

#Sprint26

Some tests only make sense to run after a setup or sanity check has passed. Test Sets now know that.

• Define a prerequisite test case for any Test Set.
• Dependent test cases only run when the prerequisite passes.
• Automatic gating: Thunders gates execution based on the prerequisite result. No manual intervention.

Use this for login flows, environment health checks, or any setup step that must succeed before the rest of the suite makes sense to run.

#Sprint26

For teams already managing tests in Xray, Thunders now connects directly. No more parallel test estates.

• Import from Xray: pull an existing test case from Xray (manual or Cucumber) into Thunders, where Thunders Copilot converts it into executable test steps automatically.
• Create in Xray: from any test case in Thunders, ask Thunders Copilot to create a matching test case in Jira Xray with the full description and steps.

If you’re using Xray Cloud for test management today, you can now import those tests into Thunders, let the AI make them executable, and push new test cases back to Xray. All without rebuilding your test library from scratch.

#Sprint26

Record your test flows directly from the browser, and Thunders turns them into ready-to-run test steps. The Recorder is now generally available in Beta.

• Create from scratch or append: use the Recorder to build new test cases or add steps to an existing one.
• Clipboard support: copy and paste now works inside the live browser session.
• JS dialog support: alerts, confirms, and prompts are visible and interactable during recording.
• Iframe support: interact with iframes naturally, with reduced recording noise.

The Recorder watches what you do in the browser and converts it into executable Thunders steps. No manual step writing needed. It’s the fastest way to go from “I’ll show you the bug” to “here’s the test case.”

#Sprint26

Until now, understanding how testing was going across a project meant scrolling through runs by hand. The first version of the analytics dashboard is live.

• Project activity at a glance: see testing volume and trends without digging into individual runs.
• Test execution trends over time: track pass rates, failure rates, and run volume across days and weeks.
• Usage metrics: understand how testing is scaling across your team, who’s running what, and how often.

This is v1 of analytics. More dimensions and filters are coming, but you can already use it to answer “are we testing more?” and “are things getting better?”

#Sprint26

Sharing a failing run with a stakeholder used to mean screenshots, exports, or pulling them into a seat they didn’t need. Not anymore.

• Generate a shareable link from any test run.
• Send it to anyone, inside or outside your organization.
• Recipients view the full run in the browser (steps, screenshots, results). No Thunders account required.

A developer, a product manager, or a client can open the link and see exactly what happened. No login wall, no exports, no back-and-forth.

#Sprint26

When a Test Run stops unexpectedly due to a system failure, it no longer hangs in an ambiguous state.

• Runs interrupted by a system failure are now marked with a clear Interrupted status.
• No more stale runs sitting in your list with no explanation.

You’ll always know what happened: whether a run passed, failed, or was interrupted before it could finish.

#Sprint26

A few targeted improvements to how Thunders Copilot works day-to-day.

• Interrupt in-flight requests: cancel a Copilot generation at any time if you change your mind.
• Variable highlighting: variables in Copilot responses are now visually highlighted, so you can spot dynamic values instantly.
• Autocomplete for assets and variables: your Test Assets and Project-level variables now appear in autocomplete when you type [.

These changes make working with Copilot faster and reduce mistakes when referencing variables or test assets.

#Sprint26

You can now export any test run as a full PDF report: steps, screenshots, results, everything in one document you can share.

• Custom introduction: add your own summary text at the top of the report.
• Branding: upload your company logo and customize report colors.
• Language: choose between English and French for the report language.
• Section control: toggle which sections appear from your project settings.
• Ready to share: export the final PDF for stakeholders, compliance, or audits.

This is currently in Preview. The exported PDF includes every step with its screenshot and result, so anyone reading it gets the full picture without needing a Thunders account.

#Sprint26

Flows that include native browser popups (alerts, confirms, prompts) used to break silently. Not anymore.

• Alert, confirm, and prompt dialogs are now fully supported during test execution.
• Thunders detects and handles JS dialogs triggered from any step, automatically.

If your app uses window.alert(), confirm(), or prompt(), Thunders will interact with those dialogs as part of the test flow. No workaround needed.

#Sprint26