I am not really looking at replacing hamcrest with something different
(at the moment).
Felix
Am 28.09.19 um 20:56 schrieb Graham Russell:
> If we were looking at replacements I like Google Truth, it's like AssertJ
> but often with better error messages and with both the code reads more
>
If we were looking at replacements I like Google Truth, it's like AssertJ
but often with better error messages and with both the code reads more
naturally than Hamcrest imo e.g.
assertThat(result).isEmpty();
Almost as good as Spock ;)
result.isEmpty()
On Sat, 28 Sep 2019, 17:30 Felix
Mark>From previous experience I would suggest switching to assertj
I had something like that in my mind, however, it seemed too much to switch
to another library for one or two use cases only.
I think behind the lines of enabling Kotlin-based tests, however, that is a
bit different story.
>duplicate classpath entries (https://github.com/gradle/gradle/issues/10393
).
Is it fixed in Gradle 5.6.2?
Should we update then?
Vladimir
Am 28.09.19 um 14:41 schrieb Vladimir Sitnikov:
> I was a bit puzzled with java-hamcrest as well.
>
> It looks like we should exclude it: (see
> https://github.com/hamcrest/JavaHamcrest/issues/183#issuecomment-441154016
> and
>
From previous experience I would suggest switching to assertj. It’s not pulled
in by as many things so you are less likely to get wierd dependency conflicts
and it provides useful output when things don’t match.
Also it’s a fluent api so easy to discover the various matcher methods.
Really
I was a bit puzzled with java-hamcrest as well.
It looks like we should exclude it: (see
https://github.com/hamcrest/JavaHamcrest/issues/183#issuecomment-441154016
and
http://hamcrest.org/JavaHamcrest/distributables#upgrading-from-hamcrest-1x )
Felix, would you please check if adding
Hi all,
when I currently try to run the test TestJSONPostProcessor in eclipse as
a junit test, it complaints about a missing method
org.hamcrest.CoreMatchers.anyOf(...)
I suspect that this is a result of too many hamcrest implementations/the
wrong order of those implementations.
Felix