Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15526

Tests: Assertion arguments should be passed in the correct order

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 25.0.0.Final
    • None
    • None

      Some tests have expected and actual parameters swapped. This leads to wrong AssertionError messages. Refers to RSPEC-3415

      Fix: Swap these 2 arguments so they are in the correct order: expected value, actual value.

          1.
          		 Assertion arguments should be passed in the correct order (testsuite) Sub-task Closed Minor Boris Unckel (Inactive)
          2.
          		 Assertion arguments should be passed in the correct order (mail) Sub-task Closed Minor Boris Unckel (Inactive)
          3.
          		 Assertion arguments should be passed in the correct order (jpa) Sub-task Closed Minor Boris Unckel (Inactive)
          4.
          		 Assertion arguments should be passed in the correct order (jdr) Sub-task Closed Minor Boris Unckel (Inactive)
          5.
          		 Assertion arguments should be passed in the correct order (connector) Sub-task Closed Minor Boris Unckel (Inactive)

              xf01213 Boris Unckel (Inactive)
              xf01213 Boris Unckel (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: