Meego Wiki
Views

Quality/MeeGo1.2HandSetUXTestPlanforSyFuTe

From MeeGo wiki
< Quality(Difference between revisions)
Jump to: navigation, search
(→Component To Be Tested)
m (→Strategy and Approach)
 
(19 intermediate revisions not shown)
Line 3: Line 3:
=== System Functional Testing Summary ===
=== System Functional Testing Summary ===
This test plan is for MeeGo 1.2 HandSet UX System Functional Testing. System Functional testing covers componenent interaction testing and negative testing.
This test plan is for MeeGo 1.2 HandSet UX System Functional Testing. System Functional testing covers componenent interaction testing and negative testing.
 +
Target is to test basic (functional) system testing of several components/features simultaneously.
 +
Test case example: Listening music while receiving incoming call. For System Functional Testing we are using RBT - Risk Based Testing since othervise test case amount would be huge.
=== Component To Be Tested ===
=== Component To Be Tested ===
All testable components coming to MeeGo 1.2 HandSet UX  will be covered in this test plan.  
All testable components coming to MeeGo 1.2 HandSet UX  will be covered in this test plan.  
-
* Components to be tested are summarized as below:
+
* Components to be tested are summarized as below and also examples of tested scenarios are presented:
{| border="1"
{| border="1"
!| Component Name
!| Component Name
-
!| Description
+
!| Brief Description of tested scenarios
!| Comments
!| Comments
|-
|-
-
| Audio Player  || || xxx
+
|   Audio Player  || For Audio Player following scenarios are tested
 +
• Collaboration with DUIhome, settings, IM,Email, Web browser, BT client
 +
• Sharing music, modifying playlists, Arranging music
 +
• Incoming calls during playback
 +
• Player controls using accessories
 +
• System alarms during playback eg. clock, calendar/task during playback
 +
• Incoming messages during playback
 +
|| xxx
|-
|-
-
| Calendar || Dialer should support the following features
+
| Calendar || For calendar following scenarios are tested
-
  • User Determined User Busy
+
  • Managing events and interacting contacts
-
  • Call hold/retrieve
+
  • Event alarms while using calendar
-
  • Call waiting
+
  • Calendar synchronisation and sharing with e-mail
-
• Multiple calls
+
  • Different calendar notifications
-
• Explicit Call Transfer (ECT)
+
  • iCalendar/vCalendar interworking and merging with local calendar
-
• Call Completion to Busy Subscriber (CCBS)
+
  • Calls while using calendar
-
• USSD Service
+
-
• Multiparty call
+
-
• Private conversation during multi-party call
+
-
  • Split multiparty call
+
-
  • Mute call
+
-
  • Auto redial
+
-
• Send DTMF tones
+
-
• Volume up/down
+
|| xxx
|| xxx
|-
|-
-
| Camera || Dialer application should support call statistics of
+
| Camera and photo viewer || For Camera and photo viewer following scenarios are tested
-
  • Duration of call
+
  • Camera usage negative scenarios eg. memory full
-
  • Cost of call
+
• System alarms while using camera and viewing photos
-
  • Remaining ACM balance (TBD)
+
  • Different interactions while using camera eg. incoming call, SMS, listening music with accessories etc.
 +
  • Different camera usage scenarios and user actions while viewing photos
|| xxx  
|| xxx  
|-
|-
-
| Contacts || The system shall allow the user to initiate a call from a phone number in the
+
| Contacts || For Contacts following scenarios are tested
-
call history.
+
• Incoming calls while using contacts
 +
• System alarms while using contacts
 +
• Different interactions while using camera
 +
• Different camera usage scenarios
 +
• Collaboration with differrent settings
|| xxx
|| xxx
|-
|-
-
| Dialer || The device should support a ringing tone to be assigned to a specific contact.
+
| Dialer || For Dialer following scenarios are tested
 +
• Different ways to make a call, mute/unmute
 +
• Calls with accessories
 +
• System alarms while call is ongoing
 +
• Different interactions during call
 +
• Collaboration with settings
 +
• Offline mode
 +
• Incoming messages while call is ongoing
|| xxx
|| xxx
|-
|-
-
| E-mail || Dialer should support Call Line Identification (CLIP+CLIR) GSM Supplementary
+
| E-mail || For E-mail following scenarios are tested
-
Service.
+
• e-mail with different bearers
 +
• e-mail with attachments
 +
• System alarms while using e-mail client
 +
• Different interactions while using e-mail client
 +
• Collaboration with settings
 +
• Offline mode
 +
• Incoming messages while using e-mail client
 +
• Incoming calls while using e-mail client
|| xxx  
|| xxx  
|-
|-
-
| Photo viewer || Dialer should support to put the call on hold and retrieve it back from hold.
+
| Short Messaging Service - SMS || For SMS following scenarios are tested
 +
• Interaction with VKB and DUIHome copy/paste text content
 +
• Special characters
 +
• Different interactions while writing/viewing/sending/receiving SMS
 +
• Collaboration with settings
 +
• Network changes while sending SMS
 +
• Incoming calls while viewing, writing, receiving SMS
 +
• Incoming messages
|| xxx
|| xxx
|-
|-
-
| Short Messaging Service - SMS || Dialer should support Call waiting functionality  
+
| Video Player || For Video Player following scenarios are tested
 +
  • User actions while playback is ongoing
 +
• Video player controls from accessories
 +
• Different interactions while using video player
 +
• System alarms while using player
 +
• Incoming calls while using player
 +
• Incoming messages
 +
• Collaboration with settings
|| xxx
|| xxx
|-
|-
-
| Video Player || Dialer should support handling Multiple calls at the same time. Minimum 2 calls
+
| Web Browser || For Web Browser following scenarios are tested
-
at the same time should be supported (one on hold, one on line).  
+
• Browsing with different bearers
 +
• Music listening while bowsing
 +
• Accessory usage while brosing and viewing content
 +
• Different interactions while using browser
 +
• Collaboration with settings
 +
• Network changes while browsing
 +
• Browsing different types of content
 +
• Incoming calls while browsing
 +
  • Incoming messages while browsing
|| xxx
|| xxx
|-
|-
-
| Web Browser|| Dialer application should support to be able to mute incoming call ringing
+
| Applets || Applets are allready tested in other testsets
-
tone. 
+
|| xxx
|| xxx
|-
|-
-
| Applets || Dialer should support sending Dual-Tone Multi-Frequency (DTMF) tones to the
+
| Virtual Key Board || Virtual keyboard is tested while testing other components eg. SMS and browser
-
network in order to interact with provided network services, such as service
+
-
numbers and conference centers.  
+
|| xxx
|| xxx
|-
|-
-
| Virtual Key Board || The system shall provide one click viewing access while in a call to the
+
| Instant Messaging - IM || For IM following scenarios are tested
-
following functions: mute, contacts, call history, loud speaker, hold, and home
+
• Different usage scenarios for IM
-
screen.  
+
• System alarms while using IM client
 +
• Different interactions while using IM client
 +
  • Collaboration with settings 
 +
• Incoming messages while using IM client
 +
• Incoming calls while using IM client
|| xxx
|| xxx
|-
|-
-
| Instant MEssaging - IM || xxx
+
| DUIhome || DUIhome is tested when testing other components
|| xxx
|| xxx
|-
|-
-
| xxx || xxx
 
-
|| xxx
 
-
 
|}
|}
=== Feature Not To Be Tested ===
=== Feature Not To Be Tested ===
-
There is no features in Meego 1.2 release that are not tested.
+
Not testable components/features can be found from this query: [http://bugs.meego.com/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=MeeGo%20Features&deadlinefrom=&deadlineto=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailqa_contact2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field0-0-0=noop&longdesc=&longdesc_type=allwordssubstr&product=MeeGo%20Handset%20Features&short_desc=&short_desc_type=allwordssubstr&type0-0-0=noop&value0-0-0=&version=1.1&version=1.2&votes=&=&cf_testability=No Features not to be tested]
=== Strategy and Approach ===
=== Strategy and Approach ===
Line 89: Line 129:
* 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 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.  
 +
[[Quality/HandsetUXQATestFrequency|Testing Frequency]]
-
Testing Frequency : http://wiki.meego.com/Quality/HandsetUXQATestFrequency
+
[[Quality/TestSetGuideline|Test Set Guideline]]
-
Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
+
=== QA Contact ===
 +
* [mailto:mika.m.ikonen@nokia.com Mika Ikonen]

Latest revision as of 11:24, 25 March 2011

Contents

MeeGo 1.2 HandSet UX Test Plan for System Functional Testing

System Functional Testing Summary

This test plan is for MeeGo 1.2 HandSet UX System Functional Testing. System Functional testing covers componenent interaction testing and negative testing. Target is to test basic (functional) system testing of several components/features simultaneously. Test case example: Listening music while receiving incoming call. For System Functional Testing we are using RBT - Risk Based Testing since othervise test case amount would be huge.

Component To Be Tested

All testable components coming to MeeGo 1.2 HandSet UX will be covered in this test plan.

  • Components to be tested are summarized as below and also examples of tested scenarios are presented:
Component Name Brief Description of tested scenarios Comments
Audio Player For Audio Player following scenarios are tested 
• Collaboration with DUIhome, settings, IM,Email, Web browser, BT client 
• Sharing music, modifying playlists, Arranging music 
• Incoming calls during playback 
• Player controls using accessories
• System alarms during playback eg. clock, calendar/task during playback
• Incoming messages during playback
xxx
Calendar For calendar following scenarios are tested 
• Managing events and interacting contacts
• Event alarms while using calendar
• Calendar synchronisation and sharing with e-mail
• Different calendar notifications
• iCalendar/vCalendar interworking and merging with local calendar
• Calls while using calendar
xxx
Camera and photo viewer For Camera and photo viewer following scenarios are tested 
• Camera usage negative scenarios eg. memory full
• System alarms while using camera and viewing photos
• Different interactions while using camera eg. incoming call, SMS, listening music with accessories etc.
• Different camera usage scenarios and user actions while viewing photos
xxx
Contacts For Contacts following scenarios are tested 
• Incoming calls while using contacts
• System alarms while using contacts
• Different interactions while using camera
• Different camera usage scenarios
• Collaboration with differrent settings
xxx
Dialer For Dialer following scenarios are tested 
• Different ways to make a call, mute/unmute
• Calls with accessories
• System alarms while call is ongoing
• Different interactions during call
• Collaboration with settings 
• Offline mode 
• Incoming messages while call is ongoing
xxx
E-mail For E-mail following scenarios are tested 
• e-mail with different bearers 
• e-mail with attachments
• System alarms while using e-mail client
• Different interactions while using e-mail client
• Collaboration with settings 
• Offline mode 
• Incoming messages while using e-mail client
• Incoming calls while using e-mail client
xxx
Short Messaging Service - SMS For SMS following scenarios are tested 
• Interaction with VKB and DUIHome copy/paste text content
• Special characters
• Different interactions while writing/viewing/sending/receiving SMS
• Collaboration with settings
• Network changes while sending SMS
• Incoming calls while viewing, writing, receiving SMS
• Incoming messages
xxx
Video Player For Video Player following scenarios are tested 
• User actions while playback is ongoing
• Video player controls from accessories
• Different interactions while using video player
• System alarms while using player
• Incoming calls while using player
• Incoming messages
• Collaboration with settings
xxx
Web Browser For Web Browser following scenarios are tested 
• Browsing with different bearers 
• Music listening while bowsing 
• Accessory usage while brosing and viewing content
• Different interactions while using browser
• Collaboration with settings 
• Network changes while browsing
• Browsing different types of content
• Incoming calls while browsing
• Incoming messages while browsing
xxx
Applets Applets are allready tested in other testsets xxx
Virtual Key Board Virtual keyboard is tested while testing other components eg. SMS and browser xxx
Instant Messaging - IM For IM following scenarios are tested 
• Different usage scenarios for IM
• System alarms while using IM client
• Different interactions while using IM client
• Collaboration with settings  
• Incoming messages while using IM client
• Incoming calls while using IM client
xxx
DUIhome DUIhome is tested when testing other components xxx

Feature Not To Be Tested

Not testable components/features can be found from this query: Features not to be tested

Strategy and Approach

System Functional Testing is tested in System Functional Testset.

  • 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.

Testing Frequency

Test Set Guideline

QA Contact

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