Commons Collections
  1. Commons Collections
  2. COLLECTIONS-232

Some tests contain assertEquals arguments in the incorrect order

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0
    • Component/s: None
    • Labels:
      None

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Mark Hindess
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development