With Kotest 6.1.3, I'm getting: ```Execution faile...
# kotest
c
With Kotest 6.1.3, I'm getting:
Copy code
Execution failed for task ':gradle:templates:template-app:wasmJsBrowserTest'.
> There are test sources present and no filters are applied, but the test task did not discover any tests to execute. This is likely due to a misconfiguration. Please check your test configuration. If this is not a misconfiguration, this error can be disabled by setting the 'failOnNoDiscoveredTests' property to false.
even though I already have
Copy code
tasks.withType<Test> {
	failOnNoDiscoveredTests = false
}
in that project. How can I fix/workaround this?
s
is this only without a clean first ?
c
./gradlew clean; ./gradlew check
gives the same result
s
is this on prepared? can you link the branch
c
It's on the Playground, which is our staging repo where we test libraries before deploying them to real projects https://gitlab.com/opensavvy/playgrounds/gradle Branch
kotlin-2.3
Ah,
Copy code
tasks.withType<AbstractTestTask> {
	failOnNoDiscoveredTests = false
}
does correctly ignore the message. For now, that's acceptable for us. I saw the official examples do it as well, is there anything planned regarding this?
s
It's a Gradle thing
They added it recently
I'll update the docs for abstract test task
c
9.0 I think? But I think it's a good idea on their side
I've been bitten multiple times by situations in which Kotest didn't run JS tests even though I thought it did, it'd be nice to have that Gradle feature working so it doesn't go unnoticed
s
I think it's because of the cache though.
Happens on jvm too i think?
c
It doesn't complain for me if I only run the JVM tests
s
Hmm ok you've given me a weekend task :)
c
Sorryyyy 😅
😛 1
s
Or I can add you as a contributor if u wanna figure it out :)
c
In the meantime, I can finally upgrade to Kotlin 2.3.0 and get the unused value checker blob smile happy
Integrating a test framework with Gradle? The entire reason Prepared is a DSL on top of other frameworks is because I didn't want to do that 😅 However, #C09FQGG85EC has managed to get it working, so perhaps you can take inspiration from their code
s
simply needed to detect that the jasmine framework adapter is available in wasm mode and flip to using that over TCSM