1
0
mirror of https://github.com/pi-hole/pi-hole synced 2024-10-31 20:59:00 +00:00
pi-hole/test
bcambl 97e11bd94e
ensure installation dependencies for FTL tests which rely on /etc/init.d
Signed-off-by: bcambl <blayne@blaynecampbell.com>
2019-08-20 11:42:12 -07:00
..
__init__.py setupVar tests passing for debian & centos 2016-10-10 23:14:39 -05:00
centos.Dockerfile
conftest.py
debian.Dockerfile
fedora.Dockerfile Merge conflict Fedora Dockerfile for tests pinned to 30 2019-08-20 11:40:18 -07:00
README.md Update README.md 2018-07-12 10:22:50 -05:00
test_000_build_containers.py
test_automated_install.py ensure installation dependencies for FTL tests which rely on /etc/init.d 2019-08-20 11:42:12 -07:00
test_centos_fedora_support.py update centos version check test 2018-08-29 22:16:11 -06:00
test_shellcheck.py

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 dependancies, installing dependancies, 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 dependancies 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 :)