Adds a functional testsuite based on the Karma framework. #4281
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nable/disable specific tests via commandline
eirikbjornr
pushed a commit
to bbc/dash.js
that referenced
this pull request
Feb 14, 2024
…try-Forum#4281) * Adds a functional testsuite based on the Karma framework.
This was referenced Aug 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a functional testsuite based on the Karma framework. I have been using this for automated regression tests next to our existing functional testsuite that is executed via CI/CD.
The Karma based testsuite includes additional tests such as checking for redundant segment downloads and gap handling. For that reason, static MPDs have been created that simulate situations such as gaps in the timeline.
As the Karma testrunner is deprecated, future work will focus on using WebTestrunner instead. Moreover, the configuration of the tests should be improved. In addition, new testcases will be added to cover scenarios such as limiting the bitrate by portal size and defining a min/max bitrate.
All these additions can be made as part of the work on version 5.x.
As I was using the testuite internally for checking new features and upcoming releases, I am adding this already in version 4.7.2.