split tests/test_osmnx.py into an offline and online versions

[jgmbenoit]

Contributing guidelines

• I understand the contributing guidelines

Documentation

• My proposal is not addressed by the documentation or examples

Existing issues

• Nothing similar appears in an existing issue

What problem does your feature proposal solve?

Some distribution (e.g., Debian), tests at building time have to be performed offline (for obvious security reasons). Gathering tests that need access to the internet and those that does not need would simplify the packaging of OSMnx. I suggest to split into two files, however other solutions may do the job: introducing an environment variable for specifying that the tests must be run offline can be a good alternative the job.

What is your proposed solution?

easing distribution packaging

What alternatives have you considered?

Elaborating complex scheme to test at building time only the tests that do not access to the internet.

Additional context

https://salsa.debian.org/python-team/packages/osmnx

[gboeing]

Hi @jgmbenoit, thanks for your suggestion.

We recently refactored the OSMnx tests to change them all to run permanently offline after a single successful live run to build a persistent http response cache (see for instance #1397). This is how we'll be handling the tests going forward so there's no longer a need to hit live online APIs when the tests run. It's all offline and uses the persistent cache now. You can do this either through 1) Github actions, like this repo does; or 2) by running tests/run_tests.sh.

If you specifically want to test against live online APIs in the future, you just delete or invalidate the cache first.