Thunders News Center

Copilot can now gather context from your issue tracker to generate tests.

It can fetch details directly from a linked Linear or Jira ticket, and browse a live URL to understand the page it's being asked to test.

Previously, Copilot only had the text you typed.

Now it works with real context, producing steps that are more accurate and aligned with what's actually on the page or in the ticket.

❗ Generated test cases may still require manual review and adjustments.

You can now generate a PDF report from one or more selected test runs, formatted as a formal, shareable document for stakeholders and clients.

Select the runs you want to include, customize it by adding your logo then generate the report, and share it externally without any additional formatting work.

❗ Available on the client’s demand, talk to your CSM to activate it.

💡 Read the full article for more details about Test Run Report

You can now upload a CSV file and run the same test case once per row, with variable values set dynamically from each row.

Each test run shows which data row was used.

The CSV can include variables used in the test (such as username, email, or product ID) as well as execution settings, such as browser and environment.

Upload the CSV under Test Assets, then reference it by name in your CI pipeline OR upload it directly to Thunder before executing your test case.

💡 How to batch execute variations of your Test Case

Type / or [ in any step to trigger an auto-complete menu for variables.

The menu searches across project, environment, and step variables, and shows you the resolved value inline.

You can also create a new variable directly from the menu without leaving the step editor.

-> No more switching screens to look up or reuse a variable.

💡 Read the full article for more details about Variables and Variables Inline Editor

You can now trigger automated test runs directly from your CI pipeline and retrieve structured results in a single API call.

Supports both individual test cases and test sets.

Results include step-level detail and execution progress, no more summary-only output that's hard to parse in a CI report.

💡 Read the full article for more details on CI/CD

You can now compare two test runs side by side. The diff view shows differences across screenshots, logs, HTML, and run settings.

For screenshots, a diff overlay highlights the areas that changed between the two runs.

For logs, you can filter out timestamps to focus on meaningful differences like network calls.

Run settings are also displayed side by side, so you can spot configuration differences such as run location.

This feature is currently accessible via URL by placing both test run IDs in the path.

A more accessible entry point in the UI is coming soon ⌛

You can now upload a CSV file and run the same test case once per row, with variable values set dynamically from each row.

Each test run shows which data row was used.

The CSV can include variables used in the test case (such as first name, last name, or email) as well as execution settings like browser and environment.

Upload the CSV under Test Assets, then reference it by name in your CI pipeline.

❗This feature is currently available via CI only. UI support is coming soon.

💡 Read the full article for more details on How to batch execute variations of your Test Case

You can now set variables and credentials at the project level.

These apply across all environments and test cases within the project.

→ Variables follow a clear priority: Project, then Environment, then Test.

A variable defined at the project level is used by default. If the same variable is defined at the environment level, it overrides the project value for that specific environment.

💡This avoids duplicating the same variables across every environment. You define them once at the project level and only override where needed.

ClickUp is now available as an integration.

Once connected, bug reports from failing test runs can be sent directly to ClickUp as tasks, including repro steps and screenshots.

Setup can be done from the Knowledge base page.

Select your workspace, save the configuration, and you can start creating tickets from the bug report icon 🪲 in any failing test run.

Test case execution settings can now be saved per test case.

When you open a test case, settings are automatically loaded from the current project.

If you modify settings, you can either revert to the defaults or save them as the team's default for that test case.