pi-hole/test
dependabot[bot] 24ade13c02
Bump pytest-xdist from 3.5.0 to 3.6.1 in /test
Bumps [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) from 3.5.0 to 3.6.1.
- [Release notes](https://github.com/pytest-dev/pytest-xdist/releases)
- [Changelog](https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst)
- [Commits](https://github.com/pytest-dev/pytest-xdist/compare/v3.5.0...v3.6.1)

---
updated-dependencies:
- dependency-name: pytest-xdist
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2024-05-04 10:52:00 +00:00
..
README.md
__init__.py
_centos_8.Dockerfile
_centos_9.Dockerfile
_debian_10.Dockerfile
_debian_11.Dockerfile
_debian_12.Dockerfile
_fedora_38.Dockerfile
_fedora_39.Dockerfile Drop Fedora 36 and add Fedora 39 to the test suite 2023-11-07 22:24:34 +01:00
_ubuntu_20.Dockerfile
_ubuntu_22.Dockerfile
_ubuntu_23.Dockerfile
conftest.py
requirements.txt Bump pytest-xdist from 3.5.0 to 3.6.1 in /test 2024-05-04 10:52:00 +00:00
setup.py
test_any_automated_install.py Reduce code duplication in FTL arch detect tests. 2024-01-08 18:26:59 +00:00
test_any_utils.py
test_centos_fedora_common_support.py
tox.centos_8.ini
tox.centos_9.ini
tox.debian_10.ini
tox.debian_11.ini
tox.debian_12.ini
tox.fedora_38.ini
tox.fedora_39.ini Drop Fedora 36 and add Fedora 39 to the test suite 2023-11-07 22:24:34 +01:00
tox.ubuntu_20.ini
tox.ubuntu_22.ini
tox.ubuntu_23.ini

README.md

Recommended way to run tests

Make sure you have Docker and Python w/pip package manager.

From command line all you need to do is:

  • pip install tox
  • tox

Tox handles setting up a virtual environment for python dependencies, installing dependencies, building the docker images used by tests, and finally running tests. It's an easy way to have travis-ci like build behavior locally.

Alternative py.test method of running tests

You're responsible for setting up your virtual env and dependencies in this situation.

py.test -vv -n auto -m "build_stage"
py.test -vv -n auto -m "not build_stage"

The build_stage tests have to run first to create the docker images, followed by the actual tests which utilize said images. Unless you're changing your dockerfiles you shouldn't have to run the build_stage every time - but it's a good idea to rebuild at least once a day in case the base Docker images or packages change.

How do I debug python?

Highly recommended: Setup PyCharm on a Docker enabled machine. Having a python debugger like PyCharm changes your life if you've never used it :)