History

Sylvain Lamontagne 2e943378d1 Too many arguments while pushing route So I was trying to push a route to my client and the script failed with 'too many arguments', I reworked this part and took the opportunity to rework a little bit the way push and routes were handled. I also added some tests and validated that what I changed would not break what was there before.		2016-09-22 16:02:59 -04:00
..
client	test: Migrate from old test scripts	2016-08-31 12:42:53 -07:00
tests	Too many arguments while pushing route	2016-09-22 16:02:59 -04:00
config.sh	test: Migrate from old test scripts	2016-08-31 12:42:53 -07:00
README.md	test: Start to migrate to docker's upstream tests	2016-08-31 11:39:36 -07:00
run.sh	test: Start to migrate to docker's upstream tests	2016-08-31 11:39:36 -07:00

README.md

Tests

Philosophy is to not re-invent the wheel while allowing users to quickly test repository specific tests.

Example invocation from top-level of repository:

docker build -t openvpn .
tests/run.sh openvpn

More details: https://github.com/docker-library/official-images/tree/master/test

Continuous Integration

The set of scripts defined by config.sh are run every time a pull request or push to the repository is made.

Maintenance

Periodically these scripts may need to be synchronized with their upsteam source. Would be nice to be able to just use them from upstream if it such a feature is added later to avoid having to copy them in place.