MeeGo wiki - User contributions [en]

Quality/MeeGo1.2 Handset Applets Test Plan

2011-01-04T06:31:09Z

Cathyli: /* Test Strategy and Approach */

=Applets Test Plan=
==Component Summary==
This test plan is for MeeGo HandSet '''Applets'''. MeeGo handset '''Applets''' is composed of '''Clock''','''Alarm''','''Office viewers''', as well as '''Backup and Restore'''.

* '''Clock''' is to show the time and location,also provides users to add or delete a clock city/locations etc.
* '''Alarm''' can go off according to the user-setting, and also provides users to add/delete alarm etc.
* '''Office viewer''' provides users to view common office documents,such as Microsoft office 2000&2003&2007 documents and PDF,in both landscape and portrait orientation etc.
* '''Backup and Restore''' support to back up user data to local storage,e.g,SD card, USB mass storage or local folder path,restore all of their data back to a backup point in time.

==Feature to be Tested==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Set'''
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''

|-
|| Clock
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=3062 3062] - [FEA] Clock application
|| A clock application should be provided to show current time and date.
||
|-
|rowspan="2"| Alarm
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=7230 7230] - [FEA] Clock applications alarm functionality
|| should be provided to show current time and date,and provide alarm clock functionality;Provide common alarm clock functionality.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=11435 11435] - [FEA] Power up & shutdown - Alarm wake
||The system will "wake" from AOAC screen-off state when a user-set alarm goes off.
||
|-
|rowspan="16"| Office viewers
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8126 8126] - [FEA] Office viewers - Application interworking
|| Support application interworking by providing API for launching document rendering documents when they are contained as attachments in other applications like mail.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8127 8127] - [FEA] Office viewers - Cancel opening document
|| Opening large document must be able to be canceled.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8130 8130] - [FEA] Office viewers - Document zooming & panning
|| Document zooming in and out should be supported and be smooth and fast.
Document must be able to be panned to different directions.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8131 8131] - [FEA] Office viewers - Find inside document
|| Engine shall support Search with plain text inside document.
It should also support next and previous found words.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8132 8132] - [FEA] Office viewers - Open links in documents
|| The engine shall render links in all documents and allow opening them.
Engine shall detect URLs in the following formats: "http://" or "www.something.com"
and "http://style.com" and provide a visual cue that this is a clickable URL.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8133 8133] - [FEA] Office viewers - Show embedded content indicator
|| The engine shall render indicator of embedded Files within Office documents show that the user knows there is an embedded file.
NOTE:Opening of the files is currently not supported.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8134 8134] - [FEA] Office viewers - Show table of contents
|| Documents' table of contents should be rendered.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8135 8135] - [FEA] Office viewers - Show tables
|| Tables in documents should be rendered.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8136 8136] - [FEA] Office viewers - View Microsoft Office 2000 & 2003 documents
|| The engine shall support opening and rendering of Microsoft Office 2000 and 2003 Word, Excel and Powerpoint documents.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8137 8137] - [FEA] Office viewers - View Microsoft Office 2007 documents
|| Opening and rendering MS Office 2007 documents (Word, Excel & PowerPoint) should be supported
Main features supported: Word, Excel, PPT, text, images, tables
Main features NOT-supported: macros, embedded video, rich styling.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8138 8138] - [FEA] Office viewers - View most common charts
|| Engine shall support rendering basic charts in all office documents.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8139 8139] - [FEA] Office viewers - View most common diagrams
|| Engine shall support rendering basic Diagrams in Documents.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8140 8140] - [FEA] Office viewers - View Open Document Format (ODF) documents
|| Opening and rendering ODF documents should be supported
* ODF documents include spreadsheets, presentations and word processing documents.
* Supported File types:
.odt = word documents
.ods = spreadsheets
.odp = presentations
* ODF versions supported: 1.1 and earlier
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8141 8141] - [FEA] Office viewers - View PDF documents
|| Opening and rendering PDF documents versions PDF 1.0 to PDF 1.7 should be supported.
Features NOT-supported: Adobe extensions, Forms, password protected PDFs, videos, javascript, comments.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8178 8178] - [FEA] Viewer application for common office document formats
|| An application for viewing and possibly simple editing for common office document formats should be provided.
The formats should include common Microsoft Office formats, Adobe PDF and OpenOffice document formats.
||
|-
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8348 8348] - [FEA] [MASTER] Office Viewers
|| Master Requirement for Office Viewers - see dependencies for functional detail.
||
|-
|| Backup and Restore
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=8804 8804] - [FEA] UI for Backup and Restore
|| Backup and Restore backend needs UI.
||
|-
|| I18n and L10n
|
* Feature [http://bugs.meego.com/show_bug.cgi?id=9247 9247] - [FEA] [I18N] Applets 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==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}

==Test Strategy and Approach==
'''''Test Strategy'''''

Test will cover all features derivered from Applets application,based on user experience and applets' own functionality.
* '''Test from UI''': to check if clock,alarm,office viewers as well as backup and restore could work correctly from UI. E.g, check if clock is able to be launched to main window; if common office documents can be opened successfully by Office viewers etc.
* '''Usage Model test''': to check if clock,alarm,office viewers as well as backup and restore 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 common UI operation. It also includes i18n/l10n test.
* Functionality verification, collaboration with different settings.
'''''We will also cover the following functionality test:'''''
* Relative UI changes
* Stress and Negative testing to ensure the stability,the applets can basic work without crash.

==Test Design==
Test Design is based on [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design usage Model].According to the usage model, 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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
| Clock
|[http://bugs.meego.com/show_bug.cgi?id=3062 3062] - [FEA] Clock application
|
*Check layout:
**Display the clock application icon
**Launch/Exit clock
**Main window and each target screen layout
**Default theme layout
**Portrait and Landscape layout
*Default actions available from navigation key are also available from options menu
*Check show the current time,location and the timezone,add/delete world clock/locations
*Check could work fine after interrupted by other applications,e.g incoming messages or calls etc.
|
* System UI
* Theme
* Virtual and Hardware Keyboard
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press)

|-
| Alarm
|
:[http://bugs.meego.com/show_bug.cgi?id=7230 7230] - [FEA] Clock applications alarm functionality
:[http://bugs.meego.com/show_bug.cgi?id=11435 11435] - [FEA] Power up & shutdown - Alarm wake
|
*Check layout:
**Display the alarm application icon
**Launch/Exit alarm
**Main window and each target screen layout
**Portrait and Landscape layout
**Default theme layout
*Default actions available from navigation key are also available from options menu
*Check show the alarms,add/delete/save/cancel alarm,turn on/off alarm
*Modify the alarm name,time,snooze,alarm type as well as active Days
*Check the system can wake from off state when a user-set alarm goes off
*Check could work fine after interrupted by other applications,e.g incoming messages or calls etc.
|
* System UI
* Theme
* Virtual and Hardware Keyboard
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press)

|-
| Office viewers
|
:[http://bugs.meego.com/show_bug.cgi?id=8126 8126] - [FEA] Application interworking
:[http://bugs.meego.com/show_bug.cgi?id=8127 8127] - [FEA] Cancel opening document
:[http://bugs.meego.com/show_bug.cgi?id=8130 8130] - [FEA] Document zooming & panning
:[http://bugs.meego.com/show_bug.cgi?id=8131 8131] - [FEA] Find inside document
:[http://bugs.meego.com/show_bug.cgi?id=8132 8132] - [FEA] Open links in documents
:[http://bugs.meego.com/show_bug.cgi?id=8133 8133] - [FEA] Show embedded content indicator
:[http://bugs.meego.com/show_bug.cgi?id=8134 8134] - [FEA] Show table of contents
:[http://bugs.meego.com/show_bug.cgi?id=8135 8135] - [FEA] Show tables
:[http://bugs.meego.com/show_bug.cgi?id=8136 8136] - [FEA] View Microsoft Office 2000 & 2003 documents
:[http://bugs.meego.com/show_bug.cgi?id=8137 8137] - [FEA] View Microsoft Office 2007 documents
:[http://bugs.meego.com/show_bug.cgi?id=8138 8138] - [FEA] View most common charts
:[http://bugs.meego.com/show_bug.cgi?id=8139 8139] - [FEA] View most common diagrams
:[http://bugs.meego.com/show_bug.cgi?id=8140 8140] - [FEA] View Open Document Format (ODF) documents
:[http://bugs.meego.com/show_bug.cgi?id=8141 8141] - [FEA] View PDF documents
:[http://bugs.meego.com/show_bug.cgi?id=8178 8178] - [FEA] Viewer application for common office document formats
:[http://bugs.meego.com/show_bug.cgi?id=8348 8348] - [FEA] [MASTER] Office Viewers

|
*Check layout:
**Display the application icon
**Launch/Exit
**The layout of main window and each target screen
**Portrait and Landscape layout
**Different themes layout
*Default actions available from navigation key are also available from options menu
*Check can view the 0ffice2000&2003&2007 documents
*Check can view ODF documents
*Check can view PDF documents
*Check can zoom in/out the document
*Support find text in document
*Check can view tables,most common charts and diagrams in documents
*Check open documents as attachments in other apps
*Check Open links inside documents
*Check can show the embeded files within office documents
*Check could work fine after interrupted by other applications,e.g incoming messages or calls etc.
|
* System UI
* Themes
* Virtual and Hardware Keyboard
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press)
* Network connection
|-
| Backup and Restore
|[http://bugs.meego.com/show_bug.cgi?id=8804 8804] - [FEA] UI for Backup and Restore
|
*Check layout
**Display the application icon
**Launch/Exit
**The layout of main window and each target screen
**Portrait and Landscape layout
**Default theme layout
*Default actions available from navigation key are also available from options menu
*Check can create backup point for user data,to local storage
*Check can manual and automatic backup
*Check can restore the data back to a backup point in time
*Check can list the backup point and allow user to remove a specified backup point
*Check if show the Progress Screen when backup and restore
*Check if the data after restored are exactly the same as the data included in the backup point
*Check could work fine after interrupted by other applications,e.g incoming messages or calls etc.
|
* System UI
* Theme
* Virtual and Hardware Keyboard
* Local storage(e.g,SD card, USB mass storage)
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press)

|-
|I18n and L10n
|[http://bugs.meego.com/show_bug.cgi?id=9247 9247] - [FEA] [I18N] Applets shall be internationalized according to the dependencies listed in Core Master 5068.
|Check text internationalization support on Clock,Aalarm,Office viewers as well as Backup and Restore;
* 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 Clock,Alarm,Office viewers,Backup and Restore
* Application name and icon
* Window title
* Text
* Date, time, number format
* Help message
* Embedded link
|
|
|}

==Risk and Dependency==

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
*Backup and Restore [mailto:hongbo.min@intel.com Min hongbo]

==References==
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design Usage Model]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2011-01-04T06:30:00Z

Cathyli: /* Test Strategy and Approach */

=MeeGo 1.2 Handset Social Networking Test Plan=

==History ==

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#ebebeb"|'''Date'''
|bgcolor = "#ebebeb"|'''Modification'''

|-
|12/03/2010
|Creation of this wiki

|-
| 
| 

|}

==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

==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 and priority of each features were defined. Test design tables are drafted below, and which will become the base to design test cases.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB/HWKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in PRC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

==Reference==
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design Usage Model]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2011-01-04T06:29:22Z

Cathyli: /* Test Strategy and Approach */

=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

|-
| 
| 

|}

==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 [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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
|[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
| 
| 

|}

==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==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto: TBD]

==Reference==
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design Usage Model]

Quality/Plans/Handset UX test plan

2010-12-22T01:06:17Z

Cathyli: /* Component Test Plans */

= MeeGo HandSet UX Test Plan =

== Introduction ==

This is overall test plan for MeeGo HandSet UX of MeeGo open source project, which defines overall Quality Assurance procedure of validation activities done for MeeGo HandSet UX release. A series of component and system test plans will also be linked in this overall test plan to cover detailed test approaches. This will be joint effort from MeeGo QA Handset UX team.

=== Objectives ===

Objectives in MeeGo HandSet UX software testing is to validate the functionality of entire MeeGo HandSet UX software delivery by performing daily and weekly testing for software releases. Target is to ensure that

* Planned and delivered features for MeeGo release HandSet UX are working as specified as a part of system.
* Validate that relevant bugs are fixed in software release.
* Program maturity statement can be and is given.

=== Goal ===

The goal is to deliver software release with no open bugs with a priority level of high and a minimal number of open bugs with priority level medium.

== Test Strategy and Approach ==

=== Introduction ===

Application is launched from Graphical User Interface and features are used inside application to see that how those are working inside application. Also in system testing applications are used simultaneously to see how applications are interacting as part of system.

Overall procedure in Quality Assurance for MeeGo HandSet UX is as following

* Firstly decompose features to component, each will be associated with one component test plan
* Ensure testability of planned features forming component
* Write test design in component test plan
* Define and store (to Test Link) test cases for features
* Connect test cases to features in test management tool
* Prioritize test cases to form test sets
* Review test plan and test cases
* Automate test cases and add tests to fully automated test infrastructure
* Execute test cases in test sets for software releases following test execution and feature releasing plan
* Report test results and raise relevant bugs
* Provide maturity statement for main releases based on received test results

=== Feature Test and System Test ===

QA target is to validate MeeGo distribution
* Feature functionality
* System functionality (Interaction and negative scenarios)
* System performance
* System reliability

Following chart illuminates scope and relationship of feature and system testing.

==== Feature Testing ====
* Target is to test full functionality of specified feature forming component (e.g. Dialer) following the features' definition in featurezilla. Test case example: Make a phone call
* Every component (formed by features) basic functionality is tested in feature test set
* Each test component will be documented in component test plan. Test plans will cover all testing aspects for specific component/feature(s).

==== System Testing ====
* Target is to test basic (functional) system testing of several components/features simultaneously. Test case example: Listening music while receiving incoming call
* Target is to test system testing (performance). Test case example: Open dialer application (Target value 0.1 sec)
* Target is to test system testing (reliability). Test case example: Make 200 calls (Target 199 pass, 1 fail)
* System Test Plans are created as separate test plans containing both Functional and Non-Functional System Testing aspects

=== Testability ===

Testability of MeeGo HandSet UX features are ensured at first.
* Features are defined by Product Management and relevant stakeholders to Bugzilla tool.
* Selected Quality Assurance Owners are checking those features through from Bugzilla against defined Testability Checklist and adding comment to feature in Bugzilla that can feature be used as QA input and it is possible validate in software release with relevant test case(s). Also more information is requested from Feature owner if it is seen insufficient from QA perspective.

Relevant Links
* http://bugs.meego.com/ (MeeGo UX HandSet Features are stored in Bugzilla)
* http://wiki.meego.com/Quality/TestabilityChecklist
* http://wiki.meego.com/Quality/HandsetTestabilityStatus

=== Test Cases ===

Test Cases are designed by QA owners based on existing features and which have been approved from testability point of view. Test Cases itself are internally stored to TestLink tool. Common Test Case Template is used when designing test cases. Test cases are released publicly in MeeGo Gitorious under Handset UX Tests part.

* Overall test design process and guideline from features to actual test cases can be found http://wiki.meego.com/Quality/TestDesignProcessAndGuideline

Relevant Links
* http://wiki.meego.com/TestCaseTemplate
* http://gitorious.org/qa-tools/

=== Coverage ===

When features forming components are analysed and test cases are designed based on those also coverage matrix will be created for each component. From coverage matrix it can be seen that what is feature coverage i.e. planned test cases vs. maximum amount of test cases to cover every user scenarios from component/feature.

Relevant Links
* <Coverage Matrix Template>
* <Coverage Matrix for MeeGo HandSet UX component/features>

==== Features to be Tested ====
* Overall the MeeGo HandSet UX Testing will cover the MeeGo HandSet UX layer in [http://meego.com/developers/meego-architecture MeeGo Architecture]:
[[File:MeeGoArch.png]]

* Specific components/features to be tested will be aligned with the features under MeeGo HandSet Features product in [http://bugs.meego.com MeeGo Featurezilla @ Bugzilla]

==== Features not to be Tested ====
* List of exact features not to be tested can be found from Featurezilla @ Bugzilla. One must use Testability query there to have full list identified.
** [http://bugs.meego.com/report.cgi?x_axis_field=cf_testability&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Handset+Features&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Testability in Featurezilla (1.2)]

=== Configurations ===

MeeGo HandSet UX is tested in a number of reference devices. The public reference configurations used for this release are
* [http://meego.com/devices/handset/handset-supported-hardware Supported Hardware]

=== Test Sets, Definitions and Priorization ===

Test sets are formed to Test Management Tool by using specific field inside the tool. Test sets that are formed are
* Acceptance/Sanity Test
** Acceptance/Sanity test set is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance/sanity test reflects the most important and basic functionalities of the distribution.
** Acceptance and Sanity test sets are relatively stable and will be run on daily basis.
* Feature Test
** Key Feature Test Set is used to verify MeeGo Handset UX most critical key use cases functionalities with well selected basic feature test cases.
** Basic Feature Test Set is verifying MeeGo HandSet UX delivered features with basic feature test cases. Test set is always static to show overall feature functionalities progress and maturity of the entire MeeGo distribution. Based on test results QA is able to identify components with working features to enable extended feature testing and system testing.
** Extended Feature Test Set is used to verify delivery of features forming full functionality of entirely component. After component is fully integrated all component related test cases will be executed for selected weekly release and report out all the bugs against component and it’s features. Extended feature test set will be run again in the upcoming milestone or when significant changes are applied to component and it’s features.
* System Functional
** System Functional Test Set is targeting to evaluate delivered functionalities from system perspective. Test cases are not testing UI or Application itself, instead test cases are testing how whole system is working and interacting with Consumer (end user). Test cases are covering most critical interaction and negative scenarios that consumers will encounter in their daily usage.
* System Non-Functional
** System Performance Test Sets target is to evaluate overall system performance by executing well-selected set of cases from different test areas - for example response and reaction times, use times and frame rate measurements. Test set gives a quick view of system performance from end-user point of view.
** System Reliability Test Sets target is to provide an overview to system reliability by executing iterative tests that focus on the most important and most used end-user features of MeeGo.

Quality Assurance Owners are setting priorities for Test Cases to form these Test Sets to be used for test execution.

More detailed information: http://wiki.meego.com/Quality/TestSetGuideline

=== Test Automation ===
* Testability driver has been selected as Handset UX automation tool
* Main focus in test automation will be in acceptance, sanity and regression testing automisation
* Automated scripts are released in Gitorius: http://gitorious.org/qa-tools/ under Handset UX Tests part

=== Requirement Coverage Visibility ===

* All relevant features are taken from featurezilla @bugzilla and inserted as testing requirements to Test Link-tool requirement interleaf
* Test cases which have been designed against features are then connected under features to show feature coverage

[[File:Feature_TC_Mapping.png]]

* Target is also to be able to show latest test execution status against features

=== Test Execution ===

All automated tests are executed in a MeeGo QA automated environment, and typically test results are available for each build.

Manual tests are executed regularly, but certainly before each release.

In general, MeeGo will be tested from the following different test execution levels.

*http://wiki.meego.com/Quality/TestSetGuideline

=== Test Reporting ===

All MeeGo HandSet UX test results are stored to one place.

* MeeGo Test Repository for HandSet
** http://wiki.meego.com/Quality/HandsetTestReport

Use Test Report Templates can be found: http://wiki.meego.com/TestReportTemplateCollection

=== Milestone Criteria ===

* There will be entry and exit criteria defined for each main milestone (Developer Preview, Feature Complete, Release Candidate and Project Release).
* All materials currently related to milestone quality criteria are stored to http://wiki.meego.com/Release_Engineering/Release_Timeline

== Network Environment ==
* Networking environment needed to conduct testing
** LAN
** WiFi network
** Internet
** 3G network

== Detailed Test Plans ==
To categorize the production requirements and identify the production functionality that will be tested, the product will be broken down to series of requirement set that QA owners are responsible for the validating.

=== Component Test Plans ===

{| border="1"
!| Component
!| QA Owner
!| QA CC-owner
!| Detailed test plan
|-
| Applets || Cathy Li || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2_Handset_Applets_Test_Plan MeeGo 1.2 Handset Applets Test Plan]
|-
| Short Message Service || Mika Ikonen || Lili || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforShortMessageService MeeGo 1.2 Handset SMS Test Plan]
|-
| Dialer || Mika Ikonen || Lili || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforDialer MeeGo 1.2 Handset Dialer Test Plan]
|-
| Media Applications || Jessica Ji || Anssi Takku || [http://wiki.meego.com/Quality/Plans/Meego1.2_media_test_plan MeeGo1.2 Handset Media Applications Test Plan]
|-
| Mozilla Fennec Browser || Anssi Takku || Qin Mu || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforMozillaFennecBrowser MeeGo 1.2 Handset Mozilla Fennec Browser Test Plan]
|-
| Contacts|| Dayu Yang || Mika Ikonen || [http://wiki.meego.com/Quality/Meego_contacts_test_plan_v12 MeeGo1.2 Handset Contacts Test Plan]
|-
| Core UX (Home, Theme, System UI)|| Cathy Li || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2_Handset_CoreUX_TestPlan MeeGo1.2 Handset Core UX Test Plan]
|-
| Social Networking || Cathy Li || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2_Handset_UX_Social_Networking_TestPlan MeeGo1.2 Handset Social Networking Test Plan]
|-
| Compositing Window Manager|| N.N. || N.N. || <link to detailed test plan>
|-
| Application install/uninstall || N.N. || N.N. || No requirement yet.
|-
| Virtual Keyboard || Yi Fu || Anssi Takku || [http://wiki.meego.com/Quality/Plans/Meego1.2_vkb_test_plan/ VKB Test Plan]
|-
| Sync client || Qin Mu || N.N. || [http://wiki.meego.com/Quality/Meego_Handset_SyncUI_TestPlan_v1.2 SyncUI Test Plan]
|-
| Email ||Yi Fu || Mika Ikonen || [http://wiki.meego.com/index.php?title=Quality/Plans/Meego1.2_email_test_plan Email Test Plan]
|-
| Calendar || Dayu Yang || Anssi Takku || [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan_v12 MeeGo1.2 Handset Calendar Test Plan]
|-
| Instant Messaging || Mika Ikonen || Yi Fu || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforInstantMessaging MeeGo 1.2 Handset Instant Messaging test Plan]
|-
| Connectivity UI || Mika Ikonen || N.N. || Currently only one requirement for Internalisation available - NO testplan needed
|-
| Settings || Dayu Yang || Anssi Takku || [http://wiki.meego.com/Quality/Meego_settings_test_plan_v12 MeeGo1.2 Handset Settings Test Plan]
|-
| UI Infrastructure || Mika Ikonen || N.N || [http://wiki.meego.com/Quality/Plans/Handset_UX_test_planUI_infrastructure MeeGo 1.2 Handset UI Infrastructure Test Plan]
|}

=== System Test Plans ===

{| border="1"
!| System Test Plans
!| QA Owner
!| Detailed test plan
|-
| System Functional Test Plan || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforSyFuTe MeeGo 1.2 Handset System Functional Testing Test Plan]
|-
| System Non-Functional Test Plan || Anssi Takku || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforSystemNFT MeeGo 1.2 Handset System NFT Test Plan]
|}

== Dependency and Constraints ==
* Features' testability is a big dependency for test case design.
* Features' integration time line is another dependency for test case design. If features are integrated late, a lot of test cases' debug will be blocked.

== References ==
* QA main wiki: http://wiki.meego.com/Quality
* Feature Testability checklist: http://wiki.meego.com/Quality/TestabilityChecklist
* Testability Status Report: http://wiki.meego.com/Quality/HandsetTestabilityStatus
* Test Case Design Progress Follow-up: http://wiki.meego.com/Quality/HandsetTestSuite
* Test Result Reports: http://wiki.meego.com/Quality/HandsetTestReport
* Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
* Test Design Process and Guideline: http://wiki.meego.com/Quality/TestDesignProcessAndGuideline
* MeeGo Architecture http://meego.com/developers/meego-architecture
* MeeGo Bugzilla: http://bugs.meego.com/
* HandSet UX QA Ramp-Up follow up: http://wiki.meego.com/Quality/HandSetUXRamp-Up1.1

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-13T01:47:31Z

Cathyli: /* Reference */

=MeeGo 1.2 Handset Social Networking Test Plan=

==History ==

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#ebebeb"|'''Date'''
|bgcolor = "#ebebeb"|'''Modification'''

|-
|12/03/2010
|Creation of this wiki

|-
| 
| 

|}

==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

==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 and priority of each features were defined. Test design tables are drafted below, and which will become the base to design test cases.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB/HWKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in PRC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

==Reference==
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design Usage Model]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-13T01:47:22Z

Cathyli: /* Reference */

=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

|-
| 
| 

|}

==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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 [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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
|[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
| 
| 

|}

==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==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto: TBD]

==Reference==
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design Usage Model]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-13T01:46:52Z

Cathyli:

=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

|-
| 
| 

|}

==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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 [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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
|[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
| 
| 

|}

==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==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto: TBD]

==Reference==
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design usage Model]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-13T01:44:51Z

Cathyli:

=MeeGo 1.2 Handset Social Networking Test Plan=

==History ==

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#ebebeb"|'''Date'''
|bgcolor = "#ebebeb"|'''Modification'''

|-
|12/03/2010
|Creation of this wiki

|-
| 
| 

|}

==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

==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 and priority of each features were defined. Test design tables are drafted below, and which will become the base to design test cases.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB/HWKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in PRC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

==Reference==
* [http://wiki.meego.com/Quality/HandsetDeviceUsageModel Handset Test Design usage Model]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-13T01:43:59Z

Cathyli: /* Test Design */

=MeeGo 1.2 Handset Social Networking Test Plan=

==History ==

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#ebebeb"|'''Date'''
|bgcolor = "#ebebeb"|'''Modification'''

|-
|12/03/2010
|Creation of this wiki

|-
| 
| 

|}

==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

==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 and priority of each features were defined. Test design tables are drafted below, and which will become the base to design test cases.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB/HWKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in PRC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-13T01:43:28Z

Cathyli: /* Test Design */

=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

|-
| 
| 

|}

==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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 [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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
|[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
| 
| 

|}

==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==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T08:04:29Z

Cathyli: /* Test Design */

=MeeGo 1.2 Handset Social Networking Test Plan=

==History ==

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#ebebeb"|'''Date'''
|bgcolor = "#ebebeb"|'''Modification'''

|-
|12/03/2010
|Creation of this wiki

|-
| 
| 

|}

==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

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

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB/HWKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in PRC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T06:44:08Z

Cathyli:

=MeeGo 1.2 Handset Social Networking Test Plan=

==History ==

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#ebebeb"|'''Date'''
|bgcolor = "#ebebeb"|'''Modification'''

|-
|12/03/2010
|Creation of this wiki

|-
| 
| 

|}

==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

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

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in PRC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-07T06:43:44Z

Cathyli: /* 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

|-
| 
| 

|}

==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==
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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
|[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
| 
| 

|}

==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==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/Plans/Handset UX test plan

2010-12-07T06:33:15Z

Cathyli: /* Component Test Plans */

= MeeGo HandSet UX Test Plan =

== Introduction ==

This is overall test plan for MeeGo HandSet UX of MeeGo open source project, which defines overall Quality Assurance procedure of validation activities done for MeeGo HandSet UX release. A series of component and system test plans will also be linked in this overall test plan to cover detailed test approaches. This will be joint effort from MeeGo QA Handset UX team.

=== Objectives ===

Objectives in MeeGo HandSet UX software testing is to validate the functionality of entire MeeGo HandSet UX software delivery by performing daily and weekly testing for software releases. Target is to ensure that

* Planned and delivered features for MeeGo release HandSet UX are working as specified as a part of system.
* Validate that relevant bugs are fixed in software release.
* Program maturity statement can be and is given.

=== Goal ===

The goal is to deliver software release with no open bugs with a priority level of high and a minimal number of open bugs with priority level medium.

== Test Strategy and Approach ==

=== Introduction ===

Application is launched from Graphical User Interface and features are used inside application to see that how those are working inside application. Also in system testing applications are used simultaneously to see how applications are interacting as part of system.

Overall procedure in Quality Assurance for MeeGo HandSet UX is as following

* Firstly decompose features to component, each will be associated with one component test plan
* Ensure testability of planned features forming component
* Write test design in component test plan
* Define and store (to Test Link) test cases for features
* Connect test cases to features in test management tool
* Prioritize test cases to form test sets
* Review test plan and test cases
* Automate test cases and add tests to fully automated test infrastructure
* Execute test cases in test sets for software releases following test execution and feature releasing plan
* Report test results and raise relevant bugs
* Provide maturity statement for main releases based on received test results

=== Feature Test and System Test ===

QA target is to validate MeeGo distribution
* Feature functionality
* System functionality (Interaction and negative scenarios)
* System performance
* System reliability

Following chart illuminates scope and relationship of feature and system testing.

==== Feature Testing ====
* Target is to test full functionality of specified feature forming component (e.g. Dialer) following the features' definition in featurezilla. Test case example: Make a phone call
* Every component (formed by features) basic functionality is tested in feature test set
* Each test component will be documented in component test plan. Test plans will cover all testing aspects for specific component/feature(s).

==== System Testing ====
* Target is to test basic (functional) system testing of several components/features simultaneously. Test case example: Listening music while receiving incoming call
* Target is to test system testing (performance). Test case example: Open dialer application (Target value 0.1 sec)
* Target is to test system testing (reliability). Test case example: Make 200 calls (Target 199 pass, 1 fail)
* System Test Plans are created as separate test plans containing both Functional and Non-Functional System Testing aspects

=== Testability ===

Testability of MeeGo HandSet UX features are ensured at first.
* Features are defined by Product Management and relevant stakeholders to Bugzilla tool.
* Selected Quality Assurance Owners are checking those features through from Bugzilla against defined Testability Checklist and adding comment to feature in Bugzilla that can feature be used as QA input and it is possible validate in software release with relevant test case(s). Also more information is requested from Feature owner if it is seen insufficient from QA perspective.

Relevant Links
* http://bugs.meego.com/ (MeeGo UX HandSet Features are stored in Bugzilla)
* http://wiki.meego.com/Quality/TestabilityChecklist
* http://wiki.meego.com/Quality/HandsetTestabilityStatus

=== Test Cases ===

Test Cases are designed by QA owners based on existing features and which have been approved from testability point of view. Test Cases itself are internally stored to TestLink tool. Common Test Case Template is used when designing test cases. Test cases are released publicly in MeeGo Gitorious under Handset UX Tests part.

* Overall test design process and guideline from features to actual test cases can be found http://wiki.meego.com/Quality/TestDesignProcessAndGuideline

Relevant Links
* http://wiki.meego.com/TestCaseTemplate
* http://gitorious.org/qa-tools/

=== Coverage ===

When features forming components are analysed and test cases are designed based on those also coverage matrix will be created for each component. From coverage matrix it can be seen that what is feature coverage i.e. planned test cases vs. maximum amount of test cases to cover every user scenarios from component/feature.

Relevant Links
* <Coverage Matrix Template>
* <Coverage Matrix for MeeGo HandSet UX component/features>

==== Features to be Tested ====
* Overall the MeeGo HandSet UX Testing will cover the MeeGo HandSet UX layer in [http://meego.com/developers/meego-architecture MeeGo Architecture]:
[[File:MeeGoArch.png]]

* Specific components/features to be tested will be aligned with the features under MeeGo HandSet Features product in [http://bugs.meego.com MeeGo Featurezilla @ Bugzilla]

==== Features not to be Tested ====
* List of exact features not to be tested can be found from Featurezilla @ Bugzilla. One must use Testability query there to have full list identified.
** [http://bugs.meego.com/report.cgi?x_axis_field=cf_testability&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Handset+Features&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Testability in Featurezilla (1.2)]

=== Configurations ===

MeeGo HandSet UX is tested in a number of reference devices. The public reference configurations used for this release are
* [http://meego.com/devices/handset/handset-supported-hardware Supported Hardware]

=== Test Sets, Definitions and Priorization ===

Test sets are formed to Test Management Tool by using specific field inside the tool. Test sets that are formed are
* Acceptance/Sanity Test
** Acceptance/Sanity test set is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance/sanity test reflects the most important and basic functionalities of the distribution.
** Acceptance and Sanity test sets are relatively stable and will be run on daily basis.
* Feature Test
** Key Feature Test Set is used to verify MeeGo Handset UX most critical key use cases functionalities with well selected basic feature test cases.
** Basic Feature Test Set is verifying MeeGo HandSet UX delivered features with basic feature test cases. Test set is always static to show overall feature functionalities progress and maturity of the entire MeeGo distribution. Based on test results QA is able to identify components with working features to enable extended feature testing and system testing.
** Extended Feature Test Set is used to verify delivery of features forming full functionality of entirely component. After component is fully integrated all component related test cases will be executed for selected weekly release and report out all the bugs against component and it’s features. Extended feature test set will be run again in the upcoming milestone or when significant changes are applied to component and it’s features.
* System Functional
** System Functional Test Set is targeting to evaluate delivered functionalities from system perspective. Test cases are not testing UI or Application itself, instead test cases are testing how whole system is working and interacting with Consumer (end user). Test cases are covering most critical interaction and negative scenarios that consumers will encounter in their daily usage.
* System Non-Functional
** System Performance Test Sets target is to evaluate overall system performance by executing well-selected set of cases from different test areas - for example response and reaction times, use times and frame rate measurements. Test set gives a quick view of system performance from end-user point of view.
** System Reliability Test Sets target is to provide an overview to system reliability by executing iterative tests that focus on the most important and most used end-user features of MeeGo.

Quality Assurance Owners are setting priorities for Test Cases to form these Test Sets to be used for test execution.

More detailed information: http://wiki.meego.com/Quality/TestSetGuideline

=== Test Automation ===
* Testability driver has been selected as Handset UX automation tool
* Main focus in test automation will be in acceptance, sanity and regression testing automisation
* Automated scripts are released in Gitorius: http://gitorious.org/qa-tools/ under Handset UX Tests part

=== Requirement Coverage Visibility ===

* All relevant features are taken from featurezilla @bugzilla and inserted as testing requirements to Test Link-tool requirement interleaf
* Test cases which have been designed against features are then connected under features to show feature coverage

[[File:Feature_TC_Mapping.png]]

* Target is also to be able to show latest test execution status against features

=== Test Execution ===

All automated tests are executed in a MeeGo QA automated environment, and typically test results are available for each build.

Manual tests are executed regularly, but certainly before each release.

In general, MeeGo will be tested from the following different test execution levels.

*http://wiki.meego.com/Quality/TestSetGuideline

=== Test Reporting ===

All MeeGo HandSet UX test results are stored to one place.

* MeeGo Test Repository for HandSet
** http://wiki.meego.com/Quality/HandsetTestReport

Use Test Report Templates can be found: http://wiki.meego.com/TestReportTemplateCollection

=== Milestone Criteria ===

* There will be entry and exit criteria defined for each main milestone (Developer Preview, Feature Complete, Release Candidate and Project Release).
* All materials currently related to milestone quality criteria are stored to http://wiki.meego.com/Release_Engineering/Release_Timeline

== Network Environment ==
* Networking environment needed to conduct testing
** LAN
** WiFi network
** Internet
** 3G network

== Detailed Test Plans ==
To categorize the production requirements and identify the production functionality that will be tested, the product will be broken down to series of requirement set that QA owners are responsible for the validating.

=== Component Test Plans ===

{| border="1"
!| Component
!| QA Owner
!| QA CC-owner
!| Detailed test plan
|-
| Applets || Cathy Li || Mika Ikonen || The features are just committed and the corresponding test plan will available in 2 weeks.
|-
| Short Message Service || Mika Ikonen || Lili || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforShortMessageService MeeGo 1.2 Handset SMS Test Plan]
|-
| Dialer || Mika Ikonen || Lili || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforDialer MeeGo 1.2 Handset Dialer Test Plan]
|-
| Media Applications || Jessica Ji || Anssi Takku || [http://wiki.meego.com/Quality/Plans/Meego1.2_media_test_plan MeeGo1.2 Handset Media Applications Test Plan]
|-
| Mozilla Fennec Browser || Anssi Takku || Qin Mu || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforMozillaFennecBrowser MeeGo 1.2 Handset Mozilla Fennec Browser Test Plan]
|-
| Contacts|| Dayu Yang || Mika Ikonen || [http://wiki.meego.com/Quality/Meego_contacts_test_plan_v12 MeeGo1.2 Handset Contacts Test Plan]
|-
| Core UX (Home, Theme, System UI)|| Cathy Li || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2_Handset_CoreUX_TestPlan MeeGo1.2 Handset Core UX Test Plan]
|-
| Social Networking || Cathy Li || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2_Handset_UX_Social_Networking_TestPlan MeeGo1.2 Handset Social Networking Test Plan]
|-
| Compositing Window Manager|| N.N. || N.N. || <link to detailed test plan>
|-
| Application install/uninstall || N.N. || N.N. || <link to detailed test plan>
|-
| Virtual Keyboard || Yi Fu || Anssi Takku || [http://wiki.meego.com/Quality/Plans/Meego1.2_vkb_test_plan/ VKB Test Plan]
|-
| Sync client || Qin Mu || N.N. || [http://wiki.meego.com/Quality/Meego_Handset_SyncUI_TestPlan_v1.2 SyncUI Test Plan]
|-
| Email ||Yi Fu || Mika Ikonen || [http://wiki.meego.com/index.php?title=Quality/Plans/Meego1.2_email_test_plan Email Test Plan]
|-
| Calendar || Dayu Yang || Anssi Takku || [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan_v12 MeeGo1.2 Handset Calendar Test Plan]
|-
| Instant Messaging || Mika Ikonen || Yi Fu || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforInstantMessaging MeeGo 1.2 Handset Instant Messaging test Plan]
|-
| Connectivity UI || Mika Ikonen || N.N. || Currently only one requirement for Internalisation available - NO testplan needed
|-
| Settings || Dayu Yang || Anssi Takku || [http://wiki.meego.com/Quality/Meego_settings_test_plan_v12 MeeGo1.2 Handset Settings Test Plan]
|-
| UI Infrastructure || Mika Ikonen || N.N || [http://wiki.meego.com/Quality/Plans/Handset_UX_test_planUI_infrastructure MeeGo 1.2 Handset UI Infrastructure Test Plan]
|}

=== System Test Plans ===

{| border="1"
!| System Test Plans
!| QA Owner
!| Detailed test plan
|-
| System Functional Test Plan || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforSyFuTe MeeGo 1.2 Handset System Functional Testing Test Plan]
|-
| System Non-Functional Test Plan || Anssi Takku || [http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforSystemNFT MeeGo 1.2 Handset System NFT Test Plan]
|}

== Dependency and Constraints ==
* Features' testability is a big dependency for test case design.
* Features' integration time line is another dependency for test case design. If features are integrated late, a lot of test cases' debug will be blocked.

== References ==
* QA main wiki: http://wiki.meego.com/Quality
* Feature Testability checklist: http://wiki.meego.com/Quality/TestabilityChecklist
* Testability Status Report: http://wiki.meego.com/Quality/HandsetTestabilityStatus
* Test Case Design Progress Follow-up: http://wiki.meego.com/Quality/HandsetTestSuite
* Test Result Reports: http://wiki.meego.com/Quality/HandsetTestReport
* Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
* Test Design Process and Guideline: http://wiki.meego.com/Quality/TestDesignProcessAndGuideline
* MeeGo Architecture http://meego.com/developers/meego-architecture
* MeeGo Bugzilla: http://bugs.meego.com/
* HandSet UX QA Ramp-Up follow up: http://wiki.meego.com/Quality/HandSetUXRamp-Up1.1

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T06:11:08Z

Cathyli: /* Risk and Dependency */

=MeeGo 1.2 Handset Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

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

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in PRC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T06:10:48Z

Cathyli: /* Risk and Dependency */

=MeeGo 1.2 Handset Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

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

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Following social networking services are not unavailable in RPC: twitter, facebook, bebo, vimeo etc.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T06:10:08Z

Cathyli: /* Test Design */

=MeeGo 1.2 Handset Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

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

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks.
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if last.fm context menu (View on Last.fm, Remove from timeline) works
* Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work
* Check if settings for last.fm and twitter.com work
* Check if support individual update view for last.fm and twitter.com
|
* Home Screen
* Web browser
* Settings
* VKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T06:06:51Z

Cathyli: /* Test Design */

=MeeGo 1.2 Handset Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.2 HandSet Social networking application. 
'''Social Networking''' is an application integrates with some popular social networking web services for the MeeGo system, to allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| Social Networking
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Usage Model test''': check social networking web services functionalities and interactive with home screen work correctly by touch gestures from user perspective.
* '''Test from UI''': to ensure all GUI functionality for social networking are correct and visual effect are consistent.

