tdd

Estrellas4

Forks0

Actualizado6 de julio de 2026 a las 10:43

Test-driven development with vertical tracer-bullet slices. Use when building test-first, red-green-refactor, or when the user mentions TDD.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

stainless-code

stainless-code/persist

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

name	tdd
description	Test-driven development with vertical tracer-bullet slices. Use when building test-first, red-green-refactor, or when the user mentions TDD.

Test-driven development

Vertical RED→GREEN cycles — one behavior per loop, not horizontal "all tests then all code". Aligns with tracer-bullets and verify-after-each-step.

This repo

Runner split per docs/architecture.md § Test matrix:
- bun test <co-located *.test.ts> — src/** unit tests (core, codecs, backends, TanStack adapters, useHydrated SSR/snapshot contracts). No DOM.
- bun run test:dom — tests-dom/**/*.test.tsx (vitest + jsdom + @testing-library/react) for useHydrated rerender / unmount / useSyncExternalStore reactivity.
Co-locate tests next to the module (src/core/persist-core.ts → src/core/persist-core.test.ts).
After each GREEN: format/lint/typecheck per verify-after-each-step.
Mock at the storage backend seam (StateStorage), never inside persist-core or a codec. See PATTERNS.md.

Workflow

1. Planning

Confirm behaviors to test (not implementation steps) with the user. Prefer deep modules — small public surface (persistSource, createStorage, a codec factory), complex internals.

2. Tracer bullet (within slice)

RED:   one test for first behavior → bun test <file>   (or test:dom for hydration rerenders)
GREEN: minimal code to pass → re-run

3. Incremental loop

For each behavior: RED → GREEN → run affected tests. One test at a time; no speculative features.

4. Refactor

After GREEN — look for duplication, long methods, shallow modules, feature envy. Run bun test <file> after each step. Never refactor while RED. For production polish on a completed slice, harden-pr lite may run in parallel with tracer-bullet commits.

Checklist per cycle

[ ] Test describes behavior, not implementation
[ ] Test uses the public seam only (persistSource / createStorage / a codec / useHydrated)
[ ] Test would survive an internal refactor
[ ] Code is minimal for this test
[ ] bun test (or test:dom) passes on touched file(s)

Reference

Good/bad test patterns + mock boundaries: PATTERNS.md
Slice cadence: tracer-bullets · Verify: verify-after-each-step

Más de este repositorio

mismo repositorio

alpine-persist

stainless-code/persist

Gate Alpine.js UI on Persist hydration (Alpine.plugin + useHydrated / $hydrated). Use when wiring HydrationSignal into Alpine data components.

2026-07-234

angular-persist

stainless-code/persist

Gate Angular UI on Persist hydration with useHydrated (readonly Signal). Call inside an injection context; use when avoiding flash of default state on async backends.

2026-07-234

lit-persist

stainless-code/persist

Gate Lit element UI on Persist hydration with HydrationController. Use when wiring HydrationSignal into a ReactiveControllerHost; not a hook.

2026-07-234

persist-async-storage

stainless-code/persist

Persist with React Native AsyncStorage via @stainless-code/persist/backends/async-storage. Use for RN string-wire JSON state; always gate with useHydrated.

2026-07-234

persist-compressed

stainless-code/persist

Compress a string-wire StateStorage with @stainless-code/persist/backends/compressed (gzip/deflate). Backend wrapper — compose with createStorage; stack compress-then-encrypt.

2026-07-234

persist-crosstab

stainless-code/persist

Cross-tab sync for backends without storage events via @stainless-code/persist/transport/crosstab (createBroadcastCrossTab). Wrap storage + pass crossTabEventTarget; call close() on teardown.

2026-07-234

Test-driven development

Vertical RED→GREEN cycles — one behavior per loop, not horizontal "all tests then all code". Aligns with tracer-bullets and verify-after-each-step.

This repo

Runner split per docs/architecture.md § Test matrix:

bun test <co-located *.test.ts> — src/** unit tests (core, codecs, backends, TanStack adapters, useHydrated SSR/snapshot contracts). No DOM.
bun run test:dom — tests-dom/**/*.test.tsx (vitest + jsdom + @testing-library/react) for useHydrated rerender / unmount / useSyncExternalStore reactivity.

Co-locate tests next to the module (src/core/persist-core.ts → src/core/persist-core.test.ts).

After each GREEN: format/lint/typecheck per verify-after-each-step.

Mock at the storage backend seam (StateStorage), never inside persist-core or a codec. See PATTERNS.md.

Workflow

1. Planning

Confirm behaviors to test (not implementation steps) with the user. Prefer deep modules — small public surface (persistSource, createStorage, a codec factory), complex internals.

2. Tracer bullet (within slice)

RED: one test for first behavior → bun test <file> (or test:dom for hydration rerenders) GREEN: minimal code to pass → re-run

3. Incremental loop

For each behavior: RED → GREEN → run affected tests. One test at a time; no speculative features.

4. Refactor

Checklist per cycle

[ ] Test describes behavior, not implementation [ ] Test uses the public seam only (persistSource / createStorage / a codec / useHydrated) [ ] Test would survive an internal refactor [ ] Code is minimal for this test [ ] bun test (or test:dom) passes on touched file(s)

Reference