Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

timeout doesn't actually stop the test

See original GitHub issue

The current implementation of test timeouts makes the test’s result be failure but doesn’t actually proactively stop the test, so you can’t use it to make your tests end in a reasonable amount of time in failure.

For example, this diff applied to release/3.4 yields a failing test. (The embedded test here spins for a second.)

diff --git a/kotlintest-tests/kotlintest-tests-core/src/test/kotlin/com/sksamuel/kotlintest/TestCaseExecutorTest.kt b/kotlintest-tests/kotlintest-tests-core/src/test/kotlin/com/sksamuel/kotlintest/TestCaseExecutorTest.kt
index 51c67410..98f95459 100644
--- a/kotlintest-tests/kotlintest-tests-core/src/test/kotlin/com/sksamuel/kotlintest/TestCaseExecutorTest.kt
+++ b/kotlintest-tests/kotlintest-tests-core/src/test/kotlin/com/sksamuel/kotlintest/TestCaseExecutorTest.kt
@@ -8,6 +8,7 @@ import io.kotlintest.TestCase
 import io.kotlintest.TestCaseConfig
 import io.kotlintest.TestContext
 import io.kotlintest.TestStatus
+import io.kotlintest.matchers.numerics.shouldBeLessThan
 import io.kotlintest.milliseconds
 import io.kotlintest.runner.jvm.TestCaseExecutor
 import io.kotlintest.runner.jvm.TestEngineListener
@@ -258,12 +259,15 @@ class TestCaseExecutorTest : FunSpec() {
         override fun description(): Description = Description.spec("wibble")
       }
 
+      val executorStartTime = currentTimeMillis()
       executor.execute(testCase, context)
+      val executorTotalTimeMillis = currentTimeMillis() - executorStartTime
 
       then(listener).should().exitTestCase(
           argThat { description == Description.spec("wibble") },
           argThat { status == TestStatus.Error && this.error?.message == "Execution of test took longer than 125ms" }
       )
+      executorTotalTimeMillis.shouldBeLessThan(500)
     }
 
     test("test with infinite loop but invocations = 1 should complete with TestStatus.Failure") {

The test is commented out on master and the code seems to be pretty rewritten, so maybe this is fixed in 4.0?