After updating to assertj-core 3.11.1 I've started seeing:
java.lang.NoSuchMethodError: org.assertj.core.api.Assertions.assertThat(Ljava/lang/String;)Lorg/assertj/core/api/AbstractCharSequenceAssert;
at com.revinate.assertj.json.JsonPathAssert.jsonPathAsString(JsonPathAssert.java:32)
when running my tests.
This seems to have been caused by a signature changes in the fix for assertj/assertj#1269, in particular the change to Assertions.java:
- public static AbstractCharSequenceAssert<?, String> assertThat(String actual) {
+ public static AbstractStringAssert<?> assertThat(String actual) {
I think it's sufficient to just bump the assertj-core dependency to 3.11.1 to fix this, though probably jsonPathAsString should return an AbstractStringAssert<?> rather than AbstractCharSequenceAssert<?, String> to pick up the additional methods that were added in that assertj-core change.
After updating to assertj-core 3.11.1 I've started seeing:
when running my tests.
This seems to have been caused by a signature changes in the fix for assertj/assertj#1269, in particular the change to Assertions.java:
I think it's sufficient to just bump the assertj-core dependency to 3.11.1 to fix this, though probably
jsonPathAsStringshould return anAbstractStringAssert<?>rather thanAbstractCharSequenceAssert<?, String>to pick up the additional methods that were added in that assertj-core change.