# project-testing

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1 install · ★ 492 repo stars
- Author: aiskillstore
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/aiskillstore/marketplace/tree/HEAD/skills/consiliency/project-testing/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/project-testing

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add aiskillstore/marketplace --skill project-testing -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/project-testing/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/project-testing/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add aiskillstore/marketplace --skill project-testing -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/project-testing/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add aiskillstore/marketplace --skill project-testing -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/project-testing/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install aiskillstore/marketplace skills/consiliency/project-testing
```

2. **Manually: put the files in place**
- File: `.github/skills/project-testing/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add aiskillstore/marketplace --skill project-testing -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/aiskillstore/marketplace --path skills/consiliency/project-testing
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/project-testing/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add aiskillstore/marketplace --skill project-testing -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/aiskillstore/marketplace/tree/HEAD/skills/consiliency/project-testing/SKILL.md

## When to use it
- 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
- Write a unit test for the `calculateDiscount` function using project fixtures and mocking dependencies
- Create an integration test for the order creation API with `sample_user` and `sample_order` fixtures
- Write an E2E test for a full purchase flow using Playwright and fixtures with 30000 ms timeout

## Similar
- [playwright-e2e-testing](https://affpapa.org/en/nevibecode/skills/playwright-e2e-testing.md) — skill · 642 installs
- [testing-principles](https://affpapa.org/en/nevibecode/skills/testing-principles.md) — skill · ★ 720 repo stars
- [testing-expert](https://affpapa.org/en/nevibecode/skills/testing-expert.md) — skill · 206 installs
- [testing](https://affpapa.org/en/nevibecode/skills/rudolf-s-testing.md) — skill · ★ 587 repo stars
- [testing-craft](https://affpapa.org/en/nevibecode/skills/testing-craft.md) — skill · 1200 installs
- [unit-testing-framework](https://affpapa.org/en/nevibecode/skills/unit-testing-framework.md) — skill · 633 installs

From the same set: [aiskillstore/marketplace](https://affpapa.org/en/nevibecode/by/aiskillstore/marketplace.md) — 18 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
