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

Activity: Add Step and/or Fixture to Library

Name: TFK-07-Add_Step_andor_Fixture_to_Library
Author: FeatureFactory-io

Activity ID: 193 Order: 7 Phase: Construction Dependencies: Predecessor: Activity 192 (Establish E2E Infrastructure) Successor: Activity 194 (Validate Test Health)

Description

Add Step and/or Fixture to Library

Guidance

Add Step and/or Fixture to Library

Objective

On-demand activity invoked when ESM-05 "Write Feature Files" or BPE cannot assemble a scenario from existing steps/fixtures. Creates new reusable step definitions and/or fixtures following library conventions, then updates the catalogs.

Trigger

Called by other workflows when:

ESM-05 is writing a .feature and cannot find a matching step in the Step Library
BPE-04 needs a fixture preset that doesn't exist
A new domain area requires new step patterns

Process

1. Assess What's Needed

Identify the gap: missing step pattern, missing fixture, or both
Check if an existing step can be generalized/parameterized instead of creating a new one

2. Create Step Definition (if needed)

Follow library conventions:

Place in appropriate domain file (navigation, forms, tables, auth, assertions)
Use data-testid selectors
Parameterize generically
Log actions at INFO level

3. Create Fixture (if needed)

Follow library conventions:

JSON for static reference data → tests/fixtures/presets/
FactoryBoy for dynamic data → tests/fixtures/factories/
Document scope and dependencies

4. Update Catalogs

Add new step to Step Library Catalog
Add new fixture to Fixture Library Catalog

5. Verify

Write a small test scenario using the new step/fixture
Run it to verify it works
Ensure existing tests are not broken

Agent

None

Skill

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

Title: Gherkin Step Library Patterns Capability Domain: BDD Step Engineering Technology Stack: gherkin, behave, step-definitions

Rules

None

Artifacts Produced

None

Artifacts Consumed

Behave Configuration (Code) - Required
Step Library Catalog (Document) - Required
Fixture Library Catalog (Document) - Required
E2E Test Configuration (Code) - Required

Notes

No additional notes.

# Activity: Add Step and/or Fixture to Library **Activity ID**: 193 **Order**: 7 **Phase**: Construction **Dependencies**: Predecessor: Activity 192 (Establish E2E Infrastructure) Successor: Activity 194 (Validate Test Health) ## Description Add Step and/or Fixture to Library ## Guidance # Add Step and/or Fixture to Library ## Objective On-demand activity invoked when ESM-05 "Write Feature Files" or BPE cannot assemble a scenario from existing steps/fixtures. Creates new reusable step definitions and/or fixtures following library conventions, then updates the catalogs. --- ## Trigger Called by other workflows when: 1. ESM-05 is writing a .feature and cannot find a matching step in the Step Library 2. BPE-04 needs a fixture preset that doesn't exist 3. A new domain area requires new step patterns ## Process ### 1. Assess What's Needed - Identify the gap: missing step pattern, missing fixture, or both - Check if an existing step can be generalized/parameterized instead of creating a new one ### 2. Create Step Definition (if needed) Follow library conventions: - Place in appropriate domain file (navigation, forms, tables, auth, assertions) - Use `data-testid` selectors - Parameterize generically - Log actions at INFO level ### 3. Create Fixture (if needed) Follow library conventions: - JSON for static reference data → `tests/fixtures/presets/` - FactoryBoy for dynamic data → `tests/fixtures/factories/` - Document scope and dependencies ### 4. Update Catalogs - Add new step to Step Library Catalog - Add new fixture to Fixture Library Catalog ### 5. Verify - Write a small test scenario using the new step/fixture - Run it to verify it works - Ensure existing tests are not broken ## Agent None ## Skill **Title**: AutoFixture and FactoryBoy Patterns **Capability Domain**: Test Data Management **Technology Stack**: factory-boy, pytest-fixtures, django-orm **Title**: Gherkin Step Library Patterns **Capability Domain**: BDD Step Engineering **Technology Stack**: gherkin, behave, step-definitions ## Rules None ## Artifacts Produced None ## Artifacts Consumed - **Behave Configuration** (Code) - Required - **Step Library Catalog** (Document) - Required - **Fixture Library Catalog** (Document) - Required - **E2E Test Configuration** (Code) - Required ## Notes No additional notes.

