Hey everyone :wave: , Is there any way in Kotest i...

# kotest

[simon.vergauwen]

Hey everyone 👋 ,
Is there any way in Kotest increase the time-out for promises?

Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

[dave08]

There seems to be two timeouts in Project/Spec configs:

/**
    * A global timeout that is applied to all tests if not null.
    * Tests which define their own timeout will override this.
    */
   open val timeout: Duration? = null

   /**
    * A global invocation timeout that is applied to all tests if not null.
    * Tests which define their own timeout will override this.
    * The value here is in millis
    */
   open val invocationTimeout: Long? = null

did you try those?

[simon.vergauwen]

Hey @dave08,
Yes, this seems to be a different time-out than the one set here. I have that one on the default which is 10s, but here I am failing with an error from the Promise. This seems to come from the JS runtime, rather than the Kotest runtime but I'm not sure.

[dave08]

https://github.com/kotest/kotest/blob/0ba14983d485b1b1caef0e5a2cd7402ba47e34d2/kotest-tests/kotest-tests-timeout-sysprop/build.gradle.kts#L43

[dave08]

https://github.com/kotest/kotest/blob/0ba14983d485b1b1caef0e5a2cd7402ba47e34d2/documentation/docs/framework/timeout.md

[dave08]

Funny that the default for the first seems to be 2000, but your problem could be something else...

[simon.vergauwen]

AbstractProjectConfig is only available for JVM 😕
https://github.com/kotest/kotest/blob/4f20f3892a779bb316f346f50ff8826dc68c0d5e/kot[…]c/jvmMain/kotlin/io/kotest/core/config/AbstractProjectConfig.kt

The problem is occurring in JS only

[sam]

Interesting. Seems like yeah the 2000 is coming from karma

[simon.vergauwen]

@sam I found a workaround by manually configuring karma through Gradle. It is indeed coming from Karma, and I'm not sure how the timeout is related to the tests. The timeout does not seem to correctly correspond to the tests though, it seems like not every test is running in a Karma Promise. Is that correct? The tests are way faster than the 2000ms per test.

[sam]

Only the inner most tests run as a promise, that's how karma works

[simon.vergauwen]

So it's creating a promise for every String#invoke for StringSpec for example?

[sam]

yes, but the test shouldn't take 2000 if your tests finishes sooner

[simon.vergauwen]

Right, then I'm not sure how I'm running into this in some cases. I just saw a failure whilst the suite takes 7ms after updating the Gradle config.

[sam]

Hmm, you could try switching the js runner to use something other than karma

[simon.vergauwen]

Anyone, I'm unblocked and I just pushed my fix.

https://github.com/arrow-kt/arrow/pull/2409/files#diff-07f2fe9ccf1f32a693e54340d1fc152f4dd109cf0b2bedd48501a41b94be61e3R14
https://github.com/arrow-kt/arrow/pull/2409/files#diff-463ce234475818ec06c5554c1a43dcfecefe548c93227eda9707b739da0d4d3b

[sam]

Kotlin JS supports

Jasmine

too

[sam]

it's great that you got this to work. I'm currently working on a compiler plugin for IR that will make this work better in kotest 5

[simon.vergauwen]

😍

[sam]

and will support native

[simon.vergauwen]

Awesome, I'm really looking forward to that!

[sam]

shouldn't take much longer, I'm blocked atm on the compiler plugin as the docs are still a bit lacking

[simon.vergauwen]

Arrow Core should be ready for native, if you need a tester I'd be happy to help.

[sam]

should get there soon though 🙂

[sam]

I'm hoping Kotest 5 by end of month

[simon.vergauwen]

That's perfect, by then I hope to have 1.0.0-M1 with JS out too and I can start using Kotest for native 🥳

[sam]

I haven't played too much with the native stuff yet, but for JS I'm detecting spec classes and creating code that runs them. In theory, the native should work exactly the same way. In other words, the compiler plugin effectively creates SpecExecutor.execute(ThisClass())

[sam]

and put's that inside the main entry point (for each spec)