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 Google Groups by Prakash, 2 years ago
expected:<false> but was:<true>
via GitHub by epishkin
, 2 years ago
expected:<expected value> but was:<null>
via JDK Bug System by Amy Lu, 1 year ago
expected [[ 1] (s = 55) custom-key: custom-header Table size: 55] but found [[ 1] (s = 55) custom-key: custom-header Table size: 55]
via Google Groups by Thomas.Haines, 2 years ago
expected:<0> but was:<255>
via Google Groups by Steffan Cline, 2 years ago
expected:<0> but was:<255>
java.lang.AssertionError: expected:<0> but was:<1>	at org.testng.Assert.fail(Assert.java:89)	at org.testng.Assert.failNotEquals(Assert.java:489)	at org.testng.Assert.assertEquals(Assert.java:118)	at org.testng.Assert.assertEquals(Assert.java:365)	at org.testng.Assert.assertEquals(Assert.java:375)	at org.sonatype.nexus.integrationtests.nexus383.Nexus383SearchNGIT.searchFor(Nexus383SearchNGIT.java:111)	at org.sonatype.nexus.integrationtests.nexus383.Nexus383SearchNGIT.disableEnableSearching(Nexus383SearchNGIT.java:194)