# Test

> Runs and interprets automated tests for a module or the whole project. Use when the user asks to test, verify behavior, check coverage, or says /test.

- Skill: `axidify/test` (Agent Skill)
- Install (CLI): `npx skillmds@latest add axidify/test`
- Raw SKILL.md: https://api.skillmd.com/api/skills/axidify/test/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Axidify (https://skillmd.com/u/axidify)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/axidify/test

---


# Test

## Discover commands

From `package.json` scripts, Makefile, README, or CI config — find:

- Unit / integration test command (e.g. `pnpm test`, `pytest`, `go test ./...`)
- E2E command if present (e.g. `playwright test`)

Run what matches the user's scope. Prefer **subset** when scope is narrow:

- `pytest path/to/test_file.py::test_name`
- `pnpm vitest run path -t "name"`
- `go test ./pkg/... -run TestName`

## Automated tests

1. Locate tests related to the scope
2. Run the appropriate command
3. Report: passed / failed / skipped
4. For failures: file, test name, likely cause
5. Propose fixes only if failures relate to recent changes or the user asked

## Flaky / snapshots

- **Flaky**: note retry behavior from config; do not delete tests to greenwash
- **Snapshots / goldens**: update only when the user approves intentional output changes

## When tests are thin or missing

1. Trace main code paths for the feature
2. Note gaps: untested branches, missing validation
3. Suggest **concrete** tests worth adding (behavior, not trivial asserts)

## Rules

- Do not delete or skip tests to greenwash unless the user agrees
- Prefer the project's existing test runner and conventions

## Related skills

- **implement** — fix failures from your changes
- **debug** — when failures need root-cause analysis
- **ci** — CI-only failures or environment mismatch
- **ui-browser-check** — visual issues better verified in the browser