Meego Wiki
Views

Quality/MeeGo1.2HandSetUXTestPlanforSyFuTe

From MeeGo wiki
< Quality
Revision as of 10:05, 1 December 2010 by Mikikone (Talk | contribs)
Jump to: navigation, search

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.

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:
Component Name Description Comments
Audio Player xxx
Calendar Dialer should support the following features 
• User Determined User Busy
• Call hold/retrieve
• Call waiting
• Multiple calls
• Explicit Call Transfer (ECT)
• Call Completion to Busy Subscriber (CCBS)
• USSD Service 
• Multiparty call
• Private conversation during multi-party call
• Split multiparty call
• Mute call
• Auto redial
• Send DTMF tones
• Volume up/down
xxx
Camera Dialer application should support call statistics of 
• Duration of call
• Cost of call
• Remaining ACM balance (TBD)
xxx
Contacts The system shall allow the user to initiate a call from a phone number in the

call history.

xxx
Dialer The device should support a ringing tone to be assigned to a specific contact. xxx
E-mail Dialer should support Call Line Identification (CLIP+CLIR) GSM Supplementary

Service.

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
xxx xxx xxx
xxx xxx xxx

Feature Not To Be Tested

There is no features in Meego 1.2 release that are not 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 : 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