Meego Wiki
Views

Quality/MeeGo1.2HandSetUXTestPlanforSyFuTe

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Feature Not To Be Tested)
(→Component To Be Tested)
Line 9: Line 9:
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 also exmples of tested scenarios are presented:
{| border="1"
{| border="1"

Revision as of 12:41, 1 December 2010

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

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 also exmples of tested scenarios are presented:
Component Name Description 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
• Multiple
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 intervorking and merging with local 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 viwwing photos
xxx
Contacts For Contacts following scenarios are tested 
• Incoming calls
• System alarms
• Different interactions while using camera
• Different camera usage scenarios
xxx
Dialer For Dialer following scenarios are tested 
• Different ways to make a call, mute/unmute
• Calls with accessories
• System alarms
• Different interactions during call
• Dialer settings 
• Offline mode 
• Incoming messages
xxx
E-mail For E-mail following scenarios are tested 
• e-mail with different bearers 
• e-mail with attachments
• System alarms
• Different interactions while using e-mail client
• E-mail settings 
• Offline mode 
• Incoming messages
• Incoming calls
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
• SMS settings
• Network changes while sending SMS
• Incoming calls 
• 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
• Incoming calls 
• Incoming messages
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
• Browser settings 
• Network changes while browsing
• Browsing different types of content
• Incoming calls 
• Incoming messages
xxx
Applets Dialer should support sending Dual-Tone Multi-Frequency (DTMF) tones to the

network in order to interact with provided network services, such as service numbers and conference centers.

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
• Different interactions while using IM client
• IM settings  
• Incoming messages
• Incoming calls
xxx
DUIhome DUIhome is tested when testing other components xxx
xxx xxx xxx
xxx xxx xxx
xxx xxx xxx
xxx xxx xxx

Feature Not To Be 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

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 : http://wiki.meego.com/Quality/HandsetUXQATestFrequency

Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline

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