Any way to get more information out of kotest I have a test

Question

Any way to get more information out of kotest I have a test run that gets through 3 tests successfully and then just hangs using gradle or kotest plugin

Justin Tullgren · Answer

This run is in the gradle testImplementation configuration I have a coroutines listener to use the coroutines test dispatcher

Justin Tullgren · Answer

removing it doens t make a difference

sam · Answer

is it just a single test that is hanging

Justin Tullgren · Answer

i ll check one second

Justin Tullgren · Answer

no its not its all types that use coroutines

Justin Tullgren · Answer

tests that use coroutines

sam · Answer

are you able to share your listener

Justin Tullgren · Answer

this is clearly on my end i just can t figure out what kotest is thinking since the timeouts never expire or throw

sam · Answer

what is TestCoroutineDispatcher

sam · Answer

and is Dispatchers setMain some android thing

Justin Tullgren · Answer

its all kotin libs <https kotlin github io kotlinx coroutines kotlinx coroutines test >

Justin Tullgren · Answer

not just android swing or javafx too anything that has a Main looper for UI rendering

sam · Answer

are you wanting to run your test on that dispatcher

Justin Tullgren · Answer

Justin Tullgren · Answer

no i am not i manage that dispatcher in the tests advancing time etc

Justin Tullgren · Answer

just curious why kotest waits even though there is a timeout and invocation timeout of 60 seconds

sam · Answer

I think your listener must be changing the dispatcher for the test somehow and the coroutine kotest has created for the test is never completed

sam · Answer

if you remove that listener does it complete the tests

Justin Tullgren · Answer

no it doesn t make a difference

Justin Tullgren · Answer

already tried

sam · Answer

I would keep that listener out for now if it s not making any difference And I would need to see a test that is failing perhaps you can pare down the tests until you find the one at fault

Justin Tullgren · Answer

kk thats my plan i was just looking for more info from kotest thanks

sam · Answer

you can enable KOTEST DEBUG=true

sam · Answer

as an env var

Justin Tullgren · Answer

ahh great jvm arg

Justin Tullgren · Answer

or gradle

sam · Answer

env is easist

sam · Answer

you can do sys prop too but gradle is weird about propogating those

Justin Tullgren · Answer

k i ll give it a go thanks for your help

sam · Answer

If you can get the failure down to a single test I will be able to help you fix ti

sam · Answer

Or fix kotest if required

Justin Tullgren · Answer

thanks that debug stopped on a test started and then hung so i am looking at it

Justin Tullgren · Answer

quick question are value inline classes supported

sam · Answer

supported for what

sam · Answer

like just having them around in tests

Justin Tullgren · Answer

just in the test body

Justin Tullgren · Answer

ya

Justin Tullgren · Answer

kotest 4 6 1

sam · Answer

yeah I assume so a test is just `suspend gt Unit`

Justin Tullgren · Answer

kk

Justin Tullgren · Answer

thanks

Justin Tullgren · Answer

thanks for you help its a mockk issue

sam · Answer

ah interesting

Justin Tullgren · Answer

imma keep that prop on every build unless there is a problem with doing that

sam · Answer

no problem if you don t mind the verbose output

Justin Tullgren · Answer

great thanks again