CodeVetter · Repo Unpack · Testing signals
remix-run/remix
Tests and CI were inspected, not executed; no passing result or measured coverage is asserted. The sampled packages use the repository's own test framework with Playwright integration rather than establishing Vitest as the main runner. Source tests cover routing aborts, cookie defaults, asset policies/cache behavior, frame requests, and a fake-provider OAuth flow. Browser projects and integration job filters limit which environments a configured run exercises, and this inspection does not establish exhaustive coverage.
- The template test imports describe/it from remix/test and assertions from remix/assert; scripts also use `remix test`.
- The test runner discovers .test, .test.browser, and .test.e2e TypeScript/TSX files, defaults to a forks pool, and supports server, browser, and E2E test types.
- The test package uses `remix test`, offers a Bun server-test command, and declares Playwright as an optional peer dependency.
- The inspected template controller test checks GET / status, HTML content type, and an html element; that individual test does not assert browser hydration or interaction.
- Router abort tests assert rejection for pre-aborted requests, abort during handler processing, and aborted Request inputs.
- Session middleware tests verify protocol-derived Secure, explicit Secure overrides, and the default HTTP-only flag.
- Asset-server tests create temporary source fixtures and assert that only allowlisted script/style/configured file assets appear, excluding private and denied test files.
- Asset tests assert GET/HEAD support, POST fallthrough, no-cache headers, ETags, and a 304 response to matching If-None-Match.
- Frame tests mock fetch and verify posted FormData, frame headers, same-origin mode, abort signals, and resulting DOM content; a separate test checks same-origin mode for an explicitly external src.
- The OAuth integration test follows authorization, callback-cookie propagation, and protected dashboard access against a local fake provider; it does not demonstrate live provider compatibility.
- Component and UI Playwright configs select Chromium only; assets, component-HMR, the test framework, and the import-map polyfill select Chromium and Firefox.
- The test framework and multiple-import-map polyfill also explicitly configure Chromium and Firefox projects.
- Main CI defines Ubuntu, Bun, and Windows test jobs plus lint/typecheck; PR Bun and Windows jobs run changed-package selection from explicit base/head SHAs.
- Main CI defines conditional Memcache, Redis, PostgreSQL, MySQL, SQLite, and LocalStack S3 integration checks with service-specific environment switches; their configuration is evidence of intended checks, not execution success.