Implement Feature Acceptance Tests

APPEND TO GUIDANCE:

TFK Integration: Behave-Based Acceptance Tests

Feature acceptance tests are executed via behave-django against .feature files in docs/features/ (spec + AT runner — single source of truth). There is no separate tests/acceptance/ tree and no promote/copy step.

Updated Process

1. Locate spec: Find the feature's BDD scenarios in docs/features/act-*/.
2. Verify steps exist: Check that all steps used in the spec have implementations in docs/features/steps/. If any are missing, invoke TFK-07.
3. Remove @wip when ready: Tag unimplemented scenarios @wip during ESM; remove the tag when implementation is complete so CI runs them (behave.ini uses tags = ~@wip).
4. Prepare fixtures: Check the Fixture Library Catalog for needed test data. If presets are missing, invoke TFK-07.
5. Run acceptance tests: make test-at (runs docs/features/ via behave.ini).
6. The dual approach remains: Django test client unit/integration tests remain valuable for fast feedback. Behave AT runs the same scenarios through the BDD layer. Both must pass.

Key Principle

Acceptance tests are the real thing minus the GUI (Django test client — not Playwright). No mocking. The .feature file in docs/features/ IS the grounding executable requirements document for AT.

Skills (additional)

• Behave-Django BDD Runner (BDD_RUNNER)

Inputs (additional)

• Step Library Catalog (Document, Required) — produced by TFK-03.
• Fixture Library Catalog (Document, Required) — produced by TFK-04.
• Behave Configuration (Code, Required) — produced by TFK-02 (Artifact #51).

TFK Integration: Behave-Based Acceptance Tests

Feature acceptance tests are executed via behave-django against .feature files in docs/features/ (spec + AT runner — single source of truth). There is no separate tests/acceptance/ tree and no promote/copy step.

Updated Process

1. Locate spec: Find the feature's BDD scenarios in docs/features/act-*/.
2. Verify steps exist: Check that all steps used in the spec have implementations in docs/features/steps/. If any are missing, invoke TFK-07.
3. Remove @wip when ready: Tag unimplemented scenarios @wip during ESM; remove the tag when implementation is complete so CI runs them (behave.ini uses tags = ~@wip).
4. Prepare fixtures: Check the Fixture Library Catalog for needed test data. If presets are missing, invoke TFK-07.
5. Run acceptance tests: make test-at (runs docs/features/ via behave.ini).
6. The dual approach remains: Django test client unit/integration tests remain valuable for fast feedback. Behave AT runs the same scenarios through the BDD layer. Both must pass.

Key Principle

Acceptance tests are the real thing minus the GUI (Django test client — not Playwright). No mocking. The .feature file in docs/features/ IS the grounding executable requirements document for AT.

TFK boundary: AT (user-visible) vs @agent_proof pytest

Do not express agent orchestration proofs as Behave scenarios.

Rules:
- AT proves what the user sees — forms, redirects, ChangeSet approval UI, error messages.
- @agent_proof proves what the agent loop did under CAP-004 ScriptedLLM — trace beats via assert_agent_story, not chat prose assertions in Gherkin.
- When a feature touches both surfaces, BPE-04 adds/updates .feature scenarios and BPE-02 (or the agent slice) adds @agent_proof tests — both green before DoD; neither substitutes for the other.
- Skip @agent_proof rows in BPE-04 when SAO §17 is N/A.

Skills (additional)

• Behave-Django BDD Runner (BDD_RUNNER)
• Agent Integration Proof Patterns (TEST_INTEGRATION) — when SAO §17 in scope; AT does not replace this skill

Inputs (additional)

• Step Library Catalog (Document, Required) — produced by TFK-03.
• Fixture Library Catalog (Document, Required) — produced by TFK-04.
• Behave Configuration (Code, Required) — produced by TFK-02 (Artifact #51).
• Agent Proof Table (from BPE-01 Section G, when SAO §17) — PRF rows map to pytest, not .feature files.