catch3/projects/SelfTest/Baselines, branch v2.12.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Add status attribute to JUnit's section reporting 2020-05-15T19:00:19+00:00 Martin Hořeňovský 2020-05-15T19:00:19+00:00 f133277910c59ba5526a081e94d5e4ece406e517 This brings our output inline with GTest's. We do not handle skipped tests properly, but that should be currently less important than having the attribute exist with proper value for non-skipped tests. Thanks @joda-01. Closes #1899 
This brings our output inline with GTest's. We do not handle skipped
tests properly, but that should be currently less important than
having the attribute exist with proper value for non-skipped tests.

Thanks @joda-01.

Closes #1899
Add support for bitwise xor to the decomposer 2020-04-21T17:27:12+00:00 Martin Hořeňovský 2020-04-21T17:27:12+00:00 5c9f09e94a32ab47f16bf8353a708e226fccf645 






Fixup template type argument inference for vector matchers
2020-04-21T17:09:45+00:00

Martin Hořeňovský

2020-04-21T17:09:45+00:00

f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9












Support bitand and bitor in REQUIRE/CHECK
2020-04-21T09:00:08+00:00

Martin Hořeňovský

2020-04-21T09:00:08+00:00

4e4171420d8c3ada47d8782f419908e47e2564ad

This means that bit-flag-like types with conversion to bool can be
asserted on, like so `REQUIRE(var & Flags::AddNewline)`.





This means that bit-flag-like types with conversion to bool can be
asserted on, like so `REQUIRE(var & Flags::AddNewline)`.







Add more tests for test spec parser
2020-04-17T19:19:18+00:00

Martin Hořeňovský

2020-04-17T19:16:18+00:00

37cbf4a4fe7a2963f8ae6d6fe998f8ac9360cbc0

Originally the tests were from #1912, but as it turned out, the issue
was somewhere else. Still, the inputs provided were interesting, so
they are now part of our test suite.





Originally the tests were from #1912, but as it turned out, the issue
was somewhere else. Still, the inputs provided were interesting, so
they are now part of our test suite.







Support custom allocators in vector Matchers (#1909)
2020-04-16T13:36:54+00:00

schallerr

2020-04-16T13:36:54+00:00

38f897c88772d6640196d1bd617ebbcaf44bc05a












Fix bug in test spec parser handling of escaping in ORed patterns
2020-04-12T16:48:52+00:00

Martin Hořeňovský

2020-04-12T16:44:42+00:00

5d32ce26f4c18588f9eac3342aea122a38b8fed3

It did not clear out all of its internal state when switching from
one pattern to another, so when it should've escaped `,`, it took
its position from its position in the original user-provided string,
rather than its position in the current pattern.

Fixes #1905





It did not clear out all of its internal state when switching from
one pattern to another, so when it should've escaped `,`, it took
its position from its position in the original user-provided string,
rather than its position in the current pattern.

Fixes #1905







Fix compilation error when lambdas are used in assertions
2020-03-19T12:32:45+00:00

Martin Hořeňovský

2020-03-19T12:32:45+00:00

3a33315ff8e047b1ff46b1ee2a5be3fdd7fbac08

This is a partial revert of b7b346c3e5603.





This is a partial revert of b7b346c3e5603.







Add command line option 'never' to --wait-for-keypress (#1866)
2020-02-15T19:42:57+00:00

Tristan Stenner

2020-02-15T19:42:57+00:00

200b8b6fc05934149d9d4fa56eefbfd613ee73ea

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





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







Fix significant bug with storing composed matchers
2020-02-01T20:06:07+00:00

Martin Hořeňovský

2020-02-01T19:55:42+00:00

f20a9dbc6e115eeb2b48288bfb27234c29f7417a

Given that in the 2 or so years that matchers are thing nobody complained,
it seems that people do not actually write this sort of code, and the
possibility will be removed in v3. However, to avoid correctness bugs,
we will have to support this weird code in v2.





Given that in the 2 or so years that matchers are thing nobody complained,
it seems that people do not actually write this sort of code, and the
possibility will be removed in v3. However, to avoid correctness bugs,
we will have to support this weird code in v2.