CodeVetter · Repo Unpack · Testing signals
elysiajs/elysia
Tests and CI were inspected, not executed; no passing result is asserted. Bun tests exercise request behavior and regressions, while a separate TypeScript project checks public inference. Node and Cloudflare scripts provide integration smoke checks with narrower assertions. The inspected inventory is bounded, and commented tests identify local coverage limits without establishing repository-wide absence.
- The documented unit framework is bun:test with files under test; CONTRIBUTING recommends bun test test/<test-file>.ts for a focused check.
- Tests and CI were inspected, not executed: the aggregate test script chains functionality, type and Node checks, and CI separately invokes Cloudflare checks after building.
- Dynamic-mode tests explicitly configure aot:false and assert JSON body validation, derive/resolve context and invalid-input 422 behavior.
- Standard Schema integration tests check valid and invalid Zod bodies, coerced queries and combined status-specific responses; validator unit tests insist Check returns booleans rather than truthy failure wrappers.
- Native-static regressions assert promotion refusal for request schemas and observing hooks, preserve eligible constant routes, and require request hooks to remain uncalled during registration.
- Cookie tests exercise signature verification and key rotation; range tests check open-ended, bounded, suffix and invalid ranges, explicitly accepting only the first range of a multi-range request.
- Type tests use expect-type and tsc with test/types as the configured include; Node CJS/ESM fixtures each validate a simple typed GET through app.handle, while Cloudflare polls only the root response.
- Local coverage limits include commented cookie decoding cases, dynamic query-reference cases and a WebSocket subscribe/publish case; active WebSocket tests do exercise a real listen(0) connection.