catch3/tests/SelfTest/UsageTests, branch v3.3.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Add IsNaN matcher 2023-02-25T23:14:32+00:00 Martin Hořeňovský 2023-02-25T23:14:32+00:00 6fbb3f07235311d0c228b17b52406343a7aed8f2 






Add support for iterator+sentinel pairs in Contains matcher
2023-02-10T22:25:45+00:00

Martin Hořeňovský

2023-02-10T22:25:41+00:00

e8ba329b6c66b06c4afd07953020b74c4b0f1a75












Enable use of UnorderedRangeEquals with iterator+sentinel pairs
2023-02-06T14:34:38+00:00

Martin Hořeňovský

2023-02-06T14:34:32+00:00

cefa8fcf329c950493f80dcbf7e2870a20213e0f












Add Catch::Detail::is_permutation that supports sentinels
2023-02-06T14:29:01+00:00

Martin Hořeňovský

2023-02-05T15:40:38+00:00

772fa3f7902b534d59e5fe4306e3cc6a255a6508

Also split out helpers for testing matcher ranges (types whose
begin/end/empty/etc require ADL lookup, types whose iteration
uses iterator + sentinel pair, etc) into their own file.





Also split out helpers for testing matcher ranges (types whose
begin/end/empty/etc require ADL lookup, types whose iteration
uses iterator + sentinel pair, etc) into their own file.







Fix RangeEquals matcher to handle iterator + sentinel ranges
2023-02-03T17:22:41+00:00

Martin Hořeňovský

2023-02-03T15:12:09+00:00

f3c0a3cd091aba8341a77e5c8580e5697f0e6892

Also added tests for types that require ADL lookup for their
`begin` and `end`.





Also added tests for types that require ADL lookup for their
`begin` and `end`.







Stop exceptions in generator constructors from aborting the binary
2023-01-22T15:04:16+00:00

Martin Hořeňovský

2023-01-17T10:04:49+00:00

8359a6b244a26cffabd4440b17fac8b1392815af

Fixes #2615





Fixes #2615







Added ElementsAre and UnorderedElementsAre  (#2377)
2023-01-21T23:33:04+00:00

John Beard

2023-01-21T23:33:04+00:00

efca9a0f1826885c1574ed44fc37c8d82ded4546

Co-authored-by: Garz4 <fancygarz4@gmail.com>
Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>




Co-authored-by: Garz4 <fancygarz4@gmail.com>
Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>






Add new SKIP macro for skipping tests at runtime (#2360)
2023-01-12T14:01:47+00:00

Philip Salzmann

2023-01-12T14:01:47+00:00

d548be26e3c54abc7e0b076319057d334e3ac589

* Add new SKIP macro for skipping tests at runtime

This adds a new `SKIP` macro for dynamically skipping tests at runtime.
The "skipped" status of a test case is treated as a first-class citizen,
like "succeeded" or "failed", and is reported with a new color on the
console.

* Don't show "skipped assertions" in console/compact reporters

Also extend skip tests to cover a few more use cases.

* Return exit code 4 if all test cases are skipped

* Use LightGrey for the skip colour

This isn't great, but is better than the deep blue that was borderline
invisible on dark backgrounds. The fix is to redo the colouring
a bit, including introducing light-blue that is actually visible.

* Add support for explicit skips in all reporters

* --allow-running-no-tests also allows all tests to be skipped

* Add docs for SKIP macro, deprecate IEventListener::skipTest

Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>




* Add new SKIP macro for skipping tests at runtime

This adds a new `SKIP` macro for dynamically skipping tests at runtime.
The "skipped" status of a test case is treated as a first-class citizen,
like "succeeded" or "failed", and is reported with a new color on the
console.

* Don't show "skipped assertions" in console/compact reporters

Also extend skip tests to cover a few more use cases.

* Return exit code 4 if all test cases are skipped

* Use LightGrey for the skip colour

This isn't great, but is better than the deep blue that was borderline
invisible on dark backgrounds. The fix is to redo the colouring
a bit, including introducing light-blue that is actually visible.

* Add support for explicit skips in all reporters

* --allow-running-no-tests also allows all tests to be skipped

* Add docs for SKIP macro, deprecate IEventListener::skipTest

Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>






Add MessageMatches matcher for exception (#2570)
2022-12-11T23:40:47+00:00

lbckmnn

2022-12-11T23:40:47+00:00

9c0533a90504b2b1c308dc7cc77ff194f81046e2












Move SFINAE in decomposer into return type
2022-12-08T23:40:01+00:00

Martin Hořeňovský

2022-12-08T15:31:55+00:00

28e651f1521449f2fce8b202307b6312a0ebe429

This is needed so that we can use conjunction and other logical
type traits to workaround issue with older GCC versions (8 and
below), when they run into types that have ambiguous constructor
from `0`, see e.g. #2571.

However, using conjunction and friends in the SFINAE constraint
in the template parameter breaks for C++20 and up, due to the new
comparison operator rewriting rules. With C++20, when the compiler
see `a == b`, it also tries `b == a` and collects overload set
for both of these expressions.

In Catch2, this means that e.g. `REQUIRE( 1 == 2 )` would lead
the compiler to check overloads for both `ExprLhs<int> == int`
and `int == ExprLhs<int>`. Since the overload set and SFINAE
constraints assume that `ExprLhs<T>` is always on the left side,
when the compiler tries to resolve the template parameters, all
hell breaks loose and the compilation fails.

By moving the SFINAE constraints to the return type, the compiler
can discard the switched expression without having to resolve
the complex SFINAE constraints, and thus everything works the
way it is supposed to.

Fixes #2571





This is needed so that we can use conjunction and other logical
type traits to workaround issue with older GCC versions (8 and
below), when they run into types that have ambiguous constructor
from `0`, see e.g. #2571.

However, using conjunction and friends in the SFINAE constraint
in the template parameter breaks for C++20 and up, due to the new
comparison operator rewriting rules. With C++20, when the compiler
see `a == b`, it also tries `b == a` and collects overload set
for both of these expressions.

In Catch2, this means that e.g. `REQUIRE( 1 == 2 )` would lead
the compiler to check overloads for both `ExprLhs<int> == int`
and `int == ExprLhs<int>`. Since the overload set and SFINAE
constraints assume that `ExprLhs<T>` is always on the left side,
when the compiler tries to resolve the template parameters, all
hell breaks loose and the compilation fails.

By moving the SFINAE constraints to the return type, the compiler
can discard the switched expression without having to resolve
the complex SFINAE constraints, and thus everything works the
way it is supposed to.

Fixes #2571