MeeGo wiki - User contributions [en]

Quality/Meego contacts test plan v12

2010-12-27T02:16:53Z

Dayuyang: /* Features not to be Tested */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Features to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Features not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too. [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Features&query_format=advanced&cf_testability=No&version=1.2&component=Contacts&product=MeeGo%20Handset%20Features Not testable features]
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

Quality/Meego Handset Calendar TestPlan v12

2010-12-27T02:14:21Z

Dayuyang: /* Features not to be Tested */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Features to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Features not to be Tested==
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too. [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Features&query_format=advanced&cf_testability=No&version=1.2&component=Calendar%20and%20tasks&product=MeeGo%20Handset%20Features not testable features]
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego settings test plan v12

2010-12-27T02:02:11Z

Dayuyang: /* Feature not to be Tested */

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Features to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Features not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|-
|rowspan = "2"|5770 [FEA] Control Panel - USB behaviour
|rowspan = "2"|USB behaviour
|user can select the device behaviour once the USB is connected
|
|PC
|-
|supprted behaviours include Charging only, Mass Storage and vendor specific option
|
|
|-
|5772 [FEA] Control Panel - Wallpaper & theme
|Wallpaper & theme
|user can configure wallpaper(s), theme, sounds etc.
|
|
|-
|5774 [FEA] Control Panel - Sounds
|Sounds
|user can set and change the system sounds SMS, Ringtone, Email, Chat, system sounds, keyboard, touch screen, vibra etc
|
|
|-
|rowspan = "2"|5775 [FEA] Control Panel - Location
|rowspan = "2"|Location
|User can control the location awareness of the device, such GPS on/off, network based positioning on/off, sharing the user location for applications.
|
|
|-
|User can set the preferred network based positioning network server name and address, such as server for Assisted GPS service
|
|
|-
|5777 [FEA] Control Panel - Memory
|Memory
|User can check current memory status, such total/used/available RAM, total/used/available device user storage space, total/used/available external user storage space
|
|
|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego settings test plan v12

2010-12-27T02:02:01Z

Dayuyang: /* Feature to be Tested */

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Features to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Feature not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|-
|rowspan = "2"|5770 [FEA] Control Panel - USB behaviour
|rowspan = "2"|USB behaviour
|user can select the device behaviour once the USB is connected
|
|PC
|-
|supprted behaviours include Charging only, Mass Storage and vendor specific option
|
|
|-
|5772 [FEA] Control Panel - Wallpaper & theme
|Wallpaper & theme
|user can configure wallpaper(s), theme, sounds etc.
|
|
|-
|5774 [FEA] Control Panel - Sounds
|Sounds
|user can set and change the system sounds SMS, Ringtone, Email, Chat, system sounds, keyboard, touch screen, vibra etc
|
|
|-
|rowspan = "2"|5775 [FEA] Control Panel - Location
|rowspan = "2"|Location
|User can control the location awareness of the device, such GPS on/off, network based positioning on/off, sharing the user location for applications.
|
|
|-
|User can set the preferred network based positioning network server name and address, such as server for Assisted GPS service
|
|
|-
|5777 [FEA] Control Panel - Memory
|Memory
|User can check current memory status, such total/used/available RAM, total/used/available device user storage space, total/used/available external user storage space
|
|
|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego Handset Calendar TestPlan v12

2010-12-27T02:01:51Z

Dayuyang: /* Feature not to be Tested */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Features to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Features not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego Handset Calendar TestPlan v12

2010-12-27T02:01:42Z

Dayuyang: /* Feature to be Tested */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Features to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego contacts test plan v12

2010-12-27T02:01:34Z

Dayuyang: /* Feature not to be Tested */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Features to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Features not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

Quality/Meego contacts test plan v12

2010-12-27T02:01:22Z

Dayuyang: /* Feature to be Tested */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Features to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

Quality/Meego contacts test plan v12

2010-12-27T01:59:55Z

Dayuyang: /* I18N/L10N test */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

Quality/Meego settings test plan v12

2010-12-27T01:59:39Z

Dayuyang: /* I18N/L10N test */

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Feature not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|-
|rowspan = "2"|5770 [FEA] Control Panel - USB behaviour
|rowspan = "2"|USB behaviour
|user can select the device behaviour once the USB is connected
|
|PC
|-
|supprted behaviours include Charging only, Mass Storage and vendor specific option
|
|
|-
|5772 [FEA] Control Panel - Wallpaper & theme
|Wallpaper & theme
|user can configure wallpaper(s), theme, sounds etc.
|
|
|-
|5774 [FEA] Control Panel - Sounds
|Sounds
|user can set and change the system sounds SMS, Ringtone, Email, Chat, system sounds, keyboard, touch screen, vibra etc
|
|
|-
|rowspan = "2"|5775 [FEA] Control Panel - Location
|rowspan = "2"|Location
|User can control the location awareness of the device, such GPS on/off, network based positioning on/off, sharing the user location for applications.
|
|
|-
|User can set the preferred network based positioning network server name and address, such as server for Assisted GPS service
|
|
|-
|5777 [FEA] Control Panel - Memory
|Memory
|User can check current memory status, such total/used/available RAM, total/used/available device user storage space, total/used/available external user storage space
|
|
|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego Handset Calendar TestPlan v12

2010-12-27T01:57:53Z

Dayuyang: /* I18N/L10N test */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Feature to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is internationalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego contacts test plan v12

2010-12-27T01:57:03Z

Dayuyang:

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is internalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

Quality/Meego Handset Calendar TestPlan v12

