Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

java.lang.NullPointerException: 	at org.junit.runner.Description.createSuiteDescription(Description.java:124)	at ru.yandex.qatools.allure.junit.AllureRunListener.getSuiteUid(AllureRunListener.java:110)	at ru.yandex.qatools.allure.junit.AllureRunListener.testStarted(AllureRunListener.java:50)	at org.junit.runner.notification.SynchronizedRunListener.testStarted(SynchronizedRunListener.java:49)	at org.junit.runner.notification.RunNotifier$3.notifyListener(RunNotifier.java:121)	at org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)	at org.junit.runner.notification.RunNotifier.fireTestStarted(RunNotifier.java:118)	at org.apache.maven.surefire.common.junit4.Notifier.fireTestStarted(Notifier.java:100)	at io.kotlintest.TestBase.runTest(TestBase.kt:119)	at io.kotlintest.TestBase.runSharedInstance(TestBase.kt:104)	at io.kotlintest.TestBase.run$kotlintest_compileKotlin(TestBase.kt:43)	at io.kotlintest.KTestJUnitRunner.run(KTestJUnitRunner.kt:14)	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)