Joseph Henry b83aefcf8f Updated README, fixed node.js test bug há 10 anos atrás
..
httpd 8b9b593256 Removed old READMEs and OS files há 10 anos atrás
nginx 8b9b593256 Removed old READMEs and OS files há 10 anos atrás
nodejs b83aefcf8f Updated README, fixed node.js test bug há 10 anos atrás
redis 8b9b593256 Removed old READMEs and OS files há 10 anos atrás
README.md 1f27022fa7 Test/Code Refactor in preparation for merge há 10 anos atrás
build.sh 1f27022fa7 Test/Code Refactor in preparation for merge há 10 anos atrás
e5cd7a9e1c5311ab.conf 1f27022fa7 Test/Code Refactor in preparation for merge há 10 anos atrás
monitor_identity.public 1f27022fa7 Test/Code Refactor in preparation for merge há 10 anos atrás
monitor_identity.secret 1f27022fa7 Test/Code Refactor in preparation for merge há 10 anos atrás
netcon_identity.public 1f27022fa7 Test/Code Refactor in preparation for merge há 10 anos atrás
netcon_identity.secret 1f27022fa7 Test/Code Refactor in preparation for merge há 10 anos atrás
test.sh b83aefcf8f Updated README, fixed node.js test bug há 10 anos atrás

README.md

To run unit tests:

1) Place a blank network config file in this directory (e.g. "e5cd7a9e1c.conf")

  • This will be used to inform test-specific scripts what network to use for testing (create your own, or use the given at your own risk)

2) run build.sh

  • Builds ZeroTier with Network Containers enabled
  • Builds LWIP library
  • Builds library harness
  • Copies all aformentioned files into unit test directory to be used for building docker files

3) run test.sh

  • Will (for now, one at a time), execute each unit test's (test.sh)

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

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