Skip to content

Commit

Permalink
Replace usage of hasMessageEndingWith() with hasMessageContaining() i…
Browse files Browse the repository at this point in the history
…n SQL tests
  • Loading branch information
Grzegorz Gierlach authored and gurbuzali committed May 18, 2021
1 parent 32b32b4 commit 48d9e46
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -240,7 +240,7 @@ public void when_conversionFails_then_queryFails() {
);

assertThatThrownBy(() -> sqlService.execute("SELECT * FROM " + name).iterator().hasNext())
.hasMessageEndingWith("Cannot parse VARCHAR value to INTEGER");
.hasMessageContaining("Cannot parse VARCHAR value to INTEGER");
}

@Test
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -235,7 +235,7 @@ public void when_conversionFails_then_queryFails() {
);

assertThatThrownBy(() -> sqlService.execute("SELECT * FROM " + name).iterator().hasNext())
.hasMessageEndingWith("Cannot parse VARCHAR value to INTEGER");
.hasMessageContaining("Cannot parse VARCHAR value to INTEGER");
}

@Test
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -240,7 +240,7 @@ public void when_conversionFails_then_queryFails() {
);

assertThatThrownBy(() -> sqlService.execute("SELECT * FROM " + name).iterator().hasNext())
.hasMessageEndingWith("Cannot parse VARCHAR value to INTEGER");
.hasMessageContaining("Cannot parse VARCHAR value to INTEGER");
}

@Test
Expand Down

0 comments on commit 48d9e46

Please sign in to comment.