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. ,
    Expert tip

    Check your pattern declaration or check your assert declaration.

Solutions on the web

via QOS.ch JIRA by Joern Huxhorn, 1 year ago
Expected :1 Actual :0
via QOS.ch JIRA by Joern Huxhorn, 1 year ago
via Stack Overflow by Paul Taylor
, 2 years ago
Expected :1 Actual :0 <Click to see difference>
via JIRA by Andrew Audibert, 1 year ago
via ranger-dev by Ashish Singh, 1 year ago
expected:<0> but was:<1>
via ranger-dev by Gautam Borad, 1 year ago
expected:<0> but was:<1>
java.lang.AssertionError: Expected :1
Actual   :0	at org.junit.Assert.fail(Assert.java:93)	at org.junit.Assert.failNotEquals(Assert.java:647)	at org.junit.Assert.assertEquals(Assert.java:128)	at org.junit.Assert.assertEquals(Assert.java:472)	at org.junit.Assert.assertEquals(Assert.java:456)	at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemoval_Test.checkFileCount(TimeBasedRollingWithArchiveRemoval_Test.java:484)	at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemoval_Test.checkThatSmallTotalSizeCapLeavesAtLeastOneArhcive(TimeBasedRollingWithArchiveRemoval_Test.java:191)