1
0
mirror of https://github.com/pi-hole/pi-hole synced 2024-10-18 05:49:10 +00:00
pi-hole/test
Christian König 3731b65bd5
Remoce Fedora 34 from tests
Signed-off-by: Christian König <ckoenig@posteo.de>
2022-10-01 10:04:26 +02:00
..
__init__.py
_centos_8.Dockerfile
_debian_10.Dockerfile
_debian_11.Dockerfile
_fedora_35.Dockerfile
_fedora_36.Dockerfile
_ubuntu_20.Dockerfile
_ubuntu_22.Dockerfile
conftest.py
README.md
requirements.txt
setup.py
test_any_automated_install.py
test_any_utils.py Format all /test files with black 2022-09-19 14:50:35 +02:00
test_centos_common_support.py
test_centos_fedora_common_support.py
test_fedora_support.py
tox.centos_8.ini
tox.debian_10.ini
tox.debian_11.ini
tox.fedora_35.ini
tox.fedora_36.ini
tox.ubuntu_20.ini
tox.ubuntu_22.ini Update test requirements 2022-09-19 14:50:35 +02:00

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 :)