CodeVetter · Repo Unpack · Testing signals
python-poetry/poetry
Tests and CI were inspected, not executed; test existence does not establish a passing result. The configured suite uses pytest with xdist and supporting mocking/coverage tools. Inspected tests exercise command guards, solver operation comparisons, authentication, lock serialization, plugin loading, and installation integrity. This is bounded coverage evidence, and mocked boundaries do not establish live index, keyring, Git, or platform behavior.
- pyproject declares pytest, pytest-cov, pytest-mock, pytest-randomly, pytest-xdist, and responses; pytest targets tests with logical-worker parallelism and network/skip_git_mock markers.
- The default test configuration excludes integration-marked tests unless --integration is supplied; the inspected CI explicitly invokes poetry run pytest --integration -v.
- Autouse fixtures replace user Config, keyring, configuration directories, and selected environment variables; Git.clone/Get_revision are mocked unless skip_git_mock applies, and the HTTP fixture uses responses.
- Install command tests assert dry-run state propagation and absence of editable builds, plus successful non-package-mode installation; the dry-run tests patch Installer.run and therefore do not verify actual dependency mutation.
- Executor tests check fixture-backed installation/hash metadata, rejection of filenames absent from the lock, and abortion of wheel installation after a mocked builtin-uninstall failure.
- Authenticator tests inspect mocked Authorization headers for URL/config credentials and HTTPS-to-HTTP restrictions; Locker tests assert unchanged contents after a version-comment-only difference and preservation of line endings.
- Plugin tests assert activation and invalid-type rejection, and mock addsitedir to check path handling; the solver test helper compares Transaction operations, including update endpoints and skipped state.
- Inspected CI defines Ubuntu/Windows/macOS runs across Python 3.10–3.15, mypy, build/install smoke checks, and external poetry-plugin-export tests; these are workflow declarations, not observed execution results.