CodeVetter · Repo Unpack · Testing signals
cypress-io/cypress
Tests and CI were inspected, not executed; their existence is not a passing result. The repository combines Vitest, Mocha, Jest, Cypress browser suites, and a system-test harness. Inspected coverage includes option translation, session persistence/probing, subscription behavior, configuration child failures, and browser interception. The inventory and test inspection are bounded, so local TODOs and mocks describe specific limits rather than whole-repository coverage gaps.
- Root Vitest discovers package/tooling/script project configurations and the CLI project, excludes system-tests, and configures V8 coverage plus default/JUnit reporting; server test-unit runs Mocha then Vitest, while data-context uses Jest with experimental VM modules.
- CLI run tests assert project-path rejection, conflicting headed/headless flags, testing-type choices, and POSIX argument forwarding; verify/spawn are mocked, so these tests do not establish real binary launch behavior.
- Server session tests use temporary cache directories and inspect actual JSON files, covering immutable identity, temporary-file cleanup, swallowed write failure, pending-write removal, and project-switch preservation.
- CLI session tests exercise fake HTTP sessions and closed ports, asserting rejection of recycled-port/session mismatches, malformed JSON, timeout, and stale CDP endpoints while retaining browser identity.
- InterceptedRequest Vitest tests resolve pending handlers through a mocked socket and assert enabled/disabled subscription dispatch counts; they do not exercise a real proxy or CDP transport.
- The driver interception suite asserts route state and backend event frames in browser tests, but declares 15 retries and unique route names for documented flakiness/request leakage. runEachSpec also carries an explicit TODO for a cancelled just-in-time component-run system test.
- A Jest ProjectConfigIpc test loads a real configuration child and injects EPIPE; system config tests cover invalid settings and JS/TS config filenames, and the harness offers withBinary mode. A config-spec TODO requests environment-variable coverage locally.
- Inspected CircleCI definitions gate contributor builds behind approval, select suites through pipeline parameters, add Chrome forceHttp1 smoke coverage, and aggregate browser/system/type/lint checks at ready-to-release; GitHub Actions separately checks semantic PR titles/changelog and generates release SBOMs.