Build Fixture Library

Objective

Create a shared library of test fixtures at multiple scopes (session, suite, test) using both JSON fixtures and FactoryBoy. Establish patterns for context passing, AutoFixture support, and fixture presets.

Process

1. Fixture Organization

tests/fixtures/
├── seed.json                # Base data loaded once per session
├── presets/
│   ├── team_preset.json     # A group with set of users with specific roles
│   ├── project_preset.json  # Project with workflows, activities, artifacts
│   └── empty_preset.json    # Clean slate for isolation tests
├── factories/
│   ├── user_factory.py      # FactoryBoy user factory
│   ├── model_factories.py   # Domain model factories
│   └── __init__.py
├── autofixture/
│   └── fixture_creator.py   # AutoFixture helper
├── llm_scripts/             # Lane 1 — ScriptedLLM queues (when SAO §17 applies)
│   └── <prf-id>/
│       ├── happy.json
│       └── reject_*.json
└── agent_tasks/             # Lane 4 — frozen TASK-* corpora (when SAO §17 applies)
    └── <task-id>/
        ├── input/
        ├── expected.yaml
        └── meta.yaml

2. When to Use JSON vs FactoryBoy

3. Fixture Scopes

• Session-level (seed.json): loaded once via loaddata in before_all
• Suite-level (presets/): loaded for a specific group of related tests
• Test-level (FactoryBoy): created per test function, rolled back after

4. AutoFixture Support

For lazy fixture creation — create model instances with sensible random defaults when you don't care about specific field values.

Idempotent behave Given Steps (Background + scenario)

When a feature file uses Background: to seed reference entities and scenarios add their own Given steps for the same natural keys (slug, code, username, composite unique):

1. Step definitions MUST use get_or_create or update-in-place — never blind Model.objects.create() for keys Background may already insert.
2. Document in the Step Library Catalog which Givens are idempotent vs create-only.
3. On IntegrityError during AT, first suspect double-seeding — fix the step, not the scenario order.

Reference: Skill 45 Pattern 5 (Behave-Django BDD Runner).

Fixture Library Catalog — agent eval entries

When SAO §17 applies, extend the Fixture Library Catalog with two agent-specific roots. Skip catalog rows when §17 is N/A.

llm_scripts/<prf-id>/ (lane 1 — PRF integration proof)

File shape: ordered JSON array of LLM response strings or objects consumed by CAP-004 ScriptedLLM. Reject variants must exhaust the queue with an explicit error — never silent empty fallback (see TFK-08).

agent_tasks/<task-id>/ (lane 4 — TASK golden eval)

Oracle schema (expected.yaml / meta.yaml):

Document dependencies (seed preset, factory hooks) in catalog notes. TFK-07 adds new rows when BPE/MIN introduces a PRF script or TASK golden not yet cataloged.