Docker container for Pytest

[nucleogenic]

Container providing an alternative to a local Python venv for test execution.

Usage

Basic usage:

docker compose run pytest

Running with specific parameters:

docker compose run pytest -v -k test_download_file

Accessing a shell:

docker compose run --entrypoint=bash pytest

The container can be rebuilt if needed (e.g. when requirements-dev.txt is updated) with:

docker compose build pytest [--no-cache --progress=plain]

[rdmark]

@nucleogenic Minor thing, but it'd be helpful if you could make branches in this project instead of your fork. It makes it slightly more convenient to check out your work branch and try out the code. :)

[rdmark]

This change means that you have to override --base_url now when running in a default non-dockerized environment. Is there a particular reason for changing it for the purpose of the docker environment?

BTW, this is also a good reminder to write a README with some pointers / reminders when running the tests. :)

[nucleogenic]

Fair point! I can probably define an environment var inside the container and set some defaults based on container vs non container environments. Can you describe the environment you want to run the tests on? e.g. on dev machine against local web.py process, dev machine against remote Pi, executed directly on the Pi?

[rdmark]

My main use case is "executed directly on the Pi" but I can imagine that the other two scenarios are potentially useful for other people.

[nucleogenic]

Base URL now defaults to http://localhost:8080 as before, unless the env var DOCKER is truthy.

[rdmark]

Seems good. Just one remark.

[nucleogenic]

@rdmark Please could you re-test this in your Pi environment?

You can now use the --home_dir=/home/user parameter when executing the tests.

[rdmark]

Thank for the excellent improvements!