Re: [Boost-users] [Boost.Test] BOOST_FAIL vs BOOST_ERROR

Subject: Re: [Boost-users] [Boost.Test] BOOST_FAIL vs BOOST_ERROR
From: Greg Christopher (gchristopher_at_[hidden])
Date: 2009-05-26 11:58:50

> -----Original Message-----
> From: boost-users-bounces_at_[hidden] [mailto:boost-users-
> bounces_at_[hidden]] On Behalf Of Gennadiy Rozental
> Sent: Friday, May 22, 2009 4:56 AM
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] [Boost.Test] BOOST_FAIL vs BOOST_ERROR
> 
> Greg Christopher <gchristopher <at> vmware.com> writes:
> > As it turns out this throws off the monitor. If my setup step throws
> this,
> boost test thinks that my test was
> > ill defined (no assertions):
> >
> > Entering test case "TEST_2"
> > Test case TEST_2 doesn't include any assertions
> > Leaving test case "TEST_2"
> > Leaving test suite "BasicTest"
> > Leaving test suite "BasicTest"
> >
> > If I don't abort the setup, this executes all the test cases and
> doesn't say
> it doesn't include any
> > assertions. I suppose the error message is harmless, but incorrect.
> 
> Why was it incorrect? Your test case indeed did not run any assertions.
> This
> warning you can ignore safely in your case.

Well, the message says "include any assertions" not "did not run any assertions". However the bigger issue is: How do I grep the log to see if there was an aborted test run due to setup? I guess I can look for this string "doesn't include any assertions". That seems like I'm doing it by side effect less than a more direct message that explains that the test case chose to quit because setup failed.

Greg

> 
> Gennadiy
> 
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users