junit.framework.ComparisonFailure: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:&... ...& but was:&......&

Atlassian JIRA | johan compagner | 10 years ago
  1. 0

    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...

    Atlassian JIRA | 10 years ago | johan compagner
    junit.framework.ComparisonFailure: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:&... ...& but was:&......&
  2. 0

    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...

    Atlassian JIRA | 10 years ago | johan compagner
    junit.framework.ComparisonFailure: wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:&... ...& but was:&......&
  3. 0

    CTS android.core.vm-tests-tf tests failure

    Google Groups | 4 years ago | vijay kumar
    junit.framework.ComparisonFailure: ANDROID_DATA=/data/local/tmp/vm-tests dalvikvm -Xint:portable -Xmx512M -Xss32K -Djava.io.tmpdir=/data/local/tm p/vm-tests -classpath /data/local/tmp/vm-tests/dot/junit/dexcore.jar:/data/local/tmp/vm-tests/dot/junit/opcodes/add_float_2addr/Main_testB9.jar:/ data/local/tmp/vm-tests/dot/junit/opcodes/add_float_2addr/d/T_add_float_2addr_1.jar dot.junit.opcodes.add_float_2addr.Main_testB9 expected:<[]> b ut was:<[Segmentation fault ]>
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    JUnit - How to aggregate differences instead of asserting just the first difference ?

    Google Groups | 1 decade ago | tomjbr....@bloglines.com
    junit.framework.ComparisonFailure: my message expected:<...> but was:<...d>
  6. 0

    GitHub comment 27#131693528

    GitHub | 1 year ago | shinsahara
    junit.framework.ComparisonFailure: PO #3 expected:<... bind1:(int * int), [j:int, i]:int & (arg1 = bind1...> but was:<... bind1:(int * int), [i:int, j]:int & (arg1 = bind1...>

  1. marcelojaf 24 times, last 6 months ago
2 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. junit.framework.ComparisonFailure

    wicket/markup/html/basic/SimplePageExpectedResult_3.html expected:&... ...& but was:&......&

    at junit.framework.Assert.assertEquals()
  2. JUnit
    Assert.assertEquals
    1. junit.framework.Assert.assertEquals(Assert.java:81)
    1 frame
  3. wicket.util.diff
    DiffUtil.validatePage
    1. wicket.util.diff.DiffUtil.validatePage(DiffUtil.java:107)
    1 frame
  4. wicket
    WicketTestCase.executeTest
    1. wicket.WicketTestCase.executeTest(WicketTestCase.java:81)
    1 frame
  5. wicket.markup.html
    SimplePageTest.testRenderHomePage_3
    1. wicket.markup.html.basic.SimplePageTest.testRenderHomePage_3(SimplePageTest.java:283)
    1 frame