PushOneCommit: Fix usage of assertThat

The expected and actual values were passed in the wrong order,
resulting in confusing failure messages.

Change-Id: Ic283261fd5d6afd3c9988c04349785ea9d43da8f

1 files changed, 3 insertions, 3 deletions

diff --git a/gerrit-acceptance-tests/src/test/java/com/google/gerrit/acceptance/PushOneCommit.java b/gerrit-acceptance-tests/src/test/java/com/google/gerrit/acceptance/PushOneCommit.java
index 6cd8031b92..67b6f518c2 100644
--- a/gerrit-acceptance-tests/src/test/java/com/google/gerrit/acceptance/PushOneCommit.java
+++ b/gerrit-acceptance-tests/src/test/java/com/google/gerrit/acceptance/PushOneCommit.java
@@ -282,10 +282,10 @@ public class PushOneCommit {
 
     private void assertStatus(Status expectedStatus, String expectedMessage) {
       RemoteRefUpdate refUpdate = result.getRemoteUpdate(ref);
-      assertThat(expectedStatus)
+      assertThat(refUpdate.getStatus())
         .named(message(refUpdate))
-        .isEqualTo(refUpdate.getStatus());
-      assertThat(expectedMessage).isEqualTo(refUpdate.getMessage());
+        .isEqualTo(expectedStatus);
+      assertThat(refUpdate.getMessage()).isEqualTo(expectedMessage);
     }
 
     public void assertMessage(String expectedMessage) {