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.
Pull request
Description
This PR aims to provide some tools to be able to easily test a player.
Changes made
PlayerIdlingResource
to wait until the player under test reaches a specific stateExoPlayerRule
that setup the playerTestSimpleProgressTrackerState
to show how to use these two new classesWarning
This PR is in draft because for the moment the player under test remains in the buffering state. Once this is fixed (and probably
TestSimpleProgressTrackerState
too),PlayerIdlingResource
andExoPlayerRule
can be moved topillarbox-player-testutils
.Note
These new classes are only necessary when we need to directly access the player. Otherwise,
ExoPlayerTestRunner
frommedia3-test-utils
is probably a better solution, as it already takes care of setting up the player, handling state change, and providing various assertions.ExoPlayerTest
shows various examples of how to use that class (look forExoPlayerTestRunner.Builder
).Checklist
main
branch.