'''''Based on the direction, 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 home screen，web browser　and with related devices.

'''''We will also cover the following functionality test:'''''
* Relative UI changes in social networking application etc.
* Stress and Negative testing to ensure the stability and robust of the social networking.

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

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Social Networking
|
|
* Check Social networking UI, layout (Portrait and Landscape), theme and button response.
* Check if social networking application could be launched and closed in full screen mode and live thumbnail mode
* Check if social networking integrates following web services (Last.fm, twitter) by directly clicking the web service icon.
* Check if social networking accounts (Last.fm, twitter) can be configured and login
* Check if viewing social network postings/feeds ( see your friends' Twitter updates or Last.fm updates) for all libsocialweb-supported social networks with the following functionality work:
** View on social network web page showing update (i.e. if you click a Twitter update, it will take you to the web browser with the Twitter URL for that update loaded)
** Auto-display of twitpic.com-linked pictures in Twitter posts
** Re-tweet functionality
** Reply functionality
** Remove item from view
* Check if corresponding web services objects present on My Friends Panel
* Check if social network status/broadcast timely updated (i.e. post a Twitter update, post a Last.fm update) for all libsocialweb-supported social networks.
* Check if support to upload/share media content with social networks (i.e. share pictures to Picasa).

** Check Social networking UI, layout, theme and button response.
** check if social networking application could be launched and closed in full screen mode and live thumbnail mode.
** Check if social networking accounts (last.fm and twitter) can be configured
** Check if last.fm context menu (View on Last.fm, Remove from timeline) works
** Check if status update and Refresh works
** Check if settings for last.fm and twitter.com work
** Check if support individual update for last.fm and twitter.com
** Check if support to post new twitter status
** Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work

|
* Home Screen
* Web browser
* Settings
* VKB
|
* Orientation (landscape and portrait view)
* Gesture: tap, swipe, tap and hold (long press), drag

|-
|I18n and L10n
| 
|Check text internationalization & Chinese language localization support on social networking application, which covers:
* Application name and icon
* Button label and its icon
* Window title
* Text message
* Date, time format
| 
| 
|}

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* nCDK
* iCDK

===Tools===
* bluetooth devices, wlan devices, network simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==Developers==
* [mailto:james.ausmus@intel.com James Ausmus]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T05:44:00Z

Cathyli:

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-07T05:42:53Z

Cathyli: /* Hardware Platforms */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==
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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
|[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
| 
| 

|}

==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==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T05:42:40Z

Cathyli: /* Hardware Platforms */

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T05:42:28Z

Cathyli: /* Test Environment */

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T05:41:41Z

Cathyli: /* Test Strategy and Approach */

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-07T05:37:18Z

Cathyli: /* Feature to be Tested */

Quality/MeeGo1.2 Handset UX Social Networking TestPlan

2010-12-03T08:51:09Z

Cathyli: Created page with "=MeeGo 1.2 Handset Social Networking Test Plan= ==Component Summary== This test plan is for MeeGo 1.2 HandSet Social networking application. '''Social Networking''' is an a…"

Quality/Plans/Handset UX test plan

2010-12-03T07:10:33Z

Cathyli: /* Component Test Plans */

= MeeGo HandSet UX Test Plan =

== Introduction ==

This is overall test plan for MeeGo HandSet UX of MeeGo open source project, which defines overall Quality Assurance procedure of validation activities done for MeeGo HandSet UX release. A series of component and system test plans will also be linked in this overall test plan to cover detailed test approaches. This will be joint effort from MeeGo QA Handset UX team.

=== Objectives ===

Objectives in MeeGo HandSet UX software testing is to validate the functionality of entire MeeGo HandSet UX software delivery by performing daily and weekly testing for software releases. Target is to ensure that

* Planned and delivered features for MeeGo release HandSet UX are working as specified as a part of system.
* Validate that relevant bugs are fixed in software release.
* Program maturity statement can be and is given.

=== Goal ===

The goal is to deliver software release with no open bugs with a priority level of high and a minimal number of open bugs with priority level medium.

== Test Strategy and Approach ==

=== Introduction ===

Application is launched from Graphical User Interface and features are used inside application to see that how those are working inside application. Also in system testing applications are used simultaneously to see how applications are interacting as part of system.

Overall procedure in Quality Assurance for MeeGo HandSet UX is as following

* Firstly decompose features to component, each will be associated with one component test plan
* Ensure testability of planned features forming component
* Write test design in component test plan
* Define and store (to Test Link) test cases for features
* Connect test cases to features in test management tool
* Prioritize test cases to form test sets
* Review test plan and test cases
* Automate test cases and add tests to fully automated test infrastructure
* Execute test cases in test sets for software releases following test execution and feature releasing plan
* Report test results and raise relevant bugs
* Provide maturity statement for main releases based on received test results

=== Feature Test and System Test ===

QA target is to validate MeeGo distribution
* Feature functionality
* System functionality (Interaction and negative scenarios)
* System performance
* System reliability

Following chart illuminates scope and relationship of feature and system testing.

==== Feature Testing ====
* Target is to test full functionality of specified feature forming component (e.g. Dialer) following the features' definition in featurezilla. Test case example: Make a phone call
* Every component (formed by features) basic functionality is tested in feature test set
* Each test component will be documented in component test plan. Test plans will cover all testing aspects for specific component/feature(s).

==== System Testing ====
* Target is to test basic (functional) system testing of several components/features simultaneously. Test case example: Listening music while receiving incoming call
* Target is to test system testing (performance). Test case example: Open dialer application (Target value 0.1 sec)
* Target is to test system testing (reliability). Test case example: Make 200 calls (Target 199 pass, 1 fail)
* System Test Plans are created as separate test plans containing both Functional and Non-Functional System Testing aspects

=== Testability ===

Testability of MeeGo HandSet UX features are ensured at first.
* Features are defined by Product Management and relevant stakeholders to Bugzilla tool.
* Selected Quality Assurance Owners are checking those features through from Bugzilla against defined Testability Checklist and adding comment to feature in Bugzilla that can feature be used as QA input and it is possible validate in software release with relevant test case(s). Also more information is requested from Feature owner if it is seen insufficient from QA perspective.

Relevant Links
* http://bugs.meego.com/ (MeeGo UX HandSet Features are stored in Bugzilla)
* http://wiki.meego.com/Quality/TestabilityChecklist
* http://wiki.meego.com/Quality/HandsetTestabilityStatus

=== Test Cases ===

Test Cases are designed by QA owners based on existing features and which have been approved from testability point of view. Test Cases itself are internally stored to TestLink tool. Common Test Case Template is used when designing test cases. Test cases are released publicly in MeeGo Gitorious under Handset UX Tests part.

* Overall test design process and guideline from features to actual test cases can be found http://wiki.meego.com/Quality/TestDesignProcessAndGuideline

Relevant Links
* http://wiki.meego.com/TestCaseTemplate
* http://gitorious.org/qa-tools/

=== Coverage ===

When features forming components are analysed and test cases are designed based on those also coverage matrix will be created for each component. From coverage matrix it can be seen that what is feature coverage i.e. planned test cases vs. maximum amount of test cases to cover every user scenarios from component/feature.

Relevant Links
* <Coverage Matrix Template>
* <Coverage Matrix for MeeGo HandSet UX component/features>

==== Features to be Tested ====
* Overall the MeeGo HandSet UX Testing will cover the MeeGo HandSet UX layer in [http://meego.com/developers/meego-architecture MeeGo Architecture]:
[[File:MeeGoArch.png]]

* Specific components/features to be tested will be aligned with the features under MeeGo HandSet Features product in [http://bugs.meego.com MeeGo Featurezilla @ Bugzilla]

==== Features not to be Tested ====
* List of exact features not to be tested can be found from Featurezilla @ Bugzilla. One must use Testability query there to have full list identified.
** [http://bugs.meego.com/report.cgi?x_axis_field=cf_testability&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Handset+Features&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Testability in Featurezilla (1.2)]

=== Configurations ===

MeeGo HandSet UX is tested in a number of reference devices. The public reference configurations used for this release are
* [http://meego.com/devices/handset/handset-supported-hardware Supported Hardware]

=== Test Sets, Definitions and Priorization ===

Test sets are formed to Test Management Tool by using specific field inside the tool. Test sets that are formed are
* Acceptance/Sanity Test
** Acceptance/Sanity test set is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance/sanity test reflects the most important and basic functionalities of the distribution.
** Acceptance and Sanity test sets are relatively stable and will be run on daily basis.
* Feature Test
** Key Feature Test Set is used to verify MeeGo Handset UX most critical key use cases functionalities with well selected basic feature test cases.
** Basic Feature Test Set is verifying MeeGo HandSet UX delivered features with basic feature test cases. Test set is always static to show overall feature functionalities progress and maturity of the entire MeeGo distribution. Based on test results QA is able to identify components with working features to enable extended feature testing and system testing.
** Extended Feature Test Set is used to verify delivery of features forming full functionality of entirely component. After component is fully integrated all component related test cases will be executed for selected weekly release and report out all the bugs against component and it’s features. Extended feature test set will be run again in the upcoming milestone or when significant changes are applied to component and it’s features.
* System Functional
** System Functional Test Set is targeting to evaluate delivered functionalities from system perspective. Test cases are not testing UI or Application itself, instead test cases are testing how whole system is working and interacting with Consumer (end user). Test cases are covering most critical interaction and negative scenarios that consumers will encounter in their daily usage.
* System Non-Functional
** System Performance Test Sets target is to evaluate overall system performance by executing well-selected set of cases from different test areas - for example response and reaction times, use times and frame rate measurements. Test set gives a quick view of system performance from end-user point of view.
** System Reliability Test Sets target is to provide an overview to system reliability by executing iterative tests that focus on the most important and most used end-user features of MeeGo.

Quality Assurance Owners are setting priorities for Test Cases to form these Test Sets to be used for test execution.

More detailed information: http://wiki.meego.com/Quality/TestSetGuideline

=== Test Automation ===
* Testability driver has been selected as Handset UX automation tool
* Main focus in test automation will be in acceptance, sanity and regression testing automisation
* Automated scripts are released in Gitorius: http://gitorious.org/qa-tools/ under Handset UX Tests part

=== Requirement Coverage Visibility ===

* All relevant features are taken from featurezilla @bugzilla and inserted as testing requirements to Test Link-tool requirement interleaf
* Test cases which have been designed against features are then connected under features to show feature coverage

[[File:Feature_TC_Mapping.png]]

* Target is also to be able to show latest test execution status against features

=== Test Execution ===

All automated tests are executed in a MeeGo QA automated environment, and typically test results are available for each build.

Manual tests are executed regularly, but certainly before each release.

In general, MeeGo will be tested from the following different test execution levels.

*http://wiki.meego.com/Quality/TestSetGuideline

=== Test Reporting ===

All MeeGo HandSet UX test results are stored to one place.

* MeeGo Test Repository for HandSet
** http://wiki.meego.com/Quality/HandsetTestReport

Use Test Report Templates can be found: http://wiki.meego.com/TestReportTemplateCollection

=== Milestone Criteria ===

* There will be entry and exit criteria defined for each main milestone (Developer Preview, Feature Complete, Release Candidate and Project Release).
* All materials currently related to milestone quality criteria are stored to http://wiki.meego.com/Release_Engineering/Release_Timeline

== Network Environment ==
* Networking environment needed to conduct testing
** LAN
** WiFi network
** Internet
** 3G network

== Detailed Test Plans ==
To categorize the production requirements and identify the production functionality that will be tested, the product will be broken down to series of requirement set that QA owners are responsible for the validating.

=== Component Test Plans ===

{| border="1"
!| Component
!| QA Owner
!| QA CC-owner
!| Detailed test plan
|-
| Applets || Cathy Li || Mika Ikonen || <link to detailed test plan>
|-
| Short Message Service || Mika Ikonen || Lili || <link to detailed test plan>
|-
| Dialer || Mika Ikonen || Lili || <link to detailed test plan>
|-
| Media Applications || Jessica Ji || Anssi Takku || <link to detailed test plan>
|-
| Mozilla Fennec Browser || Anssi Takku || Qin Mu || <link to detailed test plan>
|-
| Contacts|| Dayu Yang || Mika Ikonen || <link to detailed test plan>
|-
| Core UX (Home, Theme, System UI)|| Cathy Li || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.2_Handset_CoreUX_TestPlan MeeGo1.2 Handset Core UX Test Plan]
|-
| Social Networking || Cathy Li || Mika Ikonen || <link to detailed test plan>
|-
| Compositing Window Manager|| N.N. || N.N. || <link to detailed test plan>
|-
| Application install/uninstall || N.N. || N.N. || <link to detailed test plan>
|-
| Virtual Keyboard || Yi Fu || Anssi Takku || <link to detailed test plan>
|-
| Sync client || Qin Mu || N.N. || <link to detailed test plan>
|-
| Email ||Yi Fu || Mika Ikonen || <link to detailed test plan>
|-
| Calendar || Dayu Yang || Anssi Takku || <link to detailed test plan>
|-
| Instant Messaging || Mika Ikonen || Yi Fu || <link to detailed test plan>
|-
| Connectivity UI || Mika Ikonen || N.N. || <link to detailed test plan>
|-
| Settings || Dayu Yang || Anssi Takku || <link to detailed test plan>
|-
| UI Infrastructure || Mika Ikonen || N.N || <link to detailed test plan>

|}

=== System Test Plans ===

{| border="1"
!| System Test Plans
!| QA Owner
!| Detailed test plan
|-
| System Functional Test Plan || Mika Ikonen || <link to detailed test plan>
|-
| System Non-Functional Test Plan || Anssi Takku || <link to detailed test plan>
|}

== Dependency and Constraints ==
* Features' testability is a big dependency for test case design.
* Features' integration time line is another dependency for test case design. If features are integrated late, a lot of test cases' debug will be blocked.

== References ==
* QA main wiki: http://wiki.meego.com/Quality
* Feature Testability checklist: http://wiki.meego.com/Quality/TestabilityChecklist
* Testability Status Report: http://wiki.meego.com/Quality/HandsetTestabilityStatus
* Test Case Design Progress Follow-up: http://wiki.meego.com/Quality/HandsetTestSuite
* Test Result Reports: http://wiki.meego.com/Quality/HandsetTestReport
* Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
* Test Design Process and Guideline: http://wiki.meego.com/Quality/TestDesignProcessAndGuideline
* MeeGo Architecture http://meego.com/developers/meego-architecture
* MeeGo Bugzilla: http://bugs.meego.com/
* HandSet UX QA Ramp-Up follow up: http://wiki.meego.com/Quality/HandSetUXRamp-Up1.1

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T03:31:45Z

Cathyli: /* Test Design */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==
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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
|[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
| 
| 

|}

==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===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T03:30:19Z

Cathyli: /* References */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==
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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
| 
|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===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T03:29:49Z

Cathyli: /* Test Design */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==
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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
| 
|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===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T03:28:33Z

Cathyli: /* Test Design */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==
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.

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|bgcolor = "#dcffff"|'''Feature Category'''
|bgcolor = "#dcffff"|'''Feature ID-description'''
|bgcolor = "#dcffff"|'''Test Points'''
|bgcolor = "#dcffff"|'''Collaboration'''
|bgcolor = "#dcffff"|'''Conditions'''

|-
|Home Screen
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2680 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
|[https://bugzilla.otcshare.org/show_bug.cgi?id=2685 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
| 
|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===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T02:47:10Z

Cathyli: /* Risk and Dependency */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T02:46:01Z

Cathyli: /* Test Strategy and Approach */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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 direction, 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T02:43:16Z

Cathyli: /* Feature to be Tested */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T02:32:18Z

Cathyli: /* Feature to be Tested */

=Core UX Test Plan=
==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==
{|border="1" cellspacing="0" cellpadding="4" width="90%"
|bgcolor = "#dcffff"|'''Feature Name'''
|bgcolor = "#dcffff"|'''Detailed Feature Description'''
|bgcolor = "#dcffff"|'''Comments'''
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 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 [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:
* 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 [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
|| 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==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T02:17:38Z

Cathyli: /* Component Summary */

=Core UX Test Plan=
==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==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework
||
* Home screen main page UI, layout and button response check
* Application launcher UI UI, layout and button response check
* Open/close application launcher
* Launch/close application from application launcher
* Switch between running applications with home screen
* 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
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|-
| '''Theme''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine
||
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
* Home default theme
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
||
|-
| '''System UI''' ||
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
* Open/Close System UI drop down menu
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
* Volume status and value adjustment (TBD)
* Invoke Settings application
|| No feature request for system UI
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T01:33:53Z

