CodeVetter · Repo Unpack · Testing signals
fastify/fastify
Tests and CI were inspected, not executed; no passing result is asserted. The inspected runtime tests use node:test, selected by borp, while type assertions use TSTyche. CI defines operating-system, runtime, packaging, coverage, and integration checks. Inspection is bounded and does not establish exhaustive coverage or application-plugin correctness.
- borp selects test/**/*.test.js and test/**/*.test.mjs; inspected injection tests import node:test.
- npm test combines lint, unit, and type checks; test:ci omits lint and runs unit plus types.
- Injection tests assert readiness waiting, JSON payload, status code, and content length.
- Prototype-poisoning tests use real listen/fetch requests and assert rejection, removal, and ignore-policy behavior.
- Handler-timeout tests cover option validation, lazy AbortSignal creation, and client-disconnect abortion using a TCP connection.
- TSTyche provider tests assert unknown defaults, provider remapping, explicit overrides, and TypeBox-derived typing.
- Primary unit CI defines Node 24/26 across macOS, Ubuntu, and Windows, after quality and both coverage jobs.
- The coverage command requires 100 percent lines; this is a configured threshold rather than an observed coverage result.
- Production-install integration CI starts integration/server.js and invokes a shell smoke test covering GET, POST, PUT, and DELETE responses.
- esbuild and webpack fixtures define bundle-and-test scripts; alternative-runtime packaging CI invokes both.
- CITGM tests selected external plugins by linking this Fastify checkout into each plugin's own test environment; several database entries are commented out.