-
-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expect(nil).toAlways(equal(0))
incorrectly succeeds
#1120
Comments
Thanks for identifying this! |
After looking into this more, this type of issue also applies to |
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! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: