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

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

Revision as of 01:59, 21 August 2008

5,315 bytes added , 21 August 2008

no edit summary

Ctalbert

Confirmed users

3,816

edits

@@ Line 4: / Line 4: @@
 * Something to include in Litmus/Gristmill: {{bug|448630}}
-Feature <abc> Test Plan
+;<Video> and <Audio> Test Plan
 = Overview =
+Video and audio HTML 5 suport has landed on trunk for the 3.1 release.  It implements the [http://www.whatwg.org/specs/web-apps/current-work/#video WHATWG specification] for these tags.  So, far, only the ogg-theora codec support has landed.  However, the tests below must be tested with each codec supported unless otherwise noted.
-(Provide an abstract of the feature and the test strategy.  Are there particular challenges with testing this feature?)
+= Test Strategy =
+I am breaking these into three basic blocks of testing:
+* What must be done to ensure good coverage of the feature
+* What should be done to test around the area of the feature and its interoperability with other HTML content
+* What might be done in a wonderful perfect world i.e. less important stuff that might get timeboxed)
-= Scope of planned testing =
+== What MUST be Tested ==
+{| class="standard-table"
+|-
+| class="header"|Test Idea
+|-
+| Analyze the unit tests to ensure they test all default values of the attributes
+|-
+|}
+* 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 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
+* 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.
+* 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 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
+** make video bigger than space (in div, in table, in frame/span)
+** make video smaller than space
+** make video smaller than normal size
+** make video much larger than normal size -can you size video outside of content?
+** 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.
+** include a data URL in the video
+** use a javascript source file in the src directive and see what happens (or a data URL encoded javascript alert that claims to be a video based on its mimetype, maybe even begins with OGG)
+** Litmus or gristmill tests using the controls and verifying that the interaction works properly?
+** automatically remove the controls after a moment of playing the video via javascript.
+** create a shape or a object that sits over a video
+** use javascript to turn the volume all the way up on the vdeo and blare it at the user. (shoudl we allow that -- I'm htinking about ads here that might exploit that)
+** see if yo can find a way to allow video to block the user from the chrome controls by positioning the video over it or in a flotaed frame.
+** Can you launch code from a video by doing soehting evil inside the video stream?
+** do all the interactivity tests with javascirpt with just audio too.
+** audio - test turning controls on and thensizing the frame area such that there is no location for the controls to exist in.
+** use all the ideas for video with audio especially the ones involved in embedding audio into the web page.
+* test what happens if you have video with an embedded sound clip in it and you specify an audio clip and the javascript plays both at the same time, pehraps the audio doesn't match the video.
+* test that playback of both formats stops on closing the tab
+* test that reload of page causes both to restart
+* test that back/forward work as expected (video back to beginning)
+* session restore should restore the original state of the video, not the mid-point where it was when you crashed. (I think).
+* test cross site video reference - should probably be disallowed
+** or should it?  is there any harm in that? pehraps you want to rembed someone else's hosted video?
+* test attaching javascript event listeners to the controls themselves.  They should not really be able to take over a control, for example, you could move the control every time the mouse hovered over it making it impossible to stop the video
+* test playing a large video that must be buffered.  Ensure the buffering works properly
+* Ensure the poster setting works properly, that seek offsets can be used well.
+* Ensure that save page as funcitonality works and downloads the video/audio as well as the HTML
+* what happens if you put video inside content editable? can you drag the video around?
+** what about inside of SVG?
+** test dragging video to a new window and that it doesn't stop playing (via tab drag)
+** test that it continues to play (or doesn't play - current behavior is to continue) when you switch to a new tab.
+* play with the access controls and see if you can force hieght to change based on a wacked out width setting and telling it to maintain aspect ratio - it is currently fixing height to a value
+* Test accessibility of the video/audio controls
-(What do you plan to test?  What is covered by Developer testing?  What is not practical to test?)
+= Discovered Bugs =
+* chaning width crops controls and can no longer properly control the video any more
+** should there be a context click menu for video control?
-= Platform and Configurations =
-( Describe any particular OS platform, environmental configurations or FireFox configuration considerations)
+= Schedule Scoping =
-= Major Test Areas =
+  Estimate amount of time it will take to complete feature
+  (Consider nightly builds, security reviews, bugs turnaround time)
-(describe major test areas of the feature and major test cases.  Once the plan is done, these major test cases can be fleshed out into litmus or automated test cases)
-= Schedule/milestones =
-( Provide some breakdown of the major areas of the feature, how long it will take to develop or run the tests, and an approximate time this will be done.
 = References =
-(List useful links to the bug containing design info, feature meeting notes, wiki info, standards info, litmus group or subgroup, etc)
+  Include notes, links, specs, relevant bugs