1
0
mirror of https://github.com/pi-hole/pi-hole synced 2025-04-10 21:25:44 +00:00
pi-hole/test
dependabot[bot] d6e25403ee
Bump tox from 4.2.8 to 4.3.5 in /test
Bumps [tox](https://github.com/tox-dev/tox) from 4.2.8 to 4.3.5.
- [Release notes](https://github.com/tox-dev/tox/releases)
- [Changelog](https://github.com/tox-dev/tox/blob/main/docs/changelog.rst)
- [Commits](https://github.com/tox-dev/tox/compare/4.2.8...4.3.5)

---
updated-dependencies:
- dependency-name: tox
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2023-01-21 10:01:41 +00:00
..
__init__.py setupVar tests passing for debian & centos 2016-10-10 23:14:39 -05:00
_centos_8.Dockerfile Add initscripts to CentOS8 dockerfile 2022-10-08 22:08:39 +02:00
_centos_9.Dockerfile
_debian_10.Dockerfile
_debian_11.Dockerfile
_fedora_36.Dockerfile
_fedora_37.Dockerfile add Fedora 37 to distro-test 2022-12-17 04:18:38 -05:00
_ubuntu_20.Dockerfile
_ubuntu_22.Dockerfile
conftest.py
README.md
requirements.txt
setup.py
test_any_automated_install.py
test_any_utils.py
test_centos_common_support.py
test_centos_fedora_common_support.py
test_fedora_support.py
tox.centos_8.ini Set testenv explicitly 2022-12-18 14:41:18 +01:00
tox.centos_9.ini
tox.debian_10.ini
tox.debian_11.ini
tox.fedora_36.ini
tox.fedora_37.ini
tox.ubuntu_20.ini
tox.ubuntu_22.ini Set testenv explicitly 2022-12-18 14:41:18 +01: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 :)