From 71b38a48ac1ccf1d0080193b35dc850e2227b729 Mon Sep 17 00:00:00 2001 From: Joseph Henry Date: Mon, 23 Nov 2015 06:22:09 -0800 Subject: Replaced README --- netcon/docker-test/README.md | 33 --------------------------------- 1 file changed, 33 deletions(-) delete mode 100644 netcon/docker-test/README.md (limited to 'netcon/docker-test') diff --git a/netcon/docker-test/README.md b/netcon/docker-test/README.md deleted file mode 100644 index a3b21e1d..00000000 --- a/netcon/docker-test/README.md +++ /dev/null @@ -1,33 +0,0 @@ -### Unit Tests - -To run unit tests: - -1) Set up your own network, use its network id as follows: - -2) Place a blank network config file in this directory (e.g. "e5cd7a9e1c5311ab.conf") - - This will be used to inform test-specific scripts what network to use for testing - -3) run build.sh - - Builds ZeroTier-One with Network Containers enabled - - Builds LWIP library - - Builds intercept library - - Copies all aformentioned files into unit test directory to be used for building docker files - -4) run test.sh - - Will execute each unit test's (test.sh) one at a time and populate _results/ - - -### Anatomy of a unit test - -A) Each unit test's test.sh will: - - temporarily copy all built files into local directory - - build test container - - build monitor container - - remove temporary files - - run each container and perform test and monitoring specified in netcon_entrypoint.sh and monitor_entrypoint.sh - -B) Results will be written to the 'zerotierone/docker-test/_result' directory - - Results will be a combination of raw and formatted dumps to files whose names reflect the test performed - - In the event of failure, 'FAIL.' will be appended to the result file's name - - (e.g. FAIL.my_application_1.0.2.x86_64) - - In the event of success, 'OK.' will be appended -- cgit v1.2.3