Martin Hořeňovský

I am finally back around for long enough to go through the larger PRs. I rebased the PR and will pick it up during this week. Sorry for the long...

@psalz I read through it again today, I think the changes are fine, but the other reporters need to have a better support for skipping. I tried a few, and...

I also went to the original post (this is a very high quality PR btw) and > Consider adding a CLI option for whether skipped tests should be reported or...

I started looking at the reporter formats. **TeamCity** - I think the Ignored tests message matches up with the intent of `SKIP`, see https://www.jetbrains.com/help/teamcity/service-messages.html#Nested+Test+Reporting, Ctrl+F to "Ignored tests". ----- Went...

re the flag to turn `SKIP`s into failures, I thought about it and I think a new warning flag is the simplest (and cleanest) solution

Don't worry, you will have to be waaaay slower before the PR has spent more time waiting on you than it has waiting on me.

Do you have an idea about when you are going to have time to finish this? I am planning next release and wondering whether I should wait for this or...

No problem, I'll pull in things I want to have in the next release and plan for this to be in a later one. * Sure, `skipTest` can be marked...

I gave this some thought for #2509. I still believe that the ability to print out stringified generator states is too valuable to give up, so, here are two options...

> the biggest issue might not be getting everything to compile at all, but output that is too noisy. Agreed, I intend the default output to be just the "indices"...