commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Created: (COLLECTIONS-232) Some tests contain assertEquals arguments in the incorrect order
Date Mon, 30 Oct 2006 11:49:19 GMT
Some tests contain assertEquals arguments in the incorrect order
----------------------------------------------------------------

                 Key: COLLECTIONS-232
                 URL: http://issues.apache.org/jira/browse/COLLECTIONS-232
             Project: Commons Collections
          Issue Type: Improvement
            Reporter: Mark Hindess
            Priority: Trivial
         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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message