Re: [Boost-users] testing command-line interface using Boost.Test

Subject: Re: [Boost-users] testing command-line interface using Boost.Test
From: Olaf Meeuwissen (olaf.meeuwissen_at_[hidden])
Date: 2011-10-04 19:59:35

Gennadiy Rozental <rogeeff_at_[hidden]> writes:

> Olaf Meeuwissen <olaf.meeuwissen <at> avasys.jp> writes:
>
>> My guess is that the execution_monitor gets a go at the system error
>> before the unit_test_monitor gets a chance and I would really have to
>
> unit_test_monitor IS execution_monitor. No the issue here is that it picks up
> the value every time it start new test case from the value of runtime parameter,
> so you really can't have it differently in a different test cases.

I was referring to the execution_monitor instance that is used in
framework::run() which appears to be another instance than the
execution_monitor singleton but I readily admit that I don't really
understand what's going on in there.

>> Thanks for the help so far.  I'm still open to suggestions but it looks
>> like I'll be going with two test runners, each with their own main so
>> that can set BOOST_TEST_CATCH_SYSTEM_ERRORS before unit_test_main().
>
> You might as well use CLA. It's still going to have one global value for all
> test cases.

I know, but it's just that the automake provided test infrastructure
makes it cumbersome to differentiate the CLAs for individual runners.
It is easier to set the value from within the runner then.

> You can also rebuild your boost version and comment out SIGCHLD handling.

Thanks, but no thanks.  Mucking around in Boost code and rebuilding is
not my idea of fun.  I really just want to use it as is to help get my
job done.

Thanks,
-- 
Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962               Help support software freedom
                 http://www.fsf.org/jf?referrer=1962