Uploaded image for project: 'Groovy'
  1. Groovy
  2. GROOVY-1376

rename (or alias) assertArrayEquals to assertEquals

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Won't Fix
    • None
    • 1.1-beta-1
    • None
    • None

    Description

      JUnit 4 supports:

      /** Asserts that two object arrays are equal. (new in JUnit 4.x) */
      static void assertEquals(java.lang.Object[] expecteds, java.lang.Object[] actuals)

      GroovyTestCase supports:

      /** Asserts that the arrays are equivalent and contain the same values */
      protected void assertArrayEquals(Object[] expected, Object[] value) {

      Is it worthwhile dropping the 'Array' part of the Groovy method
      so that a future transition would be more seamless and users
      switching between the two will be more at home?

      Attachments

        Activity

          People

            codevise Dierk König
            paulk Paul King
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: