Meego Wiki
Views

Quality/MeeGo1.1HandSetUXTestPlanforMozillaFennecBrowser

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Feature To Be Tested)
(Feature To Be Tested)
Line 92: Line 92:
| Feature [http://bugs.meego.com/show_bug.cgi?id=4131 4131] - [FEA] Browser - Security (HTTPs) support || Browser support Hypertext Transfer Protocol Secure (HTTPS) which is a combination of the Hypertext Transfer Protocol with the SSL/TLS protocol to provide encrypted communication and secure identification of a network web server || xxx
| Feature [http://bugs.meego.com/show_bug.cgi?id=4131 4131] - [FEA] Browser - Security (HTTPs) support || Browser support Hypertext Transfer Protocol Secure (HTTPS) which is a combination of the Hypertext Transfer Protocol with the SSL/TLS protocol to provide encrypted communication and secure identification of a network web server || xxx
|-
|-
-
| Feature [] || || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=5679 5679] - FEA] Control Panel - WiFi on-off switching || User shall be able to turn on and off the WiFi radio at anytime. || xxx
|-
|-
-
| Feature [] || || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=5680 5680] - [FEA] Control Panel - WiFi list networks || User shall be provided a list of available WiFi networks in range. || xxx
|-
|-
-
| Feature [] || || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=5681 5681] - [FEA] Control Panel - WiFi connect || User shall be able to connect and use a WiFi network of any supported type. || xxx
|-
|-
-
| Feature [] || || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=5682 5682] - [FEA] Control Panel - WiFi prompt passphrase || User shall be prompted for WiFi passphrase if required || xxx
|-
|-
-
| Feature [] || || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=5683 5683] - [FEA] Control Panel - WiFi connect hidden networks || User shall be able to specify and connect to a "hidden" network, including specifying SSID and necessary security parameters as supported by the system. || xxx
|-
|-
| Feature [] ||  || xxx
| Feature [] ||  || xxx

Revision as of 08:56, 10 September 2010

Contents

MeeGo 1.1 HandSet UX Test Plan for Mozilla Fennec Browser

Component Summary

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

Feature To Be Tested

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

  • Mozilla Fennec browser Features to be tested are summarized as below:
