(→System Functional Testing Summary) |
(→Feature Not To Be Tested) |
||
| Line 138: | Line 138: | ||
=== Feature Not To Be Tested === | === 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 | + | 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 === | ||
Contents |
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 Functioal Testing we are using RBT - Risk Based Testing since othervise testcase amount would be huge.
All testable components coming to MeeGo 1.2 HandSet UX will be covered in this test plan.
| 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 • 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 • 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 • Different interactions during call • Collaboration with settings • Offline mode • Incoming messages | xxx |
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 • Collaboration with 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 • Collaboration with 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 • 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 • 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 • Collaboration with 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 |
Not testable components/features can be found from this query: Features not to be tested
System Functional Testing is tested in System Functional Testset.
Testing Frequency : http://wiki.meego.com/Quality/HandsetUXQATestFrequency
Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline