# Testing

> Test-driven development workflow for Noodle. Use when testing changes, writing tests, fixing bugs, creating fixtures, or running the test suite. Triggers: "test", "write a test", "fix this bug", "add a fixture", "run tests", "TDD", or any task involving verification of code changes.

- Skill: `poteto/testing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add poteto/testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/poteto/testing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: poteto (https://skillmd.com/u/poteto)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/poteto/testing

---


# Testing

Test-driven by default. Prove the problem before solving it.

## Core Workflow: Bug First

1. **Reproduce** — Run the failing scenario and observe the actual behavior
2. **Write a failing test** — Minimal reproduction as a test case
3. **Commit the failing test** — Use `Skill(commit)` with message like `test: reproduce #issue-description`
4. **Fix the code** — Only now attempt the fix
5. **Verify** — Run `pnpm test` and confirm the test passes
6. **Commit the fix** — Separate commit from the test

This applies to all bug fixes. The failing test proves the bug exists and prevents regressions.

## Fixture Tests

Noodle uses directory-based fixtures in `testdata/`. Read [references/fixtures.md](references/fixtures.md) for full format, helper API, and code patterns.

### Creating a New Fixture

```sh
./scripts/scaffold-fixture.sh <package-dir> <fixture-name> [state-count]
```

Fill in the generated `input.json`/`input.ndjson` and `expected.md`, then:

```sh
pnpm fixtures:hash:sync
```

### Bug Fixtures

See [references/fixtures.md](references/fixtures.md) for full bug fixture format (frontmatter fields, expected error sections, and the fix workflow).

## Key Commands

| Command | Purpose |
|---------|---------|
| `pnpm test` | Run all tests |
| `pnpm test:short` | Skip integration tests |
| `pnpm check` | Full local CI (test + vet + lint + fixtures) |
| `pnpm bugs` | List fixtures marked as known bugs |
| `pnpm fixtures:loop` | Verify loop fixtures match expected |
| `pnpm fixtures:loop:record` | Regenerate loop fixture expected output |
| `pnpm fixtures:hash` | Verify fixture input hashes |
| `pnpm fixtures:hash:sync` | Update fixture input hashes |
| `pnpm vet` | Run `go vet` |
| `pnpm lint:arch` | Architecture lint (file sizes, legacy patterns) |

## Running Specific Tests

```sh
# Single package
go test ./loop

# Single test
go test ./loop -run TestLoopDirectoryFixtures

# Bypass cache
go test -count=1 ./parse

# With race detector
go test -race ./...

# Verbose
go test -v ./tui
```

## Integration Tests

Long-running or external-dependency tests use `testing.Short()`:

```go
if testing.Short() {
    t.Skip("skipping integration test in short mode")
}
```

`pnpm test:short` skips these. `pnpm test` runs everything.