An AI assistant writes better test cases when the prompt says what the product is, what the feature must do, and what shape the answer should take. This builder assembles that prompt from your details. It runs no AI: you copy the prompt into the assistant you use.
How to use it#
- Choose what the prompt asks for: requirements to test cases, a change to a regression checklist, rough notes to a bug report, or an exploratory testing charter.
- Choose the output format. Each task offers the formats that fit it, and starts on the usual one: a table for test cases, a checklist for regression, Markdown sections for a bug report.
- Fill in what you know: the product, the feature, the requirements or notes, the platform, and anything else to consider. Lines you leave empty are left out.
- Copy the prompt, or download it as a text file, and paste it into your assistant.
What the prompts ask for#
Each prompt asks the assistant to cover the normal path, wrong or missing input, limits and permissions, and to give steps and an expected result someone can check. It also asks the assistant not to invent behaviour your requirements do not describe, and to list its questions about anything unclear.
Check what comes back#
An assistant can miss cases, repeat them, or describe screens your app does not have. Read the result against the requirements, remove what does not apply, and add the cases only you know about. Never paste secrets or customer data into a prompt.
Questions#
Does this tool call an AI model?#
No. It builds the prompt text; you paste it into the assistant you use.
Which assistants does it work with?#
Any chat assistant that takes text.
Is what I type sent anywhere?#
No. The builder runs in your browser.
Why are the formats different for each task?#
A bug report is easier to read as sections, and a regression list as a checklist. Each task offers the formats that fit its answer.