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







Sweep out some Wsign-conversion warnings
2021-11-23T22:16:08+00:00

Martin Hořeňovský

2021-11-20T22:40:32+00:00

8cb8f0b08b0ec35edd346df999f3b854ad05aa41












Allow test sharding for e.g. Bazel test sharding feature
2021-10-27T15:24:30+00:00

Ben Dunkin

2021-07-11T19:46:05+00:00

3087e19cc72ccb6caddc42ec2f39eebc56160754

This greatly simplifies running Catch2 tests in single binary
in parallel from external test runners. Instead of having to
shard the tests by tags/test names, an external test runner
can now just ask for test shard 2 (out of X), and execute that
in single process, without having to know what tests are actually
in the shard.

Note that sharding also applies to test listing, and happens after
tests were ordered according to the `--order` feature.





This greatly simplifies running Catch2 tests in single binary
in parallel from external test runners. Instead of having to
shard the tests by tags/test names, an external test runner
can now just ask for test shard 2 (out of X), and execute that
in single process, without having to know what tests are actually
in the shard.

Note that sharding also applies to test listing, and happens after
tests were ordered according to the `--order` feature.