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-26 08:53:52 +01:00
Code Issues Releases Activity
746704cf30
docker-letsencrypt-nginx-pr.../test
History
Nicolas Duchon 746704cf30
tests: use pre generated dhparam.pem on companion
2021-12-08 01:42:27 +01:00
..
github_actions CI/CD: Test against both Boulder and Pebble 2020-12-28 11:31:20 +01:00
setup tests: use pre generated dhparam.pem on companion 2021-12-08 01:42:27 +01:00
tests tests: use pre generated dhparam.pem on companion 2021-12-08 01:42:27 +01:00
config.sh Enable local tests with both Boulder and Pebble 2020-12-28 16:28:18 +01:00
README.md chore: project name change 2021-04-05 00:27:52 +02:00
run.sh chore: project name change 2021-04-05 00:27:52 +02:00

README.md

acme-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/acme-companion.git
cd acme-companion
test/setup/setup-local.sh --setup

Then build the docker image and run the tests:

docker build -t nginxproxy/acme-companion .
test/run.sh nginxproxy/acme-companion

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

test/run.sh -t docker_api nginxproxy/acme-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 nginxproxy/acme-companion

To remove the test setup:

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