Prerequisites:
Created Test Project
Created Test Case
Creating Your First Test Case Scenario
You can create Test Case Steps by describing your Test Scenario to Thunders AI. The Thunders AI will analyze your description and automatically generate a sequence of Steps.
This guide walks you through creating and refining Test Cases through natural-language interaction, and through direct editing.
Editing Test Case Steps
There are two ways to edit your Test Cases: through Thunders AI, where you describe your changes in natural language, or using the Steps Editor for direct, precise modifications.
Edit Test Steps via Thunders AI
Access the Test Case: Open your Project and select the Test Case you want to edit.
Open Thunders AI: Find the Thunders AI panel on the right side of the Test Runner screen. If it's collapsed, expand it; you can also resize it by dragging its edge.
Describe your Changes: In the Text Field at the bottom of the Chat Panel, type your instructions for modifying the Test Steps. For example: • "Update Step 3 to update the Email with [email protected]" • "Add a Verification Step after the first Step"
(Optional) Add context: Attach a file, or select an MCP server from the input toolbar to give Thunders AI extra context for the change.
Submit your Request: Click the up-arrow button (tooltip: "Update") to send your request.
Review and Apply: Thunders processes your instructions and proposes updated steps. Proposed changes surface as a suggestion popover on the affected step(s) — click "Apply this update" to accept, or "Ignore" to discard.
Switch between versions: Thunders AI keeps a history of the versions it generates. Use the version cards in the Thunders AI timeline to compare and switch back to an earlier version.
Edit Test Steps with the Steps Editor
The Steps Editor gives you direct control for precise modifications.
Locate the Step: Find the step you want to modify in the Test Steps list on the left.
Open the Edit interface: Hover over the step to reveal the Edit button (pencil icon) and click it.
Modify the Step: In the "Edit step" modal, update the step. Depending on the step's type (see below), the modal shows the relevant fields.
Save your Changes: Click "Save" to confirm.
Step types
When adding or editing a step, you can choose a step type, and the editor adapts its fields accordingly:
AI Step — natural-language action executed by the agent
API Call — HTTP request, with environment-specific parameters and a response variable
Web Step — platform action
Visual Compare / File Compare
Conditional Step — define a condition and the target step/action to run
Mechanical Assertion / Extraction
Existing Test Case — reference another Test Case as a step
Add a new step
Choose where to add the Step:
Between existing steps: hover between two steps to reveal the "+" button and click it.
At the end: click "Add a new step…" at the bottom of the Steps list.
Choose a step type and enter details: Pick the step type and fill in the fields in the "Add new step" modal.
Confirm: Click "Add" to insert the step at the chosen position.
Move a Step
Enter Editor mode: Make sure a Test Execution isn't currently running.
Drag and drop: Grab the drag handle (six-dot icon) that appears on hover and drag the step to its new position.
Release to place: The step is relocated and the change saved automatically.
💡 Note: dragging is disabled while steps are locked (e.g. during execution).
Delete a Step
Locate the Step: Find the step you want to remove.
Open delete controls: Hover over the step to reveal the Delete button (trash icon) and click it.
Confirm: In the "Delete this step?" dialog ("This action cannot be undone."), click "Delete".
More step actions
Beyond editing, each step exposes additional actions on hover or right-click:
Skip / Enable step — temporarily exclude a step from execution, then re-enable it.
"Why did this step fail?" — on a failed step, this CTA opens Thunders AI with the failed step already loaded as context, so you can investigate and fix it.
Auto-Heal — for Discovery-type steps, regenerate/heal the step (with a confirmation if it has sub-steps).
Open original Test Case — for steps that reference another Test Case, jump to the source.
