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

  1. ,

    My guess is there is some kind of static state in the code being tested or in the test itself, so the tests aren't isolated. Adding the test changes the test order. In any case, your best course of action is to use the debugger to see why the tests fail.

  2. ,

    Check your assert declaration and the method implementation with the condition.

Solutions on the web

via GitHub by anuraaga
, 1 year ago
expected:<3> but was:<2>
via Google Groups by Peter Firmstone, 1 year ago
expected:<0> but was:<3>
via wicket-dev by Martin Grigorov, 1 month ago
via wicket-dev by Maxim Solodovnik, 1 month ago
via wicket-dev by Martin Grigorov, 1 month ago
via wicket-dev by Maxim Solodovnik, 1 month ago
java.lang.AssertionError: expected:<3> but was:<2> 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)