CodeVetter · Repo Unpack · Testing signals
mswjs/msw
Tests and CI were inspected, not executed; their existence does not establish a passing result. Vitest separates unit, Node, browser, memory, typings, and CLI suites, while Playwright handles page lifecycle and multi-tab scenarios. Read assertions cover several important persistence, isolation, streaming, and teardown branches. This is a bounded inspection, and configured browser coverage is Chromium rather than evidence of cross-browser parity.
- Vitest selects adjacent src unit tests and separate Node, memory, browser, types, and e2e projects; inspected configuration establishes suite routing, but no project was executed during this investigation.
- Shared integration tests run in Node and browser unless filename suffixes exclude them; startNetwork creates the actual setupServer/setupWorker API, and its fixture defaults unhandled traffic to bypass unless options override it.
- Concurrent boundary tests assert initial/override/initial responses in separate async scopes; browser cookie tests assert document forwarding, hidden Set-Cookie headers, multiple cookies, and continued cookie inference after localStorage quota failure.
- Lifecycle assertions cover an in-flight mocked request surviving worker stop, later requests bypassing, finalize callbacks after abort including late registration, and simultaneous handler/source disposal rejection handling.
- The Node frame-retention test warms up 500 failing requests, measures 1,500 more with forced GC and heap snapshots, and allows frame growth below 5% of the measured request count; this is a regression threshold, not a measured result from this brief.
- Inspected protocol tests assert GraphQL subscription publication/completion, WebSocket extension decoding with unchanged upstream wire traffic, and SSE cessation of upstream reconnects after consumer close.
- Vite tests build and inspect production output for removal of DEV-guarded mocks and then inspect rendered application behavior; CLI tests assert copied worker files and saved paths, while typings tests expect errors for incompatible declared response bodies.
- CI specifies Node 22.23.2/24/26 with lint/build/Vitest/Playwright, compatibility jobs inspect package exports and TypeScript 5.9/6.0/7.0, and smoke automation tests external examples; browser configurations inspected here select Chromium, and no CI run status was retrieved.