Meego Wiki
Views

Quality/MeeGo1.1HandSetUXTestPlanforShortMessageService

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Feature To Be Tested)
(→Feature To Be Tested)
Line 14: Line 14:
!| Comments
!| Comments
|-
|-
-
| || || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=2655 2655] -  [FEA] SMS application message handling functionality || SMS should support following message handling functionality
 +
-Open message
 +
-Forward message
 +
-Reply to message
 +
-Extract phone number from SMS header and text
 +
-Call back to SMS sender
 +
-Extract URL from SMS text body
 +
-Send Multi-page messages
 +
-Automatic storage of last edited message in drafts
 +
-Sending to multiple recipients by selecting recipients from address book &
 +
multiple phone numbers entries
 +
-Display number of characters in the SMS while it is being composed. 
 +
  || xxx
|-
|-
| Feature [http://bugs.meego.com/show_bug.cgi?id=2629 2629] -  [FEA] Short Message Service (SMS) application  || A short message service application (SMS) is required to send and receive
| Feature [http://bugs.meego.com/show_bug.cgi?id=2629 2629] -  [FEA] Short Message Service (SMS) application  || A short message service application (SMS) is required to send and receive
Line 25: Line 37:
SMS should support message notifications of success of the message delivery to
SMS should support message notifications of success of the message delivery to
-
the recipient   
+
the recipient.
 +
|| xxx  
|-
|-
-
| xxx || xxx || xxx  
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=4529 4529] -  [FEA] Cellular - SMS || The solution shall have an SMS (Short Messaging Service)  communication service
 +
to facilitate the exchange of text messages between mobile devices. 
 +
|| xxx  
|-
|-
-
| xxx || xxx || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=4531 4531] - [FEA] Cellular - SMS reply path selection for sender || The solution shall support the ability to Reply path setting - allows to chose
 +
which SMSC outgoing message will use 
 +
|| xxx
|-
|-
-
| xxx || xxx || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=4533 4533] -  [FEA] Cellular - Multiple SMS centers  || Multiple SMS profiles with different SMSC numbers 
 +
|| xxx
|-
|-
-
| xxx || xxx || xxx  
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=4534 4534] - [FEA] Cellular - User-selectable bearer choice  ||The solution shall support SMS CS/PS bearer selection.  Several operators
 +
mandate a particular setting for the SMS bearer.  Determien if this should be
 +
exposed as a property or a global setting.
 +
|| xxx
|-
|-
-
| xxx || xxx || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=4535 4535] - [FEA] Cellular - Source / Destination Port Addressing Scheme  || The solution shall support the source/destination port addressing scheme as
 +
specified in 3GPP 23.040.  A special header is used to indicate the
 +
source/destination port of the application this SMS message belongs to. Such
 +
messages which are encoded in 8-bit should be decoded by oFono automatically.
 +
The handler associated with this source/destination port is called with the
 +
decoded stream. 
 +
|| xxx
|-
|-
-
| xxx || xxx || xxx
+
| Feature [http://bugs.meego.com/show_bug.cgi?id=4551 4551 - [FEA] Cellular - Reading access to CBMI ] || xxx || xxx
-
|-
+
-
| xxx || xxx || xxx
+
-
|-
+
-
| xxx || xxx || xxx
+
|-
|-
| xxx || xxx || xxx
| xxx || xxx || xxx

Revision as of 10:02, 10 September 2010

Contents

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
Feature 2655 - [FEA] SMS application message handling functionality SMS should support following message handling functionality

-Open message -Forward message -Reply to message -Extract phone number from SMS header and text -Call back to SMS sender -Extract URL from SMS text body -Send Multi-page messages -Automatic storage of last edited message in drafts -Sending to multiple recipients by selecting recipients from address book & multiple phone numbers entries -Display number of characters in the SMS while it is being composed.

xxx
Feature 2629 - [FEA] Short Message Service (SMS) application A short message service application (SMS) is required to send and receive

cellular short text messages.

SMS should support numeric key entry to enter a recipient phone number and integration to a Contacts application to select a recipient.

SMS should support message history of sent and received message.

SMS should support message notifications of success of the message delivery to the recipient.

xxx
Feature 4529 - [FEA] Cellular - SMS The solution shall have an SMS (Short Messaging Service) communication service

to facilitate the exchange of text messages between mobile devices.

xxx
Feature 4531 - [FEA] Cellular - SMS reply path selection for sender The solution shall support the ability to Reply path setting - allows to chose

which SMSC outgoing message will use

xxx
Feature 4533 - [FEA] Cellular - Multiple SMS centers Multiple SMS profiles with different SMSC numbers xxx
Feature 4534 - [FEA] Cellular - User-selectable bearer choice The solution shall support SMS CS/PS bearer selection. Several operators

mandate a particular setting for the SMS bearer. Determien if this should be exposed as a property or a global setting.

xxx
Feature 4535 - [FEA] Cellular - Source / Destination Port Addressing Scheme The solution shall support the source/destination port addressing scheme as

specified in 3GPP 23.040. A special header is used to indicate the source/destination port of the application this SMS message belongs to. Such messages which are encoded in 8-bit should be decoded by oFono automatically. The handler associated with this source/destination port is called with the decoded stream.

xxx
Feature 4551 - [FEA Cellular - Reading access to CBMI ] 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

Retrieved from "http://wiki.meego.com/Quality/MeeGo1.1HandSetUXTestPlanforShortMessageService"
Personal tools