Thunders News Center
Link an existing test case to its source
A test written directly in Thunders can now be linked to an existing item in a connected tool. You no longer need to have imported the test, or created the external item from Thunders, to establish that connection. This is useful when you already have a test library and want to connect it to the items your team tracks elsewhere.
- Open Source in the properties panel: for a test case with no source, click + or use the S shortcut to open the source picker.
- Paste a URL or item ID: Thunders looks for the item in your connected tools and shows the key, title and tool for each match. Choose the result to create the link.
- Use the existing result-sync workflow where supported: linking a corresponding Xray Test or Squash TM test makes a hand-written case eligible for the same result-sync workflow as an imported case.
A source link and result synchronization are different: linking an item from another connected tool does not mean that tool supports receiving test results. Thunders checks the item before creating the link; an unavailable connection is not saved as an unchecked match.
#Sprint35
Resume test fixes without repeating the whole run
Fixing a step should not always mean running every earlier step again. When Thunders AI runs and stabilizes a single web test in Chrome or Chromium, it can now continue in the browser left open by the failed attempt. After a compatible fix, execution resumes at the first changed step, while earlier successful steps keep their results.
- See where the next attempt begins: the run card identifies a resumed attempt and its starting step, or shows when the test has restarted from the beginning.
- Keep the successful part of the run: a resumed attempt runs the changed portion rather than repeating the steps that already passed.
- Restart when continuing would be unsafe: if the browser session is no longer available, or the fix changes, removes or reorders a previously successful step, Thunders AI falls back to a full restart. This is a single-test web workflow, not a resume option for every test run or mobile run.
Thunders AI also searches the content of Xray Cloud test steps, alongside titles and descriptions. A test can now be found when the topic you ask about appears in its steps rather than its name.
#Sprint35
Run mobile tests on emulators and iOS simulators
Mobile test execution now supports Android emulators and iOS simulators alongside physical devices. You can choose a virtual device for an automated run, using the redesigned device picker to find the model and operating-system version you need.
- Choose a device from the picker: tabs and filters separate virtual and physical devices, so you can select the device type that matches your test and build.
- Provide the right iOS build: an iOS simulator needs a .zip containing a simulator .app build. An .ipa is for a physical iPhone and cannot be used on a simulator.
- Review the execution evidence: virtual-device runs start with a fresh session and provide step screenshots, rather than a live interactive view.
This release supports automated execution on virtual devices, not recording or live interaction. Use a physical device when you need to record a mobile flow or work with a live device session. Device PIN entry and gallery uploads also remain physical-device workflows.
#Sprint35
Watch Thunders AI browse your app, live
You can now follow a Thunders AI web browse from inside the conversation. Instead of waiting for the browse to finish before seeing what happened, open the live browser to see which page it is on and how it is interacting with your app. This gives you context when a flow takes time or reaches an unexpected screen.
- Open Watch live: open it on the browse row to display the browser in the chat. The view is read-only: you can watch, but you cannot click or type in it.
- Hide the view without interrupting the browse: Thunders AI continues working when you close the live view.
- Browse sites protected by HTTP basic authentication: in Web Browse → advanced settings, enter a username and password for the conversation. These override the environment credentials and apply only to the first website opened, not to other sites reached later. Clear them to use the environment credentials again.
- Explore drag-and-drop and reload flows: Thunders AI can now perform these actions while browsing, including flows that move an item and then refresh the page to check the result.
#Sprint35
Open tests directly from Thunders AI answers
When Thunders AI finds a test, explains a failure or suggests work on an existing case, you can now open the test directly from its answer. Test cases, test sets and test plans appear as links in the conversation, so you can move from the discussion to the relevant test without searching the list by name.
- Preview before opening: hover over a test case to see its status, step count, owner and last run. You can check that it is the case you need without leaving the conversation.
- Open the relevant test: click a linked test case, test set or test plan to go to its detail page. Test case links also support opening in a new tab.
- Keep the same workflow across chats: links work on the Thunders AI page and in the chats attached to test cases, test sets, test plans and test runs, including when you reopen a saved conversation.
A test that has been deleted or is not available in the current project stays as plain text rather than linking to an unavailable page.
#Sprint35
Swipe, long press, pull to refresh and deep links
Mobile tests can now describe more of the interactions people use in an app. Swipes, long presses, pull-to-refresh gestures and deep links are supported as mobile actions, so a test can cover the flow beyond opening a screen and tapping a button.
- Add gestures in the step editor or write them as steps: use a swipe to move through content, a long press to open a contextual action, or pull to refresh to update a list.
- Open a flow through a deep link: include the link as a mobile step when the scenario starts from a specific destination inside the app.
- Ask Thunders AI to author these actions: the same gesture vocabulary is available when Thunders AI writes mobile test steps.
- Work with native selection controls: mobile runs can select options and dates in supported Android and iOS native pickers, including Android spinners and iOS picker wheels.
These additions concern mobile interactions; choose the action that matches the control in the app rather than describing a native picker as a web dropdown.
#Sprint35
Save a test set’s setup and reuse it on the next run
Test sets now keep their execution settings, so the next run can start from the setup you have already chosen. There is also a clearer distinction between launching a new run with the test set’s saved settings and repeating an existing run with the settings it actually used.
- Save the default setup on the test set: click Execute to open the run dialog with those saved settings, ready to review and launch.
- Repeat a specific run: re-execute uses the source run’s execution settings rather than asking you to rebuild its setup. A separate settings action remains available when you want to change the configuration.
- Manage several schedules together: select rows in the test set’s Schedules tab to run, pause, resume or delete them from the bulk action bar. Schedules paused by the system may require their underlying problem to be resolved before they can resume.
- Understand a completed run’s duration: open the duration breakdown to distinguish the first attempts, re-runs and time between tests. It helps explain why the overall duration differs from the time spent on an individual test.
#Sprint35
Create a test case from a test set
When you organize a test set, you sometimes find that a test case is missing. You can now create it from the test set you are working on, instead of leaving the set to create the case elsewhere and then adding it back.
- Open Manage Test Cases: in the test set, click Add to open the dialog where you choose the test cases of the set.
- Create the missing case: click New Test Case in that dialog. You stay in the context of the test set while you create it.
- Keep adding existing cases: the same dialog still lets you search your test cases and select the ones to include.
#Sprint34
Find and continue your Thunders AI conversations
Test authoring and investigation rarely finish in a single conversation. The Thunders AI session launcher gives you a clearer place to find earlier work, while improvements to history and saved replies make it easier to return to the context you need.
You can reopen an existing conversation rather than reconstruct the request and the decisions that led to it.
- Open Thunders AI sessions from the launcher in the sidebar, and return to the latest session associated with a test case, test set or test run.
- Search the session history, with matching words highlighted in conversation titles. The list loads ahead of opening and renders progressively, making long histories easier to navigate.
- Recover the completed reply from the saved conversation if your connection drops while the response is being delivered.
- Attach binary Excel files in the older .xls format directly in the chat, without first converting them to .xlsx.
#Sprint34
Clearer device choices and more control over mobile runs
A mobile run depends on both the device and the application's setup. Thunders now gives you clearer options when a device is unavailable, and lets you adjust WebView handling and Appium capabilities for an environment without relying on deployment-wide settings.
These changes help you match execution settings to the app you are testing, whether it is entirely native or includes embedded web content.
- When the selected device is unavailable, Thunders can propose another device instead of leaving you with an unexplained failure. You still choose how to proceed.
- Turn WebView handling on or off in the environment's run settings, and provide custom Appium capabilities for setups that need them.
- When no device pool exists, the device picker opens on the platform that matches the selected environment's APK or IPA, helping you choose an appropriate Android or iOS device.
- A failed mobile debug run can keep its device session open during the intervention window. The failure screenshot and countdown remain visible; skipping the intervention or letting the window expire releases the device.
#Sprint34