Trevor

Three stages required: short: 2m long: ~5m full: ~1h

Need a soak-test mechanism that captures a flaky test (e.g. DHCP).

=============== Report summary Test results codes: PASS - the test has been successful FAIL - the test has been unsuccessful WARN - the test has generated one or more warnings...

SKIP base.switch.ping PASS base.target.ping target PASS security.ports.nmap

pull image run image execute in image options etc...

when using faux with a physical interface, don't rename it when it's moved into the container... so when the container is killed it appears bash in the host properly.

e.g., daqf/test_ping:0.9.5 should be a downloadable thing to speed up system use for a released version.

Need clarification on useful test output to include in the report.

Calculate overall time to test a device

1

Just something useful for tracking system behavior. From device-detect to test-finished!

specifically more direct clarity around logging events (e.g. links to stackdriver)