CodeVetter · Repo Unpack · Testing signals
lerna/lerna
Tests and CI were inspected, not executed; no passing result or coverage percentage is established. Vitest supplies shared Node-environment configuration for unit, integration, and e2e projects. Inspected suites mix mocked command boundaries with actual CLI and local-registry scenarios. The inventory is bounded, and mock coverage does not establish live service correctness.
- Shared Vitest configuration enables globals, a Node environment, single-run mode, spec/test discovery, Jest-compatible snapshot formatting, cleared mocks, and V8 coverage output.
- Run unit tests mock npm script execution and assert script validation, filtering, streaming/prefix behavior, no-match success, alternate clients, and bail/non-bail exit propagation.
- Version unit tests mock push and upstream checks while checking working-tree validation, version prompts, updated manifests, commit snapshots, and push arguments.
- Publish unit tests mock packing, publishing, authentication helpers, and checkout; they assert rejected CLI options and package publication order, so those assertions do not exercise a live npm service.
- Integration tests invoke the CLI on fixtures and check exec filtering, shell environment expansion, streaming, and failure codes; inspected non-bail cases are conditional on non-Windows platforms.
- E2e defaults serialize spec files and retry failures up to three times; an inspected publish scenario uses localhost:4873 to verify recovery when one version already exists, and task-runner assertions check environment loading.
- The inspected OIDC suite has two mocked cases: CircleCI token exchange and skipping unsupported CI. The ESM compatibility suite checks built output, ESM imports, synchronous require contracts, and CLI version output.
- CI defines a Node 22.22.2 package-entrypoint job, distributed Linux checks, Windows unit/integration jobs, and isolated task-runner e2e; core config excludes three config-chain suites on Windows.