Reordering of assert parameters partially broken

[nkiesel]

The reordering of assert parameters should only happen if the assertion has a description parameter:

org.junit.Assert.assertEquals("Greeting broken", "Hello, world!", suspect.generateGreeting()); is correctly converted to
org.junit.jupiter.api.Assertions.assertEquals("Hello, world!", suspect.generateGreeting(), "Greeting broken");

However, parameters to asserts w/o the description parameter should be kept unchanged. Right now, org.junit.Assert.assertEquals("Hello, world!", suspect.generateGreeting()); is incorrectly converted to
org.junit.jupiter.api.Assertions.assertEquals(suspect.generateGreeting(), "Hello, world!"); (ie. expected and actual are swapped).

Looks to me the fix would be to add a "check number of parameters" test to

    if ("assertTrue".equals(methodName) || "assertFalse".equals(methodName) || "assertNotNull".equals(methodName) ||
                    "assertArrayEquals".equals(methodName) || "assertEquals".equals(methodName) ||
                    "assertNotEquals".equals(methodName)) {
              pushFirstAsLastArgument(methodCallExpr, "Assertions");
     }