New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write test cases that cover the use of the API #1
Comments
There is an open bounty to complete this task. https://www.bountysource.com/issues/26763180-write-test-cases-that-cover-the-use-of-the-api |
Hello @gajus , I am interested in solving this issue. Can you let me know where to get started from? |
What browser targets would you like to see the tests pass in? Will the usual stable of latest Chrome, Safari, Firefox, IE11, and Edge be sufficient? |
@H3Chief PhantomJS (ie. Chrome) would be enough. |
great. Thanks! |
Does still need to get done? |
@eimfach Absolutely. |
Resolves gajus#1
Resolves gajus#1
Resolves gajus#1
Resolves gajus#1
Resolves gajus#1
Resolves gajus#1
Resolves gajus#1
The existing tests were testing |
react-youtube-player
has a simple API:./example/
demonstrates how to control areact-youtube-player
component using property values that are controlled using user input.However, testing how properties affect YouTube player state is not as straightforward. Tests need to account for things such as state change when video stops playing. How state of the YouTube player affects how properties are interpreted, etc.
The nature of the component requires that it is tested using a real browser (using a test runner such as Karma).
The scope of this issue is to write a test scope and implement it.
The text was updated successfully, but these errors were encountered: