CodeVetter · Repo Unpack · Testing signals
effect-ts/effect
Tests and CI were inspected, not executed; no passing result or coverage measurement is asserted. The repository separates Vitest runtime tests, Tstyche compiler contracts, and generated documentation tests. Representative tests exercise lifecycle ordering, HTTP contracts, provider request mapping, and SQLite storage/transactions. Runtime conditions and explicit integration flags limit which tests a particular invocation includes, and the inspected inventory is not exhaustive coverage.
- Vitest discovers package test/**/*.test.{ts,tsx}, uses shared setup and concurrent sequencing, and offers V8 HTML coverage. @effect/vitest re-exports Vitest and adds effectful/property-test contracts with interruption-aware timeouts.
- ManagedRuntime.test.ts asserts build memoization, Context provision, shared MemoMap reuse, await-using cleanup, interruption on disposal, request-before-resource cleanup ordering, and finalizer completion under interrupted disposal.
- The Node HTTP API tests construct real test-server layers and generated clients, checking catch-all routing and middleware error encoding on both server and client boundaries.
- SQLite KeyValueStore tests reuse a serialized suite for default and custom tables, covering overwrite/size, binary representation, UTF-8 strings, removal, and clear. Client tests separately cover rollback, deferred-commit recovery, busy-timeout configuration, contention, and readonly transactions.
- Inspected OpenAiClient tests assert Bearer headers, default/custom URLs, organization/project headers, and transform ordering using captured requests and synthetic responses; those assertions do not establish live-provider compatibility.
- Tstyche discovers .tst files in package typetest trees and includes Effect.isEffect narrowing assertions. Documentation tests use @effect/doctest/Plugin with includeSource covering top-level and nested package source.
- Inspected Check CI enables EFFECT_INTEGRATION_TESTS=1 and defines Node, Deno, and Bun test commands; separate jobs run lint/circular/document-generation checks, TypeScript/Deno/Tstyche checks, distribution builds, and documentation tests. These definitions were not executed in this investigation.
- Ordinary runs exclude integration tests unless EFFECT_INTEGRATION_TESTS=1; cluster integration additionally requires Node and EFFECT_CLUSTER_TESTS=1 and has a manual workflow. Bun excludes named core HTTP/schema/reactivity tests, and platform projects depend on the detected runtime.