Repository navigation
action that skip tests that require internet connection #730
Description
Activity
Hi, I’d be happy to take a look at this if help is still needed.
Before implementing, I wanted to clarify the intended direction:
- Should tests requiring internet be marked explicitly (e.g. with a pytest marker like
@pytest.mark.internet) and skipped via CI? - Or should the GitHub Action detect network availability dynamically and skip affected tests?
I can prototype either approach once aligned.
- Should tests requiring internet be marked explicitly (e.g. with a pytest marker like
Neither. Tests are marked. We just wanted to figure out a way to test if we marked them all. Meaning running ci with the marker used to skip the tests while disabling connection to the outside world. But it is very low priority I'd say.
Got it, thanks for clarifying.
I can try a minimal CI job that:
- disables outbound network access,
- runs pytest with
-m "not internet", - and fails if any unmarked test still attempts a connection.
I’ll keep it isolated (separate job / non-blocking) so it doesn’t affect existing CI. Let me know if that sounds reasonable.
Look into new action that skips tests that need an internet connection:
xref: #726 (comment)
cc @QuLogic