QA/Firefox3/TestPlan/Places: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3‎ | TestPlan
Jump to navigation Jump to search
Line 3: Line 3:
= Overview =
= Overview =


This Testplan will focus on the rework of Bookmarks, History and to some extent RSS as they are transformed into the Places component for Firefox 3.
This Testplan will focus on the rework of Bookmarks and History as they are transformed into the Places component for Firefox 3. From the [http://wiki.mozilla.org/Places:Fx3FeaturePlan Places feature plan]:


1)
The primary objectives of this project are to:
 
    * Improve access to History and Bookmarks
    * Make it easier for people to Bookmark pages
 
Secondary objectives include:
 
    * Consolidating user data formats
    * Providing a platform for using interesting per-URL metadata
    * Improving the capabilities of Live Bookmarks
    * Providing a solid architecture for bookmark sync and remote storage


= Scope of planned testing =
= Scope of planned testing =

Revision as of 19:12, 26 July 2007

Linked from 3.0 Test Plan

Overview

This Testplan will focus on the rework of Bookmarks and History as they are transformed into the Places component for Firefox 3. From the Places feature plan:

The primary objectives of this project are to:

   * Improve access to History and Bookmarks
   * Make it easier for people to Bookmark pages 

Secondary objectives include:

   * Consolidating user data formats
   * Providing a platform for using interesting per-URL metadata
   * Improving the capabilities of Live Bookmarks
   * Providing a solid architecture for bookmark sync and remote storage

Scope of planned testing

(What do you plan to test? What is covered by Developer testing? What is not practical to test?)

Coverage includes:

  • Priority one feature test cases.

Platform and Configurations

( Describe any particular OS platform, environmental configurations or FireFox configuration considerations)

Major Test Areas

(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

The milestone schedule continues to be in flux, but this is how it roughly lays out for the next couple of milestones: (using M series where M1 was A1.. M8 should be B1)

  • M5-M6: backend of bookmarks and history landed
  • M7: performance tweaks and push to parity with 2.0 with protection against data loss
  • M8: Places front end to land

References