Sam

I'm not really a fan of interfaces where they are not needed. You can easily test code using the caeffine builder, since it's in memory, so the "mock" use case...

Yes. Good catch.

The latest snapshot has support for tags via either command line eg `./gradle kotest --tags foo` or by setting tags inside a gradle build file configuration block, eg ``` kotest...

I just remembered we don't have snapshots for gradle plugins. So I've released 0.3.8 with tags. Feedback still very much useful.

Yeah Kotest should not report specs which had zero eligible tests. Lets create another ticket for that. On Wed, 14 Apr 2021 at 11:22, Reza Malik ***@***.***> wrote: > It...

https://github.com/kotest/kotest-gradle-plugin/issues/16

Will be fixed automatically on the other fix. On Wed, 14 Apr 2021 at 11:25, Reza Malik ***@***.***> wrote: > The total also is kinda suspect there. Do we need...

I see that too. On Wed, 14 Apr 2021 at 11:41, Reza Malik ***@***.***> wrote: > I forgot to mention this works on gradle 7 and did not on 6.8....

This is easy to do, but we need to consider what syntax to use. Gradle style perhaps: entire spec `--tests a.b.SpecName` or specific test path `--tests a.b.SpecName mytest**` or `--include...

Yeah that's what I was thinking. The gradle one isn't great as it uses a ClassMethodFilter internally which assumes the test name is a method handle.