catch3/src/catch2/interfaces/catch_interfaces_config.hpp, branch constexpr_approx Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. 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
Added --skip-benchmarks command-line option. (#2408) 2022-04-23T21:14:49+00:00 Daniel Feist 2022-04-23T21:14:49+00:00 291b35b389b8e6d7b560cf7e43b6c72c4b73e522 Closes #2392 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com> 
Closes #2392

Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
 struct -> class normalization for various interface types 2022-04-11T16:32:35+00:00 Martin Hořeňovský 2022-04-10T22:00:19+00:00 8cdaebe9643f77b2e62cde01df0176d15385b12c 






Rename config::colourMode to config::defaultConfigMode
2022-04-07T10:50:13+00:00

Martin Hořeňovský

2022-04-06T19:56:29+00:00

d5bfce4d84f5dda55e1b77d2002a2726732130c6

This describes the actual intention much better.





This describes the actual intention much better.







Refactor colour handling to prepare for per-reporter colour modes
2022-03-28T11:10:13+00:00

Martin Hořeňovský

2022-03-27T21:35:41+00:00

1a8a793178d50b74b0f9a0adb3eec937b61039a9

This includes always compiling the ANSI and None colour
implementations, as they don't need to touch any platform
specific APIs, and removing their respective compile-time
configuration options.

Because the Win32 colour implementation requires Win32-specific
APIs, it is still hidden behind a compile-time toggle,
`CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`).

The commandline options for colours were also changed. The
option now uses different name, and allows to select between
different implementations, rather than changing whether
the compiled-in colour implementation is used through
"yes/no/default" options.





This includes always compiling the ANSI and None colour
implementations, as they don't need to touch any platform
specific APIs, and removing their respective compile-time
configuration options.

Because the Win32 colour implementation requires Win32-specific
APIs, it is still hidden behind a compile-time toggle,
`CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`).

The commandline options for colours were also changed. The
option now uses different name, and allows to select between
different implementations, rather than changing whether
the compiled-in colour implementation is used through
"yes/no/default" options.







Remove special handling of default stream for reporters
2022-03-17T23:41:47+00:00

Martin Hořeňovský

2022-03-17T23:14:09+00:00

06092f727d271d2128b026db99dc0d5736434481

This fixes an issue where reporter with default-output to stdout
would think that it was given a stream _not_ backed by console,
thus not using colour.





This fixes an issue where reporter with default-output to stdout
would think that it was given a stream _not_ backed by console,
thus not using colour.







Pass the whole IStream wrapper into reporter
2022-03-06T15:34:13+00:00

Martin Hořeňovský

2022-02-23T22:46:45+00:00

61d0f7a9afb88c12f8931f80321e58f2cfbc62db

This will become useful when reworking colour support, because
Win32 colour support requires checking whether the output is
stdout, which is done through the `IStream` wrapper.





This will become useful when reworking colour support, because
Win32 colour support requires checking whether the output is
stdout, which is done through the `IStream` wrapper.







Add support for multiple parallel reporters
2022-01-01T13:02:23+00:00

Martin Jeřábek

2021-02-06T19:12:07+00:00

ccd67b293d7595a0cf2dc6c4bfb2017fc18c1f14

This requires a bunch of different changes across the reporter
subsystem.

* We need to handle multiple reporters and their differing
  preferences in `ListeningReporter`, e.g. what to do when
  we mix reporters that capture and don't capture stdout.
* We need to change how the reporter is given output and
  how we parse reporter's output destination from CLI.
* Approval tests need to handle multireporter option





This requires a bunch of different changes across the reporter
subsystem.

* We need to handle multiple reporters and their differing
  preferences in `ListeningReporter`, e.g. what to do when
  we mix reporters that capture and don't capture stdout.
* We need to change how the reporter is given output and
  how we parse reporter's output destination from CLI.
* Approval tests need to handle multireporter option







Implement warning for unmatched test specs
2021-12-18T19:50:03+00:00

Martin Hořeňovský

2021-12-18T18:59:23+00:00

840acedf62b2dabb98bf4ab372a7582131d6b530












Exit with non-0 return code if no tests were run
2021-12-18T19:50:00+00:00

Martin Hořeňovský

2021-12-13T14:15:23+00:00

9f2dca5384a6a8f9f37a7dc2d998cac616545592

A new flag, `--allow-running-no-tests` was added to override this
behaviour if exit code of 0 was desired.

This change also made `-w NoTests` obsolete, and so it has been
removed.





A new flag, `--allow-running-no-tests` was added to override this
behaviour if exit code of 0 was desired.

This change also made `-w NoTests` obsolete, and so it has been
removed.