QA/Firefox3.5/SearchWidget TestPlan: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3.5
Jump to navigation Jump to search
mNo edit summary
Line 4: Line 4:


= Overview =
= Overview =
With the creation of the search textbox widget a reusable widget with the same look and behavior is provided and can be used across the whole application.


  Provide an abstract of the feature and the test strategy.
First we have to check the correct implementation of the search widget, further find all the places where it is used and at least find some potential outstanding improvements.
  Are there particular challenges with testing this feature?
 
Base Implementation:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=388811 388811] Provide a search textbox widget
* [https://bugzilla.mozilla.org/show_bug.cgi?id=449045 449045] Drop support for type="timed" for textboxes (Target: Mozilla2.0)
 
UI replacements:
* [https://bugzilla.mozilla.org/buglist.cgi?bug_id=395642%2C+405892%2C+449317%2C+449375%2C+449465%2C+449661%2C+449664%2C+449669%2C+452001 Buglist] (Firefox)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=451852 451852] (Thunderbird)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=449690 449690] (SeaMonkey)
 
Improvements:
* None filed yet


= Test Strategy =
= Test Strategy =

Revision as of 23:05, 24 August 2008

« QA/Firefox3.1/TestPlan

Feature "Search Textbox Widget" Test Plan

Overview

With the creation of the search textbox widget a reusable widget with the same look and behavior is provided and can be used across the whole application.

First we have to check the correct implementation of the search widget, further find all the places where it is used and at least find some potential outstanding improvements.

Base Implementation:

  • 388811 Provide a search textbox widget
  • 449045 Drop support for type="timed" for textboxes (Target: Mozilla2.0)

UI replacements:

Improvements:

  • None filed yet

Test Strategy

 List major areas of test coverage
 List areas that will NOT be covered (by developer, third party, etc.)
 Describe how testcases will be created (litmus, mochitests, reftests, gristmill, etc..)

Schedule Scoping

 Estimate amount of time it will take to complete feature
 (Consider nightly builds, security reviews, bugs turnaround time)

References

 Include notes, links, specs, relevant bugs