testing-strategy
Define a balanced testing strategy across unit, integration, contract, and end-to-end tests. Use when setting up test approach for a project, reviewing test quality, or deciding what kinds of tests to write.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- testing-strategy
- description
- Define a balanced testing strategy across unit, integration, contract, and end-to-end tests. Use when setting up test approach for a project, reviewing test quality, or deciding what kinds of tests to write.
03 SKILL.md 正文
Testing Strategy
Overview
Not every test provides equal value. A good strategy maximizes confidence per unit of effort and keeps the suite fast and reliable.
When to Use
- Starting a new project or major component
- Reviewing an existing test suite that is slow, flaky, or low-value
- Deciding the right level of testing for a change
Test Pyramid / Trophy Guidance
- Many fast, focused unit tests for domain logic and pure functions
- Fewer integration tests for critical boundaries (DB, external services)
- Selective end-to-end / browser tests for the most important user journeys
- Contract tests when multiple teams or services share interfaces
Principles
- Test behavior and outcomes more than implementation details
- Optimize for quick feedback on the most common failures
- Treat flakiness as a high-priority bug
- Make test failures diagnostic
Verification
- Critical paths have appropriate coverage at the right level
- The suite is fast enough to run frequently
- Flaky tests are actively managed
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.