Configuration Journey 0026 browser suite

Verification Boundary

The browser exercises the deployed console and development services. The suite retains its existing prerequisites, optional skips and run ownership.

What This Suite Proves

The individual assertion references identify the acceptance outcomes this file exercises. When a scenario spans several suites, this file supplies only its listed assertions; qualification must include the other bindings and any recorded coverage finding.

What It Does Not Prove

A successful browser run does not prove unvisited API paths or unasserted financial outcomes. Conditional skips do not count as acceptance proof. No result is claimed for the pinned revision until the suite runs and its evidence is reviewed.

Real Dependencies and Test Doubles

The console, browser session and called development APIs are real. The suite uses its existing credentials, seed routines and cleanup helpers.

Must Not Be Doubled

The console actions and acceptance assertions must reach their stated development APIs. Replacing those APIs with response handlers changes this suite’s verification boundary.