test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or
Profile →npx skills add rohitg00/skillkit --skill test-patterns --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Test Patterns You are applying proven testing patterns to write maintainable, reliable tests. These patterns help ensure tests are readable, focused, and trustworthy. ## Pattern Selection Guide Use this to choose the right pattern for your situation: - **Structuring a single test?** → Arrange-Act-Assert (AAA) or Given-When-Then - **Writing behavior/feature specs?** → Given-When-Then (BDD style) - **Repeating test setup data?** → Test Data Builders - **Many variations of complex objects?** → Object Mother - **Testing same logic with many inputs?** → Parameterized Tests - **Shared setup/teardown across tests?** → Test Fixtures - **Verifying a dependency was called?** → Spy - **Replacing an external dependency?** → Test Doubles (Stub / Mock / Fake) --- ## Pattern Combination Workflows Patterns rarely stand alone — here's how to combine them for common scenarios: **Unit tests (isolated logic):** Fixtures for setup → AAA structure → Stubs/Mocks for dependencies → Parameterized Tests for multiple input cases **Integration tests (service + external dependencies):** Fixtures for setup → AAA structure → Fakes for external services (e.g. in-memory DB) → Spies to verify interaction points *
- Pattern Selection Guide
- Pattern Combination Workflows
- Core Pattern: Arrange-Act-Assert (AAA)
- Pattern: Given-When-Then (BDD Style)
- Pattern: Test Data Builders
- Pattern: Object Mother
- Pattern: Parameterized Tests
- Pattern: Test Fixtures
- Pattern: Spy on Dependencies
- Pattern: Test Doubles
- Pattern: Test Isolation
- Naming Conventions
- Test Organization
- Verification Checklist
What does the test-patterns skill do?
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or
How do I install it?
Run `npx skills add rohitg00/skillkit --skill test-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/skillkit, a repository with 1,422 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.