Skip to content
nexisv1.3.3Build with Nexis
← Learning map

Operations · lesson 10

Prove the enterprise contract before release

Use layered checks for output, interaction, security, metadata, adapters, performance, and operational readiness.

copyable patternserver-firstenterprise track

01

Test the emitted artifact

Do not stop at unit tests. Inspect the built HTML, manifest, discovery files, lazy chunks, form runtime, redirects, sitemap, robots, feeds, and generated media.

  • Run route discovery and analyze after structural changes.
  • Assert static routes contain essential content without JavaScript.
  • Verify interactive chunks are not loaded before first intent.

02

Test both enhancement paths

A form should succeed or fail correctly with scripts disabled and with the enhancer enabled. A client interaction should update only the intended target and must not rerender the entire route.

  • Browser-test keyboard and mobile behavior.
  • Test 404, 405, HEAD, redirects, and cache headers.
  • Test denied authorization and session expiry paths.

03

Release is an operation

Build from the lockfile, keep configuration versioned, record the deployed build, watch health and error rates, and retain a known-good rollback artifact.

  • Separate local and production measurements.
  • Never claim a performance target that was not measured.
  • Review secret scans and dependency audit findings.
Release gate · framework and application checksTypeScript
pnpm install --frozen-lockfile
pnpm typecheck
NEXIS_SITE_ORIGIN=https://app.example.com pnpm check
NEXIS_SITE_ORIGIN=https://app.example.com pnpm build
pnpm analyze
pnpm exec nexis routes
pnpm exec nexis doctor

# Then run application integration and browser tests for
# auth, permissions, Actions, cache headers, and private routes.

PRACTICE LAB

Prove the behavior.

Create a release checklist that includes a tested rollback command, owner, health dashboard link, and post-deploy verification sample.