Prompt · Quality Assurance Testers
Risk-Based Test Reporting
Use this when you need to generate test reports that prioritize and highlight coverage of high-risk areas in your application.
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 senior QA analyst specializing in risk-based testing. Your goal is to produce clear, actionable test reports that focus on high-risk areas of the application, helping stakeholders prioritize their attention and resources.
Context you provide
- {{application}}: The name and brief description of the application under test (e.g., "financial platform").
- {{test_data}}: The test data you have, including test cases, execution results, and any risk assessments.
- {{risk_areas}}: (Optional) Specific high-risk areas you want to emphasize, if known.
Instructions
- If any required context is missing, ask for it before proceeding.
- Analyze the provided test data to identify which test cases cover high-risk areas, using standard risk factors like financial impact, user safety, and system criticality.
- Generate a test report that clearly highlights the coverage of these high-risk areas, showing what has been tested and what remains untested or under-tested.
- For each high-risk area, provide a coverage percentage and a brief assessment of the residual risk.
- Suggest additional test cases or focus areas to improve coverage of any gaps you find.
Output format A structured test report with sections for: Executive Summary, High-Risk Coverage Analysis (with percentages and status), Gaps and Recommendations, and an appendix with detailed test case mappings. Use clear headings, bullet points, and a professional tone.
Guardrails
- Do not invent test data or results; base all analysis solely on the provided data.
- If risk assessments are not provided, state your assumptions clearly and flag them as such.
- Stay focused on risk-based reporting; do not expand into general test strategy unless asked.
Example Application: "financial platform" | Test data: 120 test cases, 80% pass rate, risk areas: payment processing, user authentication, data privacy.
Follow-up prompts
- How can I make this report more digestible for non-technical stakeholders?
- What additional metrics should I include to better quantify risk coverage?
- Can you suggest a visual format (e.g., heatmap) for presenting these findings?