test-reporting-analytics — Claude Code skill: install and usage
test-reporting-analytics generates quality dashboards, executive reports, and failure predictions based on code diffs. Useful when tracking CI/CD trends or preparing release gates.
MIT 126 installs ★ 533 updated 2026-10-25
npx skills add proffesor-for-testing/agentic-qe --skill test-reporting-analytics -a claude-codeWhat test-reporting-analytics does
This skill segments test reporting by audience. Engineering teams receive details on flaky test percentages, suite runtimes, and coverage gaps, while executives get summaries on escaped defects and automation savings. Built-in benchmarks target over 98% pass rates, suite durations under 10 minutes, and branch coverage above 70%.
Failure forecasting runs via the qe-quality-analyzer agent. By evaluating pull request diffs against 90 days of execution history, it outputs failure probabilities for specific test files. All generated metrics, trend analyses, and forecasts reside in the aqe/reporting/ memory space.
Running end-to-end release checks relies on the companion qe-quality-gate and qe-deployment-readiness subagents, meaning threshold validation cannot complete if those agents are absent.
What it helps with
- generate executive or sprint quality summaries
- predict test failures from pull request changes
- evaluate quality gate thresholds before deployment
- detect trend anomalies across execution time and flaky tests
Example prompts for the agent
- Generate a sprint quality summary report with coverage deltas and flaky test trends
- Predict test failures for the latest pull request diff using 90-day history
- Run a quality gate check against production thresholds
How to install test-reporting-analytics
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-reporting-analytics -a claude-code2Manually: put the files in place
~/.claude/skills/test-reporting-analytics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/test-reporting-analytics/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-reporting-analytics -a codex2Manually: put the files in place
.agents/skills/test-reporting-analytics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-reporting-analytics -a cursor2Manually: put the files in place
.cursor/skills/test-reporting-analytics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install proffesor-for-testing/agentic-qe assets/skills/test-reporting-analytics2Manually: put the files in place
.github/skills/test-reporting-analytics/SKILL.md1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-reporting-analytics -a gemini-cli2Platform CLI
gemini skills install https://github.com/proffesor-for-testing/agentic-qe --path assets/skills/test-reporting-analyticsManually: put the files in place
.devin/skills/test-reporting-analytics/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-reporting-analytics -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about test-reporting-analytics
How to install test-reporting-analytics in Claude Code?
Run npx skills add proffesor-for-testing/agentic-qe --skill test-reporting-analytics -a claude-code. The definition will be placed in ~/.claude/skills/test-reporting-analytics/SKILL.md.
What does test-reporting-analytics do?
It aggregates test metrics, monitors CI/CD trends like duration and flaky tests, and structures actionable summaries tailored to developers or management.
Which agents work alongside this skill?
The workflow coordinates three agents: qe-quality-analyzer for metrics aggregation and predictions, qe-quality-gate for policy checks, and qe-deployment-readiness for release verification.
Source text
SKILL.md · MIT
---
name: test-reporting-analytics
description: "Advanced test reporting, quality dashboards, predictive analytics, trend analysis, and executive reporting for QE metrics. Use when communicating quality status, tracking trends, or making data-driven decisions."
category: analytics
priority: high
tokenEstimate: 850
agents: [qe-quality-analyzer, qe-quality-gate, qe-deployment-readiness]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-03
dependencies: []
quick_reference_card: true
tags: [reporting, analytics, dashboards, metrics, trends, predictive]
trust_tier: 3
validation:
schema_path: schemas/output.json
validator_path: scripts/validate-config.json
eval_path: evals/test-reporting-analytics.yaml
---
# Test Reporting & Analytics
<default_to_action>
When building test reports:
1. DEFINE audience (dev team vs executives)
2. CHOOSE key metrics (max 5-7)
3. SHOW trends (not just snapshots)
4. HIGHLIGHT actions (what to do about it)
5. AUTOMATE generation
**Dashboard Quick Setup:**
```
+------------------+------------------+------------------+
| Tests Passed | Code Coverage | Flaky Tests |
| 1,247/1,250 ✅ | 82.3% ⬆️ +2.1% | 1.2% ⬇️ -0.3% |
+------------------+------------------+------------------+
| Critical Bugs | Deploy Freq | MTTR |
| 0 open ✅ | 12x/day ⬆️ | 2.3h ⬇️ |
+------------------+------------------+------------------+
```
**Key Metrics by Audience:**
- **Dev Team**: Pass rate, flaky %, execution time, coverage gaps
- **QE Team**: Defect detection rate, test velocity, automation ROI
- **Leadership**: Escaped defects, deployment frequency, quality cost
</default_to_action>
## Quick Reference Card
### Essential Metrics
| Category | Metric | Target |
|----------|--------|--------|
| **Execution** | Pass Rate | >98% |
| **Execution** | Flaky Test % | <2% |
| **Execution** | Suite Duration | <10 min |
| **Coverage** | Line Coverage | >80% |
| **Coverage** | Branch Coverage | >70% |
| **Quality** | Escaped Defects | <5/release |
| **Quality** | MTTR | <4 hours |
| **Efficiency** | Automation Rate | >90% |
### Trend Indicators
| Symbol | Meaning | Action |
|--------|---------|--------|
| ⬆️ | Improving | Continue current approach |
| ⬇️ | Declining | Investigate root cause |
| ➡️ | Stable | Maintain or improve |
| ⚠️ | Threshold breach | Immediate attention |
---
## Report Types
### Real-Time Dashboard
```
Live quality status for CI/CD
- Build status (green/red)
- Test results (pass/fail counts)
- Coverage delta
- Flaky test alerts
```
### Sprint Summary
```markdown
## Sprint 47 Quality Summary
### Metrics
| Metric | Value | Trend |
|--------|-------|-------|
| Tests Added | +47 | ⬆️ |
| Coverage | 82.3% | ⬆️ +2.1% |
| Bugs Found | 12 | ➡️ |
| Escaped | 0 | ✅ |
### Highlights
- ✅ Zero escaped defects
- ⚠️ E2E suite now 45min (target: 30min)
### Actions
1. Optimize slow E2E tests
2. Add coverage for payment module
```
### Executive Report
```markdown
## Monthly Quality Report - Oct 2025
### Executive Summary
✅ Production uptime: 99.97% (target: 99.95%)
✅ Deploy frequency: 12x/day (up from 8x)
⚠️ Coverage: 82.3% (target: 85%)
### Business Impact
- Automation saves 120 hrs/month
- Bug cost: $150/bug found vs $5,000 escaped
- Estimated annual savings: $450K
### Recommendations
1. Invest in performance testing tooling
2. Hire senior QE for mobile coverage
```
---
## Predictive Analytics
```typescript
// Predict test failures
const prediction = await Task("Predict Failures", {
codeChanges: prDiff,
historicalData: last90Days,
model: 'gradient-boosting'
}, "qe-quality-analyzer");
// Returns:
// {
// failureProbability: 0.73,
// likelyFailingTests: ['payment.test.ts'],
// suggestedAction: 'Review payment module carefully',
// confidence: 0.89
// }
// Trend analysis with anomaly detection
const trends = await Task("Analyze Trends", {
metrics: ['passRate', 'coverage', 'flakyRate'],
period: '30d',
detectAnomalies: true
}, "qe-quality-analyzer");
```
---
## Agent Integration
```typescript
// Generate comprehensive quality report
const report = await Task("Generate Quality Report", {
period: 'sprint',
audience: 'executive',
includeROI: true,
includeTrends: true
}, "qe-quality-analyzer");
// Real-time quality gate check
const gateResult = await Task("Quality Gate Check", {
metrics: currentMetrics,
thresholds: qualityPolicy,
environment: 'production'
}, "qe-quality-gate");
```
---
## Agent Coordination Hints
### Memory Namespace
```
aqe/reporting/
├── dashboards/* - Dashboard configurations
├── reports/* - Generated reports
├── trends/* - Trend analysis data
└── predictions/* - Predictive model outputs
```
### Fleet Coordination
```typescript
const reportingFleet = await FleetManager.coordinate({
strategy: 'quality-reporting',
agents: [
'qe-quality-analyzer', // Metrics aggregation
'qe-quality-gate', // Threshold validation
'qe-deployment-readiness' // Release readiness
],
topology: 'parallel'
});
```
---
## Related Skills
- [quality-metrics](../quality-metrics/) - Metric definitions
- [shift-right-testing](../shift-right-testing/) - Production metrics
- [consultancy-practices](../consultancy-practices/) - Client reporting
---
## Remember
**Measure to improve. Report to communicate.**
Good reports:
- Answer "so what?" (actionable insights)
- Show trends (not just snapshots)
- Match audience needs
- Automate where possible
**Data without action is noise. Action without data is guessing.**
© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe