CodeVetter · Repo Unpack · Testing signals
nuxt/nuxt
Tests and CI were inspected, not executed; their existence and assertions establish intended coverage, not passing results. Vitest separates unit, renderer, Nuxt-environment, fixture-matrix, bundle, and type-performance projects, while Playwright drives browser scenarios. CI schedules type/API checks, runtime/unit tests, fixture tests, browser tests, and security analysis with event-specific gates. The inspection is bounded, and explicit exclusions, disabled jobs, and a fixme prevent treating the configured suite as exhaustive coverage.
- The unit Vitest project discovers package test/spec files and supplies generated-module/runtime aliases; Nuxt-environment projects run test/nuxt with @nuxt/test-utils configuration and fixture preparation.
- Fixture projects exercise Vite dev/built, async/default context, and manifest-on/off combinations; Nitro-Vite, Rspack, and Webpack intentionally use smaller matrices, with additional legacy-error projects.
- Renderer tests prepare standalone generated artifacts and inject renderer configuration; standalone.test.ts asserts HTML, asset URL helpers, SPA route behavior, hooks, and isolation between renderer options.
- Inline-error tests assert preservation of Set-Cookie and middleware headers, static fallback after an error-page failure, rejection rather than HTML for payload failures, and 404 handling for the retired error route.
- Session unit tests use synthetic Web Request events and mocked runtime config to check cookie flags, cross-request round trips, tampering, expiry, format rejection, cookie-size limits, and missing appSecret failures.
- Nuxt runtime fetching tests register local endpoints and inspect payload entries, computed request equivalence, removed params handling, serialize:false, reactive keys, basic async-data return shape, and shallow refs.
- Builder tests create temporary applications and exercise chokidar, granular chokidar, and Parcel watcher strategies, including parent-path changes and selective template recompilation.
- Playwright uses Desktop Chrome across Vite dev/built, Nitro-Vite dev/built, and built Webpack/Rspack projects; it excludes dev-only, build-only, Vite-only, shared-fixture mutation, and Rspack chunk-error scenarios as configured.
- Streaming browser tests assert redirects, pre-shell error fallback, mid-stream error payloads/client error pages, and late-status behavior; the dev SFC stylesheet-before-shell scenario is explicitly test.fixme.
- CI defines built-type/public-API checks, prepared runtime/unit/no-Jiti tests, Linux/Windows fixture projects, and Linux/Windows Playwright runs; these workflow definitions were read without executing or retrieving run results.
- The benchmark CI job is disabled with if:false pending CodSpeed's Vitest 5 support. Root test:unit includes unit and renderer but omits the separately configured renderer-legacy-errors project.
- Security/documentation checks include CodeQL for JavaScript/TypeScript and Actions, OpenSSF SARIF analysis, and Lychee checks that limit pull requests to internal docs links but expand scheduled/manual runs.