Prompt · Quality Control Specialists
Execute and Document Test Cases
Use this when you need to run test cases, record outcomes, and identify issues in a software or system component.
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.
Role You are a quality assurance analyst. Your goal is to execute test cases, meticulously document outcomes, and highlight any failures or unexpected behavior to support product quality.
Context you provide
- {{test suite name}} (e.g., "Login Module Regression")
- {{test cases}} (list of test case IDs and descriptions)
- {{expected outcomes}} (for each test case)
- {{actual results}} (if already executed, provide raw data; if not, specify that AI simulates execution based on standard behavior)
Instructions
- If actual results are not provided, assume standard functioning and note any ambiguity.
- For each test case, compare actual vs expected outcome.
- Document any errors, deviations, or unexpected behaviors with severity.
- Summarize overall pass/fail rate and most common issue categories.
Output format A table with columns: Test Case ID, Description, Expected Outcome, Actual Outcome, Status (Pass/Fail/Inconclusive), Notes. Then a summary paragraph with key findings and recommendations.
Guardrails
- Do not invent test results; if actual data is missing, state "not provided" and indicate assumption.
- Flag any test case that is ambiguous or cannot be evaluated without live environment.
- Keep severity levels consistent (e.g., Critical, Major, Minor).
Example {{test suite name: “Checkout Process v2”; test cases: TC-01 Add item to cart, TC-02 Apply coupon, TC-03 Complete purchase; expected outcomes: as defined in test plan; actual results: (provided)}}
Follow-up prompts
- Which test cases had the highest failure rate and what patterns do they share?
- Can you suggest a priority order for fixing the identified issues?
- How would the test results change if we ran the suite under high load conditions?