Hi,
> The unfortunate thing is none of the objects tested with Matchers register as
> covered assertThat(result, hasProperty("x", equalTo("xValue")),
>
> whereas making an assertion does assertEquals("xValue", result.getX()) does.
hm, maybe Jacoco gets confused because some basic Hamcrest matchers are
contained not only in the Hamcrest JAR but are also part of the JUnit
JAR, i.e., they are on the classpath twice.
Can you check that this also occurs with matchers not part of your JUnit
JAR?
Hope this helps.
Andreas
--
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
--
You received this message because you are subscribed to the Google Groups
"JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
