Implement Journey Certification Tests

BPE-5 Order: #5 Construction Has Dependencies

Updated 2 months ago

APPEND TO GUIDANCE:

TFK Integration: E2E Infrastructure

Journey certification tests that require browser-based Playwright execution use TFK's E2E infrastructure under tests/e2e/.

AT (BPE-04): Proves one particular feature works. docs/features/ via Django test client (behave --simple). Fast. Every CI run.
E2E (BPE-05): Proves the ability to fulfill a goal using system means. tests/e2e/ via Playwright + LiveServer. Sequential. Screenshots. Staging / release certification.

Same Gherkin phrases (catalog); separate step implementations and environment.py.

Locate journey intent: Read docs/features/user_journey.md for the multi-screen goal.
Write E2E .feature: Add journey scenarios to tests/e2e/ (optionally tag @e2e).
Write as multi-phase .feature: One long sequential .feature file with multiple scenarios.
Environment targeting: Use --base-url to point at any environment.
Screenshots: tests/e2e/environment.py automatically captures screenshots after every step.
Data preparation: E2E tests use --db-uri to load initial data via loaddump.
Run: make test-e2e → manage.py behave tests/e2e/.

Interactive, feature-by-feature AI-assisted development. Use BPE after ESM, DTA, DSP, and BSP are complete to build one feature spec at …

Cautious Developer Agent Guide Motto: "Code that's easy to prove correct is code that works" …

Feature Files Document Required
Produced by: Write Feature Files
Implementation Plan Template Document Required
Produced by: Plan Feature
Screen Flow / Dialogue Map Diagram Required
Produced by: Create Dialogue Maps

No output artifacts