You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/01/30 00:25:49 UTC
[jira] Updated: (COLLECTIONS-232) Some tests contain assertEquals
arguments in the incorrect order
[ https://issues.apache.org/jira/browse/COLLECTIONS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell updated COLLECTIONS-232:
--------------------------------------
Fix Version/s: 3.3
> Some tests contain assertEquals arguments in the incorrect order
> ----------------------------------------------------------------
>
> Key: COLLECTIONS-232
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-232
> Project: Commons Collections
> Issue Type: Improvement
> Reporter: Mark Hindess
> Priority: Trivial
> Fix For: 3.3
>
> Attachments: fix.assertEquals.usage.diff
>
>
> A few tests have the expected and actual arguments to assertEquals in the wrong order. This can lead to very confusing failure messages. I'll attach a patch to fix some of the more obvious ones. I've also replaced a couple of assertTrue(blah.size() == 0) with assertEquals(0, blah.size()) since the later typically gives a more helpful failure message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org