Verify unit tests are still working for piboxd
|Status:||In Progress||Start date:||27 Feb 2016|
|Target version:||PiBox - 1.1.0 - Upgrades|
|Severity:||02 - High|
The unit tests may be broken, specifically with respect to the GWIRELESS and SWIRELESS tests. However, all tests should be run individually and manually to verify they still perform correctly and pass.
RM #503: Added logging messages and test for null queue when testing expiration of a stream.
RM #503: Test for invalid action type before testing for invalid timestamp to avoid incorrect error message in the former case.
RM #503: Don't abort a failed stream as that leaves a core file. Use exit() instead.
RM #503: Updating unit tests.
Clean up unit tests so they are less verbose by default and specify PASS or FAIL after the test name.
Added validation tests for everything up to heartbeate and made sure they properly clean up so they can all be run
in sequence from a single test run.
Allow generation of a unique UUID for some tests.
Capture connection reset by peer message from nc but don't assume failure because of it.
Run piboxd with -t12 to limit stream timeouts to something useful within the unit tests.
Check for core files ater each test run and notify user.
#1 Updated by Hammel about 3 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 40
Everything up to heartbeate has been retested and cleaned up. There are few problems with the code but there were some definite problems in the unit tests. I've reduced the verbosity of the unit tests by default and added validation checks to the ones up to heartbeate. They now run cleaner when run individually and in sequence in a single test run.
More cleanup to follow...