Viktor Kirilov

In order to enumerate the test case names, you could call the test binary once with `--list-test-cases` and then use the outputted list (after trimming the first 2 and last...

I guess for now you could simply return immediately - it will be counted as a successful test case instead of a skipped one. Alternatively you could have a subcase...

> inconvenient to determine at test-program-invoke time What do you mean by that - using filters (through the command line or adding them programmatically in your ```main()```) to skip a...

Hi! This PR seems to do more than it's supposed to - changing the install option name and inverting it's behavior is a breaking change in terms of integration -...

I think your best bet would be this: https://www.jetbrains.com/help/resharper/Unit_Testing_in_CPP.html But I haven't personally tried it...

I had planned VS integration - there are a bunch of links in the [roadmap](https://github.com/onqtam/doctest/blob/master/doc/markdown/roadmap.md) under `IDE integration` but I doubt I'll have the capacity to work on that or...

Looks like JetBrains added doctest support not only for ReSharperC++ but also for CLion: https://blog.jetbrains.com/clion/2020/06/doctest-in-clion/

You can avoid the use of `thread_local` by defining `DOCTEST_THREAD_LOCAL` (without a value) before including `doctest.h` - let me know if this helps!

> Kinda works, but I'd prefer to avoid calling `CHECK`s in other threads at all. Well if you'll be avoiding asserts in multiple threads from a single test case then...

Sorry for the late reply. No, that's not supported in doctest, but you could indeed implement it as an external utility. We'll be adding extension headers to doctest (see https://github.com/onqtam/doctest/issues/405...