Skip to content

test: skip Core conformance when verdict-core is not installed - #19

Merged
mrnicholasbcarter-code merged 1 commit into
masterfrom
fix/core-conformance-importorskip
Sep 24, 2026
Merged

mrnicholasbcarter-code merged 1 commit into
masterfrom
fix/core-conformance-importorskip

Conversation

@mrnicholasbcarter-code

Copy link
Copy Markdown
Owner

A fresh clone following the normal setup (uv sync --extra dev && uv run pytest) fails at collection:

tests/test_core_conformance.py: ModuleNotFoundError: No module named 'verdict'
1 error during collection

The conformance test imports verdict (verdict-core) at module level. verdict-core is not a declared dependency; CI installs it separately at a pinned SHA. So any local contributor, or an interviewer cloning the repo, sees a red test run.

Fix: pytest.importorskip("verdict.provider_receipts"). verdict-backtest's tests/test_core_conformance.py already uses this pattern. Coverage in CI is unchanged, because CI still installs the pinned Core and runs these tests.

Verified:

  • Clean venv without Core: 51 passed, 3 skipped (before: 1 collection error).
  • Clean venv with the CI pin verdict-core@55880def…: tests/test_core_conformance.py → 2 passed.
  • ruff check and ruff format --check pass (ruff 0.16.8, the version CI currently resolves).

@mrnicholasbcarter-code
mrnicholasbcarter-code merged commit f49fc92 into master Sep 24, 2026
10 checks passed
@mrnicholasbcarter-code
mrnicholasbcarter-code deleted the fix/core-conformance-importorskip branch September 24, 2026 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant