|
|
||
|---|---|---|
| .. | ||
| __init__.py | ||
| _centos_9.Dockerfile | ||
| _debian_11.Dockerfile | ||
| _debian_12.Dockerfile | ||
| _fedora_39.Dockerfile | ||
| _fedora_40.Dockerfile | ||
| _ubuntu_20.Dockerfile | ||
| _ubuntu_22.Dockerfile | ||
| _ubuntu_23.Dockerfile | ||
| _ubuntu_24.Dockerfile | ||
| conftest.py | ||
| README.md | ||
| requirements.txt | ||
| setup.py | ||
| test_any_automated_install.py | ||
| test_any_utils.py | ||
| test_centos_fedora_common_support.py | ||
| tox.centos_9.ini | ||
| tox.debian_11.ini | ||
| tox.debian_12.ini | ||
| tox.fedora_39.ini | ||
| tox.fedora_40.ini | ||
| tox.ubuntu_20.ini | ||
| tox.ubuntu_22.ini | ||
| tox.ubuntu_23.ini | ||
| tox.ubuntu_24.ini | ||
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 toxtox
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 :)