2010-12-27T01:55:32Z

Dayuyang:

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Feature to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego settings test plan v12

2010-12-27T01:55:20Z

Dayuyang:

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Feature not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|-
|rowspan = "2"|5770 [FEA] Control Panel - USB behaviour
|rowspan = "2"|USB behaviour
|user can select the device behaviour once the USB is connected
|
|PC
|-
|supprted behaviours include Charging only, Mass Storage and vendor specific option
|
|
|-
|5772 [FEA] Control Panel - Wallpaper & theme
|Wallpaper & theme
|user can configure wallpaper(s), theme, sounds etc.
|
|
|-
|5774 [FEA] Control Panel - Sounds
|Sounds
|user can set and change the system sounds SMS, Ringtone, Email, Chat, system sounds, keyboard, touch screen, vibra etc
|
|
|-
|rowspan = "2"|5775 [FEA] Control Panel - Location
|rowspan = "2"|Location
|User can control the location awareness of the device, such GPS on/off, network based positioning on/off, sharing the user location for applications.
|
|
|-
|User can set the preferred network based positioning network server name and address, such as server for Assisted GPS service
|
|
|-
|5777 [FEA] Control Panel - Memory
|Memory
|User can check current memory status, such total/used/available RAM, total/used/available device user storage space, total/used/available external user storage space
|
|
|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

Quality/Meego settings test plan v12

2010-12-27T01:54:34Z

Dayuyang: /* Test Environment */

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Feature not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|-
|rowspan = "2"|5770 [FEA] Control Panel - USB behaviour
|rowspan = "2"|USB behaviour
|user can select the device behaviour once the USB is connected
|
|PC
|-
|supprted behaviours include Charging only, Mass Storage and vendor specific option
|
|
|-
|5772 [FEA] Control Panel - Wallpaper & theme
|Wallpaper & theme
|user can configure wallpaper(s), theme, sounds etc.
|
|
|-
|5774 [FEA] Control Panel - Sounds
|Sounds
|user can set and change the system sounds SMS, Ringtone, Email, Chat, system sounds, keyboard, touch screen, vibra etc
|
|
|-
|rowspan = "2"|5775 [FEA] Control Panel - Location
|rowspan = "2"|Location
|User can control the location awareness of the device, such GPS on/off, network based positioning on/off, sharing the user location for applications.
|
|
|-
|User can set the preferred network based positioning network server name and address, such as server for Assisted GPS service
|
|
|-
|5777 [FEA] Control Panel - Memory
|Memory
|User can check current memory status, such total/used/available RAM, total/used/available device user storage space, total/used/available external user storage space
|
|
|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==

==References==

Quality/Meego Handset Calendar TestPlan v12

2010-12-27T01:54:20Z

Dayuyang: /* Test Environment */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Feature to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==

==References==

Quality/Meego contacts test plan v12

2010-12-27T01:53:50Z

Dayuyang: /* Test Environment */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is internalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK, iCDK
* N900

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

==References==

Quality/Meego contacts test plan v12

2010-12-27T01:51:21Z

Dayuyang: /* I18N/L10N test */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is internalization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

==References==

Quality/bkm/corewatcher

2010-12-17T04:48:11Z

Dayuyang:

=Corewatcher=
Here are the steps of how to get the backtrace log of a crashed program on meego handset
* Find the "core" logs files under /tmp.
** When a program crashed, there will be a "core" file (file name like "core.xxx") generated under /tmp automatically.
** The current MeeGo supports it by default, no additional package needed.
* Find which "core" log is for the crashed program.
** In /tmp, there could be more than one "core" file, choose the latest one.
** For example, if the crashed program is "meego-handset-people", and the latest "core" log is "core.1000", we can user command "file core.1000" to check whether the "core" log is generated for "meego-handset-people".
** If it isn't, we could try the next latest "core" log with file command until we find the correct one
* Use gdb to get the backtrace information of this crash.
** Gdb hasn't been installed on the latest MeeGo image, we have to install it before we can get the backtrace information
** Before start gdb, run comman "script" command to record the following screen output
** Let’s still use "meego-handset-people" and "core.1000" for an example. Run command "gdb /usr/bin/meego-handset-people core.1000".
** Firstly, gdb starts to reproduce the crashing process recorded in "core.1000". When it stops, we can input "bt" command in gdb console, and it starts to dump the backtrace of this crash.
** After all backtrace is shown, input "quit" to leave gdb.
** Input "exit" command to stop "script", and we get the screen output in "typescript" under the current folder
** Open "typescript", the content after "bt" command is the backtrace we need for this crash

Quality/bkm/corewatcher

2010-12-17T04:47:19Z

Dayuyang: Created page with "Here are the steps of how to get the backtrace log of a crashed program on meego handset * Find the "core" logs files under /tmp. ** When a program crashed, there will be a "cor…"

Here are the steps of how to get the backtrace log of a crashed program on meego handset
* Find the "core" logs files under /tmp.
** When a program crashed, there will be a "core" file (file name like "core.xxx") generated under /tmp automatically.
** The current MeeGo supports it by default, no additional package needed.
* Find which "core" log is for the crashed program.
** In /tmp, there could be more than one "core" file, choose the latest one.
** For example, if the crashed program is "meego-handset-people", and the latest "core" log is "core.1000", we can user command "file core.1000" to check whether the "core" log is generated for "meego-handset-people".
** If it isn't, we could try the next latest "core" log with file command until we find the correct one
* Use gdb to get the backtrace information of this crash.
** Gdb hasn't been installed on the latest MeeGo image, we have to install it before we can get the backtrace information
** Before start gdb, run comman "script" command to record the following screen output
** Let’s still use "meego-handset-people" and "core.1000" for an example. Run command "gdb /usr/bin/meego-handset-people core.1000".
** Firstly, gdb starts to reproduce the crashing process recorded in "core.1000". When it stops, we can input "bt" command in gdb console, and it starts to dump the backtrace of this crash.
** After all backtrace is shown, input "quit" to leave gdb.
** Input "exit" command to stop "script", and we get the screen output in "typescript" under the current folder
** Open "typescript", the content after "bt" command is the backtrace we need for this crash

