Anything I can do to help?

You can help test once I have something shippable - give me a couple more days and we should be able to test in anger

Actually one thing I need to figure out, that if you wanted to do that, would be helpful: • work out how to detect if a dependency is on the classpath for a gradle

module

before the plugin is applied (only want to apply the gradle plugin to modules that have kotest on the classpath)

Also trying to figure out what

org.jetbrains.kotlin.analysis.api.impl.base.sessions.ProhibitedAnalysisException: Analysis is not allowed: Called from a write action.

means. I have asked in jetbrains intellij slack but no reply so far.

if anyone wants to test out the new kotest intellij and gradle plugin combo, I can give you a build. It's rough but works.

Gradle question, I think @Adam S might be the best person to answer. Inside a gradle plugin task, how do I get the source sets? Specifically, I am trying to get a handle to the "test" sourceset. At the moment I am looking for the JavaPluginExtension, and getting it from that, but this fails for android. Follow up question - when you have a layout like say

src/main/java

and

src/main/kotlin

and

src/main/scala

is "main" the sourceset, or is java kotlin scala the sourcesets?

Here are the latest builds of the intellij plugin if you want to try the new gradle plugin. After installing these, take the latest kotest snapshot or build from source, and add

io.kotest

as a plugin to each gradle module you want to run kotest in. Then you should see

kotest

as a task in the gradle task list. Running tests from intellij should go via this new plugin and appear in the IDE automatically with full navigation to all nested levels, as well as using gradle to run all tests instead of a forked java process. I imagine they'll be edge cases that don't appear on my machine 🙂 Please file on the kotest board so I can address.

Couple of gradle questions for the experts 🙂 1. How do I configure a task as I register it, since we can't pass constructor args? If I make an internal field, gradle wants to treat it as an @Input.

project.tasks.register(JVM_TASK_NAME, KotestJvmTask::class.java) {
            setme = "hello" // how to do this?
         }

2. I want to make a task that just executes other tasks. Eg I want to register say "uberkotest" which runs "kotestA" and "kotestB". All three tasks are created in the same plugin.

I'm aiming to cut M2 today

What do we think about bumping min jdk to 11 for kotest 6? There's a library I want to use that's only available on java 11, and you can run your tests on 11 but compile to 8 if you really want anyway.

@sam thinking about it, looking at https://github.com/Kotlin/kotlinx-benchmark could help with how Kotest could support KMP targets. It's the exact same situation: discover and launch tests without using JUnit. For JVM it uses JMH, but the other targets have a custom implementation using a compiler plugin and code generation. However, I know the compiler plugin is overkill and could be replaced with KSP.

@Adam S should I wait for the plugin changes v2 before cutting M2 ?

Is there any interest in trying to get the remote build cache working again? Otherwise I’ll delete that server :)

did you get around to trying the new plugin ? Or waiting for M2

I think this issue was caused by changing the BOM here. Anyone got pointers on how I can start to fix it? And as the original thread author mentions, should we just replace the BOM with a gradle version catalog?

6.0.0.M2 is published

JS tests running through our custom plugin, with support for nesting at all levels and all the other good stuff.

Ran into another issue w/ Kotest 6.0.0.M2 w/ gradle plugin in a project that uses kotest-extensions-wiremock. 🧵

Why is

afterTest

showing as

@KotestInternal

in 6.0.0.M2? Should I report an issue?

Are we gonna merge

StringSpec

,

WordSpec

and

FreeSpec

in 6.0?

We were locked out of doing this by gradle. If we are moving away from gradle in favor of Kotest plugin we can do the merge

fyi Gradle 8.13 has a new API for reporting tests. Kotest could use it to report tests directly to Gradle. https://docs.gradle.org/8.13-rc-1/userguide/test_reporting_api.html

As someone who works almost exclusively on macOS, this feels slightly hostile 😜

@EnabledIf(LinuxCondition::class)
class BindTest : StringSpec({

And am I the only one with issues running K2 mode in the Kotest repo? Weird bugs in IntellliJ until I switched back to K1

https://github.com/kotest/kotest-extensions-testcontainers says it was moved to the main repo, but I can't find it.

Should it be there? I can create it if needed

@Emil Kantis @LeoColman can you have a look at https://github.com/kotest/kotest/pull/4804 - I'm baffled. TIA!

gonna try to get M3 out tomorrow

@sam is this being addressed by any already planned work for 6.0? IIRC you were ditching test types entirely?

Hello, I would like to ask a question about this issue. Is it even worth supporting such special iterators as described in the issue? It seems to me that the undefined behavior when dealing with such non-conventional iterators is the user's concern, not the library's. I mean, it's easy to support, but I'm not sure it's worth it. What do you think?