Martin Hořeňovský

If you mean that we don't document that it exists, then yes, because [`BUILD_SHARED_LIBS` is a standard CMake option](https://cmake.org/cmake/help/latest/variable/BUILD_SHARED_LIBS.html) and I generally don't want to duplicate CMake docs. We admittedly...

Ooooh, that's a repeat of #797 due to the v2 versions using the number of listed tests (things in general) as the return code. Should be easy enough to fix.

After some investigation, you are right in that verbosity is currently only taken into account by the listings. However, it is also meant for reporters if they can meaningfully support...

Opening up a new PR would be better, yes.

I will consider rewriting the docs to guide the reader more strongly towards the default set up, but I generally do not want Catch2's documentation to explain things like build...

Thanks to the new multi reporter support, the benchmark reporter doesn't have to handle non-benchmarking events.

Is the output you are seeing something like this? ``` 26/34 Test #26: EscapeSpecialCharactersInTestNames ................... Passed 0.15 sec Start 27: NegativeSpecNoHiddenTests 27/34 Test #27: NegativeSpecNoHiddenTests ............................ Passed 0.15 sec Start...

Removed bunch of less-used or completely unused normalization checks in 4ff8b27bb6bed4b8b309e56cd269b4f1fbc24e89. The approvals will need a reduction in how many tests are run for further improvements. Also the multireporter approvals...

Yeah, I can see how that output would be very confusing.

I am not convinced that empty tags are useful, but they shouldn't cause crashes (I think they should be rejected).