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
dependabot[bot] 05707c624d
Bump pytest from 8.3.2 to 8.3.3 in /test 
Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.3.2 to 8.3.3.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](https://github.com/pytest-dev/pytest/compare/8.3.2...8.3.3)

---
updated-dependencies:
- dependency-name: pytest
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
 		2024-09-14 10:36:07 +00: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_9.Dockerfile Disable SELINUX on CentOS 9 test dockerfile 2024-09-01 22:30:45 +02:00
_debian_11.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
_debian_12.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
_fedora_39.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
_fedora_40.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
_ubuntu_20.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
_ubuntu_22.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
_ubuntu_23.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
_ubuntu_24.Dockerfile Fix Dockerfile syntax ENV legacy warning 2024-07-02 20:45:34 +02:00
conftest.py REVISIT: Don't rely on existence of setupVars.conf 2023-05-27 11:51:16 +01:00
requirements.txt Bump pytest from 8.3.2 to 8.3.3 in /test 2024-09-14 10:36:07 +00:00
setup.py Format all /test files with black 2022-09-19 14:50:35 +02:00
test_any_automated_install.py Reduce code duplication in FTL arch detect tests. 2024-01-08 18:26:59 +00:00
test_any_utils.py Remove obsolet getFTLPIDFile() 2024-07-27 22:00:52 +02:00
test_centos_fedora_common_support.py Format all /test files with black 2022-09-19 14:50:35 +02:00
tox.centos_9.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.debian_11.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.debian_12.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.fedora_39.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.fedora_40.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.ubuntu_20.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.ubuntu_22.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.ubuntu_23.ini Set column width to 120 2024-07-02 20:39:22 +02:00
tox.ubuntu_24.ini Set column width to 120 2024-07-02 20:39:22 +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 :)