This skill generates comprehensive test reports with coverage metrics, trends, and stakeholder-friendly formats (HTML, PDF, JSON). It aggregates test results from various frameworks, calculates key metrics (coverage, pass rate, duration), and performs trend analysis. Use this skill when the user requests a test report, coverage analysis, failure analysis, or historical comparisons of test runs. Trigger terms include "test report", "coverage report", "testing trends", "failure analysis", and "historical test data".
93
53%
Does it follow best practices?
Impact
97%
1.00xAverage score across 15 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/test-report-generator/skills/test-report-generator/SKILL.mdHTML report with aggregated metrics and failure analysis
HTML output format
100%
100%
Coverage percentage
100%
100%
Pass rate
100%
100%
Test duration
100%
100%
Failing tests listed
100%
100%
Failure messages included
100%
100%
Multi-suite aggregation
100%
100%
Skipped tests reported
100%
100%
Errors vs failures distinction
100%
100%
Summary section
100%
100%
Cross-build trend analysis and regression detection
Both builds compared
100%
100%
Pass rate trend
60%
80%
Coverage trend
100%
100%
Duration trend
100%
100%
Regressions highlighted
100%
100%
Improvements highlighted
100%
100%
New failures identified
100%
100%
Fixed tests identified
100%
100%
Side-by-side metric comparison
100%
100%
Scoped JSON report with failure details
JSON output format
100%
100%
Scoped to API tests
100%
100%
Coverage metric included
100%
100%
Pass rate included
100%
100%
Duration included
100%
100%
Failing test names
100%
100%
Failure messages included
100%
100%
Structured JSON hierarchy
100%
100%
Skipped test count
100%
100%
PDF format report generation
PDF output file
0%
0%
Coverage percentage included
100%
100%
Pass rate included
80%
80%
Test duration included
100%
100%
Failing tests named
100%
100%
Failure messages included
100%
100%
Error distinguished from failure
100%
100%
Multi-suite aggregation
100%
100%
Project context included
100%
100%
Skipped test count
100%
100%
Multi-build historical trend analysis
All 5 builds included
100%
100%
Pass rate trend shown
100%
100%
Coverage trend shown
100%
100%
Duration trend shown
100%
100%
Regressions identified
100%
100%
Improvements identified
100%
100%
Persistent failures highlighted
100%
100%
Comparative presentation
100%
100%
Time period scoped
100%
100%
Summary conclusion
100%
100%
CI/CD pipeline integration for automated test reporting
GitHub Actions workflow file
100%
100%
Triggered on build events
100%
100%
Test execution step included
100%
100%
Report generation step included
100%
100%
Report output format specified
100%
100%
Coverage metrics collected
100%
100%
Report artifact uploaded or shared
100%
100%
JUnit XML output enabled
100%
100%
Report generation script produced
100%
100%
Project context in report
100%
100%
Coverage gap analysis — identifying areas needing more testing
Low-coverage files named
100%
100%
Per-file line coverage %
100%
100%
Branch coverage metric
100%
100%
Files ranked or prioritized
100%
100%
Overall aggregate coverage
100%
100%
Missing lines or uncovered area noted
100%
100%
High-coverage files identified
100%
100%
Project context and environment metadata in test reports
Project name included
100%
100%
Version or environment included
100%
100%
Build or CI reference included
100%
100%
Test framework info included
100%
100%
Pass rate computed correctly
100%
100%
Test duration included
100%
100%
Failing test names listed
100%
100%
Error vs failure distinguished
100%
100%
Failure messages included
100%
100%
Dual-format report generation (HTML and JSON outputs)
HTML file produced
100%
100%
JSON file produced
100%
100%
Consistent pass rate across formats
100%
100%
Coverage in both formats
100%
100%
Failing tests in both formats
100%
100%
HTML structured presentation
100%
100%
JSON nested structure
100%
100%
Duration in both formats
100%
100%
13d35b8
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.