QA/Fennec/Milestones/2.0/TestPlan:PlatformIntegration: Difference between revisions

QA/Fennec/Milestones/2.0/TestPlan:PlatformIntegration (view source)

Revision as of 16:57, 26 August 2010

1,735 bytes added , 26 August 2010

→‎General

Ashah

451

edits

@@ Line 36: / Line 36: @@
 ===General===
 *Helper Apps
-*** 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 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.
+** 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.
+** An mailto link should open the native email application.
-*Native notifications
+* Interaction with text input elements
-*** File download notifications.
+** Single Tap inside Text input element should result in:
-*** Add-ons download notifications.
+*** 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===