From: SourceForge.net <no...@so...> - 2009-04-17 19:41:26
|
Bugs item #1675905, was opened at 2007-03-07 11:55 Message generated for change (Comment added) made by dsaff You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1675905&group_id=15278 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Fixed Priority: 9 Private: No Submitted By: Johnathan Conley (jconley) Assigned to: Nobody/Anonymous (nobody) Summary: assertEquals array comparison doesnt handle nulls Initial Comment: Assert.assertEquals(new Object[]{null},new Object[]{null}); throws a NullPointerException @ 133 Assert.assertEquals(null,null) is successful java.util.Arrays.equals(new Object[]{null},new Object[]{null}) returns true Assert.assertEquals(Object[],Object[]) should support null checking. ---------------------------------------------------------------------- >Comment By: David Saff (dsaff) Date: 2009-04-17 15:41 Message: Fixed in 4.6 ---------------------------------------------------------------------- Comment By: Santiago L. Valdarrama (svpino) Date: 2007-03-20 13:45 Message: Logged In: YES user_id=818352 Originator: NO This bug not longer appear with version 4.3. This was already fixed. Please, update to the latest JUnit version. Also, remember to use the assertArrayEquals method to carry out array comparisons due that the use of arrayEquals to compare arrays is deprecated in version 4.3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1675905&group_id=15278 |