CodeVetter · Repo Unpack · Testing signals
microsoft/rushstack
Tests and CI were inspected, not executed; test existence establishes neither passing results nor measured coverage. The inspected suite combines Jest tests over compiled JavaScript, snapshots, temporary-workspace subprocess fixtures, and Playwright demonstrations. CI specifies Linux/Windows and multiple Node versions, including cross-checkout cache exercises. Coverage observations are limited to the inspected files, and the inventory does not establish whole-repository coverage or absence.
- Shared Heft Jest configuration uses Node, clears mocks, matches compiled .test.js/.test.cjs files, and disables coverage collection by default; rush-lib overrides roots/testMatch to lib-intermediate-commonjs.
- ExtractorConfig-lookup tests verify <lookup> project-folder discovery for root, config/, and nested configuration locations; these cases test configuration resolution rather than complete extraction output.
- CustomMarkdownEmitter tests construct TSDoc headings, emphasis, links, and whitespace cases, then snapshot emitted text; that inspected test does not exercise MarkdownDocumenter’s output-folder deletion.
- Lockfile graph tests snapshot a PNPM v9 edge-case fixture; PnpmfileRunner tests assert transformed dependencies, forwarded logs, disposal, and rejection of calls after disposal.
- Heft CLI tests create temporary plugin/config fixtures and spawn the compiled executable; assertions cover task failure with zero/negative/positive prior exit codes, successful tasks, and alias-name collisions.
- Public-client IPC boundary tests cover changed direct/inherited/rig descriptors, generation changes and child replacement, native NoOp/missing-script/empty-selection behavior, preassigned shard runners, and --no-ipc.
- CI specifies Node 20/22/24/26 on Linux and Node 24/26 on Windows, production retest, package-manager integration tests, and repeated source-built test commands in a second checkout sharing the build cache; these steps were not run here.
- Browser-tunnel Playwright configuration selects five browser/channel projects, one worker, zero retries, and tracing; the inspected demo only navigates to about:blank and checks its URL, providing no assertion of launch-option rejection.