Quality/MeeGo1.1HandSetUXTestPlanforShortMessageService

Contents 1 MeeGo 1.1 HandSet UX Test Plan for Short Message Service 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 Short Message Service

Component Summary

This test plan is for MeeGo 1.1 HandSet UX Short Message Service (SMS). SMS depends on ofono (for telephony services), SMS history (ofono SMS history plugin) and libseaside (for contacts data).

Feature To Be Tested

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

• SMS 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

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

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

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

Hardware Platforms

• N900, AAVA and MRST CDK

QA Contact

• Mika Ikonen