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 darklynx
, 8 months ago
expected [ACTIVE] but found []
via GitHub by Stephan202
, 1 year ago
expected [dummyArg] but found [arg0]
via GitHub by chavdar
, 1 year ago
expected [1] but found [0]
via GitHub by doom369
, 1 year ago
expected [404] but found [200]
via GitHub by catull
, 1 month ago
expected [2016-01-03] but found [2016-01-02]
java.lang.AssertionError: expected [404] but found [200]	at org.testng.Assert.fail(Assert.java:94)	at org.testng.Assert.failNotEquals(Assert.java:513)	at org.testng.Assert.assertEqualsImpl(Assert.java:135)	at org.testng.Assert.assertEquals(Assert.java:116)	at org.testng.Assert.assertEquals(Assert.java:389)	at org.testng.Assert.assertEquals(Assert.java:399)	at org.asynchttpclient.PerRequestRelative302Test.redirected302InvalidTest(PerRequestRelative302Test.java:140)	at org.asynchttpclient.PerRequestRelative302Test.runAllSequentiallyBecauseNotThreadSafe(PerRequestRelative302Test.java:86)