What gradle version are you using?
# kotest
l
What gradle version are you using?
t
Copy code
5.6.4
l
Could you please try to upgrade to 6.2.2 or to 6.3 (released this week) and tell us if there's any difference?
t
I’ll try that rn
s
It should work with 5.6.4
that error you see is usually when it can't find kotest or junit jupiter or whatever on teh clsasspath
t
@LeoColman 6.3 doesn’t seem to work either. Any other tips on how to run kotest in android project?
btw. current kotest version 3.3.2 works fine
just upgrading from that breaks
s
where you using junit4 or 5 previously ?
t
junit5 and 4 support in vintage mode
s
with kotlintest were you using the junit5 runner then ?
t
yeah. Does it have junit4 version tho?
s
It did
kotest4 doesn't
t
where I can find more Info about that?
s
ask me I guess lol
there isn't much docs atm
t
Copy code
kotlintest-runner-junit5
I used this artifact
I guess it have 5 in the name =)
s
yes so it should just work as before
I've asked @LeoColman to help me by creating a sample android project that I can get working on kotest to show as an example
You could help out too if you had time
t
well, I can’t even setup it in my project rn, lol
s
No I mean a vanilla android project
I don't do android so I'm not sure how to create a basic hello world view model controller thingy
t
maybe it is a junit5 concrete version that messes it up? Any compatability pitfalls here?
s
shouldn't be
you could try specifying the test engine
t
Any tools helping to debug test discovery? I have only one test class, maybe there is the way to log why it was ommited by discovery?
s
you can add kotlin.log=true as a system property
t
Not sure what you mean by "system property"
s
In your gradle.properties add
Copy code
org.gradle.kotlin.log=true
t
well, it did nothing
s
Let me find out exactly what it is
It's
Copy code
KOTEST_DEBUG
you can do it as an ENV var or a System Property. So
systemProp.KOTEST_DEBUG=true
in gradle.properties should active the logging
t
hmmm, I didn’t find any logs. And my time budget on investigating this is going to the end
so I guess I’ll stay on 3.x for now