catch3/src/catch2/interfaces, branch devel-piped-redirect Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. 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







Fix spelling
2023-04-29T10:55:51+00:00

Vertexwahn

2023-04-25T18:14:27+00:00

46539b6d9b1d429fcc2261d3e687482c878a9ddb












Cleanup internal includes by splitting out some event structs
2023-03-31T17:31:51+00:00

Martin Hořeňovský

2023-03-31T08:44:29+00:00

9f08097f55eb29a61efcdb4af41952a67e155215

* Split out BenchmarkInfo and BenchmarkStats to their own header
* Outline BenchmarkStats<> declaration to separate header
* Split out TestRunInfo into its own header

These changes let us remove the large `interfaces_reporter.hpp`
include from `benchmark.hpp`, and replace it with
`interfaces_capture.hpp` in `run_context.hpp`.

I also cleaned out `interfaces_repoter.hpp` from reporter headers
that depend on `reporter_common_base.hpp`. This will not change
anything in the actual inclusion set, but makes it logically
more consistent.





* Split out BenchmarkInfo and BenchmarkStats to their own header
* Outline BenchmarkStats<> declaration to separate header
* Split out TestRunInfo into its own header

These changes let us remove the large `interfaces_reporter.hpp`
include from `benchmark.hpp`, and replace it with
`interfaces_capture.hpp` in `run_context.hpp`.

I also cleaned out `interfaces_repoter.hpp` from reporter headers
that depend on `reporter_common_base.hpp`. This will not change
anything in the actual inclusion set, but makes it logically
more consistent.







Split ITestInvoker into its own header
2023-03-23T15:50:11+00:00

Martin Hořeňovský

2023-03-23T13:02:45+00:00

1f881ab4641b866304b818a063164dae976dba5f












Reduce misc includes all around
2023-03-23T15:50:07+00:00

Martin Hořeňovský

2023-03-23T12:41:04+00:00

c487b27d9d98e69358f3eee7b02c7d2ad0889139