Cathyli: /* Feature to be Tested */

=Core UX Test Plan=
==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.
* '''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.
* '''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==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework
||
* Home screen main page UI, layout and button response check
* Application launcher UI UI, layout and button response check
* Open/close application launcher
* Launch/close application from application launcher
* Switch between running applications with home screen
* 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
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|-
| '''Theme''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine
||
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
* Home default theme
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
||
|-
| '''System UI''' ||
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
* Open/Close System UI drop down menu
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
* Volume status and value adjustment (TBD)
* Invoke Settings application
|| No feature request for system UI
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T01:32:36Z

Cathyli: /* Feature to be Tested */

=Core UX Test Plan=
==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.
* '''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.
* '''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==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| '''Home''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework
||
* Home screen main page UI, layout and button response check
* Application launcher UI UI, layout and button response check
* Open/close application launcher
* Launch/close application from application launcher
* Switch between running applications with home screen
* 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
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|-
| '''Theme''':
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine
||
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
* Home default theme
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
||
|-
| '''System UI''' ||
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
* Open/Close System UI drop down menu
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
* Volume status and value adjustment (TBD)
* Invoke Settings application
|| No feature request or UI design wireframe for system UI
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T01:31:46Z

Cathyli: /* Component Summary */

=Core UX Test Plan=
==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.
* '''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.
* '''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==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Home:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework
||
* Home screen main page UI, layout and button response check
* Application launcher UI UI, layout and button response check
* Open/close application launcher
* Launch/close application from application launcher
* Switch between running applications with home screen
* 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
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|-
| Theme:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine
||
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
* Home default theme
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
||
|-
| System UI ||
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
* Open/Close System UI drop down menu
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
* Volume status and value adjustment (TBD)
* Invoke Settings application
|| No feature request or UI design wireframe for system UI
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-12-03T01:27:13Z

