project-testing — Claude Code skill: test patterns and fixtures
project-testing — a skill with ready-made patterns and fixtures for unit, integration, and E2E tests. Speeds up isolated test writing by one standard, prevents hardcoded data and flaky tests.
no license 1 installs ★ 492 updated 2026-10-25
npx skills add aiskillstore/marketplace --skill project-testing -a claude-codeWhat project-testing does
The skill provides a structured testing approach: separate directories for unit tests (tests/unit/), integration tests (tests/integration/), and E2E (tests/e2e/), pre-built fixtures for databases and mock services, and function naming by scenario. Includes configurable variables (COVERAGE_TARGET, E2E_TIMEOUT, parallel execution) and coverage tables: core logic 90%, API routes 80%, utilities 70%. A red-flag checklist catches common mistakes—unisoleated tests, missing cleanup, hardcoded test data instead of fixtures, timing-dependent or order-dependent tests.
Without fixtures and patterns, tests often become brittle and slow. The skill helps agents (Claude, GitHub Copilot, and others) distinguish unit from integration, pick the right directory and fixture, name functions by project rules. CI integration follows: unit and integration run on PR, E2E is added on merge, nightly runs the full regression suite.
What it helps with
- write unit tests with proper isolation and no hardcoded data
- build database and mock-service fixtures instead of manual setup
- pick the right test type (unit/integration/E2E) for a given task
- avoid flaky tests that depend on timing or execution order
- configure CI pipeline so different test types run at the right time
Example prompts for the agent
- Write a unit test for the
calculateDiscountfunction using project fixtures and mocking dependencies - Create an integration test for the order creation API with
sample_userandsample_orderfixtures - Write an E2E test for a full purchase flow using Playwright and fixtures with 30000 ms timeout
How to install project-testing
1Skills CLI (Vercel)
npx skills add aiskillstore/marketplace --skill project-testing -a claude-code2Manually: put the files in place
~/.claude/skills/project-testing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/project-testing/
1Skills CLI (Vercel)
npx skills add aiskillstore/marketplace --skill project-testing -a codex2Manually: put the files in place
.agents/skills/project-testing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aiskillstore/marketplace --skill project-testing -a cursor2Manually: put the files in place
.cursor/skills/project-testing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aiskillstore/marketplace skills/consiliency/project-testing2Manually: put the files in place
.github/skills/project-testing/SKILL.md1Skills CLI (Vercel)
npx skills add aiskillstore/marketplace --skill project-testing -a gemini-cli2Platform CLI
gemini skills install https://github.com/aiskillstore/marketplace --path skills/consiliency/project-testingManually: put the files in place
.devin/skills/project-testing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aiskillstore/marketplace --skill project-testing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about project-testing
How do I install project-testing in Claude Code?
Run npx skills add aiskillstore/marketplace --skill project-testing -a claude-code. The skill will load into ~/.claude/skills/project-testing/SKILL.md.
What does project-testing do?
It gives your agent patterns, fixtures, and checklists for writing unit, integration, and E2E tests. It prevents hardcoding, flaky tests, and missing test isolation.
What coverage is required for core logic?
90% coverage for core logic, 80% for API routes, 70% for utilities.