test-reporting

Original：🇨🇳 Chinese
Translated

Generate professional test reports, including executive summaries, metrics, defect analysis, and risk assessments. Support daily reports, weekly reports, release reports, etc. The default output is Markdown, and Excel/CSV/JSON/PDF formats are available upon request. Use for test reporting.

9installs
Sourcenaodeng/awesome-qa-skills
Added on

NPX Install

npx skill4agent add naodeng/awesome-qa-skills test-reporting

Tags

Translated version includes tags in frontmatter
test-reportingreport-templatesquality-metricsdefect-analysistest-documentation

SKILL.md Content (Chinese)

View Translation Comparison →

Test Report (Chinese Version)

English Version: See the skill 
test-reporting-en
.
Refer to 
prompts/test-reporting.md
in this directory for prompts.

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

This skill outputs Markdown by default. If other formats are required, please specify clearly at the end of your request.

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

markdown
# 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

Execution Metrics:
  • Total number of test cases
  • Number of executed cases
  • Pass rate
  • Failure rate
Quality Metrics:
  • Defect density
  • Defect escape rate
  • Fix time
  • Reopen rate
Efficiency Metrics:
  • Automation rate
  • Execution time
  • Productivity

Troubleshooting

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

Solution: Use a pyramid structure:
  1. Executive Summary (1 page)
  2. Key Metrics (1 page)
  3. Detailed Data (Appendix)

Issue 2: Inaccurate data

Solution:
  1. Use test management tools
  2. Automate data collection
  3. Regularly verify data
Related Skills: test-strategy, bug-reporting, test-case-writing.