Assertion failed are not shown without adding opentest4j dependency.

Before adding opentest4j dependency, it shows this exception whenever assertion failed occur:

java.lang.NoClassDefFoundError: org/opentest4j/AssertionFailedError
	at strikt.internal.AssertionStrategy.createAssertionFailedError$strikt_core(AssertionStrategy.kt:195)
	at strikt.internal.AssertionStrategy$Throwing.afterStatusSet(AssertionStrategy.kt:151)
	at strikt.internal.AssertionStrategy$appendAtomic$1.fail(AssertionStrategy.kt:44)
	at strikt.api.AtomicAssertion$DefaultImpls.fail$default(AtomicAssertion.kt:19)
	at strikt.assertions.CollectionKt$hasSize$1.invoke(Collection.kt:12)
	at strikt.assertions.CollectionKt$hasSize$1.invoke(Collection.kt)
	at strikt.internal.AssertionBuilder.assert(AssertionBuilder.kt:64)
	at strikt.internal.AssertionBuilder.assert(AssertionBuilder.kt:11)
	at strikt.assertions.CollectionKt.hasSize(Collection.kt:9)
       at ....
	at org.spekframework.spek2.runtime.scope.TestScopeImpl.execute(Scopes.kt:94)
	at org.spekframework.spek2.runtime.Executor$execute$$inlined$executeSafely$lambda$1$1.invokeSuspend(Executor.kt:52)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:740)
Caused by: java.lang.ClassNotFoundException: org.opentest4j.AssertionFailedError
	at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 18 more

After I added testImplementation group: 'org.opentest4j', name: 'opentest4j', version: '1.2.0', everything works fine.

I’m using spek version 2.0.6 for testing an Android app. It works fine with other assertion library like AssertJ.

P/S I think it is still not fine after I adding opentest4j dependency. Here is what I got after addin the dependency:

  ✗ has size 2 : found 1
org.opentest4j.AssertionFailedError: ▼ Expect that [Mock for Class, hashCode: 17337594]:
  ✗ has size 2 : found 1
	at ...
	at ....
	at org.spekframework.spek2.runtime.scope.TestScopeImpl.execute(Scopes.kt:94)
	at org.spekframework.spek2.runtime.Executor$execute$$inlined$executeSafely$lambda$1$1.invokeSuspend(Executor.kt:52)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
	Suppressed: org.opentest4j.AssertionFailedError
		at strikt.internal.AssertionStrategy.createAssertionFailedError$strikt_core(AssertionStrategy.kt:195)
		at strikt.internal.AssertionStrategy$Throwing.afterStatusSet(AssertionStrategy.kt:151)
		at strikt.internal.AssertionStrategy$appendAtomic$1.fail(AssertionStrategy.kt:44)
		at strikt.api.AtomicAssertion$DefaultImpls.fail$default(AtomicAssertion.kt:19)
		at strikt.assertions.CollectionKt$hasSize$1.invoke(Collection.kt:12)
		at strikt.assertions.CollectionKt$hasSize$1.invoke(Collection.kt)
		at strikt.internal.AssertionBuilder.assert(AssertionBuilder.kt:64)
		at strikt.internal.AssertionBuilder.assert(AssertionBuilder.kt:11)

[robfletcher]

That’s a deliberate bit of behavior so that the stack trace originates at the line in your test where the assertion is. Any internal stack frames from the strikt code are shifted into the suppressed section.

[robfletcher]

No problem. Thanks for the bug report!