Any way to get more information out of kotest? I h...

# kotest

[Justin Tullgren]

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]

Global Config.txt

[Justin Tullgren]

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

[Justin Tullgren]

removing it doens't make a difference

[sam]

is it just a single test that is hanging ?

[Justin Tullgren]

i'll check, one second

[Justin Tullgren]

no its not. its all types that use coroutines

[Justin Tullgren]

tests that use coroutines

[sam]

are you able to share your listener ?

[Justin Tullgren]

Untitled.kt

[Justin Tullgren]

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

[sam]

what is TestCoroutineDispatcher

[sam]

and is Dispatchers.setMain some android thing ?

[Justin Tullgren]

its all kotin libs: https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-test/

[Justin Tullgren]

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

[sam]

are you wanting to run your test on that dispatcher ?

[Justin Tullgren]

https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-test/kotlinx.coroutines.test/-test-coroutine-dispatcher/index.html

[Justin Tullgren]

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

[Justin Tullgren]

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

[sam]

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]

if you remove that listener does it complete the tests ?

[Justin Tullgren]

no, it doesn't make a difference

[Justin Tullgren]

already tried

[sam]

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]

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

[sam]

you can enable KOTEST_DEBUG=true

[sam]

as an env var

[Justin Tullgren]

ahh great. jvm arg?

[Justin Tullgren]

or gradle?

[sam]

env is easist

[sam]

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

[Justin Tullgren]

k i'll give it a go. thanks for your help

[sam]

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

[sam]

Or fix kotest if required

[Justin Tullgren]

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

[Justin Tullgren]

quick question, are value/inline classes supported ?

[sam]

supported for what

[sam]

like just having them around in tests ?

[Justin Tullgren]

just in the test body

[Justin Tullgren]

ya

[Justin Tullgren]

kotest 4.6.1

[sam]

yeah I assume so, a test is just suspend () -> Unit

[Justin Tullgren]

kk

[Justin Tullgren]

thanks

[Justin Tullgren]

thanks for you help, its a mockk issue

[sam]

ah interesting

[Justin Tullgren]

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

[sam]

no problem if you don't mind the verbose output

[Justin Tullgren]

great thanks again