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 MuleSoft JIRA by Andrew Cooke, 1 year ago
expected:<4> but was:<3>
via MuleSoft JIRA by andrew cooke, 2 years ago
expected:<4> but was:<3>
via apache.org by Unknown author, 2 years ago
expected:<6> but was:<4>
via apache.org by Unknown author, 1 year ago
expected:<6> but was:<4>
via apache.org by Unknown author, 1 year ago
expected:<6> but was:<4>
via continuum-dev by Roald Bankras, 11 months ago
expected:<1> but was:<2>
junit.framework.AssertionFailedError: expected:<4> but was:<3> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:280) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:133) at junit.framework.Assert.assertEquals(Assert.java:139) at org.mule.providers.quartz.QuartzFunctionalTestCase.testMuleReceiverJob(QuartzFunctionalTestCase.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)