Cathyli: /* References */

=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 Framework (MTF)''' (a full set of widgets and window manager), '''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.
* '''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.
* '''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==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Home:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework
||
* Home screen main page UI, layout and button response check
* Application launcher UI UI, layout and button response check
* Open/close application launcher
* Launch/close application from application launcher
* Switch between running applications with home screen
* 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
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|-
| Theme:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine
||
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
* Home default theme
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
||
|-
| System UI ||
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
* Open/Close System UI drop down menu
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
* Volume status and value adjustment (TBD)
* Invoke Settings application
|| No feature request or UI design wireframe for system UI
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* iCDK
* nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
* [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]

Quality/MeeGo1.2 Handset CoreUX TestPlan

2010-11-25T08:51:48Z

Cathyli: 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 …"

=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 Framework (MTF)''' (a full set of widgets and window manager), '''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.
* '''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.
* '''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==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Home:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework
||
* Home screen main page UI, layout and button response check
* Application launcher UI UI, layout and button response check
* Open/close application launcher
* Launch/close application from application launcher
* Switch between running applications with home screen
* 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
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|-
| Theme:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine
||
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
* Home default theme
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
||
|-
| System UI ||
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
* Open/Close System UI drop down menu
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
* Volume status and value adjustment (TBD)
* Invoke Settings application
|| No feature request or UI design wireframe for system UI
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* Medfield iCDK
* Medfield nCDK

