You can easily generate and refine your test steps interactively using the Thunders chat interface.
What You'll Learn
How to generate Test Steps from a scenario description
How to refine, update, or summarize generated steps
How to add API Calls and Teardown Steps
Best practices for giving clear step requests in chat
How to Generate Test Steps
Start a New Chat with Thunders AI
When you create a new Test Case, you will be redirected to Thunders AI. It will prompt you to describe your scenario.
Describe Your Scenario
Type a detailed description of what you want to test. Example:
"Log in as a user, navigate to dashboard, verify the projects are listed, and log out as teardown."
Once your test scenario is generated, you will be redirected to the Test Steps view.
Refine Your Test Steps
You can:
Ask follow-up questions (“Can you make step 2 more specific?”)
Request summaries (“Summarize the test case for me”)
Ask for variations (“Show a version without the logout step”)
Request improvements (“Combine steps 1 and 2”)
For each request you make, a chat bubble will be added. You can navigate between the different versions by hovering on one of the older versions and clicking on “Use these test steps” to compare the results.
Add Special Steps
Teardown Step: Explicitly mention this for cleanup, logout, or environment reset at the end.
“Add a teardown step to logout the user.”
API Call Steps: Provide the request type, URL, authentication, and body or parameters.
“Add a POST Request to https://example.com with a bearer token XX and a body containing id and name.”
Choosing what Thunders AI can read
Under the chat input, Connectors lists the sources Thunders AI may use for this conversation. Open it and switch on what the request needs. Only the sources you switch on are used.
Web Browse sits at the top of the list and is always there: it needs no setup, and it lets Thunders AI open a URL you give it and read the live page, so the steps it writes quote the field labels and buttons that are actually on screen. Switch it on before a prompt that names a URL.
Enabling Web Browse allows Thunders AI to interact with the target page. This may change page state, trigger form submissions, or navigate away. Use with caution on production environments.
Everything else in the list is a tool you connect once from the Connectors page, such as an issue tracker or a documentation space. Once connected, it can be switched on per conversation in the same way.
Editing several steps at once
A request does not have to name one step. Describe the range and Thunders AI applies the change across it, then shows you the result as a new version you can compare against the previous one.
“Delete everything after step 8.”
“Delete steps 3 to 6.”
“Make every assertion check the success banner instead of the page title.”
Name the boundary steps by number, as they are numbered in the steps list. A range that starts or ends on a step you cannot see in the list is the usual reason a bulk request removes more or less than you meant, so check the resulting version before you keep it.
Deleting Chat Messages
Why Delete Chat Messages?
Sometimes you may want to clean up your chat history for the following reasons:
To remove irrelevant or outdated messages that are no longer needed
To keep your chat interface clean and focused on your current testing needs
To delete any sensitive data that’s been sent previously
How to Delete Messages
Click on the trash icon that appears next to the message.
Click the trash icon to delete that specific message.
A confirmation modal will appear, click "Delete" to proceed with the changes.
The message will be removed from your chat history, helping you maintain a cleaner workspace. Note that deleting messages doesn't affect any test steps you've already added to your test case.
What the Chat Can Do
Generate and update test steps
Add teardown or API steps (if you specify)
Maintain full chat history so you can reference earlier decisions or clarify requests
Answer your questions about creating, improving, or suggesting test steps or scenarios
Limitations
Cannot create or heal Discovery steps
Will not add teardown steps unless explicitly told
For best results, always be clear and specific about which step to edit, move, or delete (referencing step numbers or positions)
Tips for Effective Step Generation
Clearly state where to add, edit, or delete steps.
“Move step 4 to position 2.”
“Edit step 3 to say ‘Select the admin panel tab’ instead.”For teardown steps, clearly mention "teardown."
“Add a teardown step to logout”
Be Specific: The more details you provide in your scenario or follow-up, the better your steps will fit your needs.
“After step 2, add a step to verify the user profile modal is opened.”
Request Variations: If the first version isn’t right, ask for changes. The assistant uses your feedback to improve.