Skip to content

test(suggest): gate remote-tier assertions behind requires_remote_data#1

Merged
jm-rivera merged 1 commit into
mainfrom
fix/gate-remote-data-suggest-tests
Jun 11, 2026
Merged

test(suggest): gate remote-tier assertions behind requires_remote_data#1
jm-rivera merged 1 commit into
mainfrom
fix/gate-remote-data-suggest-tests

Conversation

@jm-rivera

Copy link
Copy Markdown
Owner

The initial-commit CI run failed on all three OSes: test_suggest_york_returns_new_york_admin1 and test_suggest_default_to_with_on_missing_raise_does_not_raise assert geoId/36 (New York admin1) in suggest('york'), but admin1 is a remote tier that clean CI never downloads. They pass only on machines with a warm cache (same failure existed on the dev repo's final run — pre-existing, not migration-related).

Fix: mark both @pytest.mark.requires_remote_data, the suite's existing convention for remote-tier tests.

Verified locally: pytest tests/test_suggest.py → 29 passed 2 skipped; with --run-remote-data → 31 passed.

The two 'york' tests assert geoId/36 (New York admin1) in suggest results,
which requires the remote admin1 tier — absent in clean CI, present only on
machines with a warm cache. Mark them requires_remote_data per the suite
convention so clean CI skips them.
@jm-rivera jm-rivera merged commit 2d09016 into main Jun 11, 2026
4 checks passed
@jm-rivera jm-rivera deleted the fix/gate-remote-data-suggest-tests branch June 11, 2026 12:49
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