Firefox:188.8.131.52:Test Plan:Leopard TestPlan
- 1 Firefox Leopard Test Plan
- 1.1 Overview
- 1.2 Scope of Planned Testing
- 1.3 Will Not Test
- 1.4 Platforms and Configurations
- 1.5 Major Test Areas
- 1.6 Gettings bugs that need attention to developers
- 1.7 Helpful Bug Links
- 1.8 Bugs to Keep an eye on
- 1.9 Litmus test cases added or changed
- 1.10 Schedule/milestones
- 1.11 Sites that don't work in Safari but work in Firefox
- 1.12 Building a Community of Leopard testers
Firefox Leopard Test Plan
Maintained by: Marcia Knous
- First Draft, 10/03/07
- Revisions made 10-10-07
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
- Flip for Mac
- Enabling and Disabling
- Finding Updates
- Add-ons Compatibility checks
- Popups management
- Preferences and Dialogs
- Check scrolling and buttons
- Ensure basic printing functionality
- Save as PDF
- Search plugins
- Changing them, testing the suggestions and history
- Scrolling and Drawing
- XUL Controls
- Password Manager
- 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
- 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
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
- 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
- Developer List of Critical Bugs: http://wiki.mozilla.org/FF2:Leopard
- Current 10.5 bugs ->http://tinyurl.com/32j6jg
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.
- Focused testing on OS integration points
- 5 days
- Focused testing of Firefox 184.108.40.206 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