fix: test failure due to message start appending entity (#609)

* fix:test failure due to message start appending entity * format fix
googleapis · Oct 19, 2020 · 63b1762 · 63b1762
1 parent 99c6a9d
commit 63b1762
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/...t/java/com/google/cloud/bigquery/storage/v1alpha2/it/ITBigQueryWriteManualClientTest.java b/...t/java/com/google/cloud/bigquery/storage/v1alpha2/it/ITBigQueryWriteManualClientTest.java
@@ -16,6 +16,7 @@
 
 package com.google.cloud.bigquery.storage.v1alpha2.it;
 
+import static com.google.common.truth.Truth.assertThat;
 import static org.junit.Assert.assertEquals;
 import static org.junit.Assert.assertFalse;
 import static org.junit.Assert.assertTrue;
@@ -517,9 +518,8 @@ public void testStreamError() throws IOException, InterruptedException, Executio
         response2.get().getOffset();
         Assert.fail("Should fail");
       } catch (ExecutionException e) {
-        assertEquals(
-            "OUT_OF_RANGE: The offset is beyond stream, expected offset 1, received 100",
-            e.getCause().getMessage());
+        assertThat(e.getCause().getMessage())
+            .contains("OUT_OF_RANGE: The offset is beyond stream, expected offset 1, received 100");
       }
       // We can keep sending requests on the same stream.
       ApiFuture<AppendRowsResponse> response3 =