Meego Wiki
Views

Quality/MeeGo1.2 Handset CoreUX TestPlan

From MeeGo wiki
< Quality(Difference between revisions)
Jump to: navigation, search
(Created page with "=Core UX Test Plan= ==Component Summary== This test plan is for MeeGo 1.1 HandSet Core UX. MeeGo handset '''Core UX''' is composed of whole '''home screen''' with '''MeeGo Touch …")
(→Test Strategy and Approach)
 
(19 intermediate revisions not shown)
Line 1: Line 1:
-
=Core UX Test Plan=
+
=MeeGo 1.2 Handset Core UX Test Plan=
 +
 
 +
==History ==
 +
 
 +
{|border="2" cellspacing="0" cellpadding="4" width="80%"
 +
|bgcolor = "#ebebeb"|'''Date'''
 +
|bgcolor = "#ebebeb"|'''Modification'''
 +
 
 +
|-
 +
|12/03/2010
 +
|Creation of this wiki
 +
 
 +
|-
 +
|&nbsp;
 +
|&nbsp;
 +
 
 +
|}
 +
 
==Component Summary==
==Component Summary==
-
This test plan is for MeeGo 1.1 HandSet Core UX. MeeGo handset '''Core UX''' is composed of whole '''home screen''' with '''MeeGo Touch Framework (MTF)''' (a full set of widgets and window manager), '''theme style and engine''', as well as '''system UI'''.
+
This test plan is for MeeGo HandSet '''Core UX'''. MeeGo handset '''Core UX''' is composed of whole '''home screen''', '''theme style and engine''', as well as '''system UI'''.  
-
* '''Home Screen ''' is an application that allows the user to start an application, switch between applications, and interact with system UI. All interactive operations between users and MeeGo functionality is handled by Home Screen.
+
* '''Home Screen ''' is the central point of access to all the applications and contents on your device, it's the first screen you see when you switch on your device. All interactive operations between users and MeeGo functionality is handled by Home Screen.
-
* '''MeeGo Touch Framework ''' is a widget and interaction framework that provides a collection of touch centric widgets as well as an overall platform navigation model.  
+
* '''Theme''' provides device orientation, object hierarchy and mode styling, which is required by any MTF application.
* '''Theme''' provides device orientation, object hierarchy and mode styling, which is required by any MTF application.
* '''System UI''' supports run time status (connectivity, battery status, volume status), date&time and notifications appearing on top bar of home screen.
* '''System UI''' supports run time status (connectivity, battery status, volume status), date&time and notifications appearing on top bar of home screen.
==Feature to be Tested==
==Feature to be Tested==
-
{| cellspacing="0" border="1"
+
{|border="1" cellspacing="0" cellpadding="4" width="90%"
-
!| Feature Name
+
|bgcolor = "#dcffff"|<font color="#000000">'''Feature Name'''</font>
-
!| Detailed Feature Description
+
|bgcolor = "#dcffff"|<font color="#000000">'''Detailed Feature Description'''</font>
-
!| Comments
+
|bgcolor = "#dcffff"|<font color="#000000">'''Comments'''</font>
|-
|-
-
| Home:
+
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework  
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework  
-
||  
+
|| MeeGo Touch UI Framework, including
-
* Home screen main page UI, layout and button response check
+
* Common UI components
-
* Application launcher UI UI, layout and button response check
+
* Application lifecycle management
-
* Open/close application launcher
+
* Application layouting
-
* Launch/close application from application launcher
+
* Multitouch event handling including basic gestures, at least pan, flick/swipe, pinch
-
* Switch between running applications with home screen
+
* Theme & style system
-
* Gestures and Touch Interactions (Tap, Long press, Drag, Flick, Double tap, Pinch)
+
* OpenGL shader effects API
-
* Security setting (lock/unlock screen)
+
* Application service framework
-
* System notification handle and interaction with home screen or running applications 
+
* Localization & Internationalization extensions 
-
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.  
+
|| The feature is for '''UI Infrastructure''', which related with home screen behaviors. All these sub-features depend on *Core OS features*. These test cases covered several feature points from UX.  
|-
|-
-
| Theme:
+
| '''Theme''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine  
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine  
-
||  
+
|| Theme & style system for MeeGo Handset and Touch based devices should support:
-
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
+
* Styling based on Device Orientation
-
* Home default theme
+
* Styling based on Object hierarchy and Objects
-
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
+
* Styling based on Mode 
||
||
|-
|-
-
| System UI  ||  
+
| '''System UI''' ||  
-
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
+
Run time status (connectivity, battery status), date&time, notifications appearing on system UI, and its drop down menu.
-
* Open/Close System UI drop down menu
+
|| No feature request for system UI
-
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
+
|-
-
* Volume status and value adjustment (TBD)
+
| '''I18n and L10n''':
-
* Invoke Settings application 
+
* Feature [http://bugs.meego.com/show_bug.cgi?id=9254 9254] -  [FEA] [I18N] DUIHome shall be internationalized according to the dependencies listed in Core Master 5068 
-
|| No feature request or UI design wireframe for system UI
+
|| 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 
 +
||  
|}
|}
Line 62: Line 85:
* '''Usage Model test''': to check if running application, home screen, system UI could work fine from user perspective.  
* '''Usage Model test''': to check if running application, home screen, system UI could work fine from user perspective.  
-
'''''Test Type and Approach''''' <br>
+
'''''Based on the test strategy, following areas will be tested with high priority:'''''
 +
* UI experience and functionality test, interaction with touch screen, common UI operation etc. It also includes i18n/l10n test.
 +
* Functionality verification, collaboration with other applications and with related devices.
-
Core UX components are tested in different test sets: <br>
+
'''''We will also cover the following functionality test:'''''
-
* Sanity Test Set
+
* Relative UI changes in Home screen, system UI etc.
-
** Contains BAT test cases of Core UX components.
+
* Stress and Negative testing to ensure the stability and robust of the Core UX.
-
* Basic Feature Test Set
+
-
** Contains basic feature (Functional) test cases for every testable feature of Core UX components.
+
-
* Extended Feature Test Set
+
-
** Contains bunch of well selected test cases of Core UX components to deeply verify functionality of every delivered features.
+
-
* System Functional Test Set
+
-
** Contains test cases of Core UX components that interacting and collaborating with other components to support a system usage.
+
-
 
+
-
Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
+
==Test Design==
==Test Design==
 +
Test Design is based on [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design usage Model]. According to the usage modal, characteristics and application features, the check points of each features were defined. Test design tables are drafted below, and which will become the base to design test cases.
-
===Home Screen===
+
{|border="2" cellspacing="0" cellpadding="4" width="100%"
-
* '''Test Points'''
+
|bgcolor = "#dcffff"|<font color="#000000">'''Feature Category'''</font>
-
** Check home screen, application launcher, system UI layout.
+
|bgcolor = "#dcffff"|<font color="#000000">'''Feature ID-description'''</font>
-
** Open/close application launcher
+
|bgcolor = "#dcffff"|<font color="#000000">'''Test Points'''</font>
-
** Launch/close application from application launcher or quick launch bar
+
|bgcolor = "#dcffff"|<font color="#000000">'''Collaboration'''</font>
-
** Switch between running applications with home screen
+
|bgcolor = "#dcffff"|<font color="#000000">'''Conditions'''</font>
-
** Gestures and Touch Interactions (Tap, Long press, Drag, Flick, Double tap, Pinch)
+
-
** Security setting (lock/unlock screen)
+
-
** System notification handle and interaction with home screen or running applications
+
-
===Theme===
+
|-
-
* '''Test Points'''
+
|Home Screen
-
** Check home and key applications default theme
+
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 2680] -  [FEA] Meego touch framework
-
** Update theme to check if it could take effect
+
|
-
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)
+
* Check Home Screen layout
 +
** Display selected applications icon in quick launch bar
 +
** Display apps icons with label in application launcher
 +
** Grid of apps layout, arrange order left to right
 +
** Portrait and Landscape layout
 +
* Navigate to view all apps in application launcher
 +
* Launch/close applications
 +
* Open/close application launcher
 +
* Animation of launch application
 +
* Lock/unlock screen
 +
* Running applications switch with home screen
 +
* Navigation to view all running applications
 +
* Tap running application to maximize app window
 +
* Tap to launch apps already run
 +
|
 +
* Theme
 +
* System UI
 +
* Key Applications
-
===System UI===
+
|
-
* '''Test Points'''
+
* Orientation (landscape and portrait view)
-
** Check System UI layout. For instance, if correct date/time appears.
+
* Gesture: tap, swipe, tap and hold (long press)
-
** Check if drop down menu is shown by dragging system UI, and be able to close. 
+
-
** Check toggle switch On/Off button could enable/disable Gps, WiFi, 3G, Bluetooth, Airplane connectivity.
+
-
** Check if corresponding connectivity status appears on system UI when enable Gps, WiFi, 3G, Bluetooth, Airplane.
+
-
** Check whether correct battery status displays when charging and not charging.
+
-
** Check if notification appears on system UI.
+
-
** Check if setting could be invoked by tapping settings button.
+
-
** Check if volume value could be adjusted (TBD).
+
-
===L10n Supporting===
+
|-
-
* '''Test Points''': to check if following items in target locale could be displayed correctly
+
|Theme
-
** Application name and icon
+
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 2685] -  [FEA] MeeGo Theme and style engine
-
** Button label and its icon
+
|
-
** Window title
+
* Check home theme, no red/white/black block appearing
-
** Text message
+
* Check key applications default theme, no red/white/black block appearing
-
** Date, time, number format
+
* Check system UI (including notifications) theme, no red/white/black block appearing
-
** Help message
+
* Update theme to check if it could take effect (TBD)
-
** Embedded link
+
|
 +
* Home
 +
* System UI
 +
* Key applications
 +
|
 +
 
 +
|-
 +
|System UI
 +
|
 +
|Check System UI display and layout: <br>
 +
* System UI displays on the top of the screen
 +
* Check icons (battery, network, roaming status, GPS, BT, time) display on system UI in idle screen
 +
* Check if drop down menu is shown by dragging system UI, and is able to close.
 +
* Check toggle switch On/Off button could enable/disable Gps, WiFi, 3G, Bluetooth, Airplane connectivity.
 +
* Check whether correct battery status displays when charging and not charging.
 +
* Check if notification appears on system UI.
 +
* Check if setting could be invoked by tapping settings button.
 +
* Check if volume value could be adjusted.
 +
|
 +
* Network (Bluetooth, wireless, 2G/2.5G/3G/4G)
 +
* Clock to set Date/time
 +
* Dialer/SMS
 +
* Email
 +
* Sound settings
 +
* Notifications:
 +
** new email
 +
** missed call
 +
** new SMS
 +
|
 +
* Network connection:
 +
** Bluetooth on/off
 +
** Wireless connected/disconnected/scanning
 +
** 2G/2.5G/3G/4G
 +
* GPS active/inactive
 +
* Charge/uncharged battery
 +
* Gesture: tap, swipe
 +
 
 +
|-
 +
|I18n and L10n
 +
|[https://bugzilla.otcshare.org/show_bug.cgi?id=9254 9254] -  [FEA] [I18N] DUIHome shall be internationalized according to the dependencies listed in Core Master 5068
 +
|Check text internationalization support on home screen, application launcher, System UI:
 +
*  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
 +
Check the Chinese language localization support on home screen, application launcher, System UI:
 +
* Application name and icon
 +
* Button label and its icon
 +
* Window title
 +
* Text message
 +
* Date, time, number format
 +
* Help message
 +
* Embedded link
 +
|&nbsp;
 +
|&nbsp;
 +
 
 +
|}
==Risk and Dependency==
==Risk and Dependency==
-
* Lack of home screen feature request. All MTF sub-features depend on *Core OS features*. These test cases covered several feature points from UX.  
+
* Lack of home screen features. All MTF sub-features depend on *Core OS features*. These test cases covered several feature points from UX.  
-
* Lack of system UI feature request or UI design wireframe.
+
* Lack of system UI features.
==Test Environment==
==Test Environment==
===Hardware Platforms===
===Hardware Platforms===
-
* Medfield iCDK
+
* nCDK
-
* Medfield nCDK 
+
* iCDK
===Tools===
===Tools===
Line 130: Line 213:
* [mailto:cathy.li@intel.com Cathy Li]
* [mailto:cathy.li@intel.com Cathy Li]
-
==References==
+
==Developers==
-
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
+
* [mailto: TBD]
-
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
+
 
 +
==Reference==
 +
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design Usage Model]

Latest revision as of 06:29, 4 January 2011

Contents

MeeGo 1.2 Handset Core UX Test Plan

History

Date Modification
12/03/2010 Creation of this wiki
   

Component Summary

This test plan is for MeeGo HandSet Core UX. MeeGo handset Core UX is composed of whole home screen, theme style and engine, as well as system UI.

  • Home Screen is the central point of access to all the applications and contents on your device, it's the first screen you see when you switch on your device. All interactive operations between users and MeeGo functionality is handled by Home Screen.
  • Theme provides device orientation, object hierarchy and mode styling, which is required by any MTF application.
  • System UI supports run time status (connectivity, battery status, volume status), date&time and notifications appearing on top bar of home screen.

Feature to be Tested

Feature Name Detailed Feature Description Comments
Home:
  • Feature 2680 - [FEA] Meego touch framework
MeeGo Touch UI Framework, including
  • Common UI components
  • Application lifecycle management
  • Application layouting
  • Multitouch event handling including basic gestures, at least pan, flick/swipe, pinch
  • Theme & style system
  • OpenGL shader effects API
  • Application service framework
  • Localization & Internationalization extensions
The feature is for UI Infrastructure, which related with home screen behaviors. All these sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
Theme:
  • Feature 2685 - [FEA] MeeGo Theme and style engine
Theme & style system for MeeGo Handset and Touch based devices should support:
  • Styling based on Device Orientation
  • Styling based on Object hierarchy and Objects
  • Styling based on Mode
System UI

Run time status (connectivity, battery status), date&time, notifications appearing on system UI, and its drop down menu.

No feature request for system UI
I18n and L10n:
  • Feature 9254 - [FEA] [I18N] DUIHome 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 not to be Tested

Feature Name Feature Description Comments
  • Translation for other languages except Chinese Simplified will not be covered in Handset Core UX Test Plan.

Test Strategy and Approach

Test Strategy

  • Test from UI: to check home screen, application launcher, system UI layout, theme and functionalities work correctly from UI. E.g, check if application is able to be launched to home screen with full screen; if could switch application to home screen by clicking home button; if correct runtime status (battery, networking) appears on system UI etc.
  • Usage Model test: to check if running application, home screen, system UI could work fine from user perspective.

Based on the test strategy, following areas will be tested with high priority:

  • UI experience and functionality test, interaction with touch screen, common UI operation etc. It also includes i18n/l10n test.
  • Functionality verification, collaboration with other applications and with related devices.

We will also cover the following functionality test:

  • Relative UI changes in Home screen, system UI etc.
  • Stress and Negative testing to ensure the stability and robust of the Core UX.

Test Design

Test Design is based on Handset Test Design usage Model. According to the usage modal, characteristics and application features, the check points of each features were defined. Test design tables are drafted below, and which will become the base to design test cases.

Feature Category Feature ID-description Test Points Collaboration Conditions
Home Screen 2680 - [FEA] Meego touch framework
  • Check Home Screen layout
    • Display selected applications icon in quick launch bar
    • Display apps icons with label in application launcher
    • Grid of apps layout, arrange order left to right
    • Portrait and Landscape layout
  • Navigate to view all apps in application launcher
  • Launch/close applications
  • Open/close application launcher
  • Animation of launch application
  • Lock/unlock screen
  • Running applications switch with home screen
  • Navigation to view all running applications
  • Tap running application to maximize app window
  • Tap to launch apps already run
  • Theme
  • System UI
  • Key Applications
  • Orientation (landscape and portrait view)
  • Gesture: tap, swipe, tap and hold (long press)
Theme 2685 - [FEA] MeeGo Theme and style engine
  • Check home theme, no red/white/black block appearing
  • Check key applications default theme, no red/white/black block appearing
  • Check system UI (including notifications) theme, no red/white/black block appearing
  • Update theme to check if it could take effect (TBD)
  • Home
  • System UI
  • Key applications
System UI Check System UI display and layout:
  • System UI displays on the top of the screen
  • Check icons (battery, network, roaming status, GPS, BT, time) display on system UI in idle screen
  • Check if drop down menu is shown by dragging system UI, and is able to close.
  • Check toggle switch On/Off button could enable/disable Gps, WiFi, 3G, Bluetooth, Airplane connectivity.
  • Check whether correct battery status displays when charging and not charging.
  • Check if notification appears on system UI.
  • Check if setting could be invoked by tapping settings button.
  • Check if volume value could be adjusted.
  • Network (Bluetooth, wireless, 2G/2.5G/3G/4G)
  • Clock to set Date/time
  • Dialer/SMS
  • Email
  • Sound settings
  • Notifications:
    • new email
    • missed call
    • new SMS
  • Network connection:
    • Bluetooth on/off
    • Wireless connected/disconnected/scanning
    • 2G/2.5G/3G/4G
  • GPS active/inactive
  • Charge/uncharged battery
  • Gesture: tap, swipe
I18n and L10n 9254 - [FEA] [I18N] DUIHome shall be internationalized according to the dependencies listed in Core Master 5068 Check text internationalization support on home screen, application launcher, System UI:
  • 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

Check the Chinese language localization support on home screen, application launcher, System UI:

  • Application name and icon
  • Button label and its icon
  • Window title
  • Text message
  • Date, time, number format
  • Help message
  • Embedded link
   

Risk and Dependency

  • Lack of home screen features. All MTF sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
  • Lack of system UI features.

Test Environment

Hardware Platforms

  • nCDK
  • iCDK

Tools

  • bluetooth devices, wlan devices, wireless AP

QA Contact

Developers

  • [mailto: TBD]

Reference

Retrieved from "http://wiki.meego.com/Quality/MeeGo1.2_Handset_CoreUX_TestPlan"
Personal tools