From test-strategy
Analyzes test cases for automation ROI using weighted criteria like frequency, criticality, stability, complexity, and data availability to recommend prioritization.
npx claudepluginhub melodic-software/claude-code-plugins --plugin test-strategyThis skill is limited to using the following tools:
Evaluate test cases for automation potential and calculate ROI to prioritize automation efforts.
Plans test automation strategies with ROI analysis, candidate selection, framework evaluation, and maintainable architecture.
Expert approach to data-driven-testing in test automation. Use when working with .
Prioritizes testing effort on highest-risk areas using probability-impact scoring, effort allocation (60% critical, 25% high), and dynamic reassessment for test strategy, resource allocation, and coverage decisions.
Share bugs, ideas, or general feedback.
Evaluate test cases for automation potential and calculate ROI to prioritize automation efforts.
Collect test cases to evaluate:
Invoke the test-strategy:automation-strategy skill for ROI calculation patterns.
For each test case, assess:
Selection Criteria (Score 1-5):
| Criterion | Weight | Description |
|---|---|---|
| Execution Frequency | 25% | How often is it run? |
| Business Criticality | 25% | How important to business? |
| Stability | 20% | How stable is the feature? |
| Automation Complexity | 15% | How hard to automate? |
| Data Availability | 15% | Is test data available? |
| Test Case | Freq | Crit | Stable | Complex | Data | Score |
|-----------|------|------|--------|---------|------|-------|
| TC-001 Login | 5 | 5 | 5 | 4 | 5 | 4.8 |
| TC-002 Checkout | 4 | 5 | 4 | 3 | 4 | 4.1 |
| TC-003 Reporting | 2 | 3 | 5 | 2 | 3 | 2.9 |
For high-scoring candidates:
## ROI Analysis: TC-001 Login
**Manual Execution:**
- Time per run: 15 minutes
- Runs per month: 20
- Duration: 12 months
- Total manual time: 15 × 20 × 12 = 3,600 minutes = 60 hours
**Automation Cost:**
- Development: 4 hours
- Monthly maintenance: 0.5 hours
- Total maintenance: 0.5 × 12 = 6 hours
- Total cost: 4 + 6 = 10 hours
**ROI Calculation:**
- Time saved: 60 - 10 = 50 hours
- ROI: (50 / 10) × 100 = 500%
- Breakeven: 4 / (0.25 - 0.04) = 19 executions (1 month)
Categorize by decision:
## Automation Recommendations
### Automate First (Score ≥ 4.0, ROI > 300%)
| Test | Score | ROI | Est. Effort |
|------|-------|-----|-------------|
| TC-001 Login | 4.8 | 500% | 4 hours |
| TC-004 Cart | 4.2 | 400% | 6 hours |
### Automate Later (Score 3.0-3.9, ROI 100-300%)
| Test | Score | ROI | Est. Effort |
|------|-------|-----|-------------|
| TC-002 Checkout | 4.1 | 250% | 8 hours |
### Keep Manual (Score < 3.0 or ROI < 100%)
| Test | Score | ROI | Reason |
|------|-------|-----|--------|
| TC-003 Reporting | 2.9 | 80% | Complex, rarely run |
| TC-005 Admin config | 2.5 | 50% | Changes frequently |
### Technical Blockers
| Test | Issue | Resolution |
|------|-------|------------|
| TC-006 External API | Rate limited | Mock service needed |
## Automation ROI Analysis Complete
**Tests Analyzed**: [count]
**Recommended for Automation**: [count] ([%])
**Total Potential Hours Saved**: [X] hours/year
**Investment Required**: [Y] hours
### Summary
| Category | Count | % |
|----------|-------|---|
| Automate First | X | X% |
| Automate Later | Y | Y% |
| Keep Manual | Z | Z% |
### Priority Roadmap
**Sprint 1** (Est. 20 hours):
1. TC-001 Login - 4 hours
2. TC-004 Cart - 6 hours
3. TC-007 Search - 10 hours
**Sprint 2** (Est. 24 hours):
4. TC-002 Checkout - 8 hours
5. TC-008 Profile - 8 hours
6. TC-009 History - 8 hours
### Expected Benefits
- Year 1 savings: [X] hours
- Year 2 savings: [Y] hours (with maintained suite)
- Regression time reduction: [Z]%
Analyze test inventory:
/test-strategy:analyze-automation-roi docs/test-cases/
Specific feature:
/test-strategy:analyze-automation-roi checkout flow tests
Quick assessment:
/test-strategy:analyze-automation-roi "Login, cart, checkout, order history"