Does anyone know what is the root cause of my test...
# kotest
s
Does anyone know what is the root cause of my test (
BehaviorSpec
), not running, when
kotest-extensions-roboelectric
dependency is added to the module ? Im using 6.0.3 and 0.5.0 versions respectively. I get the following error:
'io.kotest.engine.tags.TagExpression io.kotest.core.extensions.TagExtension.tags()'
java.lang.NoSuchMethodError: 'io.kotest.engine.tags.TagExpression io.kotest.core.extensions.TagExtension.tags()'
at io.kotest.engine.tags.TagExpressionBuilder.build(runtime.kt:15)
at io.kotest.engine.spec.interceptor.ref.enabled.TagsInterceptor.intercept-0E7RQCE(TagsInterceptor.kt:28)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.interceptor.ref.DescriptorFilterSpecRefInterceptor.intercept-0E7RQCE(DescriptorFilterSpecRefInterceptor.kt:41)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.interceptor.ref.ApplyExtensionsInterceptor.intercept-0E7RQCE(ApplyExtensionsInterceptor.kt:36)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.interceptor.ref.enabled.IgnoredSpecInterceptor.intercept-0E7RQCE(IgnoredSpecInterceptor.kt:47)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.interceptor.ref.enabled.DisabledIfInterceptor.intercept-0E7RQCE(DisabledIfInterceptor.kt:46)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.interceptor.ref.enabled.EnabledIfInterceptor.intercept-0E7RQCE(EnabledIfInterceptor.kt:41)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.interceptor.ref.enabled.RequiresPlatformInterceptor.intercept-0E7RQCE(RequiresPlatformInterceptor.kt:25)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.ClassVisibilitySpecRefInterceptor.intercept-0E7RQCE(ClassVisibilitySpecRefInterceptor.kt:29)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline$execute$3$1.invoke-gIAlu-s(SpecRefInterceptorPipeline.kt:49)
at io.kotest.engine.spec.interceptor.SpecRefInterceptorPipeline.execute-0E7RQCE(SpecRefInterceptorPipeline.kt:52)
at io.kotest.engine.spec.execution.SpecRefExecutor.execute(SpecRefExecutor.kt:45)
at io.kotest.engine.TestSuiteScheduler.executeIfNotFailedFast(TestSuiteScheduler.kt:97)
at io.kotest.engine.TestSuiteScheduler.access$executeIfNotFailedFast(TestSuiteScheduler.kt:29)
at io.kotest.engine.TestSuiteScheduler$schedule$11$1$2.invokeSuspend(TestSuiteScheduler.kt:77)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:263)
at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:94)
at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:70)
at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)
at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:48)
at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)
at io.kotest.engine.RunBlocking_jvmKt.runBlocking(runBlocking.jvm.kt:3)
at io.kotest.engine.TestEngineLauncher.launch(TestEngineLauncher.kt:206)
at io.kotest.runner.junit.platform.KotestJunitPlatformTestEngine.execute(KotestJunitPlatformTestEngine.kt:74)
at io.kotest.runner.junit.platform.KotestJunitPlatformTestEngine.execute(KotestJunitPlatformTestEngine.kt:47)
s
It looks like you have a previous version f kotest sneaking into the classpath somewhere
s
could it be that
kotest-extensions-roboelectric
needs an update for v6 ?
s
Ah yes that'll be it
not sure if there will be any breaking change if we update to 6.0.3 there