catch3/src/catch2/catch_config.cpp, branch v3.12.0 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Support Bazel's TEST_RANDOM_SEED 2025-09-28T08:48:08+00:00 Martin Hořeňovský 2025-09-27T21:20:52+00:00 91b3b3bf4057e2a7e41bf1edd3e2c68b31bb3747 As with other Bazel env vars, it overrides the corresponding CLI parameter if both are set. Closes #3021 Closes #3024 
As with other Bazel env vars, it overrides the corresponding CLI
parameter if both are set.

Closes #3021
Closes #3024
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
Allow CATCH_CONFIG_DEFAULT_REPORTER to be arbitrary reporter spec 2024-03-27T09:03:51+00:00 Martin Hořeňovský 2024-03-26T22:48:35+00:00 7ce35799767de7b9c6ba836c72e479c5f70219a3 Previously it could be just plain reporter name, e.g. `xml`, but it could not specify other reporter options. This change is not particularly useful for the built-in reporters, as it mostly comes in handy for combining specific custom reporter with custom arguments, and the built-in reporters do not have those. 
Previously it could be just plain reporter name, e.g. `xml`, but
it could not specify other reporter options. This change is not
particularly useful for the built-in reporters, as it mostly comes
in handy for combining specific custom reporter with custom arguments,
and the built-in reporters do not have those.
Fix spelling 2023-04-29T10:55:51+00:00 Vertexwahn 2023-04-25T18:14:27+00:00 46539b6d9b1d429fcc2261d3e687482c878a9ddb 






Fix references to license file
2022-10-28T09:30:15+00:00

Lars Toenning

2022-10-28T09:22:53+00:00

f1084fb30990fe40c8f5b70034970c7eb4e1da72

The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1





The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1







Simplify handling of environment in Bazel's support
2022-10-22T20:18:27+00:00

Martin Hořeňovský

2022-10-22T11:10:26+00:00

d1e7544e9f8b233af8ffd37df9bee12492215aff












Add support for Bazel's sharding env variables
2022-10-21T08:53:53+00:00

Martin Hořeňovský

2022-10-20T19:31:04+00:00

80d58a791dd41c365b731469f2ce5f5b6a3ae54d

Closes #2491





Closes #2491







Add support for Bazel's TESTBRIDGE_TEST_ONLY env var
2022-10-20T19:34:32+00:00

Martin Hořeňovský

2022-10-18T18:57:18+00:00

9d0868984506f53f084e877f392ef6ceed796283

Closes #2490





Closes #2490







Rename provideBazelReporterOutput -> enableBazelEnvSupport
2022-10-20T19:34:27+00:00

Martin Hořeňovský

2022-10-18T09:33:42+00:00

afc017ef52c17f1b9aae7a5ed2be92494dd94e45

The new name better reflects that we are adding support for more
Bazel environment variables.





The new name better reflects that we are adding support for more
Bazel environment variables.







Disable Bazel's env checking on UWP
2022-09-02T05:11:28+00:00

Martin Hořeňovský

2022-09-02T05:11:24+00:00

7b2e7d623b626ed2cae1d4b7f2b5480bdabbefd8

UWP does not support environment variables and so it cannot
compile code using getenv.





UWP does not support environment variables and so it cannot
compile code using getenv.