Sebastian Schuberth

I'm actually not so sure if the number of effected users really is that small. After all, Lenovo is on of the biggest PC manufacturers and notebooks usually don't have...

> I'll start receiving complaints of "But it doesn't work for THIS specific ISO from manufacturer XYZ! ". Does that mean you'd be opposed to accepting a contribution that adds...

> @sschuberth are you sure that using the library you mentioned is the good idea? Of course I cannot tell for *sure*. But personally I strongly prefer multiplatform Kotlin code...

Actually, when I was saying "TODO" I was not thinking of TODO-style code comments like `// TODO: Implement this`. I just wanted to give that special "section" in the test...

I see. Any idea whether first moving to JUnit 5 would make a difference here? It seems that JUnit 5 has been designed to better support TDD, but I yet...

Hmm. The whole point of "expected to fail" tests is that they *do* get run, but their failure does not count towards the fail count. We do not want to...

Ah, so that's indeed an option then!

@brucek, I've reopened this and copied your comment from https://github.com/kotest/kotest/issues/3061 here: > I couldn't re-open the issue in #187 but this does have value, esp coming to Kotlin from other...

> So your three options are - failed test, successful test, ignored test. I was hoping there was the possibility to add a fourth option, like "pending test" or "expected...

> So what I don't understand is what differs from a regular test. Coming back to that, the difference is basically just semantics. Of course you could write an "expected...