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 366345e87e
Fix no_installs
1 year ago
..
README.md
__init__.py
_centos_8.Dockerfile
_centos_9.Dockerfile
_debian_10.Dockerfile
_debian_11.Dockerfile
_fedora_36.Dockerfile
_fedora_37.Dockerfile
_fedora_38.Dockerfile
_ubuntu_20.Dockerfile
_ubuntu_22.Dockerfile
_ubuntu_23.Dockerfile Add Ubuntu 23 to test suite 1 year ago
conftest.py REVISIT: Don't rely on existence of setupVars.conf 1 year ago
requirements.txt Bump pytest-testinfra from 8.0.0 to 8.1.0 in /test 1 year ago
setup.py
test_any_automated_install.py Fix no_installs 1 year ago
test_any_utils.py Don't check and install old FTL config file 1 year ago
test_centos_fedora_common_support.py
tox.centos_8.ini Remove the EPEL related tests on centos/fedora - no longer neccasery 1 year ago
tox.centos_9.ini Remove the EPEL related tests on centos/fedora - no longer neccasery 1 year ago
tox.debian_10.ini
tox.debian_11.ini
tox.fedora_36.ini Remove the EPEL related tests on centos/fedora - no longer neccasery 1 year ago
tox.fedora_37.ini Remove the EPEL related tests on centos/fedora - no longer neccasery 1 year ago
tox.fedora_38.ini centos_common_support.py was removed 1 year ago
tox.ubuntu_20.ini
tox.ubuntu_22.ini
tox.ubuntu_23.ini Add Ubuntu 23 to test suite 1 year 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 :)