GODRIVER-2667 [master] Replacing the assert.Soon with the assert.Eventually function #1679
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.