Quality/Plans/Handset UX test plan

2010-12-06T05:04:43Z

Dayuyang: /* 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 || Currently no social networking requirements.
|-
| 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 || [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/Meego settings test plan v12

2010-12-06T05:03:38Z

Dayuyang: /* Meego 1.2 Settings test plan */

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Feature not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|-
|rowspan = "2"|5770 [FEA] Control Panel - USB behaviour
|rowspan = "2"|USB behaviour
|user can select the device behaviour once the USB is connected
|
|PC
|-
|supprted behaviours include Charging only, Mass Storage and vendor specific option
|
|
|-
|5772 [FEA] Control Panel - Wallpaper & theme
|Wallpaper & theme
|user can configure wallpaper(s), theme, sounds etc.
|
|
|-
|5774 [FEA] Control Panel - Sounds
|Sounds
|user can set and change the system sounds SMS, Ringtone, Email, Chat, system sounds, keyboard, touch screen, vibra etc
|
|
|-
|rowspan = "2"|5775 [FEA] Control Panel - Location
|rowspan = "2"|Location
|User can control the location awareness of the device, such GPS on/off, network based positioning on/off, sharing the user location for applications.
|
|
|-
|User can set the preferred network based positioning network server name and address, such as server for Assisted GPS service
|
|
|-
|5777 [FEA] Control Panel - Memory
|Memory
|User can check current memory status, such total/used/available RAM, total/used/available device user storage space, total/used/available external user storage space
|
|
|}

==Test Environment==
* nCDK

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==

==References==

Quality/Meego settings test plan v12

2010-12-06T05:03:02Z

Dayuyang: /* Test Design */

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Feature not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|-
|rowspan = "2"|5770 [FEA] Control Panel - USB behaviour
|rowspan = "2"|USB behaviour
|user can select the device behaviour once the USB is connected
|
|PC
|-
|supprted behaviours include Charging only, Mass Storage and vendor specific option
|
|
|-
|5772 [FEA] Control Panel - Wallpaper & theme
|Wallpaper & theme
|user can configure wallpaper(s), theme, sounds etc.
|
|
|-
|5774 [FEA] Control Panel - Sounds
|Sounds
|user can set and change the system sounds SMS, Ringtone, Email, Chat, system sounds, keyboard, touch screen, vibra etc
|
|
|-
|rowspan = "2"|5775 [FEA] Control Panel - Location
|rowspan = "2"|Location
|User can control the location awareness of the device, such GPS on/off, network based positioning on/off, sharing the user location for applications.
|
|
|-
|User can set the preferred network based positioning network server name and address, such as server for Assisted GPS service
|
|
|-
|5777 [FEA] Control Panel - Memory
|Memory
|User can check current memory status, such total/used/available RAM, total/used/available device user storage space, total/used/available external user storage space
|
|
|}

Quality/Meego settings test plan v12

2010-12-06T04:57:33Z

Dayuyang: /* Meego 1.2 Settings test plan */

=Meego 1.2 Settings test plan=
==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo Settings is a package of application applets; each applet is for a specific functionality, such as WIFI setting, Bluetooth setting, date and time setting, language setting, etc

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset settings 1.2 Featurezilla. Settings test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stress test. 
Settings is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments
|-
|[http://bugs.meego.com/show_bug.cgi?id=5755 5755]
|[FEA] Control Panel - Device time and date setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5756 5756]
|[FEA] Control Panel - Device time and date format setting
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5758 5758]
|[FEA] Control Panel - Network Operator Time
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5759 5759]
|[FEA] Control Panel - Network Time Protocol
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5760 5760]
|[FEA] Control Panel - Display and light control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5761 5761]
|[FEA] Control Panel - Display and light manual control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5762 5762]
|[FEA] Control Panel - Keyboard backlight and LEDs control
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5763 5763]
|[FEA] Control Panel - Display and light control power saving
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5764 5764]
|[FEA] Control Panel - Display calibration
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5766 5766]
|[FEA] Control Panel - About the device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5767 5767]
|[FEA] Control Panel - Language & region
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5768 5768]
|[FEA] Control Panel - Reset Factory Settings
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5769 5769]
|[FEA] Control Panel - Erase and reset device
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5770 5770]
|[FEA] Control Panel - USB behaviour
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5772 5772]
|[FEA] Control Panel - Wallpaper & theme
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5774 5774]
|[FEA] Control Panel - Sounds
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5775 5775]
|[FEA] Control Panel - Location
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5776 5776]
|[FEA] Control Panel - Input methods
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=5777 5777]
|[FEA] Control Panel - Memory
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=9258 9258]
|[FEA] [I18N] Settings shall be internationalized according to the dependencies listed in Core Master 5068.
|Hig
|

|}

