Boost Testing :
Subject: Re: [Boost-testing] Testing
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-09-12 17:13:47
On 09/12/2018 10:30 AM, Robert Ramey via Boost-Testing wrote:
> On 9/12/18 8:26 AM, Steven Watanabe via Boost-Testing wrote:
>> On 09/12/2018 09:03 AM, Robert Ramey via Boost-Testing wrote:
>>> <snip> What
>>> do I have to do to be sure that compilers which do not support C++14 or
>>> above are skipped?
>> Add [ config.requires /some list of required C++14 features/ ]
>> to the project requirements.Â See
> This looks what I do now for certain specific tests.Â OK.Â But seems
> cumbersome to add this to all the tests.Â Is there a convenient way to
> specify that the whole test suite is to be skipped for compilers which
> don't support some specific feature?
# Automatically add requirements to every target
# in the Jamfile.
project : requirements [ config.requires ... ] ;
>Â It seems to me that this is
> essential if libraries are going to differ as to what level of C++
> compliance they offer.
> At one time I remember skipping the whole compiler by fiddling with
> something on the test web page.Â I forgot how to do this.Â In any case,
> it would require knowing ahead of time which compilers are to be skipped.
It's explicit-failures-markup.xml. This doesn't
skip the tests, it just hides the results and
is a lot more cumbersome.