Build Step Library

Objective

Create a reusable library of Gherkin step definitions that ESM can compose scenarios from when the library already exists. The library grows over time — initial seed covers generic patterns, project-specific steps are added via TFK-07 as needed.

Same phrases, different engines: AT steps in docs/features/steps/ use the Django test client. E2E counterparts in tests/e2e/steps/ use Playwright. Gherkin vocabulary is shared via the Step Library Catalog; implementations are not merged into one module.

Process

1. Organize Steps by Domain

docs/features/steps/          # AT — Django test client
├── navigation_steps.py
├── form_steps.py
├── table_steps.py
├── auth_steps.py
├── assertion_steps.py
├── dialog_steps.py
├── common_steps.py
└── __init__.py

tests/e2e/steps/              # E2E — Playwright-backed counterparts

2. Generic Step Patterns

Navigation:
- Given {user} is on the "{page_name}" page
- When {user} navigates to "{url}"
- Then {user} should see the "{page_name}" page

Forms:
- When {user} enters "{value}" into "{field}"
- When {user} selects "{option}" from "{dropdown}"
- When {user} clicks "{button}"
- When {user} submits the form

Tables:
- Then {user} sees table "{table_name}" with {n} rows
- Then the table "{table_name}" should contain "{text}"
- When {user} sorts table "{table_name}" by "{column}"

Auth:
- Given {user} is logged in as "{role}"
- Given {user} is not authenticated

Assertions:
- Then {user} should see "{text}"
- Then {user} should not see "{text}"
- Then the element "{test_id}" should be visible

3. Step Implementation Conventions

• All steps use data-testid selectors for element targeting
• Parameterize generically — avoid hardcoding entity names
• Log actions at INFO level
• Add module-level docstring listing all steps

Agent proofs vs AT

Footnote — do not add PRF/TASK scenarios to the Gherkin Step Library.

PRF- integration proofs (lane 1) and TASK- golden evals (lane 4) are pytest integration tests**, not behave AT scenarios. They live under tests/integration/agent/ and use assert_agent_story / structured oracles — not docs/features/steps/.

When BPE or MIN declares agent_proof_command or checkpoint.agent_proof_command, implement pytest tests — do not invent Gherkin phrases for tool-call traces or blackboard state. Reuse AT steps only for human-facing GUI journeys; agent control-plane behavior belongs in lane 1/2 pytest per artifact 56 Part 4.5.

TFK-07 may still add fixtures (llm_scripts/, agent_tasks/) when a PRF script or TASK golden is missing — that is fixture catalog work, not step library work.