test-reporting-analytics
について
このスキルは、品質ダッシュボード、予測分析、QEメトリクスの傾向分析を含む高度なテストレポートと分析機能を提供します。品質ステータスの伝達、傾向の追跡、データ駆動型意思決定のサポートを目的としています。開発者は、実行レポートの作成や、実用的な洞察に焦点を当てた品質メトリクスの分析が必要な場合に使用すべきです。
クイックインストール
Claude Code
推奨npx skills add proffesor-for-testing/agentic-qe/plugin add https://github.com/proffesor-for-testing/agentic-qegit clone https://github.com/proffesor-for-testing/agentic-qe.git ~/.claude/skills/test-reporting-analyticsこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
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.
GitHub リポジトリ
関連スキル
Verification & Quality Assurance
その他This skill provides automated quality verification for code and agent outputs using truth scoring and quality checks. It automatically rolls back changes that fall below a 0.95 accuracy threshold, ensuring codebase reliability. Use it for CI/CD integration and maintaining high-quality standards in development workflows.
performance-analysis
その他This skill provides comprehensive performance analysis and bottleneck detection for Claude Flow swarms, helping developers identify optimization opportunities. It offers real-time monitoring, profiling of swarm operations, and generates detailed reports with actionable recommendations. Use this skill when you need to diagnose performance issues and improve the efficiency of your Claude Code applications.
Verification & Quality Assurance
その他This skill provides automated verification and quality assurance for code and agent outputs, including truth scoring and validation checks. It enables automatic rollback for failed quality checks and integrates with CI/CD pipelines. Use it to validate code changes before merging or to ensure the correctness of generated outputs.
Report Writer
その他The Report Writer skill generates professional reports from research and data, supporting technical, business, and academic styles. It structures input content with features like an optional table of contents and outputs formatted markdown. Use this skill to quickly transform raw findings into polished, audience-appropriate documentation.