==Feature not to be Tested==
* All SyncUI related features are covered in SyncUI test plan
* Telephony related features are covered in telephony setting test plan
* Input method setting is covered in virtual keyboard test plan
* This document covers only 1.2 features, for 1.1 features, please reference MeeGo setting 1.1 test plan.

==Test Strategy and Approach==
===Functional test===
All basic settings usage model are covered in functional test
* check if each setting applet is integrated
* check if each setting applet could work properly (for more details see test design section)
===Negative test===
Negative test will use different malformed input to test the behavior of settings.
For each setting applet, there are many fields to be filled, so negative test is an important part for settings test
The malformed input includes:
* Very short and long string
* Special character in string
* Input non-number in number filed
* Incorrect date format
* Incorrect IP address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close each setting applet very frequently, and check whether it could be opened and closed properly each time.

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to each setting applet.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration
|-
|5755 [FEA] Control Panel - Device time and date setting
|Device time and date setting
|user can set time and date
|
|
|-
|5756 [FEA] Control Panel - Device time and date format setting
|Device time and date format setting
|user can select time and date formats according to his locale user preferences
|
|
|-
|5758 [FEA] Control Panel - Network Operator Time
|Network Operator Time
|user can enable/disable Network operator time (NITZ) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5759 [FEA] Control Panel - Network Time Protocol
|Network Time Protocol
|user can enable/disable Network time protocol (NTP) automated time changes, if enabled, the time and date can be set automatically
|
|
|-
|5760 [FEA] Control Panel - Display and light control
|Display and light control
|user can enable/disable the automated (e.g. based on ambient light) adjustment of display settings, if enabled, display will automatically change according to ambient light
|
|
|-
|5761 [FEA] Control Panel - Display and light manual control
|Display and light manual control
|user can set basic display settings, such as brightness
|
|
|-
|5762 [FEA] Control Panel - Keyboard backlight and LEDs control
|Keyboard backlight and LEDs control
|user can enable/disable automated (e.g. based on ambient light) adjustment of keyboard backlight and leds brightness, if enabled,keyboard backlight and leds brightness will change according to ambient light
|
|
|-
|5763 [FEA] Control Panel - Display and light control power saving
|Display and light control power saving
|user can set the display blank timeout, and display will be blank when timeout
|
|
|-
|5764 [FEA] Control Panel - Display calibration
|Display calibration
|user can recalibrate the device (touch) display
|
|
|-
|5766 [FEA] Control Panel - About the device
|About the device
|there is an About box to show applicable licenses and basic device HW and SW data, such as device Serial #, IMEI code, MAC addresses, key SW versions
|
|
|-
|5767 [FEA] Control Panel - Language & region
|Language & region
|user can set language, region, locale settings, time and date format
|
|
|-
|5768 [FEA] Control Panel - Reset Factory Settings
|Reset Factory Settings
|user can reset device to Factory Default Settings, but not erase user data, such as images, music, documents etc
|
|contacts, calendar, media
|-
|5769 [FEA] Control Panel - Erase and reset device
|Erase and reset device
|user can reset his device to Factory Default Settings and completely erase all personal data from the device
|
|contacts, calendar, media
|}

Quality/Meego settings test plan v12

2010-12-06T04:54:36Z

Dayuyang: /* Meego 1.2 Settings test plan */

Quality/Meego settings test plan v12

2010-12-06T04:53:03Z

Dayuyang: /* Meego 1.2 Settings test plan */

Quality/Meego settings test plan v12

2010-12-06T04:51:47Z

Dayuyang: /* Feature to be Tested */

Quality/Meego settings test plan v12

2010-12-06T04:50:28Z

Dayuyang: /* Meego 1.2 Settings test plan */

Quality/Meego settings test plan v12

2010-12-06T04:48:55Z

Dayuyang: Created page with "=Meego 1.2 Settings test plan= ==History == {|cellspacing="0" border="1" !|Date !|Comments |- |2010-12-03 |This document was created |} ==Summary== MeeGo Settings is a pack…"

Quality/Plans/Handset UX test plan

2010-12-06T03:13:48Z

Dayuyang: /* 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 || Currently no social networking requirements.
|-
| 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 || [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 || <link to detailed 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/Meego Handset Calendar TestPlan v12

2010-12-06T03:12:47Z

Dayuyang: /* MeeGo 1.2 Calendar test plan */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Feature to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

==Test Environment==
* nCDK

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==

==References==

Quality/Meego Handset Calendar TestPlan v12

2010-12-06T03:12:08Z

Dayuyang: /* Test Design */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Feature to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|-
|rowspan = "4"|4218 [FEA] Calendar Settings
|rowspan = "4"|calendar settings
|can set start of week
|
|settings application
|-
|can set start of the day
|
|settings application
|-
|can set end of the day
|
|settings application
|-
|can add/remove accounts
|
|settings application

|}

Quality/Meego Handset Calendar TestPlan v12

2010-12-06T03:10:59Z

Dayuyang: /* MeeGo 1.2 Calendar test plan */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Feature to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

==Test Design==
{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "3"|4207 [FEA] Calendar Home Screen actions - Search
|rowspan = "3"|search event
|there is a search box when tapping search button
|
|
|-
|can search tasks by keywords, matched results are shown in a scrollable list
|
|
|-
|can search in all or a specific account
|
|

|}

Quality/Meego Handset Calendar TestPlan v12

2010-12-06T03:07:30Z

Dayuyang: /* MeeGo 1.2 Calendar test plan */

=MeeGo 1.2 Calendar test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}
==Summary==
MeeGo calendar is designed for managing date, event and task on MeeGo platform. With this application user can add/remove event, can view events in different views (coming up, 3 day, month). This application supports vCard and vCalendar data format.

