[SEDONA-139] Fix wrong argument order in Flink unit tests

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Labels: pull-request-available
• Assignee: Kengo Seki
• Reporter: Kengo Seki
• Created: 08/Aug/22 08:50
• Updated: 22/Oct/22 16:16
• Resolved: 22/Oct/22 16:16

Description

Some unit tests for Flink pass the "expected" and "actual" values to the assert methods in a wrong order. But JUnit shows messages like the following when it fails, so switching the expected and actual values is confusing for developers and should be fixed.

java.lang.AssertionError: expected:<0> but was:<999>

Issue Links

• links to: GitHub Pull Request #660