Bug #503

Verify unit tests are still working for piboxd

Added by Hammel over 5 years ago. Updated over 1 year ago.

Status:ClosedStart date:27 Feb 2016
Priority:UrgentDue date:
Assignee:Hammel% Done:


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.

Associated revisions

Revision b977ef12
Added by Hammel over 5 years ago

RM #503: Added logging messages and test for null queue when testing expiration of a stream.

Revision 75be2ba6
Added by Hammel over 5 years ago

RM #503: Test for invalid action type before testing for invalid timestamp to avoid incorrect error message in the former case.

Revision 0b7d2826
Added by Hammel over 5 years ago

RM #503: Don't abort a failed stream as that leaves a core file. Use exit() instead.

Revision 756de70d
Added by Hammel over 5 years ago

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.

Revision fa03a6ca
Added by Hammel over 5 years ago

RM #503: Verified and updated unit tests giflist through sipv4.

Revision d92e0299
Added by Hammel about 5 years ago

RM #503: Changed "echo" to "fail" in various places. Added additional/missing headers to some tests.


#1 Updated by Hammel over 5 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...

#2 Updated by Hammel about 5 years ago

  • Severity changed from 01 - Critical to 02 - High

#3 Updated by Hammel almost 5 years ago

  • Target version changed from 0.11.0 to 0.12.0

#4 Updated by Hammel about 3 years ago

  • Priority changed from Immediate to Urgent

#5 Updated by Hammel over 2 years ago

  • Target version changed from 0.12.0 to 1.1.0 - Upgrades

#6 Updated by Hammel over 1 year ago

Currently failing on TWOCAM, possibly due to changes made to allow low and high resolution streams. Fix that, and try -a again.

#7 Updated by Hammel over 1 year 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.

#8 Updated by Hammel over 1 year 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.

Also available in: Atom PDF