Leonardo Colman Lopes

Reproduced on Kotest 5.8.0; Doesn't happen when running with Gradle

We can also use git submodules instead of migrating to a different repository. During the build we could detect what part was changed and run the build only on those

> Dropping support might be controversial, but I think it's worth investigating. I like the idea of dropping support. That would help with artifacts that get lost every now and...

An extension to generate the output in the same format as TestNG seems feasible

I'm not sure it should be incorporated to the core code. It would need maintenance to something we try the best we can to avoid: bringing mocking dependencies in. I...

You're not using the plugin to run. It's already possible to run single tests with Kotest plugin. Could you elaborate?

Should probably be `instanceOf`, I think you are right. It doesn't need to be exactly `Exception`, but the class you passed. I agree it should be Class and Subclasses.

I think it's missing the class that the exception ocurred, and that's what they're pointing out

- Consider switching default `TestIsolationMode` to `InstancePerTest` to better align with the 'expected' default behavior from JUnit - Consider/Check possibility/ignore gradle limitations on `TEST_AND_CONTAINER` If you remember the problem, we...

@kshired The reason we keep some tests in `com.sksamuel.kotest` is usually to test things related to package where we don't want to exclude it. We usually exclude `io.kotest.*` from anything...