Firefox:2.0.0.8:Test Plan:Leopard TestPlan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(19 intermediate revisions by the same user not shown)
Line 2: Line 2:
Maintained by: Marcia Knous
Maintained by: Marcia Knous
*''First Draft'', 10/03/07
*''First Draft'', 10/03/07
*Revisions made 10-10-07


==Overview==
==Overview==


The primary goal of this QA test plan is the testing of the OS integration piece of Firefox as it relates to Leopard, the latest operating system which Apple is expected to release in October. This is make sure that existing functionality works and that all newly supported functionality works (primarily support of parental controls). Note that this test plan was written primarily for the 2.0.0.x branch, but should easily translate to Firefox 3 as well.
The primary goal of this QA test plan is the testing of the OS integration piece of Firefox as it relates to Leopard, the latest operating system which Apple is expected to release in October. This is make sure that all basic existing functionality works (especially  and that all newly supported functionality works (primarily support of spaces, parental controls, etc.). Note that this test plan was written primarily for the 2.0.0.x branch, but should easily translate to Firefox 3 as well. Areas that need special attention and focus in Firefox 3 are called out in the plan in bold.


==Scope of Planned Testing==
==Scope of Planned Testing==
Line 22: Line 23:
*Interfacing with Growl '''[Trunk only]'''
*Interfacing with Growl '''[Trunk only]'''
**Ensuring you can register Firefox with Growl
**Ensuring you can register Firefox with Growl
**Ensuring you receive notifications when Firefox is registered


* Setting Firefox as the Default Application
* Setting Firefox as the Default Application
Line 30: Line 32:
**Setting FF as the default before a software update
**Setting FF as the default before a software update
**Checking FF is the default by launching from link or shortcuts
**Checking FF is the default by launching from link or shortcuts
*Migration/Import of bookmarks, history, etc from other browser
**Parity with what we have on Tiger


* RSS Feed Reader - Support of Client Side Applications
* RSS Feed Reader - Support of Client Side Applications
* Downloading files to the desktop
* Downloading files to the desktop
**Honoring whatever is set as the default download location on Vista
**Honoring whatever is set as the default download location on Leopard
* Fonts
* Fonts
* Plugins
* Plugins
Line 49: Line 54:
**Finding Updates
**Finding Updates
**Add-ons Compatibility checks
**Add-ons Compatibility checks
*Popups management


*Preferences and Dialogs
*Preferences and Dialogs
Line 56: Line 63:
**Ensure basic printing functionality
**Ensure basic printing functionality
**Save as PDF
**Save as PDF
*Search plugins
**Changing them, testing the suggestions and history


*Scrolling and Drawing
*Scrolling and Drawing
Line 64: Line 74:
**Browsing secure sites
**Browsing secure sites
**Saving Passwords
**Saving Passwords
**Password management
**Setting a Master Password
**Setting a Master Password
**Installing a certificate
**Installing a certificate
Line 69: Line 80:
*Software Update
*Software Update
**Ensuring that users can perform a minor update
**Ensuring that users can perform a minor update
**Ensuring that users can perform a major update
**Make sure non-admin users do not get the option to update
**Make sure non-admin users do not get the option to update
*Spaces
**Ensuring that Firefox can be added to Spaces
**Confirming that nothing shows in Spaces when Firefox is minimized to the dock.
*Tabbed browsing
*Tagging of Downloaded Applications
**Confirm that Apple dialog correctly identifies Firefox when you have downloaded a program or file using Firefox
*New Default theme for Mac (proto)
**Please see http://wiki.mozilla.org/QA/Firefox3/TestPlan/Mac_Theme for the test plan


==Will Not Test==
==Will Not Test==
Line 85: Line 109:
*1. Functional testing and  
*1. Functional testing and  
*2. Some stress/boundary/negative tests (depth of functionality):
*2. Some stress/boundary/negative tests (depth of functionality):
** FFT in Litmus run on the Windows Vista platform
** '''FFT in Litmus run on the Leopard platform'''
*3. Ad hoc and regression testing
*3. Ad hoc and regression testing


Line 92: Line 116:
*We will run the Litmus Leopard specific testing suite.
*We will run the Litmus Leopard specific testing suite.
*Litmus test cases will be added for any new Leopard specific features that are supported.
*Litmus test cases will be added for any new Leopard specific features that are supported.
*We will run the Litmus Native Form Controls suite.


'''Stress testing/Negative Testing(depth of functionality):
'''Stress testing/Negative Testing(depth of functionality):
Line 98: Line 123:
'''Ad hoc & regression testing'''
'''Ad hoc & regression testing'''


The Mozilla community users will cover some of the Ad hoc testing. Regression testing will cover:
The Mozilla community users may cover some of the Ad hoc testing. Regression testing will cover:


* QA Verification of Resolved bugs
* QA Verification of Resolved bugs
* Daily smoketesting of builds
* Daily smoketesting of builds


== Current 10.5 bugs ==
== Gettings bugs that need attention to developers ==
*http://tinyurl.com/32j6jg


The Mac platform team takes notice of Firefox 2 bugs fitting the following description:
*1. Assigned to Widget:Mac
*2. At least Josh cc'd, if not the rest of the team and Damon.
*3. Marked as a release blocker.
*4. If you need assistance from a MoCo platform developer with a Mac bug that does not fit that description, please email Josh and Damon directly.
== Helpful Bug Links  ==
*Developer List of Critical Bugs: http://wiki.mozilla.org/FF2:Leopard
*Current 10.5 bugs ->http://tinyurl.com/32j6jg
*http://wiki.mozilla.org/FF2:Leopard
== Bugs to Keep an eye on ==
== Bugs to Keep an eye on ==
*Worst bug Josh has experienced is shifted plugin rendering. Do we have a bug for this?
== Litmus test cases added or changed ==


*The Leopard Specific Test Suite is still being built out. It is chunked into the following 3 major areas:
**OS Integration
**Default Browser
**Parental Controls


== Litmus test cases added or changed ==
As of 12/17/07 the Suite is active in Litmus and has several test cases assigned to each section.


== Schedule/milestones ==
== 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.
*Focused testing on OS integration points
**5 days
 
*Focused testing of Firefox 2.0.0.8 candidate
**2 days?
 
*Creation of test cases specific to Leopard
**As time permits


== Sites that don't work in Safari but work in Firefox ==
== Sites that don't work in Safari but work in Firefox ==
*Google Groups - Page creation and editing is not supported in Safari but works in Firefox branch.
*Google Groups - Page creation and editing is not supported in Safari but works in Firefox branch.
== Building a Community of Leopard testers ==
*http://www.macleopardforums.com/forum/looking-for-leopard-users-interested-in-testing-firefox-t133.html
*http://www.macusersforum.com/index.php?showtopic=19363
*http://forums.macresource.com/read/1/376071
*http://discussions.apple.com/thread.jspa?threadID=1207966&stqc=true
*http://www.mac-forums.com/forums/showthread.php?p=518055#post518055

Latest revision as of 20:01, 20 December 2007

Firefox Leopard Test Plan

Maintained by: Marcia Knous

  • First Draft, 10/03/07
  • Revisions made 10-10-07

Overview

The primary goal of this QA test plan is the testing of the OS integration piece of Firefox as it relates to Leopard, the latest operating system which Apple is expected to release in October. This is make sure that all basic existing functionality works (especially and that all newly supported functionality works (primarily support of spaces, parental controls, etc.). Note that this test plan was written primarily for the 2.0.0.x branch, but should easily translate to Firefox 3 as well. Areas that need special attention and focus in Firefox 3 are called out in the plan in bold.

Scope of Planned Testing

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

  • Installing and Uninstalling Firefox on Leopard
    • Installing in the Default Applications Directory
    • Installing in a non-default directory (Such as a desktop folder)
    • Uninstalling Firefox
      • Note new dialog here which detects that you have downloaded Firefox and ask you explicitly whether or not you want to install it (similar to UAC on Vista).
  • Running as a User with Parental Controls invoked
    • Confirm that when someone blocks Firefox that the user cannot launch the application.
  • Interfacing with Growl [Trunk only]
    • Ensuring you can register Firefox with Growl
    • Ensuring you receive notifications when Firefox is registered
  • 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
    • Checking FF is the default after launch using "Check Now"
    • Setting FF as the default after a software update
    • Setting FF as the default before a software update
    • Checking FF is the default by launching from link or shortcuts
  • Migration/Import of bookmarks, history, etc from other browser
    • Parity with what we have on Tiger
  • RSS Feed Reader - Support of Client Side Applications
  • Downloading files to the desktop
    • Honoring whatever is set as the default download location on Leopard
  • Fonts
  • Plugins
    • Flash
    • Shockwave
    • Quicktime
    • Flip for Mac
    • PDFs
    • Java
    • RealPlayer
  • Add-ons
    • Installing
    • Uninstalling
    • Enabling and Disabling
    • Finding Updates
    • Add-ons Compatibility checks
  • Popups management
  • Preferences and Dialogs
    • Check scrolling and buttons
  • Printing
    • Ensure basic printing functionality
    • Save as PDF
  • Search plugins
    • Changing them, testing the suggestions and history
  • Scrolling and Drawing
  • XUL Controls
  • Password Manager
  • Security
    • Browsing secure sites
    • Saving Passwords
    • Password management
    • Setting a Master Password
    • Installing a certificate
  • Software Update
    • Ensuring that users can perform a minor update
    • Ensuring that users can perform a major update
    • Make sure non-admin users do not get the option to update
  • Spaces
    • Ensuring that Firefox can be added to Spaces
    • Confirming that nothing shows in Spaces when Firefox is minimized to the dock.
  • Tabbed browsing
  • Tagging of Downloaded Applications
    • Confirm that Apple dialog correctly identifies Firefox when you have downloaded a program or file using Firefox

Will Not Test

Will NOT test

Platforms and Configurations

We will test Leopard on both PPC Mac and Intel Mac. We have a variety of machines that we can test on, including those with limited memory as well as robust memory.

Major Test Areas

Our Test coverage will be a multi-leveled approach:

  • 1. Functional testing and
  • 2. Some stress/boundary/negative tests (depth of functionality):
    • FFT in Litmus run on the Leopard platform
  • 3. Ad hoc and regression testing

Functional Testing

  • We will run the Litmus Leopard specific testing suite.
  • Litmus test cases will be added for any new Leopard specific features that are supported.
  • We will run the Litmus Native Form Controls suite.

Stress testing/Negative Testing(depth of functionality):

Ad hoc & regression testing

The Mozilla community users may cover some of the Ad hoc testing. Regression testing will cover:

  • QA Verification of Resolved bugs
  • Daily smoketesting of builds

Gettings bugs that need attention to developers

The Mac platform team takes notice of Firefox 2 bugs fitting the following description:

  • 1. Assigned to Widget:Mac
  • 2. At least Josh cc'd, if not the rest of the team and Damon.
  • 3. Marked as a release blocker.
  • 4. If you need assistance from a MoCo platform developer with a Mac bug that does not fit that description, please email Josh and Damon directly.

Helpful Bug Links

Bugs to Keep an eye on

  • Worst bug Josh has experienced is shifted plugin rendering. Do we have a bug for this?

Litmus test cases added or changed

  • The Leopard Specific Test Suite is still being built out. It is chunked into the following 3 major areas:
    • OS Integration
    • Default Browser
    • Parental Controls

As of 12/17/07 the Suite is active in Litmus and has several test cases assigned to each section.

Schedule/milestones

  • Focused testing on OS integration points
    • 5 days
  • Focused testing of Firefox 2.0.0.8 candidate
    • 2 days?
  • Creation of test cases specific to Leopard
    • As time permits

Sites that don't work in Safari but work in Firefox

  • Google Groups - Page creation and editing is not supported in Safari but works in Firefox branch.

Building a Community of Leopard testers