Comments on: JUnit 4 error: reference to assertEquals is ambiguous http://www.btaz.com/java/junit-4-error-reference-to-assertequals-is-ambiguous/ Promoting the art of coding Fri, 16 Jul 2010 16:52:59 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Duran http://www.btaz.com/java/junit-4-error-reference-to-assertequals-is-ambiguous/comment-page-1/#comment-209 Duran Tue, 22 Sep 2009 12:29:12 +0000 http://www.btaz.com/?p=67#comment-209 Finally I have found what I think is the problem. With Eclipse, the delivered JUnit 4.5.0 jar doesn't behave as the 4.3 version. If I ecplicitly points to the version I have downloaded from JUint.org (a new 4.7 version, not polluted by Eclipse) it works again :-) Finally I have found what I think is the problem. With Eclipse, the delivered JUnit 4.5.0 jar doesn’t behave as the 4.3 version. If I ecplicitly points to the version I have downloaded from JUint.org (a new 4.7 version, not polluted by Eclipse) it works again :-)

]]> By: Duran http://www.btaz.com/java/junit-4-error-reference-to-assertequals-is-ambiguous/comment-page-1/#comment-208 Duran Tue, 22 Sep 2009 11:33:03 +0000 http://www.btaz.com/?p=67#comment-208 I have a similar problem but I haven't come up with a solution yet. This code doesn't behave as expected with JUnit4_4.5.0: assertEquals("Always fail: ", 0L, 0L); assertEquals("Always OK: ", Long.valueOf(0L), Long.valueOf(0L)); I haven't figured out why, and haven't come up with an acceptable solution either since similar code exists in numerous test cases. I have a similar problem but I haven’t come up with a solution yet. This code doesn’t behave as expected with JUnit4_4.5.0:

assertEquals(“Always fail: “, 0L, 0L);
assertEquals(“Always OK: “, Long.valueOf(0L), Long.valueOf(0L));

I haven’t figured out why, and haven’t come up with an acceptable solution either since similar code exists in numerous test cases.

]]> By: Virginia http://www.btaz.com/java/junit-4-error-reference-to-assertequals-is-ambiguous/comment-page-1/#comment-207 Virginia Wed, 09 Sep 2009 18:57:57 +0000 http://www.btaz.com/?p=67#comment-207 Thank you, thank you. I encountered this problem when I upgraded my JUnit4_4.3.1 to JUnit4_4.5.0. Using the older version, I was comparing "double" to "Double" and the assertEquals(Object, Object) method worked fine. After the upgrade, I received the error you describe above. Your post was very helpful. ~ Va Thank you, thank you. I encountered this problem when I upgraded my JUnit4_4.3.1 to JUnit4_4.5.0. Using the older version, I was comparing “double” to “Double” and the assertEquals(Object, Object) method worked fine. After the upgrade, I received the error you describe above. Your post was very helpful.

~ Va

]]>