Marcus,

     I was not aware of the ctest application.  Thank you for that!  Sadly
'ctest -v', 'ctest -V', 'ctest -VV', 'ctest --output-on-failure' and 'ctest
--debug' all fail to print the message or line number.  Seems the only
thing that I can do is dump the XML file in lib/.unittests.  Not ideal, but
workable.

Thanks!

-Dave

On Wed, Jul 13, 2016 at 11:57 AM, Marcus Müller <[email protected]>
wrote:

> The actual output is written to XML logs – but if you're interested in
> seeing it live, I'd recommend just running "ctest -v" from your build
> directory.
>
> Best regards,
> Marcus
>
>
> On 07/13/2016 03:39 PM, Dave NotTelling wrote:
>
> I am trying to test out my OOT module with CppUnit tests, but I am not
> able to get the message from CPPUNIT_ASSERT_MESSAGE("moo", 1 == 2) to
> output.  All I get is that the test failed (F).  Just getting that message
> is terrible for debugging.  Is there a flag I missed somewhere or some
> configuration that isn't set right?  The only option I have right now is to
> use an if statement to check the condition, print out a message if the
> condition fails, and then call CPPUNIT_FAIL() to bomb out.
>
> Thank you!
>
> -Dave
>
>
> _______________________________________________
> Discuss-gnuradio mailing 
> [email protected]https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to