with one click
automation-strategy
Plan test automation strategies including ROI analysis, automation candidate selection, framework evaluation, and maintainable automation architecture.
Menu
Plan test automation strategies including ROI analysis, automation candidate selection, framework evaluation, and maintainable automation architecture.
识别业务能力并分类子域(Core/Supporting/Generic),产出核心域声明与所有权建议。
从不变量出发设计聚合边界:聚合根、实体、值对象、事务边界与跨聚合一致性策略。
映射限界上下文间的关系与集成策略:模式选择、契约所有权、失败模式与版本策略。
设计限界上下文及其通用语言:边界、职责、词汇表、团队所有权与边界 ADR。
协作式领域发现:通过事件风暴或领域故事讲述,产出事件流、命令/事件候选、热点与歧义清单。
设计构造块间的协作机制:领域事件、领域服务、仓储接口与工厂。
| name | automation-strategy |
| description | Plan test automation strategies including ROI analysis, automation candidate selection, framework evaluation, and maintainable automation architecture. |
| allowed-tools | Read, Write, Glob, Grep, Task, WebSearch, WebFetch |
Use this skill when:
A well-planned test automation strategy maximizes ROI by automating the right tests at the right level. Poor automation choices lead to maintenance burden, flaky tests, and wasted effort.
High Business Value
│
┌──────────────────┼──────────────────┐
│ AUTOMATE │ AUTOMATE │
│ FIRST │ (careful ROI) │
│ (High ROI) │ │
Low ├──────────────────┼──────────────────┤ High
Effort │ AUTOMATE │ CONSIDER │ Effort
│ (Low effort) │ MANUAL │
│ │ (Low ROI) │
└──────────────────┼──────────────────┘
Low Business Value
| Criterion | Weight | Score (1-5) |
|---|---|---|
| Execution Frequency | 25% | 5 = Daily, 1 = Quarterly |
| Business Criticality | 25% | 5 = Revenue-critical, 1 = Rarely used |
| Stability (low change) | 20% | 5 = Never changes, 1 = Weekly |
| Complexity to Automate | 15% | 5 = Trivial, 1 = Very complex |
| Data Availability | 15% | 5 = Static, 1 = Unavailable |
Decision: Score ≥ 4.0: Prioritize | 3.0-3.9: Defer | < 3.0: Keep manual
| Good Candidates | Poor Candidates |
|---|---|
| Smoke/sanity tests | Exploratory testing |
| Regression tests | Usability testing |
| Data-driven tests | One-time tests |
| API contract tests | Rapidly changing features |
| Performance baselines | Visual design validation |
| Security scans | Edge cases rarely executed |
| Factor | Multiply Manual Time By |
|---|---|
| Simple UI automation | 3-5x |
| Complex UI automation | 8-15x |
| API automation | 1-2x |
| Database automation | 2-3x |
| Performance tests | 5-10x |
Example: 30 min manual × 1.5 = 45 min API automation. 52 weekly runs = 26 hrs saved. ROI = 3,367%
| Anti-Pattern | Problem | Solution |
|---|---|---|
| Sleep/Wait hardcoding | Flaky, slow | Use explicit waits |
| XPath over data-testid | Brittle | Use stable selectors |
| Test interdependence | Order-dependent failures | Isolated test setup |
| Shared mutable state | Race conditions | Fresh state per test |
| Too many E2E tests | Slow pipeline | Push to lower pyramid |
| Metric | Healthy | Warning | Critical |
|---|---|---|---|
| Pass rate | > 98% | 95-98% | < 95% |
| Flaky test rate | < 2% | 2-5% | > 5% |
| Avg execution time | < 10 min | 10-30 min | > 30 min |
| Maintenance hours/week | < 4 hrs | 4-8 hrs | > 8 hrs |
| Reference | Content | When to Load |
|---|---|---|
| automation-strategy-template.md | Full strategy template, framework selection, roadmap | Creating automation strategy |
| automation-patterns.md | Page Object Model, Fluent Builder, Test Fixture | Implementing .NET Playwright tests |
Inputs from:
test-strategy-planning skill → Overall strategytest-pyramid-design skill → Pyramid ratiosOutputs to:
test-case-design skill → Automatable test designsQuery: "Help me plan a test automation strategy for our e-commerce platform"
Expected: Skill activates, provides strategy template, guides through assessment
Query: "Should I automate this checkout flow test?"
Expected: Skill activates, provides selection criteria matrix, helps calculate ROI
Query: "Show me the Page Object Model pattern in Playwright"
Expected: Skill activates, loads automation-patterns.md reference, provides code examples
Last Updated: 2025-12-28