You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
pi-hole/test
Christian König cfc0d07173
Remove CentOS8 from test suite
4 weeks ago
..
README.md
__init__.py
_centos_9.Dockerfile
_debian_10.Dockerfile
_debian_11.Dockerfile
_debian_12.Dockerfile Add tests for Debian 12 1 year ago
_fedora_39.Dockerfile Drop Fedora 36 and add Fedora 39 to the test suite 8 months ago
_fedora_40.Dockerfile Add Ubuntu 24.04 and Fedora 40, remove Fedora 38 2 months ago
_ubuntu_20.Dockerfile
_ubuntu_22.Dockerfile
_ubuntu_23.Dockerfile Add Ubuntu 23 to test suite 1 year ago
_ubuntu_24.Dockerfile Add Ubuntu 24.04 and Fedora 40, remove Fedora 38 2 months ago
conftest.py REVISIT: Don't rely on existence of setupVars.conf 1 year ago
requirements.txt Bump tox from 4.15.0 to 4.15.1 in /test 4 weeks ago
setup.py
test_any_automated_install.py Reduce code duplication in FTL arch detect tests. 6 months ago
test_any_utils.py Switch to new branch name for FTL v6 development 1 year ago
test_centos_fedora_common_support.py
tox.centos_9.ini Remove the EPEL related tests on centos/fedora - no longer neccasery 1 year ago
tox.debian_10.ini Use buildx to create docker test images 1 year ago
tox.debian_11.ini Use buildx to create docker test images 1 year ago
tox.debian_12.ini Add tests for Debian 12 1 year ago
tox.fedora_39.ini Drop Fedora 36 and add Fedora 39 to the test suite 8 months ago
tox.fedora_40.ini Add Ubuntu 24.04 and Fedora 40, remove Fedora 38 2 months ago
tox.ubuntu_20.ini Use buildx to create docker test images 1 year ago
tox.ubuntu_22.ini Use buildx to create docker test images 1 year ago
tox.ubuntu_23.ini Add Ubuntu 23 to test suite 1 year ago
tox.ubuntu_24.ini Add Ubuntu 24.04 and Fedora 40, remove Fedora 38 2 months ago

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