java.lang.AssertionError: expected:<0> but was:<1>

Spring JIRA | Gary Russell | 4 years ago
  1. 0

    compile failed

    GitHub | 4 years ago | junit
    java.lang.AssertionError: expected:<0> but was:<1>
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

  3. 0

    [HDFS-3344] Unreliable corrupt blocks counting in TestProcessCorruptBlocks - ASF JIRA

    apache.org | 1 year ago
    java.lang.AssertionError: expected:<0> but was:<1>
  4. 0

    [egit-build] Build failed in Hudson: egit #2202

    eclipse.org | 1 year ago
    java.lang.AssertionError: expected:<0> but was:<1>

  1. fervidnerd 3 times, last 1 week ago
  2. davidvanlaatum 1 times, last 2 weeks ago
  3. andyglick 9 times, last 8 months ago
  4. WoodenDoors 3 times, last 9 months ago
  5. davidvanlaatum 103 times, last 9 months ago
32 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.lang.AssertionError

    expected:<0> but was:<1>

    at org.junit.Assert.fail()
  2. JUnit
    Assert.assertEquals
    1. org.junit.Assert.fail(Assert.java:91)
    2. org.junit.Assert.failNotEquals(Assert.java:645)
    3. org.junit.Assert.assertEquals(Assert.java:126)
    4. org.junit.Assert.assertEquals(Assert.java:470)
    5. org.junit.Assert.assertEquals(Assert.java:454)
    5 frames
  3. org.springframework.integration
    PipelineNamedReplyQueuesJmsTests.testPipeline2a
    1. org.springframework.integration.jms.request_reply.PipelineNamedReplyQueuesJmsTests.testPipeline2a(PipelineNamedReplyQueuesJmsTests.java:74)
    1 frame