void/ZeroTierOne
2
0
Fork 0
mirror of https://github.com/zerotier/ZeroTierOne.git synced 2025-07-24 19:22:51 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
ZeroTierOne/netcon/docker-test
History
Joseph Henry 6a3f230555 Unit test info added to README
2015-11-23 06:20:01 -08:00
..
httpd Removed old READMEs and OS files 2015-11-23 05:21:20 -08:00
nginx Removed old READMEs and OS files 2015-11-23 05:21:20 -08:00
nodejs/nodejs-0.10.36-4.fc23 Updated README, fixed node.js test bug 2015-11-23 05:59:05 -08:00
redis/redis-3.0.4-1.fc23.x86_64 Removed old READMEs and OS files 2015-11-23 05:21:20 -08:00
build.sh Test/Code Refactor in preparation for merge 2015-11-20 01:08:38 -08:00
e5cd7a9e1c5311ab.conf Test/Code Refactor in preparation for merge 2015-11-20 01:08:38 -08:00
monitor_identity.public Test/Code Refactor in preparation for merge 2015-11-20 01:08:38 -08:00
monitor_identity.secret Test/Code Refactor in preparation for merge 2015-11-20 01:08:38 -08:00
netcon_identity.public Test/Code Refactor in preparation for merge 2015-11-20 01:08:38 -08:00
netcon_identity.secret Test/Code Refactor in preparation for merge 2015-11-20 01:08:38 -08:00
README.md Unit test info added to README 2015-11-23 06:20:01 -08:00
test.sh Updated README, fixed node.js test bug 2015-11-23 05:59:05 -08:00

README.md

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
  1. 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
  1. 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