Knowledge · Rules · Development

Fixture Management

Test fixture creation, location, format, naming, and cross-cutting reuse across all test types

Tags

rule

Overview

Purpose

Test fixture creation, location, format, naming, and cross-cutting reuse across all test types

Rules

FIX-001:

Go testdata/ is language-level convention. Svelte uses fixtures/ by community convention.

FIX-002:

YAML is the workspace standard format. Type header enables indexing.

FIX-003:

Predictable naming enables automation and discovery.

FIX-004:

Input = what to feed, expected = what to verify. Dual structure enables assertion.

FIX-005:

Inline strings drift from fixture files. Single source of truth.

FIX-006:

Tags enable filtering — unit tests load unit-tagged fixtures, e2e loads e2e-tagged.

FIX-007:

Specification by Example: examples define expected behavior upfront.

FIX-008:

Test Data Builder pattern (Meszaros). Go functional options variant also acceptable.

FIX-009:

Enables curl verification: POST input, compare status + body against expected.

FIX-010:

ISO 29119-4 test design techniques: equivalence partitioning + boundary values.