Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5644

Tests: Assertion arguments should be passed in the correct order

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 18.0.0.Beta1
    • None
    • None
    • Low

      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 (protocol) Sub-task Closed Minor Boris Unckel (Inactive)
          3.
          		 Assertion arguments should be passed in the correct order (elytron) Sub-task Closed Minor Boris Unckel (Inactive)
          4.
          		 Assertion arguments should be passed in the correct order (controller) Sub-task Closed Minor Boris Unckel (Inactive)
          5.
          		 Assertion arguments should be passed in the correct order (cli) Sub-task Closed Minor Boris Unckel (Inactive)

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

                Created:
                Updated: