question-mark
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.

Unrelated test error - java.lang.AssertionError: Test 'xyz' is incomplete

See original GitHub issue

Info: Kotest = 4.2.6 SpecUsed = FunSpec gradleVersion = Gradle 6.3 Kotlin = 1.3.70 Reporting Allure = 2.8.1

Hello, I’m using gradle command line to run test on my local with specific tag. All my tests (assume A, B, C etc) are created using FunSpec style. When i want to run only single test e.g. A, in console I see logs related to B and C also.

<test path> STANDARD_ERROR java.lang.AssertionError: Test ‘B’ is incomplete at io.kotest.engine.spec.SpecExecutor.checkClosedTestCases(SpecExecutor.kt:58) at io.kotest.engine.spec.SpecExecutor.execute(SpecExecutor.kt:45) at io.kotest.engine.KotestEngine$submitBatch$$inlined$forEach$lambda$1$1.invokeSuspend(KotestEngine.kt:139) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56) at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:274) at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:84) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59) at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38) at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source) at io.kotest.engine.KotestEngine$submitBatch$$inlined$forEach$lambda$1.run(KotestEngine.kt:138) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) java.lang.AssertionError: Test ‘B’ is incomplete at io.kotest.engine.spec.SpecExecutor.checkClosedTestCases(SpecExecutor.kt:58) at io.kotest.engine.spec.SpecExecutor.execute(SpecExecutor.kt:45) at io.kotest.engine.KotestEngine$submitBatch$$inlined$forEach$lambda$1$1.invokeSuspend(KotestEngine.kt:139) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56) at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:274) at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:84) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59) at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38) at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source) at io.kotest.engine.KotestEngine$submitBatch$$inlined$forEach$lambda$1.run(KotestEngine.kt:138) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) Gradle Test Executor 5 STANDARD_ERROR at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

And in also i see

Task :test 3 tests completed, 2 failed

But the actual test A runs fine and Allure report shows only this test as expected. While running directly from intelliJ, there is no errors in console. Test A runs fine.

Questions:

  1. What does Test is incomplete means?
  2. Why does gradle/kotest initializing/running other tests?

Any help in debugging is appreciated.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
sksamuelcommented, Aug 17, 2021

<4.6 versions are no longer seeing anything but the most critical fixes so I think we can close. 5.0 is the current focus.

0reactions
Ankit-Laddhacommented, Aug 17, 2021

I upgraded kotest to 4.6.1, no longer see this problem w/o any code changes. so definitely some problem with 4.2.6 version. @sksamuel what we do with this issue then? let it be open for 4.2.6?

Read more comments on GitHub >

github_iconTop Results From Across the Web

AssertionError on totally unrelated line of code - Junit test for ...
java corresponds to registry.bind(libraryName, stub) . Well, this cannot be true, since according to the stack trace, the failure is detected by a...
Read more >
Error received when testing java.lang.AssertionError: Reading ...
Hello everyone, I tried to run the online test suit for the Core but there are two failed tests. check Resource Paths and...
Read more >
Groovy Language Documentation
is an agile and dynamic language for the Java Virtual Machine. builds upon the strengths of Java but has additional power features inspired...
Read more >
Kotlin Language Documentation 1.7.21
Check the presence of an element in a collection. String interpolation ... The Kotlin compiler detects these remaining errors,.
Read more >
String Not Empty Test Assertions in Java - Baeldung
Check out our in-depth guide on JUnit assertions here. All these assertions, when failed, will return an AssertionError. 4. Using Hamcrest Core.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found