QA/Firefox3/TestPlan/Mac Integration: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3‎ | TestPlan
Jump to navigation Jump to search
No edit summary
Line 77: Line 77:
*Finding Updates
*Finding Updates
*Add-ons Compatibility checks
*Add-ons Compatibility checks
===Performance Testing===
*Tab Switching
*Bookmark folders in the toolbar with a dozen bookmarks in them are incredibly slow to populate. I think Places is hitting us hard there. Specifically on the bookmark icons in those folders, since we're storing those in the database now.
*History will likely have similar issues


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

Revision as of 20:48, 9 July 2007

Version 1.0 created 07-06-07, this is a Work In Progress

Scope of planned testing

The primary goal of this QA test plan is Mac testing of the Firefox 3 release. With the impending release of Leopard in October, some of the testing focus will concentrate on the new OS integration pieces that could possibly be problematic. Primary emphasis will be on the following:

  • Form controls
  • Focus issues
  • Fonts
  • Context menu
  • Cocoa widgets
  • Drag and drop
  • Performance testing

For Leopard

  • Default Browser
  • Default Download Location
  • Full Keyboard Access
  • Other OS Integration Pieces

1. Will Test

Installation Scenarios

  • Installing and Uninstalling Firefox on Mac
  • Installing in the Default Directory
  • Installing on the Desktop in a folder
  • Uninstalling Firefox
  • Installing Firefox with Multiple Users

Default Application Scenarios

  • Setting Firefox as the Default Application
  • Resetting Safari as the default, then setting Firefox as the default
  • Setting FF as the default from the install
  • Setting FF as the default after a software update
  • Setting FF as the default before a software update

Software Update

  • Updating as a Admin user
  • Updating as a Standard User
  • Confiming Major/Minor Update functionality

Support of RSS Feed Reader Client Side Applications

Native Form Controls

  • We will use smokey's Camino list as a starting point to formulate some Litmus test cases for this area.

Downloading

  • Honoring whatever is set as the default download location

Fonts

  • Explore fonts in text areas

Context Menus

  • Full exploration of context menus

GROWL Integration

  • Registering GROWL

Full Keyboard Access

  • Perform Tests with FKA enabled as well as disabled

Plugins

  • Support of New Plugin model
  • JEP
  • Flash
  • Shockwave
  • Quicktime
  • Windows Media Player (Flip for Mac)
  • PDFs
  • RealPlayer
  • Viewpoint

Add-ons

  • Installing
  • Uninstalling
  • Enabling and Disabling
  • Finding Updates
  • Add-ons Compatibility checks

Performance Testing

  • Tab Switching
  • Bookmark folders in the toolbar with a dozen bookmarks in them are incredibly slow to populate. I think Places is hitting us hard there. Specifically on the bookmark icons in those folders, since we're storing those in the database now.
  • History will likely have similar issues

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

  • Testing will cover the areas below. Exceptions are noted under the "Will not test" section

Platform and Configurations

We will be testing Mac OS X 10.4.x on PPC/Intel, as well as Mac OS X 10.5 on PPC/Intel.

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) [edit]

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. [edit]

References

(List useful links to the bug containing design info, feature meeting notes, wiki info, standards info, litmus group or subgroup, etc)