CodeVetter · Repo Unpack · Testing signals
nrwl/nx
Tests and CI were inspected, not executed; test existence does not establish a passing result. Core Nx TypeScript tests use Vitest, alongside Jest configurations elsewhere and Rust tests in native source. Inspected tests cover argument parsing, staged file changes, cache failure policy, and hostile archive extraction. Mocking and disabled CI matrix entries impose specific limits, and this bounded inspection does not measure whole-repository coverage.
- Core Nx Vitest selects **/*.spec.ts in a Node environment, uses forked workers, excludes native TUI tests, and configures source export conditions plus external native bindings to avoid duplicate native heaps.
- The shared Jest preset transforms TypeScript through SWC, runs one worker in Node, and installs mock mappings; e2e/nx instead uses ts-jest with global setup/teardown. Both Jest and Vitest target defaults allow no-test runs.
- run-one.spec.ts constructs a synthetic project graph and directly verifies parsing of project:target:configuration and project:target; these inspected assertions do not launch an executor.
- tree.spec.ts creates temporary filesystem fixtures, checks staged read/write changes, flushes them, and verifies actual file contents; it exercises the Tree boundary rather than a full plugin-generation command.
- Orchestrator tests verify default rejection of cached failures, NX_CACHE_FAILURES opt-in, and failure status/output on replay; their cache and output-hash checks are mocked, so they do not establish remote-provider integration.
- Rust HTTP-cache tests construct hostile archives for parent traversal, absolute paths, and Unix symlink escape, plus a legitimate artifact; these exercise extract_tarball directly rather than the HTTP transport.
- framing-reconnect.spec.ts runs a synthetic socket peer that always sends an unframed response and expects exactly three connections followed by watcher closure, covering a concrete reconnect-loop limit.
- CI declares affected lint/test/build/e2e/native checks and fix-ci on failure; scheduled e2e configuration comments out Windows, while CodeQL comments out Java/Kotlin. These workflow definitions were inspected, with no CI results retrieved or executions performed.