Closed defagos closed 4 months ago
Thanks for identifying this!
After looking into this more, this type of issue also applies to toNever
. Lovely.
Thanks for your answer.
As a temporary workaround it is possible to force-unwrap potentially nullable values in related expectations so that mismatches at least do not get unnoticed:
expect(somePotentiallyNilValue!).toAlways(equal(1234))
This is now fixed in Nimble 13.2.1.
Thank you very much for the quick fix, really appreciated!
What did you do?
Consider the following expectation:
You would expect a test failure but the test actually succeeds.
The issue is likely associated with polling since the following expectation fails as expected:
What did you expect to happen?
The expectation in
testExpectNilToAlwaysEqualZero()
above must fail.What actually happened instead?
The expectation in
testExpectNilToAlwaysEqualZero()
above incorrectly succeeds.Environment