Skip to content

ci: gate network tests (run tests/test_network.py in CI) - #3

Merged
ajram23 merged 1 commit into
mainfrom
ci/gate-network-tests
Jun 2, 2026
Merged

ci: gate network tests (run tests/test_network.py in CI)#3
ajram23 merged 1 commit into
mainfrom
ci/gate-network-tests

Conversation

@ajram23

@ajram23 ajram23 commented Jun 2, 2026

Copy link
Copy Markdown
Owner

Problem

Both workflows run only pytest tests/test_commands/, while pyproject.toml sets testpaths = ["tests"]. The explicit path arg overrides testpaths, so CI silently skips tests/test_network.py — the entire network/curl integration suite (allow-list, redirects, private-range blocking, header transforms, and the curl compression regression tests). A transport regression (e.g. re-introducing the gzip Accept-Encoding bug) would merge and ship green.

This gap has existed since tests/test_network.py was added without updating the workflows.

Fix

Append tests/test_network.py to the pytest invocation in test.yml and release.yml:

pytest tests/test_commands/ -> pytest tests/test_commands/ tests/test_network.py

Verification

pytest tests/test_commands/ tests/test_network.py2297 passed, 1 skipped locally. (Other un-gated suites like spec_tests/ are intentionally left out — they're a partial-compliance corpus that fails ~50% by design.)

CI ran only `tests/test_commands/`, so `tests/test_network.py` (the
network/curl integration suite, including the curl compression regression
tests) was never executed by the Test or Release workflows — a transport
regression could merge or ship green. Add `tests/test_network.py` to both
pytest invocations so the network suite is gated.
@ajram23
ajram23 merged commit 6ef5dd0 into main Jun 2, 2026
3 checks passed
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