Testing

This guide is the entry point for testing Rezi apps.

If you are changing the Rezi framework itself, use the canonical developer policy instead:

Quick start

Run the deterministic suite:

npm test

Run package tests only:

npm run test:packages

Run script tests only:

npm run test:scripts

Filter to a subset:

node scripts/run-tests.mjs --filter "layout"

Focus on user-visible behavior:

Use the lowest level that proves the behavior.

Unit tests for pure helpers and reducers.
Semantic rendering or scenario tests for app behavior that does not require a real terminal.
PTY validation for terminal-visible behavior, terminal capability behavior, or terminal input recovery that headless tests cannot prove safely.

createTestRenderer() is useful for semantic rendering assertions, but it is not the final oracle for terminal-real behavior.

Use snapshots only when the snapshot encodes a clear contract. Do not use snapshots as a substitute for deciding what behavior the app should have.

Snapshot CLI:

node scripts/rezi-snap.mjs --verify
node scripts/rezi-snap.mjs --update

For layout, theme, rendering, or capability-sensitive regressions, include a live PTY run with frame-audit evidence: