Testing
Verify Expo foundation changes at the narrowest useful scope.
Foundation checks cover the generated catalog, evaluation fixtures, skill contracts, installer conflicts, and consumer guidance. Showcase checks cover lint, TypeScript, deterministic contract tests, Expo Doctor, web export, and a local browser smoke journey. Run the complete local maintainer gate from the repository root:
npm run verify
That command clean-installs both lockfiles, checks the generated catalog and
installer/guidance tooling, runs docs validate/check/build, and then runs
the showcase checks. The web smoke uses SHOWCASE_CHROME_PATH when set, the
default macOS Chrome path when present, and otherwise Playwright’s bundled
Chromium; remote CI runs the same journey (see .github/workflows/ci.yml).
Native runtime checks are reported separately when Expo Go, a simulator, or a
development client is unavailable.
For focused work, run the individual commands in the scripts reference and
showcase/README.md.
Do not substitute a paid EAS build, deployment, remote simulator, or telemetry action for a local check unless the user explicitly authorizes it.