Implement Journey Certification Tests

APPEND TO GUIDANCE:

TFK Integration: E2E Infrastructure

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

E2E vs AT (clarification)

• 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.

Using TFK E2E Infrastructure

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

Inputs (additional)

• E2E Test Configuration (Code, Required) — produced by TFK-06.
• Fixture Library Catalog (Document, Required) — produced by TFK-04.

TFK Integration: E2E Infrastructure

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

E2E vs AT (clarification)

• 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.

Using TFK E2E Infrastructure

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

Inputs (additional)

• E2E Test Configuration (Code, Required) — produced by TFK-06.
• Fixture Library Catalog (Document, Required) — produced by TFK-04.

Responsive Viewport Certification

Use the viewport matrix and Screen ID-to-recipe coverage table from docs/ux/IA_guidelines.md as executable test input.

1. Parameterize Playwright browser contexts with every required CSS-pixel viewport profile.
2. Exercise each journey screen at every profile. Shared recipe assertions may be reused across screens, but the coverage report must show every Screen ID/profile pair.
3. Assert the universal IA outcomes: no unintended page-level horizontal overflow; no clipped or overlapping essential content; coherent stacking and focus order; reachable navigation and primary action; intentional overflow contained by its component; and correct low-height or full-viewport behavior.
4. Add focused assertions for every screen-specific responsive scenario from ESM-05.
5. Capture a screenshot after the responsive layout has settled at each Screen ID/profile pair. Mask or stabilize volatile content according to the test architecture.
6. Produce a responsive evidence manifest containing Screen ID, recipe, profile, viewport dimensions, assertion result, and screenshot path.

Do not certify responsiveness from a single default browser context. A screenshot alone is review evidence, not a substitute for layout assertions; assertions alone are not a substitute for human visual review of the required evidence set.