I've noticed that Django Spanner uses tox as a test base. Other Google Python packages are using nox with generated noxfiles (with lint, docs, coverage, system and unit testing sessions) - see python-spanner noxfile.py as an example. If we're going to move this API to the original Python Spanner client, we probably should use nox here to stay in touch with the original test configurations.
Reactions are currently unavailable
I've noticed that Django Spanner uses tox as a test base. Other Google Python packages are using nox with generated noxfiles (with lint, docs, coverage, system and unit testing sessions) - see python-spanner noxfile.py as an example. If we're going to move this API to the original Python Spanner client, we probably should use nox here to stay in touch with the original test configurations.