Bug #503
closed
Verify unit tests are still working for piboxd
Added by Hammel about 8 years ago.
Updated about 4 years ago.
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.
- 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...
- Severity changed from 01 - Critical to 02 - High
- Target version changed from 0.11.0 to 0.12.0
- Priority changed from Immediate to Urgent
- Target version changed from 0.12.0 to 1.1.0 - Upgrades
Currently failing on TWOCAM, possibly due to changes made to allow low and high resolution streams. Fix that, and try -a again.
- % 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.
- 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.
Also available in: Atom
PDF
Updated by