<@UVAR0DXP0> pulling out from ^ Have a failing te...
# kotest-contributors
a
@Emil Kantis pulling out from ^ Have a failing test case:
Copy code
ZonedDateTime.now(utcTimeZone) shouldBe
   ZonedDateTime.now(utcTimeZone).plusNanos(1) plusOrMinus 1.seconds
Looking at a fix now - I think it might be related to the precision?
i.e. the
storageUnit
inside of kotlins
Duration
implementation
Never mind - it's related to the bracket calls All the other test cases wrap the
other plusOrMinus
in parenthesis If you don't wrap them, it just assumes it's a
shouldBe
and compares the two zonedDateTimes exactly A breakpoint in
ZonedDateTimeToleranceMatcher
is never even reached