catch3/src, branch v3.7.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. v3.7.1 2024-09-17T08:45:43+00:00 Martin Hořeňovský 2024-09-17T08:45:43+00:00 fa43b77429ba76c462b1898d6cd2f2d7a9416b14 






Fix compilation error from missing include in xmlwriter.hpp
2024-09-15T20:17:39+00:00

Martin Hořeňovský

2024-09-15T20:17:36+00:00

e200443b84acbfbfab849a032300e6544d3ee9aa

Fixes #2907





Fixes #2907







Standardize exit codes for various failures
2024-09-13T19:33:45+00:00

Martin Hořeňovský

2024-09-13T19:33:41+00:00

ce22c0fe8a6afed61aca682e47ddc9b084c60d4a

The main reason for this is to be able to distinguish between
different errors (or "errors") based on the return code. Before
this change, it was impossible to use the exit code to figure out
whether a test binary failed because all tests were skipped or
because exactly 4 assertions have failed.

This meant that using `catch_discover_tests` and telling it to
check for exit code == 4 to determine skipped tests could lead to
false negatives.





The main reason for this is to be able to distinguish between
different errors (or "errors") based on the return code. Before
this change, it was impossible to use the exit code to figure out
whether a test binary failed because all tests were skipped or
because exactly 4 assertions have failed.

This meant that using `catch_discover_tests` and telling it to
check for exit code == 4 to determine skipped tests could lead to
false negatives.







Sprinkle some constexpr around to make Jason happy
2024-09-13T14:40:11+00:00

Martin Hořeňovský

2024-09-13T09:16:20+00:00

18df97df00848e91bfe1b63408bba19f8b8237ae

Most of these will not matter in practice due to C++14 imposing
significant limitations on what else we can make constexpr, and we cannot
have references outliving the constexpr context either way.





Most of these will not matter in practice due to C++14 imposing
significant limitations on what else we can make constexpr, and we cannot
have references outliving the constexpr context either way.







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

Martin Hořeňovský

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

e97ebe62e700dad37fe460644e121ec462e75596












Remove pointless internal macro
2024-09-13T14:39:53+00:00

Martin Hořeňovský

2024-09-13T11:52:17+00:00

b2b7cbdc319af3103153ce68def6ef17a431fcc1












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












Add the catch_config_prefix_messages.hpp to builds
2024-09-13T14:39:49+00:00

Martin Hořeňovský

2024-09-13T12:25:15+00:00

bd70515c0831bb741eb1865e9ed31d321417d735

Closes #2903





Closes #2903







Use steady_clock in the timer
2024-09-13T14:39:47+00:00

Martin Hořeňovský

2024-09-13T09:15:54+00:00

7a89b7573749846654575fec0580e105a27c54cf












Fix bug in TokenStream parser
2024-09-13T13:32:49+00:00

Mark Jansen

2024-09-05T21:06:32+00:00

02d3304782c715cb787e53a20f4e44ec249d3466

When presented with just '-' it would access the string at position [1]





When presented with just '-' it would access the string at position [1]