mirror of
https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion
synced 2024-11-22 20:42:04 +01:00
ffffdc86bd
Matching globs are common because the script runs in the certs directory. The test uses a suffix match as the test domains don't include subdomains, although such cases should probably be considered. Fix the le3.wtf test. The existing add_location_configuration modifies "default"; a second add is not necessary. Fixes #763 |
||
|---|---|---|
| .. | ||
| github_actions | ||
| setup | ||
| tests | ||
| config.sh | ||
| README.md | ||
| run.sh | ||
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