Test Report (Chinese Version)

test-reporting-en

prompts/test-reporting.md

When to Use

• When the user mentions "test report", "test reporting", or "test summary"
• When a test report or test summary needs to be generated
• Trigger Examples: "Generate test report", "Write Sprint test summary"

Output Format Options

Reference Files

• prompts/test-reporting.md — Test report prompts
• output-formats.md — Format descriptions

Code Examples

1. Test Report Templates - Various test report templates

Common Pitfalls

• ❌ Data only without analysis → ✅ Provide insights and recommendations
• ❌ Overly lengthy reports → ✅ Highlight key points and present content in layers
• ❌ Lack of visualization → ✅ Use charts to show trends
• ❌ No action items → ✅ Clarify follow-up actions

Best Practices

1. Report Structure

# Test Report

## 1. Executive Summary
- Test overview
- Key findings
- Quality assessment
- Recommendations

## 2. Test Execution
- Execution statistics
- Coverage
- Pass rate

## 3. Defect Analysis
- Defect statistics
- Severity distribution
- Trend analysis

## 4. Risks and Issues
- Current risks
- Blocking issues
- Mitigation measures

## 5. Follow-up Plan
- Pending work
- Improvement suggestions
- Action items

2. Key Metrics

• Total number of test cases
• Number of executed cases
• Pass rate
• Failure rate

• Defect density
• Defect escape rate
• Fix time
• Reopen rate

• Automation rate
• Execution time
• Productivity

Troubleshooting

Issue 1: Reports are too long and no one reads them

1. Executive Summary (1 page)
2. Key Metrics (1 page)
3. Detailed Data (Appendix)

Issue 2: Inaccurate data

1. Use test management tools
2. Automate data collection
3. Regularly verify data