test-reporting-analytics
Generates quality dashboards and trend reports for dev teams and stakeholders.
Install
mkdir -p .claude/skills/test-reporting-analytics && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9246" && unzip -o skill.zip -d .claude/skills/test-reporting-analytics && rm skill.zipInstalls to .claude/skills/test-reporting-analytics
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Structures metrics into audience-specific summaries
- →Calculates MTTR and defect detection rates
- →Visualizes quality trends via CLI dashboard formats
- →Maps test data to executive-level status reports
- →Identifies coverage gaps based on predefined targets
How it works
Aggregates raw test execution telemetry against a schema to calculate performance KPIs and format them for reporting.
Inputs & outputs
When to use test-reporting-analytics
- →Generating test summary reports for stakeholders
- →Analyzing flaky test trends
- →Tracking deployment frequency and quality metrics
- →Communicating release readiness
About this skill
Test Reporting & Analytics
<default_to_action> When building test reports:
- DEFINE audience (dev team vs executives)
- CHOOSE key metrics (max 5-7)
- SHOW trends (not just snapshots)
- HIGHLIGHT actions (what to do about it)
- 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
## 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
## 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
// 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
// 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
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 - Metric definitions
- shift-right-testing - Production metrics
- 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.
When not to use it
- →When no underlying test data or logs are available
- →Real-time monitoring of live production traffic
Limitations
- →Dependent on accurate test execution history
- →Cannot predict future failures with high certainty
- →Limited to the metrics defined in the plugin schema
How it compares
It synthesizes qualitative and quantitative testing data for non-technical stakeholders instead of just outputting test logs.
Compared to similar skills
test-reporting-analytics side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| test-reporting-analytics (this skill) | 1 | 2mo | Review | Intermediate |
| analytics-heatmaps | 0 | 5mo | Review | Intermediate |
| omnidocbench-eval-helper | 0 | 3mo | Review | Advanced |
| backtesting-trading-strategies | 10 | 27d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
analytics-heatmaps
nlelouche
Implementation of comprehensive analytics tracking and heatmap data collection for player behavior analysis.
omnidocbench-eval-helper
opendatalab
Help users deploy, validate, run, and parse OmniDocBench evaluations. Use this skill whenever the user mentions OmniDocBench, document parsing/OCR benchmark scoring, MinerU or other model evaluation on OmniDocBench, CDM formula metrics, end2end/md2md configs, Docker/conda deployment, remote SSH/H-cl
backtesting-trading-strategies
jeremylongshore
Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".
model-usage
openclaw
Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
analytics-tracking
davila7
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
splunk-analysis
incidentfox
Splunk log analysis using SPL (Search Processing Language). Use when investigating issues via Splunk logs, saved searches, or alerts.