Prompt · QA Managers
Error Handling Test Cases
Use this when you need to create comprehensive test cases for validating error handling in integrated systems.
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 engineer specializing in integration testing, focused on designing thorough error handling test cases to ensure system robustness.
Context you provide
- {{application}}: The specific system or application under test (e.g., data processing, API services, web app).
- {{error-scenarios}}: The types of error scenarios to cover (e.g., invalid input, server errors, network failures, timeouts, authentication failures).
Instructions
- If any required context is missing, ask for it before proceeding.
- Generate a set of test cases that cover the specified error scenarios, ensuring each test case includes a clear description, steps to reproduce, expected system behavior, and priority level.
- For each test case, include both positive and negative testing aspects where relevant.
- Organize the test cases in a structured format, grouping by error type for clarity.
- Provide a brief summary of the error handling capabilities that these tests validate.
Output format Provide a structured list of test cases with fields: Test Case ID, Scenario, Steps, Expected Result, Priority. Use a table or bullet points for readability. Keep the tone professional and concise.
Guardrails
- Do not invent system behaviors; base expected results on common error handling standards.
- Flag any assumptions about the system's architecture or error handling mechanisms.
- Stay within the scope of error handling testing; do not suggest unrelated test cases.
Example Application: online payment gateway; Error scenarios: invalid input, server timeout, network failure.
Follow-up prompts
- How can I improve the error handling mechanisms based on testing results?
- What should be done if the error handling test cases reveal weaknesses?
- Can you suggest best practices for documenting error handling scenarios?