QA/Firefox3.5/TestPlan/Element Traversal: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3.5‎ | TestPlan
Jump to navigation Jump to search
No edit summary
 
(8 intermediate revisions by one other user not shown)
Line 5: Line 5:
= Overview =
= Overview =


  Provide an abstract of the feature and the test strategy.
Element Traversal is a method for writing javascript element traversal using higher performance instead of other methods of traversing through elements.  This is well outlined and straightforward.
  Are there particular challenges with testing this feature?


= Test Strategy =
= Test Strategy =


  List major areas of test coverage
As this is a set of APIs, we will just test (with normal, boundary, and error conditions) each of these APIs:
  List areas that will NOT be covered (by developer, third party, etc.)
*firstElementChild
  Describe how testcases will be created (litmus, mochitests, reftests, gristmill, etc..)
*lastElementChild
*previousElementSibling
*nextElementSibling
*childElementCount
 
Since these are API's we will use mochitests to develop a set of automated test cases.


= Schedule Scoping =
= Schedule Scoping =
 
 
  Estimate amount of time it will take to complete feature
this was landed in late august and will be run with automated test cases once developed for 3.1b1.
  (Consider nightly builds, security reviews, bugs turnaround time)


= References =
= References =


  Include notes, links, specs, relevant bugs
*[[https://bugzilla.mozilla.org/show_bug.cgi?id=447917 bug 447917]]
*[[http://dev.w3.org/2006/webapi/ElementTraversal/publish/ElementTraversal.html W3 spec]]

Latest revision as of 03:48, 24 March 2009

« QA/Firefox3.1/TestPlan

Feature Element Traversal Test Plan

Overview

Element Traversal is a method for writing javascript element traversal using higher performance instead of other methods of traversing through elements. This is well outlined and straightforward.

Test Strategy

As this is a set of APIs, we will just test (with normal, boundary, and error conditions) each of these APIs:

  • firstElementChild
  • lastElementChild
  • previousElementSibling
  • nextElementSibling
  • childElementCount

Since these are API's we will use mochitests to develop a set of automated test cases.

Schedule Scoping

this was landed in late august and will be run with automated test cases once developed for 3.1b1.

References