==Feature to be Tested==

Features listed here are abstracted from MeeGo handset calendar 1.2 Featurezilla. Calendar test will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Calendar is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negtive, stress), make them low priority in testing circle and marked as extended feature test

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=4207 4207]
|[FEA] Calendar Home Screen actions - Search
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4218 4218]
|[FEA] Calendar Settings
|Hig
|

|}

==Feature not to be Tested==
* All calendar 1.2 features are testable, so all features will be tested.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo calendar 1.1 test plan].

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 
* check if it can search and view event
* check if it can add and edit event
* check if different screen and view are shown properly: home screen, coming up view, 3 day view, month view, create new/edit screen

===Negative test===
Negative test will use different malformed input to test the behavior of Calendar. When adding new event and editing an existing event, there are many fields to be filled, so negative test is a important part for Calendar test. 

The malformed input includes: 
* Very short and long string
* Special character in string

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Calendar very frequently, and check whehter it could be opened and closed properly each time.
* Add many event
* delete all event

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Calendar.

Quality/Meego Handset Calendar TestPlan v12

2010-12-06T03:06:42Z

Dayuyang: /* MeeGo 1.2 Calendar test plan */

Quality/Meego Handset Calendar TestPlan v12

2010-12-06T03:05:34Z

Dayuyang: /* Feature to be Tested */

Quality/Meego Handset Calendar TestPlan v12

2010-12-06T03:02:46Z

Dayuyang: /* MeeGo 1.2 Calendar test plan */

Quality/Meego Handset Calendar TestPlan v12

2010-12-06T03:00:27Z

Dayuyang: Created page with "=MeeGo 1.2 Calendar test plan= ==History == {|cellspacing="0" border="1" !|Date !|Comments |- |2010-12-03 |This document was created |} ==Summary== MeeGo calendar is desi…"

Quality/Meego contacts test plan v12

2010-12-06T02:56:09Z

Dayuyang: /* MeeGo 1.2 Contacts test plan */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

==Test Environment==
* nCDK

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

==References==

Quality/Meego contacts test plan v12

2010-12-06T02:55:33Z

Dayuyang: /* Test Design */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|-
|rowspan = "3"|4191 [FEA] Contacts - contextual menu actions - IM
|rowspan = "3"|contextual menu
|there is IM action in contextual menu of a contact
|
|
|-
|select IM action will invoke IM client to send message to the IM
|IM application can work
|IM
|-
|If there are more than one IM entries present for the selected contact, the list of these IM entries is presented in another pop-up menu
|IM application can work
|IM

|-
|4801 [FEA] vCard 2.1 reception
|vCard support
|When a vCard is received, the contact information in it will be saved to contacts
|send vCard to the device
|TBD
|-
|6695 [FEA] Contacts backend - Storing phone contact(s)
|contacts backend: phone contacts
|phone number of a contact could be saved
|
|
|-
|6697 [FEA] Contacts backend - Storing contact(s) avatar
|contacts backend: contacts avatar
|avatar for phone and IM contact could be saved
|
|
|-
|8155 [FEA] Phone number characters
|contacts field: phone number
|can insert pauses and pass DTMF commands for network in a phone number
|
|
|-
|8156 [FEA] SIM Card - new card inserted
|sim card data operation
|can copy SIM card entries to contacts when a new SIM card is inserted
|SIM card is on device
|SIM card

|}

Quality/Meego contacts test plan v12

2010-12-06T02:51:17Z

Dayuyang: /* Test Design */

=MeeGo 1.2 Contacts test plan=

==History ==
{|cellspacing="0" border="1"
!|Date
!|Comments

|-
|2010-12-03
|This document was created

|}

==Summary==
MeeGo Handset People is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. MeeGo handset people is based on libseaside, and libseaside is also used by other applications, such as Dialer, SMS, Email and IM.

==Feature to be Tested==
Features listed here are abstracted from MeeGo handset contacts 1.2 Featurezilla. This test plan will cover all these features which testability is yes. And this test plan will also cover features which are not listed in Featurezilla, such as negative test, stree test, i18/l10n 
Contacts is GUI application and all functionality is exposed to user via GUI, usage models and related UI interface has top priority, and will be tested in all formal and regular testing process, basic feature test case are from it. For other scenarios (negative, stress), make them low priority in testing circle and marked as extended feature test.

{|cellspacing="0" border="1"
!|Feature ID
!|Feature
!|Priority
!|Comments

|-
|[http://bugs.meego.com/show_bug.cgi?id=3025 3025]
|[FEA] Contacts merging
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4166 4166]
|[FEA] Contacts - Recent communication
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4170 4170]
|[FEA] View Contact Screen - Actions - Share contact
|Med
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4176 4176]
|[FEA] Contact Fields - Title
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4178 4178]
|[FEA] Contact Fields - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4191 4191]
|[FEA] Contacts - contextual menu actions - IM
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=4801 4801]
|[FEA] vCard 2.1 reception
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6695 6695]
|[FEA] Contacts backend - Storing phone contact(s)
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=6697 6697]
|[FEA] Contacts backend - Storing contact(s) avatar
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8155 8155]
|[FEA] Phone number characters
|Hig
|
|-
|[http://bugs.meego.com/show_bug.cgi?id=8156 8156]
|[FEA] SIM Card - new card inserted
|Hig
|

|}

