Quality/MeeGo1.2HandSetUXTestPlanforMozillaFennecBrowser

Contents 1 MeeGo 1.2 HandSet UX Test Plan for Mozilla Fennec Browser 1.1 Component Summary 1.2 Features To Be Tested 1.3 Features Not To Be Tested 1.4 Strategy and Approach 1.5 Hardware Platforms 1.6 QA Contact

MeeGo 1.2 HandSet UX Test Plan for Mozilla Fennec Browser

Component Summary

This test plan is for MeeGo 1.2 HandSet UX Mozilla Fennec Browser. Firefox Mobile is the Browser built for the way you use the web on your mobile device.

Features To Be Tested

All testable features coming to MeeGo 1.2 HandSet UX Mozilla Fennec Browser will be covered in this test plan.

• Mozilla Fennec browser 1.2 Features that will be verified are listed below (detailed info from FeatureZilla can be found here):

Feature Name	Description	Comments
Feature 3103 - [FEA] Browser remember web passwords	Browser should provide support to remember web site passwords and pre-fill those to the web page once re-visited.	Moved from release 1.1
Feature 3128 - [FEA] Browser web page orientation	Browser should support of rendering the content optimised both on landscape and portrait modes depending on the orientation of the device (if device orientation supported by the device).	Moved from release 1.1
Feature 4104 - [FEA] Browser - File download in progress indicator	The device SHALL provide continuous progress feedback during file download so the user knows the download is still in progress. Remaining time or % in progress SHALL be indicated.	Moved from release 1.1
Feature 4127 - [FEA] Browser - Videos and CSS Layering	The browser SHALL support the display of HTML elements on top of an embedded video object using standard CSS layering (position and z-index properties).	Moved from release 1.1
Feature 4130 - [FEA] Browser - Deletion of cookies	The user SHALL be able to delete his cookies	Moved from release 1.1
Feature 9263 - [FEA] [I18N]The Web browser shall be internationalized according to the dependencies listed in Core Master 5068.	This includes such items as: Unicode support All translatable strings are externalized UI adaptability to longer and shorter strings than English Ability to accept, display, sort, search, copy, paste, and print accented and double-byte characters No concatenation of translatable strings Support for the POR languages: en_US, en_GB, fr, de, es, it, fi, sv, pl, ru, nl, pt_BR, ja, ko, zh_TW, zh_CN	Feature can be tested based on description but extended testing should be done during localization / internationalization testing.

• Also MeeGo 1.1 release browser features (link to featurezilla) are included in testing

Features Not To Be Tested

None

Strategy and Approach

Mozilla Fennec Browser is tested in different test sets. Test sets containing Mozilla Fennec Browser (MFB) related test cases are:

• Sanity Test Set
  • Contains few basic MFB test cases that MFB application is part of SW image, can be opened and basic browsing can be made
• Key Feature Test Set
  • Consists of key features defined by product management. In the begin release 1.1 key features will be used for the test set but after product management defines key features for 1.2 they will be updated to test set. Test set will be run to Preview and Weekly images
• Feature Basic Acceptance Set (BAT)
  • 10-30 important browser test cases selected from Basic Feature Test Set. Will be run weekly
• Basic Feature Test Set
  • Contains basic feature UI (Functional) test cases for every testable MFB feature. Will be run once for every major milestone
• Extended Feature Test Set
  • Contains bunch of well selected MFB test cases to verify that delivered features (Functional) forming component are working. Will be run once during Feature Development Phase (MM2-MM3) and once in Stabilization Phase (MM3-MM4)

Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline

Note! Nokia Browser team will also perform extensive UI application test set for MFB to ensure that all relevant MFB related bugs are detected and reported.

Hardware Platforms

• All official supported HW's

QA Contact

• Anssi Takku