Layout QA

Layout QA is a browser QA protocol and runner for frontend changes. It runs deterministic flows against a local or CI-served URL, captures screenshots at meaningful checkpoints, checks browser health, and writes a static HTML report.

The core loop is intentionally local:

npx @trylayout/qa init
npx @trylayout/qa run --target-url http://localhost:5173 --scenario happy_path --open
npx @trylayout/qa run --target-url http://localhost:5173 --scenario happy_path --viewport 390x844 --open

No account, upload, hosted service, or external docs are required.

Example Report

Package names:

• Canonical npm package: @trylayout/qa
• Convenience npm alias: layout-qa
• CLI binaries: trylayout and layout-qa

These commands are equivalent:

npx @trylayout/qa run --target-url http://localhost:5173 --scenario happy_path --open
npx layout-qa run --target-url http://localhost:5173 --scenario happy_path --open

Why This Exists

Frontend agents and developers can move faster when they have a visual feedback loop they can run themselves. Layout gives the repo a small protocol:

• Wire deterministic API/auth responses behind a QA env flag such as LAYOUT_QA=1 or VITE_LAYOUT_QA=1.
• Switch response states with localStorage["layout.qa.scenario"].
• Declare high-value browser flows in .layout/qa.json.
• Run the CLI locally or in GitHub Actions and inspect the generated screenshots/report.

The goal is not to replace Playwright. The goal is to make the browser QA loop simple enough for a team or coding agent to run before frontend changes merge.

Install

Use it directly with npx:

npx @trylayout/qa run --target-url http://localhost:5173

The package is also available under the unscoped alias layout-qa for agents and tools that infer the package name from this repository:

npx layout-qa run --target-url http://localhost:5173

Or install it in a project:

npm install --save-dev @trylayout/qa
npx trylayout run --target-url http://localhost:5173

The package uses Playwright. If your environment does not already have Chromium installed for Playwright, run:

npx playwright install chromium

Quick Start

Create a starter flow manifest:

npx @trylayout/qa init

Start your app with whatever QA flag your project uses:

LAYOUT_QA=1 VITE_LAYOUT_QA=1 npm run dev

Run a scenario:

npx @trylayout/qa run \
  --target-url http://localhost:5173 \
  --scenario happy_path \
  --open

Each run writes:

.layout/runs/<timestamp-scenario-viewport>/
  index.html
  result.json
  screenshots/
    01-<step>.jpg
    final.jpg

The process exits 0 on pass and 1 on failure, so the same command can run in CI.

Commands

trylayout init [options]
trylayout run --target-url <url> [options]
layout-qa run --target-url <url> [options]

Options:

--target-url <url>     URL of the running frontend to test.
--scenario <name>      Scenario to activate. Defaults to happy_path.
--flows <path>         Flow manifest path. Defaults to .layout/qa.json.
--out <path>           Artifact directory. Defaults to .layout/runs.
--viewport <value>     Viewport preset or size. Use desktop, tablet, mobile, or WIDTHxHEIGHT. Defaults to desktop.
--timeout <ms>         Browser run timeout. Defaults to 60000.
--headed               Show the browser instead of running headless.
--open                 Open the generated local HTML report after the run.
--json                 Print machine-readable JSON.
--upload-url <url>     Upload completed run JSON/screenshots to Layout.
--upload-token <token> Project upload token for hosted Layout reports.
--repo <name>          Repository full name, e.g. owner/repo.
--branch <name>        Branch name for report metadata.
--commit-sha <sha>     Commit SHA for report metadata.
--pr-number <number>   Pull request number for report metadata.
--run-source <value>   local or github_actions. Defaults from environment.
--force                Overwrite an existing flow file during init.

Flow Manifest

Default path: .layout/qa.json.

