Test your Tox knowledge with a free interactive quiz — 19 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What happens if a dependency listed in `deps` (or the project's own declared dependencies) isn't actually compatible with one of the Python versions in `envlist`?
In this round
What happens if a dependency listed in `deps` (or the project's own declared dependencies) isn't actually compatible with one of the Python versions in `envlist`?
What does the `[testenv]` section (without a specific environment name suffix) represent in a `tox.ini` file, as opposed to `[testenv:py311]`?
What does `tox --parallel` (or `-p`) do?
What underlying tool does tox rely on to actually create the isolated per-environment virtual environments?
What is the relationship between tox and a CI system like GitHub Actions?
What does running `tox -e py311` (specifying a single environment) do, as opposed to running plain `tox`?
What is the purpose of a `skip_install = true` setting on a tox environment?
What is the significance of tox testing against multiple Python versions specifically for a library maintainer publishing a package to PyPI?
What is the purpose of a `tox.ini` file?
What is the relationship between tox and `pytest` specifically — does using tox require using pytest as the test runner?
What is a reasonable comparison between tox and simply using GitHub Actions' own Python version matrix (`strategy.matrix.python-version`) without tox?
What problem does tox's per-environment isolation specifically solve, compared to just running tests in a developer's existing local environment?