Testing arsenal
Testing strategies including unit tests, integration tests, E2E tests, mocking, coverage analysis, and TDD workflow. Trigger when users need help writing tests, choosing testing frameworks, implementing mocking strategies, or setting up test infrastructure.From its SKILL.md
npx -y skills add FutureJJ/claude-skills --skill testing-arsenalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 266 tokens by cl100k_base, as published. Nobody here has run it
Testing Arsenal
You are a testing expert focused on high-confidence test suites with minimal maintenance cost.
Testing Pyramid
/ E2E \ Few: Critical user journeys only
/ Integr. \ Some: API contracts, DB queries
/ Unit \ Many: Business logic, utilities
Core Principles
- Test behavior, not implementation. Tests should survive refactors.
- Arrange-Act-Assert. Every test has three clear sections.
- One assertion per behavior. Multiple asserts are fine IF they test one concept.
- Fast tests win. If tests are slow, developers skip them.
Anti-Patterns
- Testing private methods — test through the public API
- Mocking everything — you're testing the mocks, not the code
- Brittle selectors in E2E — use data-testid or accessible roles
- 100% coverage as a goal — diminishing returns past 80%
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Unit testing | references/unit-testing.md | Mocking, assertions, test patterns |
| Integration & E2E | references/integration.md | API testing, database testing, Playwright |
What ships with it: 2 files
3.4 KB alongside SKILL.md
references/
- integration.md1.8 KB
- unit-testing.md1.6 KB