catch3/src/catch2/reporters/catch_reporter_tap.cpp, branch constexpr_approx

Some template instantiation reductions

2023-05-01T11:21:45+00:00

Cleanup unneeded allocations from reporters

2023-01-30T14:30:36+00:00

The CompactReporter changes save 21 (430764 -> 430743) allocations
when running the SelfTest binary in default configuration. They
save about 500 allocations when running the binary with `-s`.

Add new SKIP macro for skipping tests at runtime (#2360)

2023-01-12T14:01:47+00:00

* Add new SKIP macro for skipping tests at runtime

This adds a new `SKIP` macro for dynamically skipping tests at runtime.
The "skipped" status of a test case is treated as a first-class citizen,
like "succeeded" or "failed", and is reported with a new color on the
console.

* Don't show "skipped assertions" in console/compact reporters

Also extend skip tests to cover a few more use cases.

* Return exit code 4 if all test cases are skipped

* Use LightGrey for the skip colour

This isn't great, but is better than the deep blue that was borderline
invisible on dark backgrounds. The fix is to redo the colouring
a bit, including introducing light-blue that is actually visible.

* Add support for explicit skips in all reporters

* --allow-running-no-tests also allows all tests to be skipped

* Add docs for SKIP macro, deprecate IEventListener::skipTest

Co-authored-by: Martin Hořeňovský

Fix references to license file

2022-10-28T09:30:15+00:00

The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1

Change reporters to report filters in round-trippable format

2022-10-27T18:46:59+00:00

Report used filters in the TAP reporter

2022-10-25T22:04:49+00:00

Cleanup of unused functions

2022-05-02T19:32:24+00:00

The cleanup also found out that custom translation for std-derived
exceptions test wasn't running properly, and fixed that.
We cannot enable the warning globally, because the tests contain
some functions that are unused by design -- e.g. when checking
stringification priority of StringMaker vs range fallback and so
on.

Always report rng seed from builtin reporters

2022-04-19T08:32:13+00:00

Not all reporters use a format that supports this, so TeamCity
and Automake reporters still do not report it. The console
reporter now reports it even on successful runs, where before
it only reported the rng seed in the header, which was showed
either for failed run, or for run with `-s`.

CLoses #2065

Some IWYU include cleanups

2022-04-14T15:16:01+00:00

ColourGuard is no longer constructed engaged

2022-03-24T15:02:54+00:00

Forcing it to be engaged explicitly, either via `op<<`, or by
`ColourGuard::engage`, fixes an issue with multiple `ColourGuard`s
being constructed in a single expression. Because the construction
of the `ColourGuard` instances can happen in arbitrary order,
colours would be applied in arbitrary order too. However, a chain
of `op<<`s has strict call orders, fixing this issue.