Prompts that work, grouped by the job you are trying to do. Copy one, swap in your own names, and go.
Tip. Start every session by naming the project. "In the Checkout project..." saves the assistant from searching across everything you own, and makes its answers much faster.
Find your way around
List all my Thunders projects
What environments and personas are available for the Checkout project?
Show me every test case in the Checkout project, most recently updated first
Which test cases are labelled smoke?
Author new tests
Create a test case called "Login validation" in the Checkout project, then generate steps for: log in with valid credentials, check the error message on a wrong password, and verify the password reset email
Read this Jira ticket and turn its acceptance criteria into a Thunders test case in the Checkout project
Here is our checkout flow spec. Create one test case per scenario it describes, and label them all checkout-v2
Add a teardown step to "Login validation" that signs the user out
Migrate existing automated tests
Convert this Playwright spec into a Thunders test case in the Checkout project
Go through the e2e/ folder, convert every Cypress test into a Thunders test case, and label them migrated
Reuse what you already have
Clone "Checkout happy path" and change the payment step to use PayPal
Duplicate the Staging environment, call it Preview, and point every app at the appdev1 URL instead of app
Add the API_BASE_URL and TEST_USER_PASSWORD variables to the Preview environment. Mark the password as a secret.
Organise test cases into test sets
What test sets exist in the Checkout project?
Create a test set called "Smoke" in the Checkout project and add every test case labelled smoke to it
Add "Login validation" to the Regression test set
Take "Checkout with PayPal" out of the Smoke set, but keep the test case
Work with test data files
What test assets are available in the Checkout project?
Upload this CSV as a test asset in the Checkout project and tell me the file variable to reference it by
Add a step to "Bulk import" that uploads the customers CSV asset
Clean up
Delete the three draft test cases I created yesterday in the Checkout project
Delete every test case labelled obsolete in the Checkout project, and tell me which ones were skipped because they are reused elsewhere
Tighten up steps before running
Check "Login validation" for step-quality suggestions and tell me which ones are worth applying
Apply every suggestion on "Login validation" that fixes an actual error, and dismiss the rest
Run tests
Run all smoke test cases in the Checkout project on the Staging environment with the QA Engineer persona
Run the checkout suite sequentially and stop the chain if one fails
Run "Login validation" three times on Staging so I can see if it is flaky
Diagnose failures
Show me every failed run in the Checkout project from the last 7 days
Pull the full context for the most recent failed run and tell me what broke
Investigate why this run failed, then rewrite the step that caused it
Compare the last five runs of "Login validation". Is it failing consistently or intermittently?
Report
Give me a fail-rate analysis of my test executions over the last 7 days, broken down by test case
Which test cases in the Checkout project have never been run?
Summarise last night's runs as a short update I can paste into Slack
Go deeper
Full walkthroughs of these workflows on the Thunders blog: