Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ancoleman/testing-strategies
Strategic guidance for choosing and implementing testing approaches across the test pyramid.
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
2 fixed19 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are designing a multi-stage automated pipeline. Should we run slow cross-browser end-to-end tests on every local git pre-commit hook before developers can save commits? Outline the correct progression of test execution stages.
| Checked | Without skill | With skill |
|---|---|---|
| Excludes end-to-end browser tests from local pre-commit hooks. | Passed | Passed |
| Restricts end-to-end testing to pre-merge or late-stage pull request pipelines. | Missed | Passed |
The instructions your model reads when the skill loads.
Build comprehensive, effective test suites by strategically selecting and implementing the right testing approaches across unit, integration, E2E, and contract testing levels.
This skill provides strategic frameworks for:
Testing is foundational to reliable software. With microservices architectures and continuous delivery becoming standard in 2025, strategic testing across multiple levels is more critical than ever.
Invoke this skill when:
The testing pyramid guides test distribution for optimal speed and confidence:
/\
/ \ E2E Tests (10%)
/----\ - Slow but comprehensive
/ \ - Full stack validation
/--------\
/ \ Integration Tests (20-30%)
/ \ - Moderate speed
test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.