Viktor Kirilov
Viktor Kirilov
Anything else? Should we close this issue? :)
I guess it could be detected with the preprocessor and with a few lines of code the changes I suggested to you could be automated... I remember adding support for...
It's indeed not possible yet. Maybe in the future, but no ETA can be promised. Indeed the use of multiple reporters is a bit ... nonsensical atm
The junit reporter buffers everything (with the exception of the opening tag) and dumps everything else all at once at the end because it needs to report the number of...
@tknerr just pushed a commit to the `dev` branch for the `writeDeclaration` issue - let me know if it helps. But I think the really correct behavior would be to...
@srnwk hey, great that you're working on this! I've moved away from doctest and currently @Saalvage is the maintainer (and whoever decides to pitch in) and I won't have the...
Valid points! I can't promise when this will be tackled, but for now, you could use `WARN` instead of `CHECK`/`REQUIRE` for asserts that you know will fail - they won't...
Yeah - actually `WARN` isn't even an OK solution...
For now you could surround the expression with parenthesis like this: ```c++ CHECK( (factorial(3)==5 || factorial(3)==6) ); ``` This is related to this issue: https://github.com/onqtam/doctest/issues/347
I don't understand exactly what you mean by `one test at a time` - doctest simply discovers `TEST_CASE`s and executes the code inside of them - one after the other...