Overview
Thunders lets you generate a complete Test Plan from a short description, document, or connected knowledge source. You can also reuse the Variables already defined in your Project or Environment so generated scenarios and test cases stay consistent with the rest of your test suite.
What is a Test Plan
A Test Plan is a structured document generated by Thunders from your requirements. It contains:
Test Sections: logical groupings of scenarios (for example: "Authentication", "Checkout")
Scenarios: suggested end-to-end flows under each section
Generated Test Cases: concrete test cases, with a name, description and draft steps, produced from each scenario
Once the Test Plan is generated, you can review it, edit scenario titles, regenerate or associate test cases, and promote generated test cases into your Test Project.
How to Create a Test Plan
1. Open the Thunders Copilot
From the left navigation, open Thunders Copilot, or click Create on the Test Plans list page. The Thunders Copilot page opens with the input focused and the generation type pre-selected.
2. Choose your input
You can describe the feature in three ways: and you can combine them:
Type a description in the input area. Example placeholder text: "Describe the feature or paste a User Story, PRD…"
Attach a file by clicking the paperclip icon or dragging it onto the input area. Supported formats:
.pdf,.docx,.md. Only one file can be attached at a time.Connect a Knowledge Source (MCP Server) such as Jira or Linear from the Sources menu so the AI can pull real context from your issues and pages. See Jira & Linear integration for setup.
3. Reuse Variables in your description
While typing the description, you can insert any Variable that already exists in your Project or in one of its Environments. This is powered by the Inline Variable Editor, which is available in the Copilot Test Plan input.
To insert a Variable:
Type
/(slash) to open the suggestion menuType
[(open bracket) as an alternative triggerClick the Variable button (brackets icon) in the input toolbar
The menu lists all Variables available in the Project, organized by scope:
Scope | Description |
Project | Static Variables defined in Project Settings |
Environment | Static Variables defined per Environment |
App URL | Auto-generated from the URL of each active App in the Project |
Selected Variables are inserted as [VARIABLE_NAME] tokens in the description. If a Variable you need does not exist yet, use Create Variable directly from the suggestion menu without leaving the Copilot page.
📝 Note: When creating a Variable inline, the name must use only uppercase letters, numbers and underscores (_), up to 30 characters.
See Inline Variable Editor for the full list of triggers and options.
4. Generate the Test Plan
Make sure the Test Plan toggle is selected in the input footer, then press the submit button (or press Enter if only text is entered).
Thunders will:
Extract text and images from your file (if one was attached)
Consolidate content from your description, file and connected Sources
Generate a title and a structured list of Test Sections and Scenarios in parallel
Translate the output to your Project language if it is not English
Consume credits from your subscription (one Test Plan creation per call)
When the generation is complete, you are redirected to the Test Plan page:
The requirements you typed, the file path you uploaded, and the Variable placeholders you inserted are all preserved on the generated Test Plan and are visible in the Test Plan editor.
How Variables Are Reused After Generation
Variables inserted in the Copilot description are carried forward into the generated Test Plan and its children:
Test Plan requirements: your original description is saved on the Test Plan and can be viewed from the Test Plan header
Scenario titles: displayed in the Test Plan editor with inline
[VARIABLE_NAME]highlightingGenerated Test Cases: name, description and draft steps can contain
[VARIABLE_NAME]placeholders, highlighted in the editor so you can spot them at a glancePromoted Test Cases: when a generated Test Case is turned into a real Test Case in your Project, the placeholders are preserved and resolved at execution time using the same rules as any other Variable or Credential
Editing, Listing and Deleting Test Plans
Once a Test Plan exists, you can:
View it: open Test Plans from the Project sidebar and click the row
Export the list to CSV: available on the Test Plans list page once you have at least one plan
Bulk delete: select multiple rows and confirm
Delete a single plan: from the row action menu
