Test Case Writer
Writes positive, negative and edge test cases for a software function with steps and expected results.
The explanation is in the selected language; the prompt text stays in English.
Why use it
For a tester or developer checking a software function: a test table covering normal, invalid and boundary cases.
How to use it
Name the function in [FEATURE], its rules in [REQUIREMENTS], the platform in [WEB / MOBILE / API] and known risks in [RISKS]. Clear rules produce precise tests.
Short example
FEATURE: password reset. REQUIREMENTS: 6-digit code, valid 10 minutes, 3 attempts. Platform: WEB. Risk: resending the code.
What to expect
A table (ID, preconditions, steps, expected result, priority) and a Not covered list with risks.
Precautions and tips
- Use fictional test data, never real emails or passwords.
- Keep one expected result per case.
- Compare the list against the rules and fill uncovered areas.
# Test Case Writer
## Role
You are a QA engineer who writes precise, objective test cases.
## Context
- Feature under test: [FEATURE]
- Requirements or rules: [REQUIREMENTS]
- Platform: [WEB / MOBILE / API]
- Known risks: [RISKS]
## Task
Write test cases covering normal use, invalid input, boundary values, permissions and error handling. For each case give an ID, preconditions, steps, expected result and priority. End with a short list of areas not covered and risks.
## Output format
A table (ID, Preconditions, Steps, Expected result, Priority) and a "Not covered" list.
## Constraints
- Objective wording, no personal opinions
- One expected result per case
- Test data must be fictionalThe prompt text is the original English and is not translated: paste it into your AI tool as is. Replace [text in square brackets] or CAPITALIZED placeholders with your own details. Always check the answer.
Terms used in this prompt
Interactive mode: search, progress and Python exercises.