Bug #503
closed
Verify unit tests are still working for piboxd
100%
Description
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.
Updated by Hammel almost 9 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...
Updated by Hammel over 8 years ago
- Severity changed from 01 - Critical to 02 - High
Updated by Hammel about 8 years ago
- Target version changed from 0.11.0 to 0.12.0
Updated by Hammel almost 6 years ago
- Target version changed from 0.12.0 to 1.1.0 - Upgrades
Updated by Hammel almost 5 years ago
Currently failing on TWOCAM, possibly due to changes made to allow low and high resolution streams. Fix that, and try -a again.
Updated by Hammel almost 5 years ago
- % Done changed from 40 to 80
Everything is working except the very last test: iot. Since the multicast tests were not really fully implemented I suspect that the iot tests are not either. Some of the fixes were in the tests. Some were the code, so the tests worked.
But this is just about done now.
Updated by Hammel almost 5 years ago
- Status changed from In Progress to Closed
- % Done changed from 80 to 100
Done. The IoT tests could be dropped because piboxd no longer handles those requests (get/set requests). It only handles registration over multicast. The REST API (Ironman WWW project) handles all other requests.
Tested, committed and pushed.
Closing issue.