[COLLECTIONS-232] Some tests contain assertEquals arguments in the incorrect order

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 4.0
• Assignee: Unassigned
• Reporter: Mark Hindess
• Created: 30/Oct/06 11:48
• Updated: 27/Apr/13 21:47
• Resolved: 03/May/07 19:55

Description

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.