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 anuraaga
, 1 year ago
expected:<3> but was:<2>
via GitHub by Frank-Bradley
, 2 years ago
i: 0 expected: but was:
via GitHub by hasancelik
, 1 year ago
expected:<0> but was:<1000>
via GitHub by IngvarJackal
, 4 months ago
expected:<[0, 3, 4, 4]> but was:<[0, 3]>
via GitHub by hasancelik
, 2 years ago
expected:<500> but was:<4156>
java.lang.AssertionError: expected:<2> but was:<0> at org.junit.Assert.fail(Assert.java:88)... java.lang.AssertionError: expected:<2> but was:<0> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at p4Testing.PublicTests.testCopyConstructor(PublicTests.java:72)