Name: TFK-04-Build_Fixture_Library
Author: FeatureFactory-io

Prompt file imported from FeatureFactory-io/mimir (.windsurf/workflows/Edda/TFK/TFK-04-Build_Fixture_Library.md). Copyright stays with the author.

Activity: Build Fixture Library

Activity ID: 190 Order: 4 Phase: Elaboration Dependencies: Predecessor: Activity 189 (Build Step Library) Successor: Activity 191 (Wire CICD Integration)

Description

Build Fixture Library

Guidance

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

2. When to Use JSON vs FactoryBoy

Use JSON fixtures when...	Use FactoryBoy when...
Data is static reference data	Data needs to be parameterized per test
Loaded once per session (seed data)	Created dynamically with variations
Represents "the world as it is"	Represents "arrange" step of a specific test
Shared across many tests unchanged	Tests need unique data to avoid collisions

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.

Agent

None

Skill

Title: AutoFixture and FactoryBoy Patterns Capability Domain: Test Data Management Technology Stack: factory-boy, pytest-fixtures, django-orm

Rules

None

Artifacts Produced

Fixture Library Catalog (Document) - Required

Artifacts Consumed

SAO.md § Test Strategy (Document) - Required
Behave Configuration (Code) - Required

Notes

No additional notes.

Install TFK-04-Build_Fixture_Library and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Activity: Build Fixture Library **Activity ID**: 190 **Order**: 4 **Phase**: Elaboration **Dependencies**: Predecessor: Activity 189 (Build Step Library) Successor: Activity 191 (Wire CICD Integration) ## Description Build Fixture Library ## Guidance # 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 ``` ### 2. When to Use JSON vs FactoryBoy | Use JSON fixtures when... | Use FactoryBoy when... | |---------------------------|------------------------| | Data is static reference data | Data needs to be parameterized per test | | Loaded once per session (seed data) | Created dynamically with variations | | Represents "the world as it is" | Represents "arrange" step of a specific test | | Shared across many tests unchanged | Tests need unique data to avoid collisions | ### 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. ## Agent None ## Skill **Title**: AutoFixture and FactoryBoy Patterns **Capability Domain**: Test Data Management **Technology Stack**: factory-boy, pytest-fixtures, django-orm ## Rules None ## Artifacts Produced - **Fixture Library Catalog** (Document) - Required ## Artifacts Consumed - **SAO.md § Test Strategy** (Document) - Required - **Behave Configuration** (Code) - Required ## Notes No additional notes.

{ "prompt": "# Activity: Build Fixture Library\n\n**Activity ID**: 190\n**Order**: 4\n**Phase**: Elaboration\n**Dependencies**: Predecessor: Activity 189 (Build Step Library)\nSuccessor: Activity 191 (Wire CICD Integration)\n\n## Description\n\nBuild Fixture Library\n\n## Guidance\n\n# Build Fixture Library\n\n## Objective\n\nCreate 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.\n\n---\n\n## Process\n\n### 1. Fixture Organization\n\n```\ntests/fixtures/\n├── seed.json # Base data loaded once per session\n├── presets/\n│ ├── team_preset.json # A group with set of users with specific roles\n│ ├── project_preset.json # Project with workflows, activities, artifacts\n│ └── empty_preset.json # Clean slate for isolation tests\n├── factories/\n│ ├── user_factory.py # FactoryBoy user factory\n│ ├── model_factories.py # Domain model factories\n│ └── __init__.py\n└── autofixture/\n └── fixture_creator.py # AutoFixture helper\n```\n\n### 2. When to Use JSON vs FactoryBoy\n\n| Use JSON fixtures when... | Use FactoryBoy when... |\n|---------------------------|------------------------|\n| Data is static reference data | Data needs to be parameterized per test |\n| Loaded once per session (seed data) | Created dynamically with variations |\n| Represents \"the world as it is\" | Represents \"arrange\" step of a specific test |\n| Shared across many tests unchanged | Tests need unique data to avoid collisions |\n\n### 3. Fixture Scopes\n\n- **Session-level** (`seed.json`): loaded once via `loaddata` in `before_all`\n- **Suite-level** (`presets/`): loaded for a specific group of related tests\n- **Test-level** (FactoryBoy): created per test function, rolled back after\n\n### 4. AutoFixture Support\n\nFor lazy fixture creation — create model instances with sensible random defaults when you don't care about specific field values.\n\n## Agent\n\nNone\n\n## Skill\n\n**Title**: AutoFixture and FactoryBoy Patterns\n**Capability Domain**: Test Data Management\n**Technology Stack**: factory-boy, pytest-fixtures, django-orm\n\n## Rules\n\nNone\n\n## Artifacts Produced\n\n- **Fixture Library Catalog** (Document) - Required\n\n## Artifacts Consumed\n\n- **SAO.md § Test Strategy** (Document) - Required\n- **Behave Configuration** (Code) - Required\n\n## Notes\n\nNo additional notes.", "variables": [], "notes": "Build Fixture Library", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/FeatureFactory-io/mimir", "path": ".windsurf/workflows/Edda/TFK/TFK-04-Build_Fixture_Library.md", "ref": "850a123927f83a3ed209f39a5a3590bfe21aeb92", "url": "https://github.com/FeatureFactory-io/mimir/blob/850a123927f83a3ed209f39a5a3590bfe21aeb92/.windsurf/workflows/Edda/TFK/TFK-04-Build_Fixture_Library.md", "key": "FeatureFactory-io/mimir/.windsurf/workflows/Edda/TFK/TFK-04-Build_Fixture_Library.md" } } }

TFK-04-Build_Fixture_Library

About

Activity: Build Fixture Library

Description

Guidance

Build Fixture Library

Objective

Process

1. Fixture Organization

2. When to Use JSON vs FactoryBoy

3. Fixture Scopes

4. AutoFixture Support

Agent

Skill

Rules

Artifacts Produced

Artifacts Consumed

Notes

Install TFK-04-Build_Fixture_Library and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews