(→Component To Be Tested) |
(→System Functional Testing Summary) |
||
| 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 | ||
=== Component To Be Tested === | === Component To Be Tested === | ||
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
All testable components coming to MeeGo 1.2 HandSet UX will be covered in this test plan.
| 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 | For Camera following scenarios are tested
• Incoming calls • System alarms • Different interactions while using camera • Different camera usage scenarios | 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 |
For E-mail following scenarios are tested
• e-mail with different bearers • e-mail with attachments • System alarms • Different interactions using e-mail client • E-mail settings • Offline mode • Incoming messages • Incoming calls | xxx | |
| Photo viewer | Dialer should support to put the call on hold and retrieve it back from hold. | xxx |
| Short Messaging Service - SMS | Dialer should support Call waiting functionality | xxx |
| Video Player | Dialer should support handling Multiple calls at the same time. Minimum 2 calls
at the same time should be supported (one on hold, one on line). | xxx |
| Web Browser | Dialer application should support to be able to mute incoming call ringing
tone. | 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 | The system shall provide one click viewing access while in a call to the
following functions: mute, contacts, call history, loud speaker, hold, and home screen. | xxx |
| Instant MEssaging - IM | xxx | xxx |
| DUI Home | xxx | xxx |
| xxx | xxx | xxx |
| xxx | xxx | xxx |
| xxx | xxx | xxx |
| xxx | xxx | xxx |
There is no features in Meego 1.2 release that are not 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