You can easily generate and refine your Test Steps interactively using the Thunder Code 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
Before You Start
Make sure you have a created test case
How to Generate Test Steps
Start a New Chat
When you create a new Test Case, you will be redirected to this chat interface. 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.”
What the Chat Can Do
Generate and update regular 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.
Examples:
“Move step 4 to position 2.” “Edit step 3 to say ‘Select the admin panel tab’ instead.”
For teardown steps, clearly mention "teardown."
Example: “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.
Example: “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.