Generate comprehensive test reports with metrics, coverage, and visualizations.
SkillScore73Maintained
Automatic
◆QA & Test Engineering packtestingtest-reports
Last verified 8/30/2026
What it changes
Passed 16 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill73%
Checks it passed that the model alone missed
Includes coverage heatmaps
Recommends re-running the failed test suite
Names the Markdown summary file test-report.md
and 9 more in the full report
8 fixed8 passed either way6 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+28%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/30/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
We want our test report summary rendered natively on the GitHub Actions workflow run page. What bash shell command attaches the generated Markdown summary to GitHub Actions?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses cat test-report.md >> $GITHUB_STEP_SUMMARY to publish the report
Missed
Passed
case-13 · gemini-3.6-flash · 8/30/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md91 lines9 filesincludes scripts
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
Locate all test result files using Glob patterns (**/junit.xml, **/test-results.json, **/coverage/lcov.info).
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.
Parse coverage data and extract:
Line, branch, function, and statement coverage percentages.