Using Awaitility and mocks in the LogGeneratorSourceTest #4746
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.
Description
We had a test failure in
LogGeneratorSourceTest
. This is probably a timing issue as I see it relies on sleeping.See: #3481 (comment)
This PR attempts to avoid this primarily by using Awaitility. This generally allows better reliability as we can increase values to allow for delays when running, especially on GitHub. Additionally, this test was using a spy for the
Buffer
when no logic was needed. So I simplified it a bit to use a normal mock.Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.