Recurring report delivery browser journey

Verification Boundary

The browser drives the configured console and the file’s application fixtures. The checks use the configured development services and the suite’s own records.

What This Suite Proves

The file asserts the visible outcomes of its recurring report delivery browser journey. Acceptance bindings below name only corresponding specification examples; other assertions remain executable engineering evidence.

What It Does Not Prove

The file does not establish every service invariant or a passing result at the pinned revision.

Real Dependencies and Test Doubles

The configured console, application APIs and run-owned records supply the journey. Imported fixture helpers supply personas, setup and cleanup; the evidence references identify the exact file boundary.

Must Not Be Doubled

Keep the browser actions and the API readback used to verify this journey intact. Adding intercepted success responses changes the verification boundary and requires revisiting the bindings.