{
  "version": 1,
  "baseUrl": "$LAYOUT_BASE_URL",
  "viewports": ["desktop"],
  "flows": [
    {
      "id": "workspace_smoke",
      "label": "Workspace smoke",
      "scenarios": ["happy_path"],
      "steps": [
        {"visit": "/"},
        {"screenshot": "Workspace loaded", "expect": {"text": ["Dashboard"]}},
        {"click": "[data-layout-qa='open-settings']"},
        {"screenshot": "Settings open", "expect": {"text": ["Settings"]}}
      ]
    }
  ]
}

Top-level fields:

• version: currently 1.
• baseUrl: optional reference value for hosted/CI integrations. The CLI still uses --target-url as the source of truth.
• viewports: optional default viewport labels for hosted/CI integrations.
• flows: array of flow definitions.

Flow fields:

• id: stable machine-readable flow id.
• label: human-readable report title.
• scenarios: scenario names this flow can run against. Use an empty array to allow all scenarios.
• steps: ordered browser steps.

Step fields:

• id: stable machine-readable step id.
• type: explicit step type for advanced steps.
• label: optional human-readable report label.
• screenshot: set true to capture a screenshot after the step.
• expect: optional assertions attached to a step.
• timeoutMs: optional per-step timeout.
• tolerance: optional pixel tolerance for layout assertions.
• minWidth, maxWidth, minHeight, maxHeight: optional assert_box constraints.

Supported shorthand steps:

• {"visit": "/path"}: navigate to a path.
• {"click": "[data-layout-qa='action']"}: click a selector. If the string does not look like a selector, it is treated as visible text.
• {"screenshot": "Human label"}: capture a screenshot checkpoint.

Supported explicit step types:

• goto: navigate to url.
• click: click by selector or visible text.
• fill: fill a selector with value.
• assert_visible_text: require visible text.
• wait_for_text: alias for a visible text wait.
• assert_url: require current URL to equal url or contain contains.
• assert_no_horizontal_overflow: require the page not to overflow the viewport horizontally.
• assert_in_viewport: require a selector or visible text to have a nonzero box intersecting the viewport.
• assert_box: require a selector or visible text to satisfy width/height constraints.
• screenshot: capture a screenshot checkpoint.

Supported expectations:

• {"expect": {"text": ["Visible copy"]}}: require visible text after the step.
• {"expect": {"noConsoleErrors": true}}: require no console/page errors observed so far.

Examples:

{ "visit": "/checkout" }

{ "click": "[data-layout-qa='simulate-payment-timeout']" }

{ "screenshot": "Payment timeout recovery", "expect": { "text": ["Payment failed", "Try again"] } }

{ "id": "open_settings", "type": "click", "text": "Settings" }

{ "id": "email", "type": "fill", "selector": "input[name='email']", "value": "[email protected]" }

{ "id": "settings_url", "type": "assert_url", "contains": "/settings" }

{ "id": "no_overflow", "type": "assert_no_horizontal_overflow" }

{ "id": "main_visible", "type": "assert_in_viewport", "selector": "main" }

{
  "id": "primary_cta_size",
  "type": "assert_box",
  "selector": "[data-qa='primary-cta']",
  "minWidth": 120,
  "maxHeight": 56
}

Viewports

The runner defaults to the desktop viewport, 1280x900. Use --viewport to run the same flow at a preset or exact size:

npx @trylayout/qa run --target-url http://localhost:5173 --viewport desktop
npx @trylayout/qa run --target-url http://localhost:5173 --viewport tablet
npx @trylayout/qa run --target-url http://localhost:5173 --viewport mobile
npx @trylayout/qa run --target-url http://localhost:5173 --viewport 390x844

Presets:

• desktop: 1280x900
• tablet: 768x1024
• mobile: 390x844

The selected viewport is written to result.json, shown in the HTML report, and included in the run directory name.

Hosted Reports

The CLI is local-first. If you have a Layout project upload token, the same run can upload screenshots and report metadata to a hosted Layout report:

npx @trylayout/qa run \
  --target-url http://localhost:5173 \
  --upload-url https://trylayout.com/api/v1/qa/uploads \
  --upload-token "$LAYOUT_UPLOAD_TOKEN" \
  --repo owner/repo \
  --branch "$BRANCH_NAME" \
  --commit-sha "$COMMIT_SHA"

