catch3/src/catch2/interfaces, branch v3.9.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Remove assertionPassed fast path from the capture interface 2025-07-20T16:32:25+00:00 Martin Hořeňovský 2025-07-20T16:31:24+00:00 ce128f584c293b17362d838a8dc65bc81ffc8dff As it is an internal helper for RunContext to speed-up handling of succesfull assertions, I have no idea why it was added to the interface back when it was first implemented. 
As it is an internal helper for RunContext to speed-up handling of
succesfull assertions, I have no idea why it was added to the
interface back when it was first implemented.
Let reporters opt into fast path in RunContext::assertionStarting 2025-07-17T11:47:44+00:00 Martin Hořeňovský 2025-07-17T11:13:08+00:00 c22096846c98211e0bcd23dbbd155698fbd718b3 The fast path allows `RunContext` to skip disabling output redirect, and notifying the reporters, turning `RunContext::notifyAssertionStarted` into a no-op. This improves the overall performance of assertion handling significantly, and also prepares ground for future changes around assertion handling and thread safety. For simple 10M assertion run, this improves the running time by ~30% in Debug build and ~40% in Release build. For backwards-compatibility reasons, the fast path is disabled by default. However, none of the first party reporters use the `assertionStarting` event, so all first party reporters are opted-in. 
The fast path allows `RunContext` to skip disabling output redirect,
and notifying the reporters, turning `RunContext::notifyAssertionStarted`
into a no-op. This improves the overall performance of assertion handling
significantly, and also prepares ground for future changes around
assertion handling and thread safety.

For simple 10M assertion run, this improves the running time by ~30%
in Debug build and ~40% in Release build.

For backwards-compatibility reasons, the fast path is disabled
by default. However, none of the first party reporters use the
`assertionStarting` event, so all first party reporters are opted-in.
Move header from internal 2025-07-07T15:27:48+00:00 Omar Boukli-Hacene 2025-04-13T14:44:53+00:00 8dc9f1a1247a15836044501c9a791ea67a709f05 Move `catch_test_run_info.hpp` from directory `src/catch2/internal/` to be directly under `src/catch2/`. Header `catch_test_run_info.hpp` defines `Catch::TestRunInfo` which is part of the public API, since it is required when overriding `Catch::EventListenerBase`. Fixes issue caught by Clang Tidy misc-include-cleaner check. 
Move `catch_test_run_info.hpp` from directory
`src/catch2/internal/` to be directly under `src/catch2/`.

Header `catch_test_run_info.hpp` defines `Catch::TestRunInfo` which is part of the public API, since it is required when overriding `Catch::EventListenerBase`.

Fixes issue caught by Clang Tidy misc-include-cleaner check.
Remove unused headers 2025-04-27T17:08:41+00:00 Chris Thrasher 2025-04-26T16:08:05+00:00 5a6d70eebbf8201c7c76ea26fb1bb06cceeee5c3 






Remove superfluous include
2024-09-13T14:39:55+00:00

Martin Hořeňovský

2024-09-13T12:43:23+00:00

e97ebe62e700dad37fe460644e121ec462e75596












Avoid needless copy of string in runContext::handleMessage
2024-09-13T14:39:51+00:00

Martin Hořeňovský

2024-09-13T11:42:03+00:00

412cad546a89cda9eaa8ef77d8161b719182cc9e












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>






Cleanup includes in sources
2023-12-23T10:23:32+00:00

Martin Hořeňovský

2023-12-21T17:42:40+00:00

9aadc3a53d7208f8b44260dfef26b18671f7edd0

Mainly just removes some unused includes, but sometimes the include
is replaced by a smaller header instead.





Mainly just removes some unused includes, but sometimes the include
is replaced by a smaller header instead.







Fix Wredundant-decls
2023-05-12T07:51:13+00:00

Martin Hořeňovský

2023-05-12T07:50:59+00:00

598895d04866c6e85f1d703a8c3d89e8d38a2311

Closes #2682





Closes #2682







Fix assertionStarting events being sent after the expr is evaluated
2023-05-06T09:48:41+00:00

Martin Hořeňovský

2023-05-06T09:48:25+00:00

d84777c9cbf5b1b7d0e9ef2e14606ece254adf7a

Closes #2678





Closes #2678