Meego Wiki
Views

Quality/Meego contacts test plan v12

From MeeGo wiki
< Quality(Difference between revisions)
Jump to: navigation, search
(→MeeGo 1.2 Contacts test plan)
(→Features not to be Tested)
 
(10 intermediate revisions not shown)
Line 17: Line 17:
-
==Feature to be Tested==
+
==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 <br>
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 <br>
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.  
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.  
Line 85: Line 85:
|}
|}
-
 
+
==Features not to be Tested==
-
 
+
-
==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
* 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.
+
* 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]
* 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==
==Test Strategy and Approach==
Line 117: Line 114:
===I18N/L10N test===
===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.
+
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==
==Test Design==
Line 130: Line 126:
|-
|-
-
|3025 [FEA] Contacts merging  
+
|rowspan = "2"|3025 [FEA] Contacts merging  
-
|merge contacts
+
|rowspan = "2"|merge contacts
|selected contacts can be merged into one contact
|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
|conflicts in fields could be found and user is able to choose the entry they'd like to present
-
|TBD
+
|
|
|
 +
|-
 +
|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]

Latest revision as of 02:16, 27 December 2010

Contents

MeeGo 1.2 Contacts test plan

History

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.

Feature ID Feature Priority Comments
3025 [FEA] Contacts merging Med
4166 [FEA] Contacts - Recent communication Hig
4170 [FEA] View Contact Screen - Actions - Share contact Med
4176 [FEA] Contact Fields - Title Hig
4178 [FEA] Contact Fields - IM Hig
4191 [FEA] Contacts - contextual menu actions - IM Hig
4801 [FEA] vCard 2.1 reception Hig
6695 [FEA] Contacts backend - Storing phone contact(s) Hig
6697 [FEA] Contacts backend - Storing contact(s) avatar Hig
8155 [FEA] Phone number characters Hig
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. Not testable features
  • This document covers only 1.2 features, for 1.1 features, please reference 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

Feature ID Test point Checkpoint Conditions Collaboration
3025 [FEA] Contacts merging 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
4166 [FEA] Contacts - Recent communication 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
4170 [FEA] View Contact Screen - Actions - Share contact 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
4176 [FEA] Contact Fields - Title contacts field: title there is one title field for each contact
title field can be added, changed and removed
4191 [FEA] Contacts - contextual menu actions - IM 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

Developers

Retrieved from "http://wiki.meego.com/Quality/Meego_contacts_test_plan_v12"
Personal tools