allanger/container-openvpn
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Activity
62b6cc3db9
container-openvpn/test
History
Kyle Manna 379766fc5e misc: Switch from data container to data volume 
* Use the `docker volume` mechanism.
* Less confusing and makes more sense.
* Released in ~ docker v1.9
2016-09-03 16:17:50 -07:00
..
client test: Migrate from old test scripts 2016-08-31 12:42:53 -07:00
tests misc: Switch from data container to data volume 2016-09-03 16:17:50 -07: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.