catch3/tests/ExtraTests, branch v3.9.0 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Disable Wmissing-noreturn for test files 2025-07-14T10:15:25+00:00 Martin Hořeňovský 2025-07-14T10:05:03+00:00 050e14dce05b93965ecf60ec524fa4cb3f91bb70 Adding unreachable to `FAIL` and `SKIP` made Clang become very good at figuring out that tests of `FAIL` and `SKIP` will never return and thus could be marked as [[noreturn]]. To avoid introducing lot of warning suppression noise into the test files, we just disable it instead. 
Adding unreachable to `FAIL` and `SKIP` made Clang become very good
at figuring out that tests of `FAIL` and `SKIP` will never return
and thus could be marked as [[noreturn]].

To avoid introducing lot of warning suppression noise into the
test files, we just disable it instead.
Replace deprecated FindPythonInterp with FindPython3 2025-06-15T19:23:27+00:00 Eisuke Kawashima 2025-06-09T00:09:50+00:00 334827eb53bcbcaff08264baa92c2d51ff742817 fix #2755 https://cmake.org/cmake/help/v3.16/module/FindPythonInterp.html 
fix #2755

https://cmake.org/cmake/help/v3.16/module/FindPythonInterp.html
Fix formatting of CMake files 2025-04-26T16:38:36+00:00 Chris Thrasher 2025-04-08T04:09:59+00:00 8cfca70ae879ba59699b224e8d371b8bb9fa12ff 2 spaces seems to be the more common indentation level so that's what I unified around. 
2 spaces seems to be the more common indentation level so that's what
I unified around.
Downgrade required CMake to 3.16 2025-01-05T22:45:00+00:00 Martin Hořeňovský 2025-01-05T22:19:26+00:00 232e893785553796b2016b4440a7f3776ed450a0 We still want to build VS 2017 through AppVeyor, and those images have CMake 3.16.2 installed. We could install newer CMake as part of the build, but since we don't use newer CMake features yet, this is simpler. 
We still want to build VS 2017 through AppVeyor, and those images
have CMake 3.16.2 installed. We could install newer CMake as part
of the build, but since we don't use newer CMake features yet, this
is simpler.
Support adding test tags as CTest labels in catch_discover_tests 2025-01-05T19:02:00+00:00 Martin Hořeňovský 2025-01-03T09:30:47+00:00 7d7b2f89f24cbd277f6eb6912705e5e13c68a3c7 We also bump the minimum CMake version to 3.20 as per #2943 
We also bump the minimum CMake version to 3.20 as per #2943
Enable CMake project folders for better target organization 2024-10-27T22:07:55+00:00 Martin Hořeňovský 2024-10-27T22:07:51+00:00 9c5a4cf44e494bbd2e5dac151c400b3f4a4c9cbc Closes #2917 
Closes #2917
TEST_CASE_PERSISTENT_FIXTURE: A new fixture macro for allowing persistent fixtures throughout a TEST_CASE (#2885) 2024-08-05T15:01:41+00:00 Keith Stockdale 2024-08-05T15:01:41+00:00 f7cd0ba0511b61592e70f07533d7ea30a8a5395d This PR introduces a new `TEST_CASE` macro called `TEST_CASE_PERSISTENT_FIXTURE`. `TEST_CASE_PERSISTENT_FIXTURE` offers the same functionality as `TEST_CASE_METHOD` except for one difference. The object on which the test method is invoked is only created once for all invocations of the test case. The object is created just after the `testCaseStarting` event is broadcast and the object is destroyed just before the `testCaseEnding` event is broadcast. The main motivation for this new functionality is to allow `TEST_CASE`s to do expensive setup and teardown once per `TEST_CASE`, without having to resort to abusing event listeners or static function variables with manual initialization. Implements #1602 --------- Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com> 
This PR introduces a new `TEST_CASE` macro called `TEST_CASE_PERSISTENT_FIXTURE`. `TEST_CASE_PERSISTENT_FIXTURE` offers the same functionality as `TEST_CASE_METHOD` except for one difference. The object on which the test method is invoked is only created once for all invocations of the test case. The object is created just after the `testCaseStarting` event is broadcast and the object is destroyed just before the `testCaseEnding` event is broadcast.

The main motivation for this new functionality is to allow `TEST_CASE`s to do expensive setup and teardown once per `TEST_CASE`, without having to resort to abusing event listeners or static function variables with manual initialization.


Implements #1602

---------

Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
 Add test for handleFatalErrorCondition within JUnit reporter 2024-04-21T19:52:33+00:00 Martin Hořeňovský 2024-04-20T14:29:56+00:00 efb39689d94e43132e4e48f01e676ae6a56d8df6 






Specify minimum C++ version for amalgamated test build
2024-03-13T20:12:59+00:00

Chris Thrasher

2024-03-13T17:16:07+00:00

bfe3ff8f19d3436381b4e3a18c13734d21a8b089

This target previously did not specify its minimum C++ standard.
AppleClang was emitting warnings about the use of C++11 features
which is fixed by telling CMake that this target requires C++14.
Because this target does not link to the existing CMake targets
it never inherited that C++ standard requirement.





This target previously did not specify its minimum C++ standard.
AppleClang was emitting warnings about the use of C++11 features
which is fixed by telling CMake that this target requires C++14.
Because this target does not link to the existing CMake targets
it never inherited that C++ standard requirement.







Stop repeating conditional in endif()
2024-03-12T21:55:12+00:00

Chris Thrasher

2024-03-12T19:06:17+00:00

792c3b7549e67371e4ebc18c9c6b79dbc3c9fa07

This is not necessary so we can remove it. Most conditionals already
omit this anyways.





This is not necessary so we can remove it. Most conditionals already
omit this anyways.