MozillaWiki

QA/Fennec/Milestones/2.0/TestPlan:PlatformIntegration

< QA‎ | Fennec‎ | Milestones‎ | 2.0
Revision as of 22:17, 25 August 2010 by Ashah (talk | contribs) (→‎Maemo)

General Information

Area Details
Team:
  • Developer:
  • Designer: Madhava Enros (:madhava)
  • QA: Ayan Shah (:ashah)
Tracking Bugs

Designs

Maemo

Android

Major Areas of Test

General

Maemo

  • 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.
  • Use of Native dialogs
  • Maemo/Meego theming

Anroid (WIP)

  • Integration of notifications into the system bar.
    • Different notifications for download should be displayed into the system bar
    • Updates(when available) notifications should be displayed.
  • Hardware buttons functionality.
    • Menu button (WIP)
      • The Menu button should handle searching in page, save as pdf etc.
    • Back button
      • The back button should be able to move the pages back according to the session history.
      • 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)
  • 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

OS Integration Factors

  • Android:
  • Maemo:

Negative Tests

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Fennec/Milestones/2.0/TestPlan:PlatformIntegration&oldid=248491"