CodeVetter · Repo Unpack · Testing signals
blitz-js/blitz
Tests and CI were inspected, not executed; no passing result is asserted. The examined suites mix Vitest unit tests, database-backed application tests, and integration tests that launch Next.js and browsers. CI describes package/app checks and dynamically selected integration projects on Linux and Windows. Coverage is uneven: some tests exercise real assertions, while an application-generator test is effectively a placeholder.
- Core toolkit package manifests define vitest run, and root test delegates to turbo run test; these commands were inspected only, not executed.
- The inspected resolver suite checks value propagation through default, synchronous, and asynchronous Zod stages using a mocked session.$authorize.
- auth-sessions.test.ts tests append cookie merging, replacement, expiration-cookie combinations, and preservation of custom cookies; its named auth flows manipulate cookie strings rather than execute getSession or storage.
- Plugin tests assert merge and pipe behavior and reducer exports/middleware presence, including distinct request-header hooks.
- Loader utility tests assert default versus root resolver paths and include a Windows-path case.
- Forgot-password tests reset the database, mock token generation and email preview, and assert replacement token fields and a nonthrowing absent-user result.
- Reset-password tests assert rejection for a non-existent-token input with empty passwords and for an expired token, and check successful token deletion and password verification; session.$create is mocked and this test does not assert session revocation.
- The AppGenerator test's active 'runs' body immediately returns; Git-related expectations below it are commented out.
- The App Router integration fixture checks unauthenticated client/server queries, cookie creation, RPC query results, login, and HEAD CSRF exemption, then runs its assertions in Webpack and Turbopack development modes.
- Middleware integration tests verify response headers on API and RPC requests in development and built-server modes.
- Inspected CI builds and lints, filters package/app tests, discovers integration folders, installs Playwright, and excludes next-13-app-dir steps on Windows; workflow definitions do not establish successful execution.
- Test configuration needs package-level checking: toolkit-app exposes test:local rather than test and references ./test/setup.ts, while apps/web uses Jest; this bounded inspection does not establish comprehensive repository coverage.