---
id: TST-CRM-DQ-178
title: Data quality layout
kind: browser-lifecycle
product_area: crm
module: data-quality
revision: 1
status: draft
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  rhythm-v2-docs: 61315bb0538e230286687677da2b04b1d33f162b
repository: react-console
files:
  - e2e/layout/data-quality.spec.ts
implements: []
environment: mock
command: >-
  npx playwright test -c playwright.layout.config.ts e2e/layout/data-quality.spec.ts
  --workers=1
gate: This is the layout tier and establishes visual behavior only.
implementation_state: implemented
implementation_evidence: observed
latest_result: not-run
conformance: not-verified
estimated_minutes: 30
isolation: >-
  Each browser context uses layout fixtures; this selection does not create or delete
  deployed records.
retries: none
proves_controls: []
evidence:
  - provenance: test
    source:
      - 'react-console:e2e/layout/data-quality.spec.ts'
  - provenance: documented
    source: 'rhythm-v2-docs:specs/CONVENTIONS.md#10.6 Executable Test Suite'
lifecycles:
  create: not-exercised
  change: not-exercised
  archive: not-applicable
  delete: not-exercised
  merge: not-exercised
  reconcile: not-applicable
lifecycle_gaps:
  - FND-CRM-DQ-074
lifecycle_notes:
  create: >-
    Opening a mocked merge workspace is setup for measuring layout, not a checked
    plan-creation outcome.
  change: Navigation and viewport changes do not assert a persisted business change.
  archive: Ordinary record archiving belongs to Entities and is outside the layout selection.
  delete: No record cleanup or deletion outcome is asserted.
  merge: Rendering a merge page does not submit and verify an identity combination.
  reconcile: Background recovery is outside this visual selection.
---

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