catch3/docs/configuration.md, branch v3.3.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. v3.2.0 2022-11-16T19:05:48+00:00 Martin Hořeňovský 2022-11-16T15:06:45+00:00 65cc7fd2ae39a7a543767f661b096d7d521ee4f0 






Add support for PlayStation platforms (#2562)
2022-11-09T13:47:55+00:00

Masashi Fujita

2022-11-09T13:47:55+00:00

b7f4a2efb808e8d154874e168cec8e0aaf70bd06

* Add new `CATCH_CONFIG` option for using `std::getenv`, because PS does not support env vars
* Add PS to platforms that have disabled posix signals.
* Small workaround for PS toolchain bug that prevents it from compiling `std::set` with lambda based comparator.




* Add new `CATCH_CONFIG` option for using `std::getenv`, because PS does not support env vars
* Add PS to platforms that have disabled posix signals.
* Small workaround for PS toolchain bug that prevents it from compiling `std::set` with lambda based comparator.






Add Bazel support to the documentation
2022-10-21T08:53:55+00:00

Martin Hořeňovský

2022-10-21T08:46:56+00:00

2d0dcc36e8202504f870a79820ab7d4bb39cf410












Trim superfluous whitespace in docs
2022-10-17T13:02:45+00:00

Martin Hořeňovský

2022-10-17T13:02:45+00:00

6a422bae0b42313cc6a0f231c89f1b20671cf7f3












Fix typos in docs (#2514)
2022-09-09T14:00:39+00:00

tocic

2022-09-09T14:00:39+00:00

dea1a6abd92b5892956fa474540ab4424a8ca1c3












v3.1.0
2022-07-17T18:18:44+00:00

Martin Hořeňovský

2022-07-17T18:18:44+00:00

97c48e0c343d26d50764fafdc90b1e630fbd10ce












Change Bazel XML support to depend upon BAZEL_TEST
2022-06-17T14:36:14+00:00

Brandon Jones

2022-06-14T09:56:19+00:00

7e4ec432d00ccb082846bf9a74c6d8b48e039ba9












v3.0.1
2022-05-17T20:13:36+00:00

Martin Hořeňovský

2022-05-17T20:13:36+00:00

605a34765aa5d5ecbf476b4598a862ada971b0cc












Add default reporter for Bazel integration (#2399)
2022-04-08T16:01:59+00:00

Lukasz Okraszewski

2022-04-08T16:01:59+00:00

cb551b4f6d338020322eb39a2f3747c81896a1ba

When the added Bazel configuration flag is enabled,
a default JUnit reporter will be added if the XML
envrioment variable is defined.
Fix include paths for generated config header.
Enable Bazel config by default when building with
Bazel.


Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>




When the added Bazel configuration flag is enabled,
a default JUnit reporter will be added if the XML
envrioment variable is defined.
Fix include paths for generated config header.
Enable Bazel config by default when building with
Bazel.


Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>






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.