Make tests in test_play_for.cpp more deterministic and run faster #17
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.
@agalbachicar It was to tedious making a lot of comments and propose changes on code review.
I prepared all proposed changes on separate branch.
I had a concern that after last changes tests still rely on the assumption that subscription waiting for
N
messages however in tests valid expectation that it will be published less thenN
messages or nothing. And waiting time reduced to the 1 second.Such assumption tend to make tests false negative or flaky due to the possible delays on CI.
Please consider to merge my changes on your branch as result of the code review.
What has been done:
play_for()
flow when replaying in loop or multipletimes from the same player instance.
Signed-off-by: Michael Orlov michael.orlov@apex.ai