junit.framework.ComparisonFailure

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • If you look at this url: http://81.17.46.170/bamboo/build/viewBuildResults.action?buildKey=WICKET2X-WICKET&buildNumber=10 you see a build of our open source Wicket Project. It is telling me that 85 test are failing, but if you look closely you see that in the TestCase column it only reports the same one over and over again ( Render home page_3) One for every "TestSuite" but that TestSuite is not a suite, it is a TestCase by itself. if you click on one that he says it fails: http://81.17.46.170/bamboo/browse/WICKET2X-WICKET-10/test/wicket.AttributeModifierComponentTest:testRenderHomePage_3 then you see this: Test Class: wicket.AttributeModifierComponentTest Method:testRenderHomePage_3 but AttributeModifierComponentTest doesn't have a testRenderHomePage_3 you can see in the stacktrace: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:<... ...> but was:<......> junit.framework.ComparisonFailure: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:&... ...& but was:&......& at junit.framework.Assert.assertEquals(Assert.java:81) at wicket.util.diff.DiffUtil.validatePage(DiffUtil.java:107) at wicket.WicketTestCase.executeTest(WicketTestCase.java:81) at wicket.markup.html.basic.SimplePageTest.testRenderHomePage_3(SimplePageTest.java:283) Where it really comes from And that s stacktrace is mentioned everywhere. So it seems to report many times the same error on in what he things is a TestSuite. the other strange thing is that when you scrolldown to the fixed cases. You see as far as i see the exact same list (of testsuites). But then it tell is that it is fixed! and if you click on one. You see that it gives the error description. So it is not really fixed...
    via by johan compagner,
  • If you look at this url: http://81.17.46.170/bamboo/build/viewBuildResults.action?buildKey=WICKET2X-WICKET&buildNumber=10 you see a build of our open source Wicket Project. It is telling me that 85 test are failing, but if you look closely you see that in the TestCase column it only reports the same one over and over again ( Render home page_3) One for every "TestSuite" but that TestSuite is not a suite, it is a TestCase by itself. if you click on one that he says it fails: http://81.17.46.170/bamboo/browse/WICKET2X-WICKET-10/test/wicket.AttributeModifierComponentTest:testRenderHomePage_3 then you see this: Test Class: wicket.AttributeModifierComponentTest Method:testRenderHomePage_3 but AttributeModifierComponentTest doesn't have a testRenderHomePage_3 you can see in the stacktrace: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:<... ...> but was:<......> junit.framework.ComparisonFailure: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:&... ...& but was:&......& at junit.framework.Assert.assertEquals(Assert.java:81) at wicket.util.diff.DiffUtil.validatePage(DiffUtil.java:107) at wicket.WicketTestCase.executeTest(WicketTestCase.java:81) at wicket.markup.html.basic.SimplePageTest.testRenderHomePage_3(SimplePageTest.java:283) Where it really comes from And that s stacktrace is mentioned everywhere. So it seems to report many times the same error on in what he things is a TestSuite. the other strange thing is that when you scrolldown to the fixed cases. You see as far as i see the exact same list (of testsuites). But then it tell is that it is fixed! and if you click on one. You see that it gives the error description. So it is not really fixed...
    via by johan compagner,
  • CTS android.core.vm-tests-tf tests failure
    via by vijay kumar,
  • GitHub comment 27#131693528
    via GitHub by shinsahara
    ,
  • GitHub comment 291#132692593
    via GitHub by renas
    ,
  • JTidy -
    via by Unknown author,
  • Console output filter sometimes damn slow
    via by Unknown author,
    • junit.framework.ComparisonFailure: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:&... ...& but was:&......& at junit.framework.Assert.assertEquals(Assert.java:81) at wicket.util.diff.DiffUtil.validatePage(DiffUtil.java:107) at wicket.WicketTestCase.executeTest(WicketTestCase.java:81) at wicket.markup.html.basic.SimplePageTest.testRenderHomePage_3(SimplePageTest.java:283)

    Users with the same issue

    odd
    3 times, last one,
    osvzs
    4 times, last one,
    bernardpaulus
    2 times, last one,
    musketyr
    2 times, last one,
    Unknown visitor1 times, last one,
    3 more bugmates