QA/Firefox3.5/Video And Audio TestPlan: Difference between revisions

Jump to navigation Jump to search

QA/Firefox3.5/Video And Audio TestPlan (view source)

Revision as of 02:21, 21 August 2008

43 bytes added ,  21 August 2008
→‎What MUST be Tested
No edit summary
Line 19: Line 19:
|-
|-
| class="header"|Test Idea
| class="header"|Test Idea
|-
| class="header"|Status
|-
|-
| Analyze the unit tests to ensure they test all default values of the attributes
| Analyze the unit tests to ensure they test all default values of the attributes
| ?
|-
|-
|}
| Test autoplay toggle to determine if the controls appear and that the controls appear properly
* attempt to ensure that you can use play and pause to cause video to get to a certain state and then figure out if it worked by comparing to a static image of the video at that time.
| ?
* use the above to test autoplay as well and whether or not the controls appear and that the controls appear properly
|-
* can we style the page differently based on video states of play or pause or stop?  
| Can we style the page differently based on video states of play or pause or stop?
* can we change the controls to something of our own creation
| ?
* can we use video to animate objects and then insert them into a background of  frame??
|-
* what tests should be done using the various backend frameworks?  How do you test that theora works on all platforms etc
| Change the controls to something of our own creation
* Test mimetypes, and test that we handle them by default when they are dtected, if we want to do that
| ?
* test that we can automate interacting with the video by doing various JS things and then checking the states and attributes of the video both the constants and the actual attribute states.
|-
* Try to test if we can unsync the video and audio and hopefully that will not be possible.
| Use Video to animate objects and place as a background to content
* Try changing the framerate from the normal speed
| ?
* Try giving it a bad mime type for the provided file (when the file is something we support)
|-
* Try the above by giving a good mime type when the file isn't something we support
| Test mimetypes, and test that we handle them by default when they are detected, if we want to do that
* test that events are fired when a video finishes, starts and is paused and is resumed
| ?
* ensure proper observers catch those events and can do interesting things with them when they catch them.
|-
* ensure videos obey their space directives for the content they are embedded within
| Try to test if we can unsync the video and audio
| ?
|-
| Change the framerate, ensure video playback changes
| ?
|-
| Give an invalid mime type for the provided file (when the file is a codec we support
| ?
|-
| Give a valid mime type when the file isn't a codec we support
| ?
|-
| Give an incorrect,but supported, mime type for a file that is a supported codec
| ?
|-
| Test for any relevant events - video stop/start/resume/reset etc
| ?
|-
| ensure videos obey their space directives for the content they are embedded within
** make video bigger than space (in div, in table, in frame/span)
** make video bigger than space (in div, in table, in frame/span)
** make video smaller than space
** make video smaller than space
** make video smaller than normal size
** make video smaller than normal size
** make video much larger than normal size -can you size video outside of content?
** make video much larger than normal size -can you size video outside of content
| ?
|-
|}
*
== NEEDED for Automated testing ==
* Ensure that you can use play and pause to cause video to get to a certain state and then figure out if it worked by comparing to a static image of the video at that time.
* what tests should be done using the various backend frameworks?  How do you test that theora works on all platforms etc
* Ensure that we can automate interacting with the video by doing various JS things and then checking the states and attributes of the video both the constants and the actual attribute states. (in order to play to a certain time, for example)
 
*
* * ?
** have the area surrounding a video be determined by an inhereited CSS string that is changed after the page loads and autoplay begins such that the new size is too small for the video
** have the area surrounding a video be determined by an inhereited CSS string that is changed after the page loads and autoplay begins such that the new size is too small for the video
** do above case and just keep the same size, and ensure the page changes and reflow happens but video doesn't restart.
** do above case and just keep the same size, and ensure the page changes and reflow happens but video doesn't restart.
Ctalbert
Confirmed users
3,816

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/105107"

Navigation menu