Feature Name Description Comments
Feature 2633 - [FEA] Mozilla Fennec Browser A Mozilla Fennec Browser is required to surf full web content in a mobile. xxx
Feature 3032 - [FEA] Browser HTML support Browser should support full HTML4 and have partial support for HTML5. The browser SHALL support the HTML 4.01 strict document type. xxx
Feature 2952 - [FEA] Browser CSS support Browser should support full CSS Level 2.1 and have partial support for CSS 3. xxx
Feature 3034 - [FEA] Browser JavaScript support Browser should support full JavaScript 1.8 ECMAScript 3 and have partial support for ECMAScript 5. xxx
Feature 3035 - [FEA] Browser DOM support Browser should support full DOM Level 1 and 2 and have partial support for DOM Level 3. xxx
Feature 3036 - [FEA] Browser XML support Browser should support XML 1.0. xxx
Feature 3037 - [FEA] Browser XHTML support Browser should support XHTML 1.0. xxx
Feature 3038 - [FEA] Browser XSLT and XPath Browser should support XSLT and XPath. xxx
Feature 3039 - [FEA] Browser MathML support Browser should support MathML. xxx
Feature 3040 - FEA] Browser RDF support Browser should support RDF. xxx
Feature 3041 - [FEA] Browser Flash support Browser should support of installing the latest Adobe Flash (current 10.1) player as a plug-in to execute embedded Flash content on web pages. xxx
Feature 3069 - [FEA] Browser add-ons Browser should support installing and running common Firefox add-ons. xxx
Feature 3098 - [FEA] Browser quick search and access with Awesome Bar Browser should support the Awesome Bar to enable the fastest look-ups. Once typing, the Awesome Bar should display frequently or recently visited or bookmarked websites. Awesome Bar should support of entering an URL or search term and send your search directly to installed search engine add-ons, such as Google or Wikipedia. xxx
Feature 3099 - [FEA] Browser access to URL Browser should support of entering an Uniform Resource Locator (URL) of a web service to surf to that site. xxx
Feature 3100 - [FEA] Browser bookmarks Browser should support of storing and managing web pages as bookmarks. xxx
Feature 3101 - [FEA] Browser favicon support Browser should support of fetching and storing web page favorites icons (favicon) provided by web pages as visual identifier of the URL and bookmarks. xxx
Feature 3102 - [FEA] Browser privacy & security settings Browser should provide settings for user to manage passwords storing, allowing cookies, loading images, running JavaScripts and installing add-ons. xxx
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. xxx
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). Dropped from the 1.1 release
Feature 3129 - [FEA] Browser web page zoom Browser should support of zooming in and out of the web content. xxx
Feature 3130 - [FEA] Browser autocomplete forms Browser should support of storing web form fields data, such as passwords and email address, and autocomplete information once revisiting such web site xxx
Feature 3131 - [FEA] Browser Add-ons updates Browser should support of automatically updating installed Add-ons. xxx
Feature 4102 - [FEA] Browser - Icons and Indicators in Full Screen Mode In full Screen Mode, all icons and visual indicators SHALL be deleted. xxx
Feature 4103 - [FEA] Browser - Loading in progress indicator During navigation, the loading phases in progress (text, images, etc.) SHALL be indicated by an animated item (animated icon) which SHALL appear immediately. xxx
Feature 4104 - [FEA] Browser - Download in progress indicator The device SHALL provide continous progress feedback during objects download so the user knows the download is still in progress. Remaining time or % in progress SHALL be indicated Dropped from the 1.1 release
Feature 4107 - [FEA] Browser - Functionality key mapping: Back or erase If the device is BUTTON DRIVEN, back and erase SHALL be mapped to the back or erase soft key. xxx
Feature 4116 - [FEA] Browser - Bookmark: default name The name of the bookmark has to be automatically filled with the title of the page and the url with the address of the page. It SHALL be possible to rename the bookmark. xxx
Feature 4117 - [FEA] Browser - New Pages and Tabs Browser must provide mechanism to open new pages and tabs using a touch function within the browser toolbar. xxx
Feature 4121 - [FEA] Browser - Images support: recommended height The browser SHOULD support and display images whose height is equal or higher than the device screen height. xxx
Feature 4122 - [FEA] Browser - Horizontal scrolling The browser SHALL support the horizontal scrolling if the width of the image is larger than the screen width. xxx
Feature 4123 - [FEA] Browser - Image alt text support The browser SHALL support the alt text attribute for images. xxx
Feature 4124 - [FEA] Browser - Multiple objects displaying The browser SHALL be able to display several different objects (links, images, text) on the same line xxx
Feature 4125 - [FEA] Browser - Clickable image The browser SHALL support images as a link. The border of a linked image SHALL be able to be defined in the CSS file xxx
Feature 4126 - [FEA] Browser - Long links display Links longer than the width of the browser window SHALL be displayed on several lines. xxx
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). Dropped from the 1.1 release
Feature 4128 - [FEA] Browser - Access Architecture It SHALL be possible to access XHTML+CSS content with the following access architectures: Standard Internet architecture (HTTP over TCP/IP), Standard internet architecture with an explicit HTTP proxy xxx
Feature 4129 - [FEA] Browser - Cookies Browser SHALL support cookies xxx
Feature 4130 - [FEA] Browser - Deletion of cookies he user SHALL be able to delete his cookies Dropped from the 1.1 release
Feature 4131 - [FEA] Browser - Security (HTTPs) support Browser support Hypertext Transfer Protocol Secure (HTTPS) which is a combination of the Hypertext Transfer Protocol with the SSL/TLS protocol to provide encrypted communication and secure identification of a network web server xxx
Feature 5679 - FEA] Control Panel - WiFi on-off switching User shall be able to turn on and off the WiFi radio at anytime. xxx
Feature 5680 - [FEA] Control Panel - WiFi list networks User shall be provided a list of available WiFi networks in range. xxx
Feature 5681 - [FEA] Control Panel - WiFi connect User shall be able to connect and use a WiFi network of any supported type. xxx
Feature 5682 - [FEA] Control Panel - WiFi prompt passphrase User shall be prompted for WiFi passphrase if required xxx
Feature 5683 - [FEA] Control Panel - WiFi connect hidden networks User shall be able to specify and connect to a "hidden" network, including specifying SSID and necessary security parameters as supported by the system. xxx
Feature [] xxx
Feature [] xxx
Feature [] xxx
Feature [] xxx
xxx xxx xxx

Feature Not To Be Tested

List of features that are not tested as part of MeeGo 1.1 HandSet UX are:

<add here correct query from fearutezilla>

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
  • Basic Feature Test Set
    • Contains basic feature UI (Functional) test cases for every testable MFB feature
  • Extended Feature Test Set
    • Contains bunch of well selected MFB test cases to verify that delivered features (Functional) forming component are working
  • System Functional Test Set
    • Contains interaction and negative test cases were MFB is used together with other components that are part of system
  • System Performance Test Set
    • Contains only Response Time part


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. This will be done for both N900 and AAVA HW's.

Hardware Platforms

  • N900, AAVA and MRST CDK

QA Contact

Personal tools