Joseph Henry
9a25a627bb
WIP: Unit tests -- more generalization
|
10 years ago | |
|---|---|---|
| .. | ||
| _results | 10 years ago | |
| httpd | 10 years ago | |
| redis | 10 years ago | |
| ._.DS_Store | 10 years ago | |
| README.md | 10 years ago | |
| build.sh | 10 years ago | |
| e5cd7a9e1c5311ab.conf | 10 years ago | |
| intercept | 10 years ago | |
| libintercept.so.1.0 | 10 years ago | |
| liblwip.so | 10 years ago | |
| monitor_identity.public | 10 years ago | |
| monitor_identity.secret | 10 years ago | |
| netcon_identity.public | 10 years ago | |
| netcon_identity.secret | 10 years ago | |
| test.sh | 10 years ago | |
| zerotier-cli | 10 years ago | |
| zerotier-one | 10 years ago | |
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