CodeVetter · Repo Unpack · Testing signals
pypa/hatch
Tests and CI were inspected, not executed; no passing result or measured coverage is asserted. The inspected suite uses pytest, Click testing helpers, isolated storage, mocks, and capability-dependent integration tests. It exercises environment creation, signals, builds, credentials, and locking, but some tests deliberately replace process or activation boundaries. This inventory is bounded and does not establish exhaustive coverage.
- The default test environment specifies pytest, pytest-mock, pytest-randomly, pytest-rerunfailures, pytest-xdist, and coverage; tests/conftest.py wraps Click CliRunner and defaults catch_exceptions to False.
- The session isolation fixture redirects Hatch data/cache directories into temporary storage and controls shell, color, and active-environment state; marker handling skips unavailable network, OS, Git, Docker, and Cargo capabilities.
- test_automatic_creation asserts environment storage layout and the child's interpreter path; test_interrupt_signal_not_inherited checks the child's default SIGINT handler and restoration of the parent handler.
- Build tests include Flit backend artifact assertions and wheel archive-content/timestamp assertions; the CLI build module applies mock_backend_process, and process-output fixtures explicitly bypass mocking under allow_backend_process.
- Dependency-lock tests compare top-level lock with dep lock and exercise pip apply-lock rejection; the inspected uv sync test uses mock_locker and replaces safe_activation, so it does not validate a real activation layout.
- Publishing CLI tests require Docker/internet and a devpi fixture, with keyring calls replaced by an in-memory store; separate auth tests use a fake home to check .pypirc repository-name and URL matching.
- Coverage configuration requests branch coverage but omits module entrypoints, backend bridge code, migration, frontend helper scripts, and shell utilities; presence of other tests does not establish coverage of these omitted boundaries.
- Inspected CI defines Linux/Windows/macOS testing across Python 3.10–3.14 and 3.14t, randomized parallel tests with retries, combined coverage reports, downstream builds, and a separate Hyperfine CLI benchmark workflow; none was executed or its results verified.