{ "prompt": "# Activity: Add Step and/or Fixture to Library\n\n**Activity ID**: 193\n**Order**: 7\n**Phase**: Construction\n**Dependencies**: Predecessor: Activity 192 (Establish E2E Infrastructure)\nSuccessor: Activity 194 (Validate Test Health)\n\n## Description\n\nAdd Step and/or Fixture to Library\n\n## Guidance\n\n# Add Step and/or Fixture to Library\n\n## Objective\n\nOn-demand activity invoked when ESM-05 \"Write Feature Files\" or BPE cannot assemble a scenario from existing steps/fixtures. Creates new reusable step definitions and/or fixtures following library conventions, then updates the catalogs.\n\n---\n\n## Trigger\n\nCalled by other workflows when:\n1. ESM-05 is writing a .feature and cannot find a matching step in the Step Library\n2. BPE-04 needs a fixture preset that doesn't exist\n3. A new domain area requires new step patterns\n\n## Process\n\n### 1. Assess What's Needed\n\n- Identify the gap: missing step pattern, missing fixture, or both\n- Check if an existing step can be generalized/parameterized instead of creating a new one\n\n### 2. Create Step Definition (if needed)\n\nFollow library conventions:\n- Place in appropriate domain file (navigation, forms, tables, auth, assertions)\n- Use `data-testid` selectors\n- Parameterize generically\n- Log actions at INFO level\n\n### 3. Create Fixture (if needed)\n\nFollow library conventions:\n- JSON for static reference data → `tests/fixtures/presets/`\n- FactoryBoy for dynamic data → `tests/fixtures/factories/`\n- Document scope and dependencies\n\n### 4. Update Catalogs\n\n- Add new step to Step Library Catalog\n- Add new fixture to Fixture Library Catalog\n\n### 5. Verify\n\n- Write a small test scenario using the new step/fixture\n- Run it to verify it works\n- Ensure existing tests are not broken\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**Title**: Gherkin Step Library Patterns\n**Capability Domain**: BDD Step Engineering\n**Technology Stack**: gherkin, behave, step-definitions\n\n## Rules\n\nNone\n\n## Artifacts Produced\n\nNone\n\n## Artifacts Consumed\n\n- **Behave Configuration** (Code) - Required\n- **Step Library Catalog** (Document) - Required\n- **Fixture Library Catalog** (Document) - Required\n- **E2E Test Configuration** (Code) - Required\n\n## Notes\n\nNo additional notes.", "variables": [], "notes": "Add Step and/or Fixture to Library", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/FeatureFactory-io/mimir", "path": ".windsurf/workflows/Edda/TFK/TFK-07-Add_Step_andor_Fixture_to_Library.md", "ref": "a296e3cc7f28111e89a3d1ca0d3709a1f16f7a2b", "url": "https://github.com/FeatureFactory-io/mimir/blob/a296e3cc7f28111e89a3d1ca0d3709a1f16f7a2b/.windsurf/workflows/Edda/TFK/TFK-07-Add_Step_andor_Fixture_to_Library.md", "key": "FeatureFactory-io/mimir/.windsurf/workflows/Edda/TFK/TFK-07-Add_Step_andor_Fixture_to_Library.md" } } }

TFK-07-Add_Step_andor_Fixture_to_Library

About

Activity: Add Step and/or Fixture to Library

Description

Guidance

Add Step and/or Fixture to Library

Objective

Trigger

Process

1. Assess What's Needed

2. Create Step Definition (if needed)

3. Create Fixture (if needed)

4. Update Catalogs

5. Verify

Agent

Skill

Rules

Artifacts Produced

Artifacts Consumed

Notes

Use it

Manifest

Reviews