mirror/docker-letsencrypt-nginx-proxy-companion
1
0
Fork 0
mirror of https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion synced 2024-11-22 20:42:04 +01:00
Code Issues Releases Activity
11a534ecc1
docker-letsencrypt-nginx-pr.../test
History
Nicolas Duchon 11a534ecc1
chore: use the nginxproxy/nginx-proxy registry
2021-04-05 00:21:31 +02:00
..
github_actions CI/CD: Test against both Boulder and Pebble 2020-12-28 11:31:20 +01:00
setup chore: use the nginxproxy/nginx-proxy registry 2021-04-05 00:21:31 +02:00
tests chore: use the nginxproxy/nginx-proxy registry 2021-04-05 00:21:31 +02:00
config.sh Enable local tests with both Boulder and Pebble 2020-12-28 16:28:18 +01:00
README.md Update docs and comments 2020-11-27 14:46:45 +01:00
run.sh Move CI/CD from Travis to Github Actions. 2020-12-21 22:04:55 +01:00

README.md

letsencrypt-nginx-proxy-companion test suite

The test suite can be run locally on a Linux or macOS host.

To prepare the test setup:

git clone https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion.git
cd docker-letsencrypt-nginx-proxy-companion
test/setup/setup-local.sh --setup

Then build the docker image and run the tests:

docker build -t jrcs/letsencrypt-nginx-proxy-companion .
test/run.sh jrcs/letsencrypt-nginx-proxy-companion

You can limit the test run to specific test(s) with the -t flag:

test/run.sh -t docker_api jrcs/letsencrypt-nginx-proxy-companion

When running the test suite, the standard output of each individual test is captured and compared to its expected-std-out.txt file. When developing or modifying a test, you can use the -d flag to disable the standard output capture by the test suite.

test/run.sh -d jrcs/letsencrypt-nginx-proxy-companion

To remove the test setup:

test/setup/setup-local.sh --teardown