AGENT SKILL

generating-test-reports

Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".

License 许可
MIT
最近更新
2026-05-26
Stars
★ 0
Forks
0

01 前言 Front Matter

name
generating-test-reports
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
version
1.0.0
description
Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".
allowed-tools
Read, Write, Edit, Grep, Glob, Bash(test:report-*)
compatible-with
claude-code, codex, openclaw

02 资源文件 8

03 SKILL.md 正文

Test Report Generator

Overview

Generate structured, human-readable test reports from raw test runner output including JUnit XML, Jest JSON, pytest results, and coverage data. Produces Markdown summaries, HTML dashboards, and CI-compatible annotations.

Prerequisites

  • Test results in a parseable format (JUnit XML, Jest --json, pytest --junitxml, or TAP)
  • Coverage data files (Istanbul coverage-summary.json, lcov.info, or coverage.xml)
  • Node.js or Python available for report generation scripts
  • Git history accessible for trend analysis across commits

Instructions

  1. Locate all test result files using Glob patterns (**/junit.xml, **/test-results.json, **/coverage/lcov.info).
  2. Parse each result file and extract:
    • Total test count, passed, failed, skipped, and error counts.
    • Execution duration per test suite and per individual test.
    • Failure messages, stack traces, and assertion details.
  3. Parse coverage data and extract:
    • Line, branch, function, and statement coverage percentages.
    • Per-file coverage breakdown identifying files below threshold.
    • Uncovered line ranges for targeted improvement.
  4. Compute aggregate metrics:
    • Overall pass rate as a percentage.
    • Total execution time and average test duration.
    • Top 10 slowest tests with file paths and durations.
    • Coverage delta compared to the previous commit (if git history is available).
  5. Generate a Markdown report with sections for summary, failures, coverage, and performance.
  6. Optionally generate an HTML report with sortable tables and coverage heatmaps.
  7. Write CI-compatible output (GitHub Actions job summary, GitLab report artifacts, or Slack webhook payload).

Output

  • test-report.md -- Markdown summary with pass/fail table, coverage stats, and failure details
  • test-report.html -- Self-contained HTML report (optional)
  • Coverage summary table with per-file breakdown and delta from baseline
  • Slowest tests list ranked by execution time
  • CI annotation comments on failed test lines (GitHub Actions ::error format)

Error Handling

Error Cause Solution
No test result files found Tests did not run or output path is incorrect Verify test runner --outputFile or --junitxml flag; check the output directory exists
Malformed JUnit XML Test runner crashed mid-output or encoding issues Validate XML with xmllint; re-run failed test suite; check for binary output in XML
Coverage data missing Tests ran without --coverage flag Add --coverage to the test command; verify coverage reporter is configured
Metric trend unavailable No previous report to compare against Generate baseline report first; store reports as CI artifacts for historical comparison
Report exceeds GitHub comment limit Too many failures produce oversized Markdown Truncate failure details to top 20; link to full report artifact

Examples

Markdown report structure:

## Test Results -- 2026-03-10

| Metric | Value |
|--------|-------|
| Total Tests | 847 |  # 847 = configured value
| Passed | 839 (99.1%) |  # 839 = configured value
| Failed | 5 |
| Skipped | 3 |
| Duration | 42.3s |

### Coverage
| Category | Current | Threshold | Status |
|----------|---------|-----------|--------|
| Lines | 87.2% | 80% | PASS |
| Branches | 74.1% | 70% | PASS |
| Functions | 91.5% | 85% | PASS |

### Failed Tests
1. `src/utils/parser.test.ts` -- "handles malformed input" -- Expected Error but received null
2. `src/api/auth.test.ts` -- "rejects expired tokens" -- Timeout after 5000ms

GitHub Actions job summary integration:

cat test-report.md >> "$GITHUB_STEP_SUMMARY"

Resources

04 同仓库更多 Skills

SamuelChien
SamuelChien/mega-skills-collection

zustand-store-ts

Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.

★ 0
SamuelChien
SamuelChien/mega-skills-collection

zustand-store-creator

Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.

★ 0
SamuelChien
SamuelChien/mega-skills-collection

zero-trust-config-helper

Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.

★ 0
SamuelChien
SamuelChien/mega-skills-collection

zapier-integration-helper

Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.

★ 0
SamuelChien
SamuelChien/mega-skills-collection

zai-cli

Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.

★ 0
SamuelChien
SamuelChien/mega-skills-collection

yt-research

Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.

★ 0