junit.framework.AssertionFailedError: expected:<0> but was:<>

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

Samebug tips

,
Expert tip

This exception could rise due to a connection timeout.

Solutions on the web

via strutstestcase by *anonymous
, 1 year ago
via narkive.com by Unknown author, 2 years ago
integrity test expected:<0> but was:<4>
via poi-dev by avik.sengupta@itellix.com, 6 months ago
expected:<&#65533;> but > was:<?>
via coderanch.com by Unknown author, 1 year ago
junit.framework.AssertionFailedError: expected:<0> but was:<>
at junit.framework.Assert.fail(Assert.java:51)
at junit.framework.Assert.failNotEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:68)
at test.com.uhg.ut.pbd.bq.standalone.actions.PlanSearchActionTest.testAction(PlanSearchActionTest.java:101)
at junit.framework.TestCase.runTest(TestCase.java:166)
at junit.framework.TestCase.runBare(TestCase.java:140)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:131)
at junit.framework.TestSuite.runTest(TestSuite.java:173)
at junit.framework.TestSuite.run(TestSuite.java:168)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:392)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:276)

Users with the same issue

Once, 1 month ago
Once, 1 month ago
28 times, 2 months ago
Once, 3 months ago
4 times, 4 months ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.