===Tools===
* bluetooth devices, wlan devices, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

==References==
* [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
* [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]

Quality/Plans/Handset UX test plan

2010-11-17T06:27:36Z

Cathyli: /* Feature Test Plans */

= MeeGo HandSet UX Test Plan =

== Introduction ==

This is overall test plan for MeeGo HandSet UX of MeeGo open source project, which defines overall Quality Assurance procedure of validation activities done for MeeGo HandSet UX release. A series of component and system test plans will also be linked in this overall test plan to cover detailed test approaches. This will be joint effort from MeeGo QA Handset UX team.

=== Objectives ===

Objectives in MeeGo HandSet UX software testing is to validate the functionality of entire MeeGo HandSet UX software delivery by performing daily and weekly testing for software releases. Target is to ensure that

* Planned and delivered features for MeeGo release HandSet UX are working as specified as a part of system.
* Validate that relevant bugs are fixed in software release.
* Program maturity statement can be and is given.

=== Goal ===

The goal is to deliver software release with no open bugs with a priority level of high and a minimal number of open bugs with priority level medium.

== Test Strategy and Approach ==

=== Introduction ===

Application is launched from Graphical User Interface and features are used inside application to see that how those are working inside application. Also in system testing applications are used simultaneously to see how applications are interacting as part of system.

Overall procedure in Quality Assurance for MeeGo HandSet UX is as following

* Firstly decompose features to component, each will be associated with one component test plan
* Ensure testability of planned features forming component
* Write test design in component test plan
* Define and store (to Test Link) test cases for features
* Connect test cases to features in test management tool
* Prioritize test cases to form test sets
* Review test plan and test cases
* Automate test cases and add tests to fully automated test infrastructure
* Execute test cases in test sets for software releases following test execution and feature releasing plan
* Report test results and raise relevant bugs
* Provide maturity statement for main releases based on received test results

=== Feature Test and System Test ===

QA target is to validate MeeGo distribution
* Feature functionality
* System functionality (Interaction and negative scenarios)
* System performance
* System reliability

Following chart illuminates scope and relationship of feature and system testing.

==== Feature Testing ====
* Target is to test full functionality of specified feature forming component (e.g. Dialer) following the features' definition in featurezilla. Test case example: Make a phone call
* Every component (formed by features) basic functionality is tested in feature test set
* Each test component will be documented in component test plan. Test plans will cover all testing aspects for specific component/feature(s).

==== System Testing ====
* Target is to test basic (functional) system testing of several components/features simultaneously. Test case example: Listening music while receiving incoming call
* Target is to test system testing (performance). Test case example: Open dialer application (Target value 0.1 sec)
* Target is to test system testing (reliability). Test case example: Make 200 calls (Target 199 pass, 1 fail)
* System Test Plans are created as separate test plans containing both Functional and Non-Functional System Testing aspects

=== Testability ===

Testability of MeeGo HandSet UX features are ensured at first.
* Features are defined by Product Management and relevant stakeholders to Bugzilla tool.
* Selected Quality Assurance Owners are checking those features through from Bugzilla against defined Testability Checklist and adding comment to feature in Bugzilla that can feature be used as QA input and it is possible validate in software release with relevant test case(s). Also more information is requested from Feature owner if it is seen insufficient from QA perspective.

Relevant Links
* http://bugs.meego.com/ (MeeGo UX HandSet Features are stored in Bugzilla)
* http://wiki.meego.com/Quality/TestabilityChecklist
* http://wiki.meego.com/Quality/HandsetTestabilityStatus

=== Test Cases ===

Test Cases are designed by QA owners based on existing features and which have been approved from testability point of view. Test Cases itself are internally stored to TestLink tool. Common Test Case Template is used when designing test cases. Test cases are released publicly in MeeGo Gitorious under Handset UX Tests part.

* Overall test design process and guideline from features to actual test cases can be found http://wiki.meego.com/Quality/TestDesignProcessAndGuideline

Relevant Links
* http://wiki.meego.com/TestCaseTemplate
* http://gitorious.org/qa-tools/

=== Coverage ===

When features forming components are analysed and test cases are designed based on those also coverage matrix will be created for each component. From coverage matrix it can be seen that what is feature coverage i.e. planned test cases vs. maximum amount of test cases to cover every user scenarios from component/feature.

Relevant Links
* <Coverage Matrix Template>
* <Coverage Matrix for MeeGo HandSet UX component/features>

==== Features to be Tested ====
* Overall the MeeGo HandSet UX Testing will cover the MeeGo HandSet UX layer in [http://meego.com/developers/meego-architecture MeeGo Architecture]:
[[File:MeeGoArch.png]]

* Specific components/features to be tested will be aligned with the features under MeeGo HandSet Features product in [http://bugs.meego.com MeeGo Featurezilla @ Bugzilla]

==== Features not to be Tested ====
* List of exact features not to be tested can be found from Featurezilla @ Bugzilla. One must use Testability query there to have full list identified.
** [http://bugs.meego.com/report.cgi?x_axis_field=cf_testability&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Handset+Features&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Testability in Featurezilla (1.2)]

=== Configurations ===

MeeGo HandSet UX is tested in a number of reference devices. The public reference configurations used for this release are
* [http://meego.com/devices/handset/handset-supported-hardware Supported Hardware]

=== Test Sets, Definitions and Priorization ===

Test sets are formed to Test Management Tool by using specific field inside the tool. Test sets that are formed are
* Acceptance/Sanity Test
** Acceptance/Sanity test set is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in acceptance/sanity test reflects the most important and basic functionalities of the distribution.
** Acceptance and Sanity test sets are relatively stable and will be run on daily basis.
* Feature Test
** Key Feature Test Set is used to verify MeeGo Handset UX most critical key use cases functionalities with well selected basic feature test cases.
** Basic Feature Test Set is verifying MeeGo HandSet UX delivered features with basic feature test cases. Test set is always static to show overall feature functionalities progress and maturity of the entire MeeGo distribution. Based on test results QA is able to identify components with working features to enable extended feature testing and system testing.
** Extended Feature Test Set is used to verify delivery of features forming full functionality of entirely component. After component is fully integrated all component related test cases will be executed for selected weekly release and report out all the bugs against component and it’s features. Extended feature test set will be run again in the upcoming milestone or when significant changes are applied to component and it’s features.
* System Functional
** System Functional Test Set is targeting to evaluate delivered functionalities from system perspective. Test cases are not testing UI or Application itself, instead test cases are testing how whole system is working and interacting with Consumer (end user). Test cases are covering most critical interaction and negative scenarios that consumers will encounter in their daily usage.
* System Non-Functional
** System Performance Test Sets target is to evaluate overall system performance by executing well-selected set of cases from different test areas - for example response and reaction times, use times and frame rate measurements. Test set gives a quick view of system performance from end-user point of view.
** System Reliability Test Sets target is to provide an overview to system reliability by executing iterative tests that focus on the most important and most used end-user features of MeeGo.

Quality Assurance Owners are setting priorities for Test Cases to form these Test Sets to be used for test execution.

More detailed information: http://wiki.meego.com/Quality/TestSetGuideline

=== Test Automation ===
* Testability driver has been selected as Handset UX automation tool
* Main focus in test automation will be in acceptance, sanity and regression testing automisation
* Automated scripts are released in Gitorius: http://gitorious.org/qa-tools/ under Handset UX Tests part

=== Requirement Coverage Visibility ===

* All relevant features are taken from featurezilla @bugzilla and inserted as testing requirements to Test Link-tool requirement interleaf
* Test cases which have been designed against features are then connected under features to show feature coverage

[[File:Feature_TC_Mapping.png]]

* Target is also to be able to show latest test execution status against features

=== Test Execution ===

All automated tests are executed in a MeeGo QA automated environment, and typically test results are available for each build.

Manual tests are executed regularly, but certainly before each release.

In general, MeeGo will be tested from the following different test execution levels.

*http://wiki.meego.com/Quality/TestSetGuideline

=== Test Reporting ===

All MeeGo HandSet UX test results are stored to one place.

* MeeGo Test Repository for HandSet
** http://wiki.meego.com/Quality/HandsetTestReport

Use Test Report Templates can be found: http://wiki.meego.com/TestReportTemplateCollection

=== Milestone Criteria ===

* There will be entry and exit criteria defined for each main milestone (Developer Preview, Feature Complete, Release Candidate and Project Release).
* All materials currently related to milestone quality criteria are stored to http://wiki.meego.com/Release_Engineering/Release_Timeline

== Network Environment ==
* Networking environment needed to conduct testing
** LAN
** WiFi network
** Internet
** 3G network

== Detailed Test Plans ==
To categorize the production requirements and identify the production functionality that will be tested, the product will be broken down to series of requirement set that QA owners are responsible for the validating.

=== Feature Test Plans ===

{| border="1"
!| Application
!| QA Owner
!| Detailed test plan
|-
| Applets || Cathy Li || <link to detailed test plan>
|-
| Short Message Service || Mika Ikonen || <link to detailed test plan>
|-
| Dialer || Mika Ikonen || <link to detailed test plan>
|-
| Media Applications || Jessica Ji || <link to detailed test plan>
|-
| Mozilla Fennec Browser || Petri Jylha || <link to detailed test plan>
|-
| Contacts|| Dayu Yang || <link to detailed test plan>
|-
| Core UX (Home, Theme, System UI)|| Cathy Li || <link to detailed test plan>
|-
| Social Networking || Cathy Li || <link to detailed test plan>
|-
| Compositing Window Manager|| N.N. || <link to detailed test plan>
|-
| Application install/uninstall || N.N. || <link to detailed test plan>
|-
| Virtual Keyboard || Yi Fu || <link to detailed test plan>
|-
| PIM Management (Clock and Sync client) || Qin Mu || <link to detailed test plan>
|-
| Email ||Yi Fu || <link to detailed test plan>
|-
| Calendar || Dayu Yang || <link to detailed test plan>
|-
| Instant Messaging || Mika Ikonen || <link to detailed test plan>
|}

=== System Test Plans ===

{| border="1"
!| System Test Plans
!| QA Owner
!| Detailed test plan
|-
| System Functional Test Plan || Mika Ikonen || <link to detailed test plan>
|-
| System Non-Functional Test Plan || Anssi Tasku || <link to detailed test plan>
|}

== Dependency and Constraints ==
* Features' testability is a big dependency for test case design.
* Features' integration time line is another dependency for test case design. If features are integrated late, a lot of test cases' debug will be blocked.

== References ==
* QA main wiki: http://wiki.meego.com/Quality
* Feature Testability checklist: http://wiki.meego.com/Quality/TestabilityChecklist
* Testability Status Report: http://wiki.meego.com/Quality/HandsetTestabilityStatus
* Test Case Design Progress Follow-up: http://wiki.meego.com/Quality/HandsetTestSuite
* Test Result Reports: http://wiki.meego.com/Quality/HandsetTestReport
* Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
* Test Design Process and Guideline: http://wiki.meego.com/Quality/TestDesignProcessAndGuideline
* MeeGo Architecture http://meego.com/developers/meego-architecture
* MeeGo Bugzilla: http://bugs.meego.com/
* HandSet UX QA Ramp-Up follow up: http://wiki.meego.com/Quality/HandSetUXRamp-Up1.1

Quality/TestSuite/handset-test-suite

2010-09-16T07:00:23Z

Cathyli: /* Test Suite Design Progress */

== Test Suite Design Progress ==
Follow-up table for HandSet UX 1.1 Test Case creation progress.

* Planned Test: test cases are planned to be developed
* Actual Test - Designed: actual designed test cases
* Actual Test - Ready: test cases that are ready to run currently

{| border="1"
!
! Planned Test
! Actual Test - Designed
! Actual Test - Ready
! Automation %
! Test Suite Due
! Cross Review
! Test Suite Maintainer
! QA CCed
! Comments
|-
|Photo Viewer
|87
|9
|78
|0
|TBD
|Not Started
|Jessica Ji (Intel)
|Kalle Kyllönen (Nokia)
|To be updated
|-
|Audio Player
|110
|7
|103
|0
|TBD
|Not Started
|Jessica Ji (Intel)
|Juha Paukku (Nokia)
|To be updated
|-
|Video Player
|68
|7
|61
|0
|TBD
|Not Started
|Jessica Ji (Intel)
|Kalle Kyllönen (Nokia)
|To be updated
|-
|Contacts / Address Book
|149
|33
|116
|0
|End Of August
|Not Started
|Dayu Yang (Intel)
|Kalle Kyllönen (Nokia)
|To be updated
|-
|Email
|89
|29
|60
|0
|End Of August
|Not Started
|Yi Fu (Intel)
|Mika Ikonen (Nokia)
|To be updated
|-
|Core UX
|134
|16
|118
|0
|End Of August except systemUI
|Not Started
|Cathy Li (Intel)
|Juha Paukku (Nokia)
|No feature request or UI design doc for system UI. System UI test cases are based on real implementation in current stage.
|-
|Settings
|50
|26
|6
|0
|TBD
|Not Started
|Dayu Yang (Intel)
|Juha Paukku (Nokia)
|We have got the feature request in WW35, test cases are under development now
|-
|VKB
|50
|35
|15
|0
|End Of August
|Not Started
|Yi Fu (Intel)
|Juha Paukku (Nokia)
|To be updated
|-
|Calendar
|87
|0
|87
|0
|End Of August
|Not Started
|Dayu Yang (Intel)
|Juha Paukku (Nokia)
|To be updated
|-
|Social Networking
|40
|0
|40
|0
|TBD
|Not Started
|Cathy Li (Intel)
|Juha Paukku (Nokia)
|No feature request or UI design doc for social networking.
|-
|Data Sync
|30
|30
|0
|0
|TBD
|Not Started
|Qin Mu (Intel)
|Mika Ikonen (Nokia)
|To be updated
|-
|System functional
|207
|107
|100
|0
|TBD
|Not Started
|Qin Mu (Intel)
|To be updated
|To be updated
|-
|Dialer
|60
|60
|20
|0
|End Of August
|Not Started
|Mika Ikonen (Nokia)
|Lily (Intel)
|To be updated
|-
|SMS
|40
|40
|15
|0
|End Of August
|Not Started
|Mika Ikonen (Nokia)
|Lily (Intel)
|To be updated
|-
|Browser
|100
|100
|50
|0
|End Of August
|Not Started
|Petri Jylhä (Nokia)
|Qin Mu (Intel)
|To be updated
|-
|Networking
|50
|50
|30
|0
|End Of August
|Not Started
|Petri Jylhä (Nokia)
|Dayu Yang (Intel)
|To be updated
|-
|Instant Messaging
|15
|21
|27
|0
|End Of August
|Not Started
|Mika Ikonen (Nokia)
|Yi Fu (Intel)
|To be updated
|-
|VoIP
|N/A
|N/A
|N/A
|N/A
|TBD
|Not Started
|Mika Ikonen (Nokia)
|Yi Fu (Intel)
|VoIP has been removed from 1.1 content
|}

Quality/MeeGo1.1 Handset CoreUX TestPlan

2010-09-10T08:27:07Z

=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 Framework (MTF)''' (a full set of widgets and window manager), '''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.
* '''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.
* '''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==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Home:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2680 2680] - [FEA] Meego touch framework
||
* Home screen main page UI, layout and button response check
* Application launcher UI UI, layout and button response check
* Open/close application launcher
* Launch/close application from application launcher
* Switch between running applications with home screen
* 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
|| All sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|-
| Theme:
* Feature [http://bugs.meego.com/show_bug.cgi?id=2685 2685] - [FEA] MeeGo Theme and style engine
||
* Orientation (Portrait, Landscape, 90/180/270 degrees clockwise)
* Home default theme
* Key applications (Dialer, SMS, Settings, Browser, Photo, Music, Video, Contacts) default theme
||
|-
| System UI ||
* Run time status (connectivity, battery status), date&time, notifications appearing on system UI check
* Open/Close System UI drop down menu
* Connectivity (Wifi, bluetooth, 3G, GPS, Airplane) On/Off check
* Volume status and value adjustment (TBD)
* Invoke Settings application
|| No feature request or UI design wireframe for system UI
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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.

'''''Test Type and Approach''''' 

Core UX components are tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Points'''
** Check home screen, application launcher, system UI layout.
** Open/close application launcher
** Launch/close application from application launcher or quick launch bar
** Switch between running applications with home screen
** 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'''
** Check home and key applications default theme
** Update theme to check if it could take effect
** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Points'''
** Check System UI layout. For instance, if correct date/time appears.
** 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
** 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 feature request. 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.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/Plans/1.1 Handset UX TestPlan

2010-09-10T08:22:23Z

Cathyli: /* Detailed Test Plans */

= MeeGo 1.1 HandSet UX Test Plan =

== Introduction ==

This is overall test plan for MeeGo 1.1 HandSet UX of MeeGo open source project, which defines overall Quality Assurance procedure of validation activities done for MeeGo 1.1 HandSet UX release. A series of component test plans will also be linked in this overall test plan to cover detailed test approaches. This will be joint effort from MeeGo QA.

=== Objectives ===

Objectives in MeeGo 1.1 HandSet UX software testing is to validate the functionality of entire MeeGo 1.1 HandSet UX software delivery by performing daily and weekly testing for software releases. Target is to ensure that

* Planned and delivered features for MeeGo 1.1 HandSet UX are working as specified as a part of system.
* Validate that relevant bugs are fixed in software release.
* Program maturity statement can be and is given.

=== Goal ===

The goal is to deliver software release with no open bugs with a priority level of high and a minimal number of open bugs with priority level medium.

== Test Strategy and Approach ==

=== Introduction ===

Application is launched from Graphical User Interface and features are used inside application to see that how those are working inside application. Also in system testing applications are used simultaneously to see how applications are interacting as part of system.

Overall procedure in Quality Assurance for MeeGo 1.1 HandSet UX is as following

* Firstly decompose features to component, each will be associated with one component test plan
* Ensure testability of planned features forming component
* Write test design in component test plan
* Define and store (to Test Link) test cases for features
* Connect test cases to features in test management tool
* Prioritize test cases to form test sets
* Review component test plan and test cases
* Automate test cases and add tests to fully automated test infrastructure
* Execute test cases in test sets for software releases following test execution and feature releasing plan
* Report test results and raise relevant bugs
* Provide maturity statement for main releases based on received test results

=== Feature Test and System Test ===

QA target is to validate MeeGo distribution
* Feature functionality
* System functionality (Interaction and negative scenarios)
* System performance (response time)
* System reliability

Following chart illuminates scope and relationship of feature and system testing.

==== Feature Testing ====
* Target is to test full functionality of specified feature forming component (e.g. Dialer) following the features' definition in featurezilla. Test case example: Make a phone call
* Every component (formed by features) basic functionality is tested in feature test set

==== System Testing ====
* Target is to test basic (functional) system testing of several components/features simultaneously. Test case example: Listening music while receiving incoming call
* Target is to test system testing (performance). Test case example: Open dialer application (Target value 0.1 sec)
* Target is to test system testing (reliability). Test case example: Make 200 calls (Target 199 pass, 1 fail)

* Not tested NFT types: Performance (Throughput, Framerate, Load, Memory Consumption and Power Management) and Reliability (Endurance, Aging, Long Period and Low Resource)

* Each test component will be documented in component test plan. Test plan will cover all testing aspects for specific component/feature(s).

=== Testability ===

Testability of MeeGo 1.1 HandSet UX features are ensured at first.
* Features are defined by Product Management and relevant stakeholders to Bugzilla tool.
* Selected Quality Assurance Owners are checking those features through from Bugzilla against defined Testability Checklist and adding comment to feature in Bugzilla that can feature be used as QA input and it is possible validate in software release with relevant test case(s). Also more information is requested from Feature owner if it is seen insufficient from QA perspective.

Relevant Links
* http://bugs.meego.com/ (MeeGo 1.1 UX HandSet Features are stored in Bugzilla)
* http://wiki.meego.com/Quality/TestabilityChecklist
* http://wiki.meego.com/Quality/HandsetTestabilityStatus

=== Test Cases ===

Test Cases are designed by QA owners based on existing features and which have been approved from testability point of view. Test Cases itself are stored to TestLink tool. Common Test Case Template is used when designing test cases.

* Overall test design process and guideline from features to actual test cases can be found http://wiki.meego.com/Quality/TestDesignProcessAndGuideline

Relevant Links
* <Link to Test Link tool>
* http://wiki.meego.com/TestCaseTemplate

=== Coverage ===

When features forming components are analysed and test cases are designed based on those also coverage matrix will be created for each component. From coverage matrix it can be seen that what is feature coverage i.e. planned test cases vs. maximum amount of test cases to cover every user scenarios from component/feature.

Relevant Links
* <Coverage Matrix Template>
* <Coverage Matrix for MeeGo 1.1 HandSet UX component/features>

==== Features to be Tested ====
* Overall the MeeGo 1.1 HandSet UX Testing will cover the MeeGo 1.1 HandSet UX layer in [http://meego.com/developers/meego-architecture MeeGo Architecture]:
[[File:MeeGoArch.png]]

* Specific components/features to be tested will be aligned with the features under MeeGo HandSet Features product in [http://bugs.meego.com MeeGo Featurezilla @ Bugzilla]

==== Features not to be Tested ====
* <List of exact features not to be tested can be added after needed query is implemented to Featurezilla @ Bugzilla>

=== Configurations ===

MeeGo 1.1 HandSet UX is tested in a number of reference devices. The public reference configurations used for this release are
* N900
* AAVA
* MRST CDK

=== Test Sets and Priorization ===

Test sets are formed to TestLink tool by using specific field inside the tool. Test sets that are formed are
* Sanity Test Set
* Regression Test Set
* Feature Test Suite (Basic and Extended)
* System Functional Test Suite (Interactions and negative user scenarios)
* System Non-Functional Test Suite (Performance and Reliability) - Note! Excluded from 1.1 and targeted to 1.2 release.
* Milestone Test Suite

Quality Assurance Owners are setting priorities for Test Cases to form these Test Suites to be used for test execution.

When test suites are in place in public Test Link -tool, then every test suite is reviewed and approved with respective persons.

More detailed information: http://wiki.meego.com/Quality/TestSetGuideline

Note! During MeeGo 1.1 HandSet UX Timeframe QA will not form System Non-Functional Test Suites. Those will be targeted for 1.2 release.

=== Test Automation ===
* Testability driver has been selected as Handset UX automation tool

=== Requirement Coverage Visibility ===

* All relevant features are taken from featurezilla @bugzilla and inserted as testing requirements to Test Link-tool requirement interleaf
* Test cases which have been designed against features are then connected under features to show feature coverage

[[File:Feature_TC_Mapping.png]]

* Target is also to be able to show latest test execution status against features

=== Test Execution ===

All automated tests are executed in a MeeGo QA automated environment, and typically test results are available for each build.

Manual tests are executed regularly, but certainly before each release.

In general, MeeGo will be tested from the following different test execution levels.

*http://wiki.meego.com/Quality/TestSetGuideline

=== Test Reporting ===

All MeeGo 1.1 UX HandSet test results are stored to one place.

* MeeGo 1.1 Test Repository for HandSet
** http://wiki.meego.com/Quality/HandsetTestReport

Use Test Report Templates can be found: http://wiki.meego.com/TestReportTemplateCollection

=== Milestone Criteria ===

* There will be entry and exit criteria defined for each main milestone (Developer Preview, Feature Complete, Release Candidate and Project Release).
* All materials currently related to milestone quality criteria are stored to http://wiki.meego.com/Release_Engineering/Release_Timeline

== Network Environment ==
* Networking environment needed to conduct testing
** LAN
** WiFi network
** Internet
** 3G network

== Detailed Test Plans ==
To categorize the production requirements and identify the production functionality that will be tested, the product will be broken down to series of requirement set that QA owners are responsible for the validating.

{| border="1"
!| Application
!| QA Owner
!| Detailed test plan
|-
| Short Message Service || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.1HandSetUXTestPlanforShortMessageService MeeGo 1.1 HandSet UX SMS Test Plan]
|-
| Dialer || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.1HandSetUXTestPlanforDialer MeeGo 1.1 HandSet UX Dialer Test Plan]
|-
| Image Viewing || Shuang Wan || <link to detailed test plan>
|-
| Mozilla Fennec Browser || Petri Jylha || [http://wiki.meego.com/Quality/MeeGo1.1HandSetUXTestPlanforMozillaFennecBrowser MeeGo 1.1 HandSet UX Mozilla Fennec Browser Test Plan]
|-
| Contacts|| Dayu Yang || <link to detailed test plan>
|-
| Core UX (Home, Theme, System UI)|| Cathy Li || [http://wiki.meego.com/Quality/MeeGo1.1_Handset_CoreUX_TestPlan MeeGo 1.1 HandSet Core UX Test Plan]
|-
| Social Networking || Cathy Li || [http://wiki.meego.com/Quality/MeeGo1.1_Handset_UX_Social_Networking_TestPlan MeeGo 1.1 HandSet Social Networking Test Plan]
|-
| Compositing Window Manager|| N.N. || <link to detailed test plan>
|-
| Application install/uninstall || N.N. || <link to detailed test plan>
|-
| Virtual Keyboard || Yi Fu || [http://wiki.meego.com/Quality/1.1HandsetUXVkbTestPlan MeeGo 1.1 HandSet UX Virtual Keyboard Test Plan]
|-
| Clock || Qin Mu || <link to detailed test plan>
|-
| Email ||Yi Fu || <link to detailed test plan>
|-
| Music Player || Shuang Wan || <link to detailed test plan>
|-
| Calendar || Dayu Yang || <link to detailed test plan>
|-
| Video Player || Shuang Wan || <link to detailed test plan>
|-
| Instant Messaging || Mika Ikonen || [http://wiki.meego.com/Quality/MeeGo1.1HandSetUXTestPlanforInstantMessaging MeeGo 1.1 HandSet UX Instant Messaging Test Plan]
|}

== Dependency and Constraints ==
* Features' testability is a big dependency for test case design.
* Features' integration time line is another dependency for test case design. If features are integrated late, a lot of test cases' debug will be blocked.

== References ==
* QA main wiki: http://wiki.meego.com/Quality
* Feature Testability checklist: http://wiki.meego.com/Quality/TestabilityChecklist
* Testability Status Report: http://wiki.meego.com/Quality/HandsetTestabilityStatus
* Test Case Design Progress Follow-up: http://wiki.meego.com/Quality/HandsetTestSuite
* Test Result Reports: http://wiki.meego.com/Quality/HandsetTestReport
* Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
* Test Design Process and Guideline: http://wiki.meego.com/Quality/TestDesignProcessAndGuideline
* MeeGo Architecture http://meego.com/developers/meego-architecture
* MeeGo Bugzilla: http://bugs.meego.com/
* HandSet UX QA Ramp-Up follow up: http://wiki.meego.com/Quality/HandSetUXRamp-Up1.1

Quality/MeeGo1.1 Handset UX Social Networking TestPlan

2010-09-07T06:04:01Z

Cathyli: /* Feature not to be Tested */

=Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.1 HandSet Social networking application.

* '''Social Networking''' is an application that allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Social Networking
* [http://bugs.meego.com/show_bug.cgi?id=5875 Bug 5875] - [FEA] Need to add social networking to MeeGo
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments
|-
|
|
|
|-
|}
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Test from UI''': to check social networking window layout, theme work correctly from UI. E.g, check if social networking application is able to be launched to home screen with full screen; if text message shows completely in both portrait and landscape modes etc.
* '''Usage Model test''': to check if last.fm and twitter.com web services could work fine from user perspective.

'''''Test Type and Approach''''' 

Social Networking component is tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Social Networking===
* '''Test Points'''
** Check Social networking UI, layout, theme and button response.
** check if social networking application could be launched and closed in full screen mode and live thumbnail mode.
** Check if social networking accounts (last.fm and twitter) can be configured
** Check if last.fm context menu (View on Last.fm, Remove from timeline) works
** Check if status update and Refresh works
** Check if settings for last.fm and twitter.com work
** Check if support individual update for last.fm and twitter.com
** Check if support to post new twitter status
** Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work

===L10n Supporting===
* '''Test Points''': to check if following items in target locale could be displayed correctly
** Application name and icon
** Button label and its icon
** Window title
** Text message
** Date, time format

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.1 Handset UX Social Networking TestPlan

2010-09-07T06:03:35Z

Cathyli: /* Feature not to be Tested */

=Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.1 HandSet Social networking application.

* '''Social Networking''' is an application that allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Social Networking
* [http://bugs.meego.com/show_bug.cgi?id=5875 Bug 5875] - [FEA] Need to add social networking to MeeGo
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|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 social networking window layout, theme work correctly from UI. E.g, check if social networking application is able to be launched to home screen with full screen; if text message shows completely in both portrait and landscape modes etc.
* '''Usage Model test''': to check if last.fm and twitter.com web services could work fine from user perspective.

'''''Test Type and Approach''''' 

Social Networking component is tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Social Networking===
* '''Test Points'''
** Check Social networking UI, layout, theme and button response.
** check if social networking application could be launched and closed in full screen mode and live thumbnail mode.
** Check if social networking accounts (last.fm and twitter) can be configured
** Check if last.fm context menu (View on Last.fm, Remove from timeline) works
** Check if status update and Refresh works
** Check if settings for last.fm and twitter.com work
** Check if support individual update for last.fm and twitter.com
** Check if support to post new twitter status
** Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work

===L10n Supporting===
* '''Test Points''': to check if following items in target locale could be displayed correctly
** Application name and icon
** Button label and its icon
** Window title
** Text message
** Date, time format

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.1 Handset UX Social Networking TestPlan

2010-09-07T05:59:41Z

Cathyli: /* Test Strategy and Approach */

=Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.1 HandSet Social networking application.

* '''Social Networking''' is an application that allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Social Networking
* [http://bugs.meego.com/show_bug.cgi?id=5875 Bug 5875] - [FEA] Need to add social networking to MeeGo
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking Test Plan.

==Test Strategy and Approach==
'''''Test Strategy'''''
* '''Test from UI''': to check social networking window layout, theme work correctly from UI. E.g, check if social networking application is able to be launched to home screen with full screen; if text message shows completely in both portrait and landscape modes etc.
* '''Usage Model test''': to check if last.fm and twitter.com web services could work fine from user perspective.

'''''Test Type and Approach''''' 

Social Networking component is tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Social Networking===
* '''Test Points'''
** Check Social networking UI, layout, theme and button response.
** check if social networking application could be launched and closed in full screen mode and live thumbnail mode.
** Check if social networking accounts (last.fm and twitter) can be configured
** Check if last.fm context menu (View on Last.fm, Remove from timeline) works
** Check if status update and Refresh works
** Check if settings for last.fm and twitter.com work
** Check if support individual update for last.fm and twitter.com
** Check if support to post new twitter status
** Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work

===L10n Supporting===
* '''Test Points''': to check if following items in target locale could be displayed correctly
** Application name and icon
** Button label and its icon
** Window title
** Text message
** Date, time format

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.1 Handset UX Social Networking TestPlan

2010-09-07T05:56:14Z

Cathyli: /* Test Design */

=Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.1 HandSet Social networking application.

* '''Social Networking''' is an application that allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Social Networking
* [http://bugs.meego.com/show_bug.cgi?id=5875 Bug 5875] - [FEA] Need to add social networking to MeeGo
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking 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, widget could work fine each other and with other features from user perspective.

'''''Test Type and Approach''''' 

Core UX is tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Social Networking===
* '''Test Points'''
** Check Social networking UI, layout, theme and button response.
** check if social networking application could be launched and closed in full screen mode and live thumbnail mode.
** Check if social networking accounts (last.fm and twitter) can be configured
** Check if last.fm context menu (View on Last.fm, Remove from timeline) works
** Check if status update and Refresh works
** Check if settings for last.fm and twitter.com work
** Check if support individual update for last.fm and twitter.com
** Check if support to post new twitter status
** Check if Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline) work

===L10n Supporting===
* '''Test Points''': to check if following items in target locale could be displayed correctly
** Application name and icon
** Button label and its icon
** Window title
** Text message
** Date, time format

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.1 Handset UX Social Networking TestPlan

2010-09-07T05:51:25Z

Cathyli: /* Test Design */

=Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.1 HandSet Social networking application.

* '''Social Networking''' is an application that allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Social Networking
* [http://bugs.meego.com/show_bug.cgi?id=5875 Bug 5875] - [FEA] Need to add social networking to MeeGo
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking 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, widget could work fine each other and with other features from user perspective.

'''''Test Type and Approach''''' 

Core UX is tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Social Networking===
* '''Test Points'''
** Check Social networking UI layout and theme.
** 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
** Application name and icon
** Button label and its icon
** Window title
** Text message
** Date, time, number format
** Help message
** Embedded link

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.1 Handset UX Social Networking TestPlan

2010-09-07T05:43:11Z

Cathyli: /* Test Strategy and Approach */

=Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.1 HandSet Social networking application.

* '''Social Networking''' is an application that allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Social Networking
* [http://bugs.meego.com/show_bug.cgi?id=5875 Bug 5875] - [FEA] Need to add social networking to MeeGo
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking 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, widget could work fine each other and with other features from user perspective.

'''''Test Type and Approach''''' 

Core UX is tested in different test sets: 
* Sanity Test Set
** Contains BAT test cases of Core UX components.
* 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==

===Home Screen===
* '''Test Method'''
** UI layout check
** Functionality check
* '''Test Points'''
** UI layout check
*** Check home screen, application launcher, system UI layout.
** Functionality check
*** Open/close application launcher
*** Launch/close application from application launcher or quick launch bar
*** Switch between running applications with home screen
*** 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 Method'''
** UI layout check
** Functionality check
* '''Test Points'''
** UI layout check
*** Home and key applications default theme
** Functionality check
*** Update theme to check if it could take effect
*** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Method'''
** UI layout check
** Functionality check
* '''Test Points'''
** UI layout check
*** Check System UI layout. For instance, if correct date/time appears.
** Functionality check
*** 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).

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]

Quality/MeeGo1.1 Handset UX Social Networking TestPlan

2010-09-07T05:42:15Z

Cathyli: /* Risk and Dependency */

=Social Networking Test Plan=
==Component Summary==
This test plan is for MeeGo 1.1 HandSet Social networking application.

* '''Social Networking''' is an application that allows the user to fetch web services by setting up corresponding user accounts.

==Feature to be Tested==
{| cellspacing="0" border="1"
!| Feature Name
!| Detailed Feature Description
!| Comments
|-
| Social Networking
* [http://bugs.meego.com/show_bug.cgi?id=5875 Bug 5875] - [FEA] Need to add social networking to MeeGo
||
* Social networking main window UI, layout and button response check
* Launch/close social networking application
* Set up social networking accounts (last.fm and twitter)
* last.fm context menu (View on Last.fm, Remove from timeline)
* Status update and Refresh
* Settings for last.fm and twitter.com
* Individual update for last.fm and twitter.com
* Post new twitter status
* Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
||
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.
|}

==Feature not to be Tested==
* Translation for other languages except Chinese Simplified will not be covered in Handset UX Social Networking 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, widget could work fine each other and with other features from user perspective.

'''''Test Type and Approach'''''
* '''Functional test''': to check each function works as expected at the "unit" level. Such as open/close application, switch to home screen by tapping home button, lock/unlock screen, etc.
* '''Negative test''': negative test will be involved in functional test to check how it works if an unexpected input is given. E.g. give an input out of range.
* '''Stress test''': it involves testing beyond normal operational capacity and work under high workload. For instance, input long strings for text entry, repeated operations on open/close application, switch between home screen with application, switch between different running applications. About duration, we define some generic operations which run a period of time continuously.
* '''I18N/L10N testing''': test focus is for I18N mechanism in applet. Generally, we set another language environment (ex. Chinese Simplified) instead of default English environment and check if the change applied to whole home screen and widgets. Notes: only Chinese Simplified Translation will be covered by QA. For other languages, they will be covered by other teams.

==Test Design==

===Home Screen===
* '''Test Method'''
** UI layout check
** Functionality check
* '''Test Points'''
** UI layout check
*** Check home screen, application launcher, system UI layout.
** Functionality check
*** Open/close application launcher
*** Launch/close application from application launcher or quick launch bar
*** Switch between running applications with home screen
*** 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 Method'''
** UI layout check
** Functionality check
* '''Test Points'''
** UI layout check
*** Home and key applications default theme
** Functionality check
*** Update theme to check if it could take effect
*** Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)

===System UI===
* '''Test Method'''
** UI layout check
** Functionality check
* '''Test Points'''
** UI layout check
*** Check System UI layout. For instance, if correct date/time appears.
** Functionality check
*** 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).

==Risk and Dependency==
* No detailed social networking feature request in featurezilla.
* Twitter web service is blocked in China.

==Test Environment==
===Hardware Platforms===
* Aava DV1 and DV2
* Moorestown QS CDK with NEC PMIC

===Tools===
* bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP

==QA Contact==
* [mailto:cathy.li@intel.com Cathy Li]