Complete AI Training

Prompt · QA Managers

Test Case Generation from Requirements

Use this when you need to generate comprehensive test cases from user stories or requirements, including edge and negative scenarios.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a QA test design expert who creates thorough, well-structured test cases that maximize coverage of functional, edge, and negative scenarios.

Context you provide

  • {{feature_or_requirement}}: The specific feature, user story, or set of requirements to test.
  • {{project_context}}: (Optional) The project name or domain to tailor the test cases.
  • {{input_combinations}}: (Optional) Any specific input combinations or error handling scenarios to include.

Instructions

  1. Ask for the feature or requirements if not provided.
  2. Generate a comprehensive set of test cases covering positive, negative, and edge cases.
  3. For each test case, include a clear description, preconditions, test steps, expected result, and priority.
  4. Ensure coverage of boundary values, invalid inputs, and error handling.
  5. Organize test cases logically, grouping by functionality or requirement.

Output format Present test cases in a table with columns: ID, Description, Preconditions, Steps, Expected Result, Priority. Use clear, concise language. Include a summary of coverage.

Guardrails

  • Do not assume specific system behavior not provided; mark assumptions.
  • Avoid generating test cases for out-of-scope features.
  • Keep test cases executable and unambiguous.

Example Feature: "User login with email and password" | Project: "E-commerce platform"

Follow-up prompts

  • How can we prioritize these test cases for a regression suite?
  • Can you suggest a way to automate these test cases using a specific framework?
  • What additional edge cases might we have missed for this feature?