catch3/projects/SelfTest/Baselines, branch v2.11.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. 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.
Make CATCH_BREAK_INTO_DEBUGGER be user-configurable 2020-02-01T16:01:50+00:00 khyperia 2020-01-27T14:43:27+00:00 ccb1f70629e8952c4b92d77535f79ad6c7055d23 






Make hidden tags behave identically (#1847)
2020-01-31T20:44:06+00:00

dmsteck

2020-01-31T20:44:06+00:00

481f54b357f033df0edc8bd457c175a2f2236d08

Add both `[.]` and `[!hide]` tags when registering a hidden test case, as per documentation.

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





Add both `[.]` and `[!hide]` tags when registering a hidden test case, as per documentation.

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







Split [.foo] into [.][foo] when parsing test specs
2019-11-05T22:28:47+00:00

Martin Hořeňovský

2019-11-05T22:28:47+00:00

930f49a641aa6a495d264d7b5e7c007734da0b0c

b77cec05c0 fixed this problem for tagging tests, so that a test
case tagged with `[.foo]` would be parsed as tagged with `[.][foo]`.
This does the same for the test spec parsing.

Fixes #1798





b77cec05c0 fixed this problem for tagging tests, so that a test
case tagged with `[.foo]` would be parsed as tagged with `[.][foo]`.
This does the same for the test spec parsing.

Fixes #1798







Cleanup tests for C++20
2019-11-04T09:42:34+00:00

Martin Hořeňovský

2019-11-04T09:42:34+00:00

c409dccee50fb64723b98fb9c61f00a65393ade4












Improve JUnit failure report
2019-10-27T17:02:14+00:00

Alexander Stein

2019-08-07T20:39:01+00:00

2fbd66c51cbf3a406dc6bb8ddc6b9a0b96077a72

The JUnit report is improved in that:
* The message shows the testing condition, not the result
* The actual message has similar output than the console one





The JUnit report is improved in that:
* The message shows the testing condition, not the result
* The actual message has similar output than the console one







Add SonarQube Generic Test Data reporter
2019-10-27T09:02:41+00:00

sp-dani-garcia

2019-08-29T15:47:56+00:00

51b29ced1ac2bde83d977283f6e0b4f871898b8a

It outputs reports in the `Generic Execution Test Data` format, see
https://docs.sonarqube.org/latest/analysis/generic-test/, specifically
https://docs.sonarqube.org/latest/analysis/generic-test/#header-2

Close #1738 (this is a cherry-pick and fixup of that PR)





It outputs reports in the `Generic Execution Test Data` format, see
https://docs.sonarqube.org/latest/analysis/generic-test/, specifically
https://docs.sonarqube.org/latest/analysis/generic-test/#header-2

Close #1738 (this is a cherry-pick and fixup of that PR)







Enable `range` generator for floating point types
2019-10-26T18:52:09+00:00

Manuel Drews

2019-10-16T14:03:42+00:00

4327baba400f6f8158c4d686135ba7fb6ba10d54












Rework StringRef interface and internals
2019-10-25T11:57:52+00:00

Martin Hořeňovský

2019-10-21T15:44:11+00:00

50cc14c94c972fc743afca92b22ad7bdc63c429a

Now it no longer tries to be this weird hybrid between an owning
and non-owning reference, and is only ever non-owning. This is also
reflected in its interface, for example `StringRef::isNullTerminated`
is now public, and `StringRef::c_str()` has the precondition that it
is true.

Overview of the changes:
* The `StringRef::m_data` member has been completely removed, as it
had no more uses.
* `StringRef::isSubstring()` has been made public and renamed to
`StringRef::isNullTerminated()`, so that the name reflects what the
method actually does.
* `StringRef::currentData()` has been renamed to `StringRef::data()`,
to be in line with common C++ containers and container-alikes.
* `StringRef::c_str()` will no longer silently make copies. It instead
has a precondition that `isNullTerminated()` is true.
* If the user needs a null-terminated string, they should use the
`std::string` conversion operator and call `c_str()` on the resulting
`std::string`.
* Some small optimizations in various places.
* Basic functionality is now `constexpr`.





Now it no longer tries to be this weird hybrid between an owning
and non-owning reference, and is only ever non-owning. This is also
reflected in its interface, for example `StringRef::isNullTerminated`
is now public, and `StringRef::c_str()` has the precondition that it
is true.

Overview of the changes:
* The `StringRef::m_data` member has been completely removed, as it
had no more uses.
* `StringRef::isSubstring()` has been made public and renamed to
`StringRef::isNullTerminated()`, so that the name reflects what the
method actually does.
* `StringRef::currentData()` has been renamed to `StringRef::data()`,
to be in line with common C++ containers and container-alikes.
* `StringRef::c_str()` will no longer silently make copies. It instead
has a precondition that `isNullTerminated()` is true.
* If the user needs a null-terminated string, they should use the
`std::string` conversion operator and call `c_str()` on the resulting
`std::string`.
* Some small optimizations in various places.
* Basic functionality is now `constexpr`.