Quality/MeeGo1.1HandSetUXTestPlanforDialer

Contents 1 MeeGo 1.1 HandSet UX Test Plan for Dialer 1.1 Component Summary 1.2 Feature To Be Tested 1.3 Feature Not To Be Tested 1.4 Strategy and Approach 1.5 Hardware Platforms 1.6 QA Contact

MeeGo 1.1 HandSet UX Test Plan for Dialer

Component Summary

This test plan is for MeeGo 1.1 HandSet UX Dialer application. Dialer is a simple Voice Call Dialer/Manager. It depends on ofono (for telephony services), call history (ofono call history plign) and libseaside (for contacts data).

Feature To Be Tested

All testable features coming to MeeGo 1.1 HandSet UX Dialer will be covered in this test plan. Note! Also telephony setting features are covered in this test plan.

• Dialer Features to be tested are summarized as below:

Feature Name	Description	Comments
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx
xxx	xxx	xxx

Feature Not To Be Tested

List of features that are not tested as part of MeeGo 1.1 HandSet UX are:

<add here correct query from fearutezilla>

Strategy and Approach

Dialer is tested in different test sets. Test sets containing dialer related test cases are

• Sanity Test Set
  • Contains few basic dialer test cases that Dialer application is part of SW image, can be opened and basic call can be made
• Basic Feature Test Set
  • Contains basic feature (Functional) test cases for every testable dialer feature
• Extended Feature Test Set
  • Contains bunch of well selected dialer test cases to verify that delivered features (Functional) forming component are working
• System Functional Test Set
  • Contains interaction and negative test cases were Dialer is used together with other components that are part of system

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

Hardware Platforms

• N900, AAVA and MRST CDK

QA Contact

• Mika Ikonen (mika.m.ikonen@nokia.com)