CodeVetter · Repo Unpack · Testing signals
pnpm/pnpm
Tests and CI definitions were inspected, not executed; no passing result, measured coverage percentage, or benchmark outcome is established here. Rust uses ordinary and Tokio tests, process-level CLI fixtures, snapshots, and cargo-nextest configuration. TypeScript uses Jest with registry-backed project fixtures. The inspected checks span installation, filtering, integrity, recovery, and language/runtime boundaries, but the bounded sample cannot establish all untested behavior.
- The inspected Rust CLI suite is assembled in tests/suite/main.rs as one integration-test binary, while nextest runs individual tests in separate processes; its modules include install-related commands, custom resolvers/fetchers, lifecycle behavior, and linker variants.
- should_install_dependencies spawns the real CLI against a mocked registry, asserts the direct dependency is a symlink/junction, checks transitive placement in the virtual store, and snapshots workspace/store structure using insta.
- TypeScript install/only.ts uses Jest and execPnpm fixtures to check production/development filtering; its production test also checks progress counts and verifies the resolved dev-transitive version in the lockfile before store-presence assertions.
- pnpr tarball tests use Tokio, mockito, temporary storage, and Axum oneshot requests to check declaring-version integrity binding and cache replay after router reconstruction; the same file includes a tampered-stream rejection test.
- Journal-recovery tests fabricate interrupted on-disk publication state, including an older manifest format, to exercise sealed roll-forward and unsealed rollback; these recovery scenarios were read, not run.
- The nextest smoke profile selects one test per behavior area and explicitly does not prove change correctness. Default tests receive a 60-second slow interval with termination after five intervals, and separate validation is documented for stale smoke-test names.
- Rust CI invokes separate rust-test and pnpr-test pipelines and adds a Linux Node test of the built NAPI addon. TypeScript CI builds the bundle before sharded tests across Node 22.13, 24, and 26.10 on Linux, with a separate Windows shard matrix.
- Ecosystem E2E and Cargo equivalence are scheduled compatibility checks rather than per-PR merge blockers; docs CI builds the external website with repository docs and checks URLs, while the inspected CodeQL matrix selects JavaScript.