From testing-plugin
Shows test status, coverage, flaky tests, and history from cached results without re-executing. Supports pytest, Vitest, Jest, Playwright, Go, Cargo.
How this skill is triggered — by the user, by Claude, or both
Slash command
/testing-plugin:test-reportsonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Quick status check without re-running tests. Reads cached results from last test execution.
Quick status check without re-running tests. Reads cached results from last test execution.
Use when:
--history: Show trend from recent runs--coverage: Include coverage summary--flaky: Identify potentially flaky tests| Framework | Cache Location |
|---|---|
| pytest | .pytest_cache/, htmlcov/ |
| Vitest | node_modules/.vitest/ |
| Jest | coverage/, .jest-cache/ |
| Playwright | test-results/, playwright-report/ |
| Go | coverage.out |
| Cargo | target/debug/ |
Find Latest Results:
Coverage Summary (if --coverage):
Flaky Detection (if --flaky):
History (if --history):
## Test Status (last run: 5 minutes ago)
| Tier | Passed | Failed | Skipped |
|-------------|--------|--------|---------|
| Unit | 45 | 2 | 0 |
| Integration | 12 | 0 | 1 |
| E2E | 8 | 1 | 0 |
**Coverage**: 78% (target: 80%)
### Recent Failures
- test_user_validation: AssertionError (tests/test_user.py:42)
- e2e/login.spec.ts: Timeout (line 15)
### Flaky Tests (if --flaky)
- test_async_handler: 3 failures in last 10 runs
### Suggested Actions
- Run `/test:quick` to verify current state
- Use `/test:consult coverage` for gap analysis
/test:quick to verify current state/test:consult coverage/test:consult flaky/test:quick or /test:fullnpx claudepluginhub laurigates/claude-plugins --plugin testing-pluginParses JUnit XML, Jest JSON, pytest results, and coverage data to generate Markdown/HTML test reports with metrics, failures, slowest tests, and CI annotations.
Generates Playwright test reports with summaries, failed details, flakies, trends, and outputs to Markdown, HTML, Slack, TestRail, or GitHub Actions.