Thunders News Center

When Thunders AI needs more detail to write a test, browse your app or file a bug, it asks a short question and suggests the likely answers, so one click keeps the work moving.

• Pick a suggested answer instead of typing one.
• Turn on Web Browse or Mobile App Browse, or connect a tool like Jira, Xray or Linear, in the same answer when a request needs it.
• Turn on more than one capability with a single answer.

You stay in the conversation the whole time, with no detour through settings.

#Sprint32

Many teams keep their test cases in spreadsheets. Thunders AI now reads Excel files, so you can start from the file you already have.

• Attach an XLSX file to a Thunders AI conversation, the same way you attach a CSV.
• Ask Thunders AI to create test cases from it, several at once.

#Sprint32

Thunders AI is now aware of each of your environments: its variables, its credentials and its execution settings. Pick an environment and the apps to test for your next message, or keep All environments, and every tool works from that choice.

• See the variables of every environment in Thunders AI, next to your project variables and test assets, and insert the one you need.
• Let Thunders AI sign in with the credentials of the environment you picked. It never mixes values from two environments, and it asks which one to use when none is picked.
• Open protected environments with Web Browse and Mobile App Browse. Each browse tool now runs with the environment's execution settings, including its location and recorded profile.
• Change a browse setting, like the browser or the device, for one conversation, without touching the environment itself.

#Sprint32

Admins decide which projects each person can reach.

• Give a new user access to specific projects when you invite them.
• Change any user's project access later from the user modal.
• Assign the Read-only role to people who need to see a project without changing it.

#Sprint32

Most apps you test start with a login. Capture the session once, then inject it into any test that needs it, instead of repeating the login steps.

• Add a capture profile step to sign in once, by hand or through a recorded flow, and save the session.
• Add an inject profile step at the start of any test case to load that saved session before the first real step runs.
• Every captured and injected session is verified and locked, so a stale or already-replaced session fails right at the inject step.

#Sprint32

When a UI change breaks a selector, Thunders fixes it during the run, so the test passes instead of failing on something that is not a bug in your app. Each of these fixes is now shown to you.

• See each self-healed step in the run report, and what Thunders changed to keep it passing.
• See how many steps self-healed in the run summary.
• Track your failures avoided score and its trend in Analytics.

#Sprint32

Everything your team already does in Thunders on web now works on native iOS and Android, out of private beta and ready for production. Thunders AI writes the test, a real device runs it, and self-healing keeps it working as your app changes.

• Let Thunders AI explore your app with Mobile App Browse, or record gestures directly on a live device.
• Combine API and mobile steps in one test: fetch data from an API, then verify it in your app.
• Start a run in about two seconds on a warm device, instead of waiting for a phone to boot (Enterprise).
• Run on thousands of real iOS and Android devices, kept in the US or the EU if you need data residency.
• Pay per step, not per device slot: 0.05 credits per mobile step, parallel runs included, from the Pro plan.

#Sprint32

Getting your results into Xray used to mean a manual sync, every single run, and if you were on Xray Data Center, only Cloud was even supported.

• Turn on auto-sync per project and every mapped test case pushes its result to Xray the moment a run finishes.
• Xray Data Center gets the same sync Cloud already had: per-step statuses, screenshots, and timestamps included.
• Manual sync still works, whenever you want a one-off re-sync.

Your Jira dashboard stays current without anyone remembering to click sync.

#Sprint31

Add variables to a Web Step's Value field without typing their names manually.

• Type / or select the brackets button to find and insert a variable.
• Use the same variable picker available throughout Thunders.

Build variable-driven steps faster and with less guesswork.

#Sprint31

A screenshot, PDF export, or extracted file used to land with an auto-generated name, and getting it into your project's Test Assets meant uploading it by hand after the run.

• Give the step its own file name, for Screenshot, PDF Export, and Extract File steps, instead of an auto-generated one.
• Turn on Add to Test Assets and the capture publishes straight to your project's assets, overwriting the same-named file on each run.
• Leave both off and everything works exactly as it did before.

A recurring screenshot or export can now land in the same place every time, with nobody uploading it by hand.

#Sprint31