Environment fallbacks:

• LAYOUT_UPLOAD_URL
• LAYOUT_UPLOAD_TOKEN
• LAYOUT_REPOSITORY
• LAYOUT_BRANCH
• LAYOUT_COMMIT_SHA
• LAYOUT_PR_NUMBER
• LAYOUT_RUN_SOURCE

In GitHub Actions, the CLI also reads GITHUB_REPOSITORY, GITHUB_HEAD_REF, GITHUB_REF_NAME, GITHUB_SHA, GITHUB_REF, and GITHUB_EVENT_PATH when explicit flags are not provided.

If either upload flag is provided, both --upload-url and --upload-token are required. Upload failures make the CLI exit nonzero.

Scenarios

Before the app loads, the runner sets:

localStorage.setItem("layout.qa.scenario", "<scenario>");
sessionStorage.setItem("layout.qa.runner", "1");

Your app can use layout.qa.scenario to switch deterministic API/auth response states:

• happy_path: normal populated data.
• empty: successful responses with empty states.
• error: failed or error responses that should render recovery UI.

The layout.qa.runner flag is useful for hiding local-only QA switchers from screenshots.

Agent Setup Prompt

Paste this into your coding agent inside the frontend repo:

Set up Layout QA for this web app.

Goal:
Create a local-only browser QA loop that an agent can run while changing frontend code.

Rules:
- Do not add a standalone mock server.
- Do not require a hosted Layout service.
- Keep all deterministic response fixtures local to this app.
- Gate deterministic API/auth responses behind a QA env flag such as LAYOUT_QA=1, VITE_LAYOUT_QA=1, NEXT_PUBLIC_LAYOUT_QA=1, or the framework-appropriate equivalent.
- Use localStorage["layout.qa.scenario"] to select at least happy_path, empty, and error response states.
- Hide any local QA switcher or debug controls when sessionStorage["layout.qa.runner"] === "1".

Implementation:
- Add deterministic API fixtures for the highest-value frontend route.
- If the app has a central auth/session abstraction, add a deterministic QA user only when the Layout QA env flag is enabled.
- If auth is scattered or provider-SDK-only, leave a clear note in the PR/code comments and start with public or logged-out flows.
- Add .layout/qa.json with one smoke flow for the most important page.
- Prefer visible text and stable selectors.
- Add screenshot checkpoints after meaningful user-visible states.

Run:
npx @trylayout/qa run --target-url <local app url> --scenario happy_path --open
npx @trylayout/qa run --target-url <local app url> --scenario empty --open
npx @trylayout/qa run --target-url <local app url> --scenario error --open

CI Example

name: Layout QA

on:
  pull_request:

jobs:
  qa:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npx playwright install chromium
      - run: LAYOUT_QA=1 VITE_LAYOUT_QA=1 npm run dev -- --host 127.0.0.1 --port 5173 &
      - run: npx @trylayout/qa run --target-url http://127.0.0.1:5173 --scenario happy_path --run-source github_actions --upload-url https://trylayout.com/api/v1/qa/uploads --upload-token "$LAYOUT_UPLOAD_TOKEN"
        env:
          LAYOUT_UPLOAD_TOKEN: ${{ secrets.LAYOUT_UPLOAD_TOKEN }}
      - uses: actions/upload-artifact@v4
        if: always()
        with:
          name: layout-qa-report
          path: .layout/runs

Current Scope

This package is intentionally small:

• It does run Playwright against an already-running frontend.
• It does write local screenshots and an HTML report.
• It does support deterministic scenario switching.
• It does support explicit viewport sizing.
• It does support lightweight layout assertions.
• It does not build or host your app.
• It does not upload results.
• It does not perform AI review by itself.

Those hosted/reporting layers can be added later without changing the local protocol.

Feedback

Issues and examples are welcome in GitHub Issues. You can also reach me on X at @tscepo.