Martin Hořeňovský 849f2848bd Rework how warning suppression in macros is done ... Previously, each warning suppression was self-contained, with its own pair of `SUPPRESS_X_WARNING` and `UNSUPPRESS_X_WARNING` macros. This had the obvious advantage of being self-containing, but it also meant that if we needed to suppress more than one warning in a single place, then we would manipulate the compiler's warning state multiple times, even though logically we would only need one layer. The new way of suppressing warnings in macros is to push compiler's warning state with `CATCH_INTERNAL_START_WARNINGS_SUPPRESSION` macro, then disable whatever macros we need with the `CATCH_INTERNAL_SUPPRESS_X_WARNINGS` macro, and then return to the previous state using `CATCH_INTERNAL_STOP_WARNINGS_SUPPRESSION`.		2019-10-27 21:07:21 +01:00
..
Baselines	Improve JUnit failure report	2019-10-27 18:02:14 +01:00
CompileTimePerfTests	Added files for multiply inclusions of test cases	2017-11-17 15:46:57 +00:00
IntrospectiveTests	Enable range generator for floating point types	2019-10-26 20:52:09 +02:00
Misc	Add more tests for reading test specs from file	2019-10-20 15:14:50 +02:00
SurrogateCpps	Sweep out some extra warnings	2017-09-07 17:25:15 +02:00
UsageTests	Rework how warning suppression in macros is done	2019-10-27 21:07:21 +01:00
TestMain.cpp	Add SonarQube Generic Test Data reporter	2019-10-27 10:02:41 +01:00
WarnAboutNoTests.cmake	Improve reporting of unmatched filters (#1684)	2019-08-06 20:51:19 +02:00