-
Notifications
You must be signed in to change notification settings - Fork 897
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
GODRIVER-2667 Replacing the assert.Soon with the assert.Eventually function #1668
GODRIVER-2667 Replacing the assert.Soon with the assert.Eventually function #1668
Conversation
API Change ReportNo changes found! |
@timothy-kim-mongo Could you update the title of this PR to reflect the changes being made? |
Sounds good, just made the title change along with the other changes you mentioned! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please go through the remaining assert.Eventually tests and apply the changes we made for client_test.go.
f200ffd
to
2aab105
Compare
4561240
to
9ec3cc7
Compare
09a6f43
to
9991b86
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
GODRIVER-2667
Summary
The changes in this pull-request answers the ticket GODRIVER-2667 of replacing the assert.Soon with the assert.Eventually function. It may useful to note that assert.Eventually used in the code does not check initially whether the condition is satisfied meaning it must wait a minimum of the tick duration as according to #1424.
Background & Motivation
In removing the testify dependency and using a vendored subset (GODRIVER-2179), there were a number of calls to assert.Soon that became helpers.AssertSoon (testify has no perfectly analogous function). The motivation was to remove helpers.AssertSoon and refactor all calls to use assert.Eventually.