<https://stackoverflow.com/questions/54847416/warning-testengine-with-id-spek2-failed-to-discover-te...

# spek

[Shan]

https://stackoverflow.com/questions/54847416/warning-testengine-with-id-spek2-failed-to-discover-tests-with-gradle-v5-2-1 posted on Stack as well if anyone wants to answer there instead 👍

[raniejade]

Are you able to share your project? If not can you create a minimal one that fully replicates your issue? Happy to help out.

[Shan]

https://gitlab.com/Shanling/spek2test ive made a project with my issue here. Thanks for any help!

[Shan]

Feb 24, 2019 9:41:07 PM org.junit.platform.launcher.core.DefaultLauncher handleThrowable
WARNING: TestEngine with ID 'spek2' failed to discover tests
java.lang.IllegalStateException: clz.java.`package` must not be null
	at org.spekframework.spek2.runtime.scope.PathBuilder$Companion.from(Path.kt:86)
	at org.spekframework.spek2.runtime.SpekRuntime.discover(SpekJvmRuntime.kt:30)
	at org.spekframework.spek2.junit.SpekTestEngine.discover(SpekTestEngine.kt:76)
	at org.junit.platform.launcher.core.DefaultLauncher.discoverEngineRoot(DefaultLauncher.java:177)
	at org.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:164)
	at org.junit.platform.launcher.core.DefaultLauncher.discover(DefaultLauncher.java:120)
	at com.intellij.junit5.JUnit5IdeaTestRunner.startRunnerWithArgs(JUnit5IdeaTestRunner.java:52)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)

Here is the full stacktrace

[raniejade]

Hmm, pretty sure I have fixed this already. What JDK are you using?

[Shan]

Jdk1.8.0_181

[raniejade]

I'll take a look sometime this week, can you use JDK 10 in the meantime?

[Shan]

Unfortunately I can't use JDK 10 for my project (other dependencies require 8 ). Thank you for looking at this issue 👍

[raniejade]

@Shan this will be fixed in the 2.0.1 release.

[Shan]

@raniejade Thank you so much! Looking forward to it 🙂

[Shan]

Everything is working now. Thanks again!