QA/Fennec/Milestones/2.0/TestPlan:PlatformIntegration

General Information

Area	Details
Team:	Developer: Designer: Madhava Enros (:madhava) QA: Ayan Shah (:ashah)
Tracking Bugs	bug 559915 bug 559453 bug 581596 bug 582640 bug 570514 bug 575403 bug 606565 More to come...

Designs

Maemo

• selection lists - https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/Fennec_1.1%2B/Revised_layout_and_functionality_of_Fennec_Pop-up_Choice_list
• toggle switches - https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/Fennec_1.1%2B/Switch_component
• text selection - https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/Fennec_1.1%2B/Interaction_with_Text_input_elements
• Menu button - http://www.flickr.com/photos/madhava_work/5105182033/sizes/l/

Major Areas of Test

General

• Platform Helper Apps (Not sure whether this would come here or under OS integration factors)
  • A file should open in a native program for that file. For e.g., a PDF should open in a PDF reader, mp3 file should be played in the native music player etc.
  • A phone number link should open the keypad of the phone to make a phone call.
  • An mailto link should open the native email application.

• Web Helper Apps
  • RSS Feed reader

• Interaction with text input elements
  • Single Tap inside Text input element should result in:
    • Setting focus to element (if it was not focused yet)
    • Relocating cursor (if the element was already focused)
  • Single Tap outside Text input element should result in:
    • Removing focus from text input element and putting the focus back on webpage.
    • If the user tapped on any web page element, that element should perform its designated function. For e.g., if the user tapped on a link, link should be opened, if the user tapped on a search button, the text should be searched for, etc.
  • Focus should be removed when the user closes the soft keyboard
  • Dragging
    • If a text input element does not have focus and user taps the text element and starts draging, the document/canvas in the view should be panned(no matter what was the initial direction of the stroke).
    • If the text input element already has focus, the outcome of starting Drag interaction over it should be
      • panning the document/canvas in the view, if the initial direction of the stroke was Vertical
      • selecting text, if the initial direction of the stroke was Horizontal
  • Auto-Scrolling
    • If the user taps on a text field which is at the bottom of the page, the browser should auto-scroll to the input element so that it is visible to the user with the soft keyboard present.
• Toggle switches
  • Only the switch component would be interactive - Not the label.
  • You should be able to set switch component on/off by tapping it.
  • You should be able to set switch component by initializing horizontal drag interaction over it.
• Selection Lists
  • Opening a pop up menu
  • Selecting an item from pop up menu
  • Cancel selection
  • (-ve test?) Panning the list with the drag or flick interactions should not result selecting a list item.

Maemo

• Native notifications/Use of native dialogs(?)
  • Click on an addon in AMO to get install/cancel notification
  • File download notifications.
  • Add-ons download notifications.

• Blur background when we have a popped up dialog

• Maemo/Meego theming(?)

• Add close app button on more screens / possible use of Maemo icons in more places(?)
• Revised maemo/meego theme (?)
• Text selection (in fields, perhaps in arbitrary text) (?)

Anroid

• Integration of notifications into the system bar.
  • Notification for any downloads(add on download as well as file download) should be displayed into the status bar of Android.
  • Updates(when available) notifications should be displayed (not sure about this).
  • Tapping on notification should take you to the respective managers(download manager or add-ons manager)

• Hardware buttons functionality.
  • Menu button (WIP)
    • This is the menu button that is present on the android phones. Pressing this buton should bring up the app menu for fennec.
    • The availability and contents of the app menu depend on what section of the Fennec UI is active. The contents of the menu will change over time and can be modified by add-ons. Here are the contents for the initial release:
      1. Main browser UI:
      o Site Options - opens the identity panel / site menu.
      o Preferences - opens the preference panel
      o Add-ons - opens the add-on manager
      o Downloads - opens the download manager
      2.Awesomescreen:
      o No menu for this release. (Nothing happens when "Menu" key is pressed.)
      3.Tool panels (prefs, add-ons, downloads, console, etc.):
      o No menu for this release. (Nothing happens when "Menu" key is pressed.)
    • Pressing the menu button shows the app menu and locks the titlebar to the top of the screen.
    • Pressing the menu button again hides the app menu and unlocks the titlebar.
    • Touching outside the app menu hides the app menu and unlocks the titlebar.
    • Opening any panel or popup (e.g., opening the awesomescreen by pressing the system "Search" key) hides the app menu and unlocks the titlebar.
    • Tapping on a menu button makes the menu disappear, unlocks the titlebar, and executes the button action.
    • If you touch a menu button and then move your finger off the button before releasing it, the tap is canceled and nothing happens (just like any other button in Fennec).

• • Back button
    • Pressing the system "Back" key hides the app menu and unlocks the titlebar.
    • The back button should be able to move the pages back according to the session history.
    • After opening a link in a new tab, back button closes the new tab and returns to the original tab.
    • If on the home page or on a page that does not have a session history, the back button should act as a way to close the browser.
    • If there is a modal dialog box or pop up, the back button should dismiss the dialog box leaving the user on whatever as underneath.
    • If the awesomebar or bookmark manager are opened, back button closes them, but the browser stays on the same page. If hit back again, it goes back in session history.
  • Search (WIP)
    • Pressing the search button on the browser UI should bring up the awesome screen with the virtual keyboard shown
    • The Search button should open the open the search menu, when the awesome screen is already opened.
    • Pressing the search button on the preferences menu(prefs, addons, downloads, beta tools) should bring up the awesome screen with the soft keyboard visible.

• Variants of onscreen keyboard.
  • When typing into the awesome bar, use the keyboard with .com button
  • When entering a phone number, pop up the numbered keyboard

• Use menu key as shortcut accelerator
  • For hardware keyboards, shortcuts should be supported( For eg. - Menu+L = open location bar, Menu+T = new tab etc.)

OS Integration Factors

• Android and Maemo:
  • Soft keyboard
  • (Android only)Identity button should open the Open Search popup list when touching the Menu button on Android bug 591133
  • Native Applications
    • Email
    • Phone
    • PDF reader
    • Feed reader
    • DOC reader
    • mp3 player

• • Native Notifications
    • Download
    • Installation