Jeff and I worked out a patch for this. It turns out that it's not limited to the ARM platform, it's a bug in TestTestRunner.cpp which affect *all* architectures, but only show up (for me, thus far) on ARM & PPC Linux.
The intent in TestTestRunner.cpp is for MockTest to override Test::RunImpl(TestResults&), but at some point that base method was refactored to be Test::RunImpl(void), therefore MockTest::RunImpl(TestResults&) was not actually being run. So TestTestRunner.cpp was pretty much doing no useful testing. Here is the patch which fixes it (tested on Linux [i686, x86_64, arm, ppc], MacOSX [x86_64] and Windows [i386]): https://github.com/makestuff/libutpp/commit/e8194a74846959b18958236874ebc361fe036cc5 Notice I have had to save and restore the testing context in each test using the FixtureBase::RunTestsIf() delegate, since the intent of these tests is to verify the behaviour of the testing context itself. Chris On Thu, 2011-12-07 at 17:11, Jeffrey Franks wrote: > Hi, > > I'm new to this list and am looking for help on resolving a > TestUnitTest++ issue. > I've grep'd the source code for 107 and do not find it. > Can anyone help me with discovery of what is going on here? > > The response from running TestUnitTest++ on the ARM target is: > > root@...# TestUnitTest++ > :107: error: Failure in test: Expected 2 but was 0 > FAILURE: 1 out of 174 tests failed (1 failures). > Test time: 0.15 seconds. > root@...# > > Thanks, > Jeff Franks > ------------------------------------------------------------------------------ 10 Tips for Better Server Consolidation Server virtualization is being driven by many needs. But none more important than the need to reduce IT complexity while improving strategic productivity. Learn More! http://www.accelacomm.com/jaw/sdnl/114/51507609/ _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
