flywithu/kopano-docker
1
0
Fork 0
mirror of https://github.com/zokradonh/kopano-docker.git synced 2026-08-22 05:42:54 +00:00
Code Issues Releases Wiki Activity

Further improve commander test cases (#233)

Browse Source 
* add a more detailed example based on https://github.com/SimonBaeumer/commander/pull/82
include test for '!include /usr/share/kopano/ldap.openldap.cfg'?
* add readme on testing
* add goss wait files for dagent and spooler
This commit is contained in:
Felix Bartels
2019-09-12 13:26:05 +02:00
committed by GitHub
parent c057337097
commit ab35522da5
6 changed files with 75 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+10
View File
@@ -111,6 +111,16 @@ If you are running a private Docker Registry then you may also change `docker_re
The built image includes your subscription key! Do not push this image to any public registry like e.g. https://hub.docker.com!
### When building my own containers, how can I make sure my build works as expected?
This project includes a few automated tests that can be run to ensure that containers start up and are operational.
The startup test can be executed by calling `make test-startup`. It spins up all containers and checks if they listen on their expected interfaces afterwards and executs some commands.
A more detailed test can be executed by calling `make test-goss`. This uses [Goss](https://github.com/aelsabbahy/goss) and its helper [dcgoss](https://github.com/aelsabbahy/goss/tree/master/extras/dcgoss) to validate the container configuration at runtime. These tests have not been implemented for all containers yet, but as an upside the same validation is used as part of the container healtcheck. Contributions are welcome!
Testing the startup scripts of the containers is still a work in progress. When running `make test-commander` then [Commander](https://github.com/SimonBaeumer/commander) will be used to test output of the `version.sh` script and the container startup scripts.
### What if I want to use a different front facing proxy than the one in docker-compose? Or just some part of the compose file?
While using kweb is recommended, this is of course possible.