# test-automator

test-automator is a Claude Code subagent that plans automated tests and connects them to CI/CD. It activates for coverage work or when a project needs a testing setup from scratch.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/agents/quality-testing/test-automator.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/qdhenry-test-automator

## What it does

test-automator helps define a testing plan, create unit, integration, and end-to-end tests, and wire checks into CI/CD. It can review test results and defects, and work with test data and environments. Browser-based E2E checks can use its Playwright tools.

The listed testing frameworks include Jest, Pytest, Cypress, and Playwright. The subagent favors tests based on observable application behavior, with cases split into setup, action, and outcome checks. It also tracks failing tests and build quality.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/test-automator.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/test-automator.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/test-automator.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/agents/quality-testing/test-automator.md

## When to use it
- increase test coverage
- add unit and integration checks
- write browser-based end-to-end tests
- connect test runs to CI/CD
- review test results and defects

## Example prompts
- Plan a testing strategy for this project and choose suitable test types.
- Add unit and integration tests for the new API.
- Create end-to-end checks for this user flow and connect them to CI/CD.

## Similar
- [backend-development-test-automator](https://affpapa.org/en/nevibecode/agents/backend-development-test-automator.md) — subagent · ★ 42780 repo stars
- [codebase-cleanup-test-automator](https://affpapa.org/en/nevibecode/agents/codebase-cleanup-test-automator.md) — subagent · ★ 42780 repo stars
- [setup-comprehensive-testing](https://affpapa.org/en/nevibecode/commands/setup-comprehensive-testing.md) — command · 278 installs
- [qe-test-generation](https://affpapa.org/en/nevibecode/skills/qe-test-generation.md) — skill · 142 installs
- [test-automation-orchestrator](https://affpapa.org/en/nevibecode/commands/test-automation-orchestrator.md) — command · 350 installs
- [qe-test-execution](https://affpapa.org/en/nevibecode/skills/qe-test-execution.md) — skill · 122 installs

## Other versions with the same name
- [test-automator · voltagent](https://affpapa.org/en/nevibecode/agents/test-automator.md) — 625 installs
- [test-automator · voltagent](https://affpapa.org/en/nevibecode/agents/voltagent-test-automator.md) — ★ 6505 repo stars

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 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
