Data quality layout

Verification Boundary

A real browser renders the console using mock records and responses. The selection measures six data-quality and merge screens at wide viewports.

What This Suite Proves

Each screen declares full page width. Screens with spanning content must fill the workspace; the centered merge-list notice instead must avoid horizontal overflow. The largest viewport also produces a screenshot.

What It Does Not Prove

The checks establish page geometry. They do not verify persisted decisions, authorization, completed merges or background recovery, and no capability scenario is assigned to this register.

Level and Rationale

Rendered widths and overflow require a browser. API assertions cannot establish how content occupies the available workspace.

Lifecycle Coverage

Creation, change, deletion and merge receive no lifecycle credit. Opening pages and a mocked merge workspace supplies the layout under measurement; the assertions do not establish business state changes. The lifecycle finding preserves the missing proof obligations.

Real Dependencies and Test Doubles

Browser rendering and the console layout components are real. The layout project supplies mock data and responses, so the service and database are outside the verification boundary.

Must Not Be Doubled

Keep the page layout, rendered content and geometry measurement real. Replacing them would bypass the behavior these checks measure.

Fixtures and Isolation

Each browser context uses the layout fixtures and selected viewport. No deployed record creation, shared rule change or service cleanup is needed for this selection.

Determinism and Retries

The tests settle the page before measuring it and use fixed viewport dimensions. This examination records no execution result; any future run must report failures without treating a screenshot as lifecycle proof.

How It Runs

Use the layout Playwright configuration and the single-worker selection recorded in frontmatter from the console repository. The project must supply its console build and mock environment.

Coverage Gaps

The layout selection remains unmapped to capability scenarios. Its lifecycle finding records the absent business-state assertions; a separate suite must establish those outcomes.