CodeVetter · Repo Unpack · Testing signals
QwikDev/qwik
Tests and CI configuration were inspected, not executed; test existence is not a passing result. Vitest exercises package-level specifications, Playwright exercises browser and adapter behavior, and Rust optimizer tests use Insta snapshots. Inspected tests provide concrete coverage signals for serialization, streamed events, action responses, request limits, and database aggregation. Coverage remains bounded: this investigation did not establish complete test coverage or production behavior.
- The inspected root Vitest configuration includes package *.spec.* and *.unit.* files, excludes generated/dependency trees, loads vitest-setup.ts, and enables the TypeScript optimizer.
- Serialization tests snapshot encoded Plain and RootRef values and separately test decoding; additional assertions restore signal effect back references and compute QRLs.
- qwikloader.behavior.unit.ts reads dist/qwikloader.debug.js and executes it inside mocked browser globals, so its intended checks depend on current build output.
- A loader regression test asserts that a click does not run before streamed-container data is ready and runs after QwikEvContainerReady is pushed.
- Playwright events.e2e.ts checks independent counter updates, prevented navigation, propagation behavior, and mouseleave/mouseover execution ordering.
- Action-handler unit tests deserialize response bodies and assert default, explicit, and strict-mode invalidation semantics plus validator failure status.
- Request-body-limit tests cover exact-limit acceptance, oversized single/multiple chunks, and invalid limit configuration.
- Insights query tests use an in-memory libSQL client with explicit fixtures to check cross-manifest aggregation and isolation from another application's rows.
- Rust test_input_fn invokes transform_modules and snapshot_res records emitted modules, maps, segment metadata, and diagnostics using insta::assert_snapshot!.
- Core Playwright configuration uses *.e2e.ts, parallel execution, a localhost dev-server command, CI-only traces/screenshots, and forbidOnly; docs use a separate Chromium configuration.
- Inspected CI defines unit and MCP checks plus sharded browser runs with QWIK_OPTIMIZER set from TS/Rust matrix entries; no CI run result was retrieved.
- The inspected action unit harness mocks parseBody and QRL execution, and the Insights query fixtures test reads rather than the full authenticated ingestion path; those tests alone do not prove those integrations.