catch3/docs/cmake-integration.md, branch ci/platforms-like-visual-xsharp Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Complete Catch3 documentation and Windows CI: distinguish compatibility docs, correct fork integration, fix Conan CRT and Xmake test entry point 2026-09-24T21:36:48+00:00 Leitwolf11 2026-09-24T21:36:48+00:00 c3a325d284ab2487f472f3a8b928c0b12a200979 






Document that DISCOVERY_MODE PRE_TEST should be used with catch_discover_tests when used with XCode.
2026-07-22T18:50:17+00:00

Phil Nash

2026-07-10T15:42:51+00:00

eb431764b4cb9b6fa2296a034b4231064f8e464e

This addresses https://github.com/catchorg/Catch2/issues/2411 by making the "workaround" the official approach and is consistent with how gtest and cmake deal with the same situation.





This addresses https://github.com/catchorg/Catch2/issues/2411 by making the "workaround" the official approach and is consistent with how gtest and cmake deal with the same situation.







Use latest release in docs
2025-06-15T19:05:41+00:00

Chris Thrasher

2025-06-15T19:05:35+00:00

ac207fc90fcc6e7c5facde215128c41ff6f1a5ec












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







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>






Update CMake build instructions for current CMake version
2024-02-19T14:02:08+00:00

Martin Hořeňovský

2024-02-08T21:05:08+00:00

82e9b9b5f2b62f5eb7b0381d65e69da2b974100b












Add Bazel instructions to integration docs (#2812)
2024-02-16T15:58:09+00:00

Fædon Jóhannes

2024-02-16T15:58:09+00:00

3157d6bbf163c8c10534ef6e0d8a834d20b3660a


Co-authored-by: Fædon Jóhannes Sinis <fs@treble.tech>





Co-authored-by: Fædon Jóhannes Sinis <fs@treble.tech>






Fix minor typos in documentation (#2769)
2023-12-10T21:01:13+00:00

Blake-Madden

2023-12-10T21:01:13+00:00

4ab0af8bafe3d5cb53bea3c2a91cb410a1c22afc


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





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






lifted suggested version
2023-11-14T16:10:31+00:00

Gerald Senarclens de Grancy

2023-11-10T11:45:17+00:00

2c68a0d05f4fa8fb79cd43824f69568eb3954d4c

Did this, because with 3.0.1, the files
- catch_xmlwriter.cpp
- catch_string_manip.hpp
- catch_test_case_info.hpp

were missing

This led to some obvious and some obscure compile errors when compiling
with g++ 13.2.0 (std c++17 or c++20)
One of these errors being "Elaborated-type-specifier for a scoped enum
must not use the ‘class’ keyword"

Since this is a rather bad experience and debugging it is
time-consuming, I suggest to simply boost the recommended version in the
snippet which is likely copied by new Catch2 users





Did this, because with 3.0.1, the files
- catch_xmlwriter.cpp
- catch_string_manip.hpp
- catch_test_case_info.hpp

were missing

This led to some obvious and some obscure compile errors when compiling
with g++ 13.2.0 (std c++17 or c++20)
One of these errors being "Elaborated-type-specifier for a scoped enum
must not use the ‘class’ keyword"

Since this is a rather bad experience and debugging it is
time-consuming, I suggest to simply boost the recommended version in the
snippet which is likely copied by new Catch2 users