catch3/tests/ExtraTests, branch v3.11.0 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Disable test for deprecated CATCH_CONFIG_BAZEL_SUPPORT option 2025-09-28T10:57:55+00:00 Martin Hořeňovský 2025-09-28T10:46:32+00:00 4be9de6c549af6e1e4c5fda1e3adf9c9ec4ae515 Because it requires full rebuild of the base library, it adds about 20% to the build time of the test suite. Between the fact that the option is deprecated, and that Bazel has added the `BAZEL_TEST` env var _years_ ago, nobody should be using it, and the chance of breakage is tiny, the test is not worth its compile-time cost. 
Because it requires full rebuild of the base library, it adds about
20% to the build time of the test suite. Between the fact that the
option is deprecated, and that Bazel has added the `BAZEL_TEST`
env var _years_ ago, nobody should be using it, and the chance
of breakage is tiny, the test is not worth its compile-time cost.
Improve QNX support 2025-09-22T13:36:46+00:00 Martin Hořeňovský 2025-09-22T13:12:28+00:00 9048c24fa7c6b568d52f76cbf06bbd62b7f83556 This cherry-picks the source changes from PR made by @pkleymonov-qnx, without including the build path changes that are irrelevant unless we can add a QNX target to our CI. Close #2953 
This cherry-picks the source changes from PR made by @pkleymonov-qnx,
without including the build path changes that are irrelevant unless
we can add a QNX target to our CI.

Close #2953
Support Bazel's TEST_PREMATURE_EXIT_FILE and add it to CLI as well 2025-09-22T12:02:45+00:00 Martin Hořeňovský 2025-09-21T09:19:18+00:00 8ed8c431c601c7b303dbfe7eb412a63f1641b812 This tells Catch2 to create an empty file at specified path before the tests start, and delete it after the tests finish. This allows callers to catch cases where the test binary silently exits before finishing (e.g. via call to `exit(0)` inside the code under test), by looking whether the file still exists. Closes #3020 
This tells Catch2 to create an empty file at specified path before
the tests start, and delete it after the tests finish. This allows
callers to catch cases where the test binary silently exits before
finishing (e.g. via call to `exit(0)` inside the code under test),
by looking whether the file still exists.

Closes #3020
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>