tyler.durden
/
pi-hole
mirror of https://github.com/pi-hole/pi-hole.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
pi-hole/test
History
Christian König 518cbd10e0
Rename also in docker files 
Signed-off-by: Christian König <ckoenig@posteo.de>
 		2022-07-06 22:58:14 +02:00
..
README.md unit test for umask problems in #3177 and #2730 (#3191) 2021-11-11 16:44:57 +00:00
__init__.py setupVar tests passing for debian & centos 2016-10-10 23:14:39 -05:00
_centos_7.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_centos_8.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_debian_10.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_debian_11.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_fedora_34.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_ubuntu_18.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_ubuntu_20.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_ubuntu_21.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
_ubuntu_22.Dockerfile Rename also in docker files 2022-07-06 22:58:14 +02:00
centos7.epel.override Fix for epel mirror timeouts 2022-07-03 11:48:12 -07:00
conftest.py Update the tests (#4427) 2021-11-18 01:03:37 +00:00
requirements.txt Update the tests (#4427) 2021-11-18 01:03:37 +00:00
setup.py Remove Travis CI config 2020-12-01 10:02:31 +00:00
test_any_automated_install.py Change tests to mock dialog 2022-07-03 11:08:56 -07:00
test_any_utils.py Split the tests, too. Enhance the descriptions 2022-04-19 18:35:56 +01:00
test_centos_7_support.py Change tests to mock dialog 2022-07-03 11:08:56 -07:00
test_centos_8_support.py Change tests to mock dialog 2022-07-03 11:08:56 -07:00
test_centos_common_support.py Change tests to mock dialog 2022-07-03 11:08:56 -07:00
test_centos_fedora_common_support.py Update the tests (#4427) 2021-11-18 01:03:37 +00:00
test_fedora_support.py Update the tests (#4427) 2021-11-18 01:03:37 +00:00
tox.centos_7.ini Split new function out into a separte utility script and add a test for it. Can be used in future to organise re/commonly-used code 2022-01-30 23:05:28 +00:00
tox.centos_8.ini Split new function out into a separte utility script and add a test for it. Can be used in future to organise re/commonly-used code 2022-01-30 23:05:28 +00:00
tox.debian_10.ini Split new function out into a separte utility script and add a test for it. Can be used in future to organise re/commonly-used code 2022-01-30 23:05:28 +00:00
tox.debian_11.ini Split new function out into a separte utility script and add a test for it. Can be used in future to organise re/commonly-used code 2022-01-30 23:05:28 +00:00
tox.fedora_34.ini Split new function out into a separte utility script and add a test for it. Can be used in future to organise re/commonly-used code 2022-01-30 23:05:28 +00:00
tox.ubuntu_18.ini Split new function out into a separte utility script and add a test for it. Can be used in future to organise re/commonly-used code 2022-01-30 23:05:28 +00:00
tox.ubuntu_20.ini Split new function out into a separte utility script and add a test for it. Can be used in future to organise re/commonly-used code 2022-01-30 23:05:28 +00:00
tox.ubuntu_21.ini Re-add Ubuntu21 tests 2022-06-25 23:04:16 +02:00
tox.ubuntu_22.ini Update test to reflect currently supported OS 2022-06-20 10:34:32 +02:00

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