==Feature not to be Tested==
* Libseaside API level test isn’t included in this test plan, since currently there isn't test plan for libseaside API level test. It depends on how much unittest is done by developer
* There are still some 1.2 features marked as untestable, when they are testable, this document will cover them, too.
* This document covers only 1.2 features, for 1.1 features, please reference [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo contacts 1.1 test plan]

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==

{|cellspacing="0" border="1"
!|Feature ID
!|Test point
!|Checkpoint
!|Conditions
!|Collaboration

|-
|rowspan = "2"|3025 [FEA] Contacts merging
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|
|
|-
|conflicts in fields could be found and user is able to choose the entry they'd like to present
|
|

|-
|rowspan = "3"|4166 [FEA] Contacts - Recent communication
|rowspan = "3"|recent communication
|recent communication (phone , SMS , email) of contacts is indicated
|
|Dialer, SMS application, Email client

|-
|recent activity is indicated verbose in landscape mode, and using icons in portrait mode
|
|

|-
|if there are multiple activity from same contact then a number is indicated in portrait mode
|
|

|-
|rowspan = "3"|4170 [FEA] View Contact Screen - Actions - Share contact
|rowspan = "3"|share contact
|there is a share button, when tapping a new pop-up prompts user to select the method of sharing (e.g. SMS, IM or Email), and user shall be able to cancel the action.
|
|SMS, IM, Email
|-
|User shall be able to select the details to share, such as Share 'All details' or list of all available populated field in the contact. when at least one field (or 'All details'), 'Done' button shall become
|
|
|-
|if share via email, a vCard with selected entries should be attached to the email
|
|Email

|-
|rowspan = "2"|4176 [FEA] Contact Fields - Title
|rowspan = "2"|contacts field: title
|there is one title field for each contact
|
|
|-
|title field can be added, changed and removed
|
|

|}

Quality/Meego contacts test plan v12

2010-12-06T02:37:16Z

Dayuyang: /* Test Design */

Quality/Meego contacts test plan v12

2010-12-06T02:36:24Z

Dayuyang: /* MeeGo 1.2 Contacts test plan */

Quality/Meego contacts test plan v12

2010-12-06T02:16:47Z

Dayuyang: /* MeeGo 1.2 Contacts test plan */

Quality/Meego contacts test plan v12

2010-12-06T02:12:44Z

Dayuyang: /* MeeGo 1.2 Contacts test plan */

Quality/Meego contacts test plan v12

2010-12-06T02:07:56Z

Dayuyang: /* MeeGo 1.2 Contacts test plan */

Quality/Plans/Handset UX test plan

2010-12-06T01:49:10Z

