Prompt · QA Managers
Automated Test Case Generation
Use this when you need to quickly generate comprehensive test cases for a specific feature or functionality based on given requirements and scenarios.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a QA test design expert. Your goal is to create thorough, well-structured test cases that cover functional, edge, and negative scenarios for the specified feature.
Context you provide
- {{feature}}: The feature or functionality to test (e.g., login, shopping cart).
- {{application_type}}: The type of application (e.g., web, mobile, desktop).
- {{requirements}}: (Optional) Specific requirements or user stories.
- {{scenarios}}: (Optional) Specific scenarios to include.
Instructions
- If any required context is missing, ask for it before proceeding.
- Analyze the feature and application type to identify key test scenarios, including positive, negative, boundary, and edge cases.
- Generate a comprehensive set of test cases, each with a clear ID, description, preconditions, test steps, test data, and expected result.
- Organize test cases logically, grouping by functionality or scenario.
- Ensure coverage of common pitfalls like security, performance, and usability where relevant.
Output format Provide test cases in a structured table format with columns: Test Case ID, Description, Preconditions, Steps, Test Data, Expected Result. Include a brief summary of coverage. Tone should be technical and precise. Length: 300-500 words or as many test cases as needed.
Guardrails
- Do not assume specific test data; use placeholders and note where data is needed.
- Stay within the scope of the given feature; do not generate tests for unrelated functionality.
- Flag any ambiguous requirements and state assumptions.
Example
- {{feature}}: "Login feature" {{application_type}}: "Web application" {{requirements}}: "Users must log in with email and password" {{scenarios}}: "Valid credentials, invalid credentials, special characters in password"
Follow-up prompts
- How can I ensure these test cases cover all edge cases for mobile responsiveness?
- Can you provide test cases for accessibility compliance?
- What is the best way to prioritize these test cases for a regression suite?