jan-moeller / bugspray Goto Github PK

Is your feature request related to a problem? Please describe.
It is easy to forget to write the EVAL_TEST_CASE macro. In this case, the tests are only run at runtime, but the programmer thinks they are actually running at compile time.

Describe the solution you'd like
If a test case marked "compiletime" or "both" exists that doesn't have EVAL_TEST_CASE invoked on it, the build should fail.

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.
For the [REQUIRE|CHECK]_NOTHROW APIs, currently only the source code location of the failed check is reported.

If the exception escapes the TEST_CASE, then the only information reported is "Exception escaped test case".

Describe the solution you'd like
We should report the message, if possible. There might also be an opportunity to trace back where the exception came from by compiling in some try/catch/rethrow into SECTIONs and assertions.

Is your feature request related to a problem? Please describe.
Currently, the only way to integrate bugspray with ctest is to run/compile the entire test executable as a single ctest test.

Describe the solution you'd like
At least for the runtime tests it should be possible to generate one ctest entry per TEST_CASE. It might further be feasible to generate ctest entries for independent compilation units. This would facilitate at least some ctest support for compile-time tests.

Describe alternatives you've considered
Don't support ctest. Not great.

Additional context
None.