Dayuyang: /* 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 || Currently no social networking requirements.
|-
| 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 || [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 || <link to detailed 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/Meego contacts test plan v12

2010-12-06T01:46:53Z

Dayuyang: Created page with "=MeeGo 1.2 Contacts test plan= ==History == {|cellspacing="0" border="1" !|Date !|Comments |- |2010-12-03 |This document was created |} ==Summary== MeeGo Handset People …"

Quality/temp test plan

2010-12-02T05:50:25Z

Dayuyang:

=Meego contacts test plan=
==Component Summary==

==Feature to be Tested==
{|cellspacing="0" border="1"
!|Feature
!|Feature Description
!|Comments

|-
|Bluetooh
|
* device can be discovered
* device can be paired
* device can be connected
* device can be browsed
|

|-
|Set ringtone
|ringtones can be set and changed
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Device time and date setting
|wall clock time can be set and changed
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Device time and date format setting
|time and date formats can be set according to the locale preferences
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Daylight Saving Time manual setting
|it can set automatic or manual change Daylight Saving Time
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Network Operator Time
|it can set Network operator time (NITZ) automated time changes
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Network Time Protocol
|it can set Network time protocol (NTP) automated time changes
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Display and light control
|it can enable/disable the automated adjustment of display settings based on ambient light
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Display and light manual control
|basic display settings could be set
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Keyboard backlight and LEDs control
|it can enable/disable automated adjustment of keyboard backlight and leds brightness based on ambient light
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Display and light control power saving
|it can set the display blank timeout
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Display calibration
|it can recalibrate the device (touch) display
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Battery status
|it can check battery status
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|About the device
|About the device can be shown properly
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Language & region
|it can set Language and region
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Reset Factory Settings
|it can reset the device to Factory Default Settings
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Erase and reset device
|it can reset his device to Factory Default Settings
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|USB behaviour
|it can set the device behaviour once the USB is connected
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|User/device profile
|it can set the active device profile
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Wallpaper & theme
|Wallpaper and theme can be set
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Volume
|Volume can be set
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Sounds
|it can set and change the system sounds
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Location
|it can control the location awareness of the device
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Input methods
|input methods preferences can be set
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Memory
|current memory status could be shown properly
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|-
|Device lock
|device lock preferences can be set
|This feature hasn't been integrated, and no wireframe now, more details are TBD

|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature Name
!|Feature Description
!|Comments

|-
|Network (Wifi)
|
|this feature is covered by Nokia

|-
|Telephony
|
|this feature is covered by Nokia

|}

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test 

===Negative test===

==Test Design==
===Bluetooth===
* Check if nearby device can be discovered
* Check if nearby device can be paired
* Check if paired device can be removed
* Check if paired device can be connected
* Check if paired device can be browsed
* Check if bluetooh can be turned on|off
===Other Features===
* TBD

==Test Environment==
* MSRT CDK
* Aava
* Netbook
** With DUI image for netbook

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==

==References==

Quality/temp test plan

2010-11-25T07:04:03Z

Dayuyang: Created page with "=Meego contacts test plan= ==Component Summary== Meego handset people is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete c…"

=Meego contacts test plan=
==Component Summary==
Meego handset people is the contacts program on MeeGo handheld. With this program, end user can view, search, add, edit, delete contacts information, and can also make phone call, send SMS or email. Meego handset people is based on libseaside, and libseaside is also used by other applications, such as Dailer, SMS, Email and IM. 

==Feature to be Tested==
{|cellspacing="0" border="1"
!|Feature Category
!|Feature Description
!|Comments

|-
|Basic function

|
* view contact
* add new contact
* edit existing contact
* search contact

|
Contacts fields include Name,Phone,Company,Title,Email,IM,Address,Birthday,Notes,URL

|-
|GUI layout and function

|
* Home Screen and actions
* View Contact Screen and actions
* Add new/Edit contact screen and actions
* contextual menu

|
* Home screen actions include: Go back to home screen, Filter for 'All', 'Recent' and 'Favorites' groups, Add new contact, Search contact, close Contacts application
* View Contact Screen actions include: Link Contact,Share contact,Edit Contact,Go back
* Add new/Edit contact screen actions include: Home screen, Save, Go back
* contextual menu items include: Call,Messaging,EMAIL,IM,View,Favorite/Unfavorite,Delete
|-
|Interact with other program

|
* Dialer
* SMS
* Email
* IM

|
* It can launch these programs from contacts to communicate with the selected contact
* It can share contacts information with these programs

|}

==Feature not to be Tested==
{|cellspacing="0" border="1"
!|Feature
!|Feature Description
!|Comments

|-
|full features of programs which interact with contacts
|Dialer, SMS, Email, IM
|we only test the features in these programs related to contacts

|-
|social networking services support
|
|this feature isn't very clear and won't be integrated soon

|-
|avatar support
|
|this feature isn't very clear and won't be integrated soon

|-
|import and export
|
|this feature isn't very clear and won't be integrated soon

|-
|vCard Support
|
|this feature isn't very clear and won't be integrated soon

|-
|Libseaside API level test

|
|
* Currently there isn't test plan for libseaside API level test
* it depends on how much unittest is done by developer

|}

==Test Strategy and Approach==
===Functional test===
All basic functionalities are covered in functional test.
* check if search and view could work properly, search and view include: show all, show recent, show favorites, search contacts, view one contact
* check if Add new contact, edit a contact, delete a concact could work properly
* check if differnet screen could be shown properly: home screen, view screen, add new/edit screen
* check if contacts could Interact with other programs, the programs include:Dialer, SMS, Email, IM

===Negative test===
Negative test will use different malformed input to test the behavior of Contacts. 
When adding new contact and editing an existing contact, there are many fields to be filled, so negative test is a important part for Contacts test. 
The malformed input includes:
* Very short and long input
* Special character
* Non number in for phone number
* incorrect email address

===Stress test===
Stress test focuses on testing beyond normal operational capacity, such as
* Open and close Contacts very frequently, and check whehter it could be opened and closed properly each time
* Start other program (Dialer, SMS, Email, IM) from Contacts very frequently, and check whehter it could be opened and closed properly each time
* Add many contacts, delete all contacts

===I18N/L10N test===
This is localization test. We will set another language environment (such as Chinese Simplified) instead of default English environment and check whether the change applied to Contacts.

==Test Design==
===Basic search and view===
* Check if all contacts could be shown properly in home screen
* Check if favorite contacts could be shown properly in home screen
* Check if all recenet called contacts could be shown properly in home screen
* Check if all contacts wth recent sms could be shown properly in home screen
* Check if all contacts with recent email could be shown properly in home screen
* Check contacts could be searched
* Check if contacts could be searched by name
* Check contacts could be searched by email
* Check if contacts could be searched by phone number
* Check contacts could be searched by address
* Check can search contacts with full keyword
* Check can search contacts with partial keyword
* Check contacts could be searched by title
* Check contacts could be searched by birthday
* Check contacts could be searched by URL
* Check contacts could be searched by note
* Check contacts could be searched by IM
* Check name field is shown properly in view contact screen
* Check icon field is shown properly in view contact screen
* Check company field is shown properly in view contact screen
* Check phone number field is shown properly in view contact screen
* Check email field is shown properly in view contact screen
* Check address field is shown properly in view contact screen
* Check title field is shown properly in view contact screen
* Check birthday field is shown properly in view contact screen
* Check URL field is shown properly in view contact screen
* Check note field is shown properly in view contact screen
* Check IM field is shown properly in view contact screen
* Check if Home Screen is shown properly, contacts is sorted alphabetically, alphabetical bar is shown, contact name, recent activity and favorites indicator are shown
* Check if tapping alphabetical bar can jump to the correct contact
* Check if tappling close action in home screen can close contacts
* Check if tapping add new action in home screen can open add new/edit screen for adding a new contact
* Check if in View Contact Screen all contacts fields are shown properly
* Check current search term can be cleared
===Contact Edit===
* Check if Add new/Edit contact screen is shown properly, all fields are presented for adding/editing value
* Check if name can be added for a new contact
* Check if company can be added for a new contact
* Check if phone number can be added with mobile type for a new contact
* Check if phone number can be added with home type for a new contact
* Check if phone number can be added with work type for a new contact
* Check can canel adding phone number for a new contact
* Check if more than one phone number can be added for a contact
* Check if email can be added for a new contact
* Check can add more than one email for a new contact
* Check can canel adding email for a new contact
* Check can add address for a new contact
* Check can add addressw with home type for a new contact
* Check can add address with work type
* Check if more than one address can be added
* Check can cancel adding address for a new contact
* Check if title can be added for a new contact
* Check can add brithday for a new contact
* Check can add URL with personal type for a new contact
* Check can add URL with company type for a new contact
* Check can add new URL with blog type for a new contact
* Check can add more than one URL for a new contact
* Check can cancel adding URL for a new contact
* Check can add note for a new contact
* Check if IM can be added for a new contact
* Check can add IM with jabber type for a new contact
* Check can add IM with yahoo type for a new contact
* Check can add IM with msn type for a new contact
* Check can add more than one IM for a new contact
* Check can cancel adding IM for a new contact
* Check if name can be changed for a contact
* Check can change icon for a contact
* Check if company can be changed for a contact
* Check if phone number can be changed for a contact
* Check can change phone number type for a contact
* Check can delete phone number for a contact
* Check if email can be changed for a contact
* Check can delete email for a contact
* Check can change address for a contact
* Check can change address type for a contact
* Check can delete address for a contact
* Check if title can be changed for a contact
* Check can change birthday for a contact
* Check can change url for a contact
* Check can change url type for a new contact
* Check can delete URL for a contact
* Check can change note for a contact
* Check can change user name of IM for a contact
* Check if type of IM can be changed for a contact
* Check can delete IM for a contact
* Check can delete a contact
===interaction with other programs===
* Check can send SMS to the selected contact
* Check can show and seach contact from SMS
* Check can Call from contacts to the selected contact
* Check can show and seach contact from Dialer
* Check can send email from contacts to the selected contact
* Check can show and seach contact from Email
* Check can start IM application for the selected contact to send message
* Check can start browser to browse the URL of the selected contact
===contextual menu===
* Check if it can make a call from contextual menu
* Check if it can send SMS from contextual menu
* Check if it can send email from contextual menu
* Check if it can start IM to send message from contextual menu
* Check if it can view the selected contact by contextual menu
* Check if it can set favorite/unfavorite for the selected contact from contextual menu
* Check if it can delete the selected contact from contextual menu
* Check if contextual menu can be opened, and the menu is shown properly
===Negative test===
* Check can input very long string in a string field
* Check can input very short string in a string field
* Check can input string with strange characters in a string field
* Check negtaive test for name field, can input long/short/strange string in name field field
* Check negtaive test for company field, can input long/short/strange string in company field field
* Check negtaive test for string field: address, can input long/short/strange string in string field: address field
* Check negtaive test for title field, can input long/short/strange string in title field field
* Check negtaive test for note field, can input long/short/strange string in note field field
* Check can input very long number in number field
* Check can input very short number in number field
* Check can not input non number in number
* Check negative test for phone field, input long/short/non number in phone field
* Check can input very long email address in email field
* Check can input very short email address in email field
* Check can not input invalid email address in email field
* Check negtaive test for email field, can input long/short/invalid email address in email field field
* Check negtaive test for IM account field, can input long/short/invalid email address in IM account field field
* Check can input very long URL in URL field
* Check can input very short URL in URL field
* Check can NOT input invalid URL in URL field
* Check negative test for URL field, input long/short/invalid url in URL field
* Check can Not input invalid date in date field
* Check can input 2 contacts with same phone number
* Check can input 2 contacts with same name
* Check can input 2 contacts with same email
* Check can input same title for one contact
* Check can input same URL for one contact
* Check can input same birthday for one contact
* Check can input same IM for one contact
* Check can input 2 contacts with complete same content (name, phone, email, address)
===Stress test===
* Check can Open and close Contacts very frequently
* Check can Start other program (Dialer, SMS, Email) from Contacts very frequently
* Check can Add many contacts
* Check can Delete all contacts
===Misc features===
* Check if it can support Landscape and Portrait orientations, home screen, view contact screen and add/edit screen are shown properly in both mode
* Check if it can support touch gestures to scroll the list, open pop-up menu
* Check if it can go back to previous screen from view contact screen
* Check if it can save contact from add new/Edit contact screen
* Check if it can open Add new/Edit contact screen for editing the current contact
* Check if it can go back to previous screen from add new/edit contact screen
* Check if taping go home button can go back to dui home
==Test Environment==
* MSRT CDK
* Aava
* Netbook
** With DUI image for netbook

==QA Contact==
* [mailto:dayu.yang@intel.com Dayu Yang]

==Developers==
* [mailto:connie.berardi@intel.com Berardi, Connie]

==References==

Quality/Plans/1.1 Handset UX TestPlan

2010-09-13T07:11:10Z

Dayuyang:

= 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]
|-
| Media Applications || Jessica Ji || [http://wiki.meego.com/Quality/MeeGo1.1_Handset_Media_TestPlan MeeGo 1.1 Handset UX Media 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 || [http://wiki.meego.com/Quality/Meego_contacts_test_plan MeeGo 1.1 Handset Contacts 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]
|-
| PIM Management (Clock and Sync client) || Qin Mu || [http://wiki.meego.com/Quality/MeeGo1.1_HandSet_UX_PIM_TestPlan MeeGo 1.1 HandSet UX PIM Test Plan]
|-
| Email ||Yi Fu || [http://wiki.meego.com/Quality/1.1HandsetUXEmailTestPlan MeeGo 1.1 HandSet UX Email application Test Plan]
|-
| Calendar || Dayu Yang || [http://wiki.meego.com/Quality/Meego_Handset_Calendar_TestPlan MeeGo 1.1 Handset Calendar 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