Testing and performance — Nexis documentation

Use layered verification

Test packages in isolation, then route rendering, browser behavior, runtime parity, and the full production artifact. Do not use a single snapshot as a substitute for behavioral checks.

Budget the browser output

Static routes should remain free of route-specific JavaScript. Interactive output must remain inside its configured compressed budget and be inspected with the manifest and analyzer.

Report measured results honestly

Separate controlled lab measurements from field Web Vitals. Capture the command, environment, route, and method alongside any performance claim.

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

Use a layered release gate

Shell

pnpm typecheck
pnpm test
pnpm check
pnpm build
pnpm analyze
git diff --check

OUTPUT: Source, behavior, artifact budget, and output are reviewed separately.
BOUNDARY: A local score does not prove field Web Vitals, indexing, or traffic.
PROVE IT: Record commit, runtime versions, routes, raw/gzip assets, environment, thresholds, and limits.

VERIFICATION

Prove the contract.

Run build, checks, browser tests, route analysis, form/stream/SEO/security checks, and record reproducible measurement conditions.