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

Solutions on the web

via GitHub by charlesa101
, 1 year ago
Event count expected:<2> but was:<1>
via metamodel-dev by Arvind Prabhakar, 2 years ago
expected:<Fri Dec 31 > > 12:00:00 > > > > PST 2010> but was:<Fri Dec 31 00:00:00 PST 2010>
via metamodel-dev by Ankit Kumar, 2 years ago
expected:<Fri Dec 31 > 12:00:00 > > > PST 2010> but was:<Fri Dec 31 00:00:00 PST 2010>
via metamodel-dev by Henry Saputra, 2 years ago
expected:<Fri Dec 31 >> > 12:00:00 >> > > > PST 2010> but was:<Fri Dec 31 00:00:00 PST 2010>
junit.framework.AssertionFailedError: expected:<5> but was:<4> at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.failNotEquals(Assert.java:329) at junit.framework.Assert.assertEquals(Assert.java:78) at junit.framework.Assert.assertEquals(Assert.java:86) at junit.framework.TestCase.assertEquals(TestCase.java:253) at org.camunda.bpm.engine.test.examples.mgmt.ManagementServiceTest.testTableCount(ManagementServiceTest.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at junit.framework.TestCase.runTest(TestCase.java:176) at org.camunda.bpm.engine.impl.test.PvmTestCase.runTest(PvmTestCase.java:85) at junit.framework.TestCase.runBare(TestCase.java:141) at org.camunda.bpm.engine.impl.test.AbstractProcessEngineTestCase.runBare(AbstractProcessEngineTestCase.java:91)