CodeVetter · Repo Unpack · Testing signals
vercel/turborepo
Tests and CI were inspected, not executed; no passing result is asserted. The inspected coverage includes Rust integration behavior, executor policies, archive safety regressions, GraphQL host checks, and Jest package tests. CI spans multiple operating systems and Node versions, but exclusions, mocked boundaries, and release-PR skips limit what any individual job establishes.
- Rust integration tests under crates/turborepo/tests use #[test], temporary repositories, shared setup helpers, and subprocess output assertions; run_caching checks env-sensitive misses/hits and JSON cache metadata.
- Executor unit tests cover all three continuation policies and ensure cache hits, output-flush failures, task failures, shutdowns, restarts, and internal errors do not trigger output saving.
- Archive regression tests include an existing symlink pointing outside the restore anchor and assert replacement with a directory plus no external write.
- Query-server tests check GraphiQL response content and allowed/rejected host strings; the displayed tests call helper functions rather than exercising live HTTP middleware.
- create-turbo and turbo-utils use Jest; inspected tests include starter agent guidance and mocked child-process/fetch boundaries, so these examples do not establish live download or toolchain success.
- Rust CI uses macOS, Ubuntu, and Windows with two hash partitions; turbo.json invokes nextest while excluding LSP, schema generation, and N-API from that workspace test task.
- JavaScript CI covers Ubuntu/macOS and Node 22/24/26, runs affected package checks in strict env mode, excludes @turbo/repository from this job, and skips the job for validated release PRs.
- Lint CI separately configures cargo fmt, cargo lint, and license checking; nextest limits experimental OTel integration tests to one minute with no retries.