From: SourceForge.net <no...@so...> - 2007-05-08 22:56:10
|
Bugs item #1715326, was opened at 2007-05-08 17:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&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: framework Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrew Dick (malekith) Assigned to: Nobody/Anonymous (nobody) Summary: assertEquals does not compare java.math.BigDecimal properly Initial Comment: When using assertEquals to compare BigDecimals, it appears to only compare the integer portion of the BigDecimal: For example, the following assert will pass when I would expect it to fail: assertEquals("Testing non-equal BigDecimals.", new BigDecimal("123.4"), new BigDecimal("123.0")); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&group_id=15278 |
From: SourceForge.net <no...@so...> - 2007-07-03 03:52:19
|
Bugs item #1715326, was opened at 2007-05-08 18:56 Message generated for change (Comment added) made by anshnd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&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: framework Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrew Dick (malekith) Assigned to: Nobody/Anonymous (nobody) Summary: assertEquals does not compare java.math.BigDecimal properly Initial Comment: When using assertEquals to compare BigDecimals, it appears to only compare the integer portion of the BigDecimal: For example, the following assert will pass when I would expect it to fail: assertEquals("Testing non-equal BigDecimals.", new BigDecimal("123.4"), new BigDecimal("123.0")); ---------------------------------------------------------------------- Comment By: Anli Shundi (anshnd) Date: 2007-07-02 23:52 Message: Logged In: YES user_id=180255 Originator: NO You're doing something wrong -- if you're right it would indicate a problem in Java anyway... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&group_id=15278 |
From: SourceForge.net <no...@so...> - 2007-07-03 18:08:36
|
Bugs item #1715326, was opened at 2007-05-08 18:56 Message generated for change (Settings changed) made by dsaff You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&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: framework Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Andrew Dick (malekith) Assigned to: Nobody/Anonymous (nobody) Summary: assertEquals does not compare java.math.BigDecimal properly Initial Comment: When using assertEquals to compare BigDecimals, it appears to only compare the integer portion of the BigDecimal: For example, the following assert will pass when I would expect it to fail: assertEquals("Testing non-equal BigDecimals.", new BigDecimal("123.4"), new BigDecimal("123.0")); ---------------------------------------------------------------------- >Comment By: David Saff (dsaff) Date: 2007-07-03 14:08 Message: Logged In: YES user_id=325156 Originator: NO The original poster was correct. This has been fixed in the latest check-in, which will go into JUnit 4.4 ---------------------------------------------------------------------- Comment By: Anli Shundi (anshnd) Date: 2007-07-02 23:52 Message: Logged In: YES user_id=180255 Originator: NO You're doing something wrong -- if you're right it would indicate a problem in Java anyway... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&group_id=15278 |
From: SourceForge.net <no...@so...> - 2007-07-03 20:31:11
|
Bugs item #1715326, was opened at 2007-05-08 18:56 Message generated for change (Comment added) made by anshnd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&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: framework Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Andrew Dick (malekith) Assigned to: Nobody/Anonymous (nobody) Summary: assertEquals does not compare java.math.BigDecimal properly Initial Comment: When using assertEquals to compare BigDecimals, it appears to only compare the integer portion of the BigDecimal: For example, the following assert will pass when I would expect it to fail: assertEquals("Testing non-equal BigDecimals.", new BigDecimal("123.4"), new BigDecimal("123.0")); ---------------------------------------------------------------------- Comment By: Anli Shundi (anshnd) Date: 2007-07-03 16:31 Message: Logged In: YES user_id=180255 Originator: NO Indeed -- it turns out Eclipse was using JUnit 4.1... When will the new build be published? ---------------------------------------------------------------------- Comment By: David Saff (dsaff) Date: 2007-07-03 14:08 Message: Logged In: YES user_id=325156 Originator: NO The original poster was correct. This has been fixed in the latest check-in, which will go into JUnit 4.4 ---------------------------------------------------------------------- Comment By: Anli Shundi (anshnd) Date: 2007-07-02 23:52 Message: Logged In: YES user_id=180255 Originator: NO You're doing something wrong -- if you're right it would indicate a problem in Java anyway... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=115278&aid=1715326&group_id=15278 |