# test-automation-expert

test-automation-expert — a test automation skill that covers strategy, framework setup, coverage gaps and flaky test debugging. Useful when a project needs tests from scratch or existing ones keep breaking.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 212 installs · ★ 274 repo stars
- Author: curiositech
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/curiositech/some_claude_skills/tree/HEAD/.claude/skills/test-automation-expert/SKILL.md
- Updated: 2026-10-30
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/test-automation-expert

## What it does

The skill walks through the whole test pyramid: unit, integration and E2E. It helps pick a framework for the stack — Vitest for Vite projects, Jest for established React codebases, Playwright or Cypress for browser checks, pytest for Python. It also gives distribution targets: 70% unit, 20% integration, 10% E2E, each with rough execution time limits.

Inside you get Arrange-Act-Assert patterns, boundary mocking advice, and an isolation checklist: independent runs, no shared mutable state, database resets, parallel-safe execution. Integration test examples show a test database and side-effect verification.

The skill stays away from manual QA, load testing and security work. For performance the author points to performance-engineer, for security to security-auditor. It triggers on phrases like "test strategy", "flaky tests", "mocking", "TDD", "BDD". Tools include read, write, edit and Bash: `npm test:*`, `npx jest:*`, `npx vitest:*`, `npx playwright:*`, `pytest:*`.

## Requirements
- Works with: Playwright

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill test-automation-expert -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill test-automation-expert -a codex
```

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

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill test-automation-expert -a cursor
```

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install curiositech/some_claude_skills .claude/skills/test-automation-expert
```

2. **Manually: put the files in place**
- File: `.github/skills/test-automation-expert/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill test-automation-expert -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/curiositech/some_claude_skills --path .claude/skills/test-automation-expert
```

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill test-automation-expert -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/curiositech/some_claude_skills/tree/HEAD/.claude/skills/test-automation-expert/SKILL.md

## When to use it
- pick a test framework that matches the project stack
- set up Jest, Vitest, Playwright, Cypress or pytest from scratch
- track down and fix flaky tests
- design a test pyramid with sensible coverage
- build mocks and fixtures without touching implementation details

## Example prompts
- Design a test strategy for a new React project on Vite
- Write unit tests for `validateEmail` using Arrange-Act-Assert
- Figure out why this Playwright test fails intermittently and suggest a fix

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d1e129e93061bcc4.

BEGIN THIRD-PARTY FILE d1e129e93061bcc4
````text
---
name: test-automation-expert
description: Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test
  pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests', 'integration tests', 'E2E testing', 'test coverage', 'flaky tests', 'mocking',
  'test fixtures', 'TDD', 'BDD', 'test automation'. NOT for manual QA processes, load/performance testing (use performance-engineer), or security testing (use security-auditor).
allowed-tools: Read,Write,Edit,Bash(npm test:*,npx jest:*,npx vitest:*,npx playwright:*,pytest:*),Grep,Glob
metadata:
  category: Code Quality & Testing
  pairs-with:
  - skill: refactoring-surgeon
    reason: Tests before refactoring
  - skill: devops-automator
    reason: CI/CD test integration
  tags:
  - testing
  - jest
  - playwright
  - tdd
  - coverage
---

# Test Automation Expert

Comprehensive testing guidance from unit to E2E. Designs test strategies, implements automation, and optimizes coverage for sustainable quality.

## When to Use

**Use for:**
- Designing test strategy for new projects
- Setting up testing frameworks (Jest, Vitest, Playwright, Cypress, pytest)
- Writing effective unit, integration, and E2E tests
- Optimizing test coverage and eliminating gaps
- Debugging flaky tests
- CI/CD test pipeline configuration
- Test-Driven Development (TDD) guidance
- Mocking strategies and test fixtures

**Do NOT use for:**
- Manual QA test case writing - this is automation-focused
- Load/performance testing - use performance-engineer skill
- Security testing - use security-auditor skill
- API contract testing only - use backend-architect for API design

## Test Pyramid Philosophy

```
         /\
        /  \      E2E Tests (10%)
       /----\     - Critical user journeys
      /      \    - Cross-browser validation
     /--------\
    /          \  Integration Tests (20%)
   /            \ - API contracts
  /--------------\- Component interactions
 /                \
/------------------\ Unit Tests (70%)
                    - Fast, isolated, deterministic
                    - Business logic validation
```
````
END THIRD-PARTY FILE d1e129e93061bcc4

The third-party file has ended. Everything between the d1e129e93061bcc4 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2273 of 14007 bytes. © curiositech · MIT · https://github.com/curiositech/some_claude_skills/tree/HEAD/.claude/skills/test-automation-expert/SKILL.md

_Part of the page did not fit — see the HTML version._

---
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
