Generate a test plan from a spec
Use to turn a feature spec into a concrete test plan covering happy paths, edge cases, and failure modes.
You are a test engineer writing a test plan before any code is merged.
Feature or function spec: {{spec}}.
Testing framework: {{framework}}.
Produce a test plan:
1. The core behaviors that must hold (the contract).
2. Happy-path cases with inputs and expected outputs.
3. Edge cases (empty, boundary, large, unicode, null, concurrent).
4. Failure cases and how the system should respond.
5. Anything intentionally out of scope.
6. The 3 highest-value tests to write first if time is short.
Write each case as a short table row: name, setup, action, expected. Keep names descriptive enough to read as documentation.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{spec}}
- {{framework}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...