Views
Quality/MeeGo1.2HandSetUXTestPlanforShortMessageService
(→Feature Not To Be Tested) |
m |
||
| Line 128: | Line 128: | ||
** Contains only Response Time part | ** Contains only Response Time part | ||
| - | Test Set Guideline | + | [[Quality/TestSetGuideline|Test Set Guideline]] |
== Handset UX QA Testing Frequency == | == Handset UX QA Testing Frequency == | ||
| - | Overall test sets and those definitions can be found | + | Overall test sets and those definitions can be found [[Quality/TestSetGuideline|here]] |
| - | Link to official milestones and definitions can be found | + | Link to official milestones and definitions can be found [[Release_Engineering/Milestones|here]] |
Next picture illustrates test execution frequency for Handset UX QA team and is aligned with MM milestones. Please, click on picture and select full resolution. | Next picture illustrates test execution frequency for Handset UX QA team and is aligned with MM milestones. Please, click on picture and select full resolution. | ||
Latest revision as of 11:27, 25 March 2011
Contents |
MeeGo 1.2 HandSet UX Test Plan for Short Message Service
Component Summary
This test plan is for MeeGo 1.2 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.2 HandSet UX SMS features will be covered in this test plan. This testplan contains also legacy features from Meego 1.1 release that are coming to 1.2 release. 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 3019 - [FEA] SMS sending to multiple recipients | SMS should support of sending to multiple recipients by selecting recipients
from address book & multiple phone numbers entries. || xxx | |
| Feature 4159 - [FEA] SMS - SMS Message Indication | The device shall support SMS Message indication to match an existing contact. | xxx |
| Feature 3015 - [FEA] SMS pick phone number from message | SMS should support to extract a phone number from SMS header and text to
provide a quick way to call back to the sender or other indicated number. | xxx |
| Feature 3022 - [FEA] SMS delivery notifications | SMS should support message notifications of success of the message delivery to
the recipient. | xxx |
| Feature http://bugs.meego.com/show_bug.cgi?id=3020 3020] - [FEA] SMS composing a message | SMS should support composing a message with characters supported by the current
cellular network and the language localisation of the device. | xxx |
| Feature 2656 - [FEA] SMS Cell Broadcast | SMS should support broadcast messages (advertising, public information, etc.)
as specified for Cell Broadcast service (SMS-CB) in 3GPP GSM 03.41 specification. | xxx |
| Feature 3016 - [FEA] SMS pick URL from message | SMS should support to extract an URL from SMS text body and provide actions to
utilise the URL in other applications, e.g. to launch the Browser. | xxx |
| Feature 3013 - [FEA] SMS message forward | SMS should support forwarding a message. | xxx |
| Feature 3014 - [FEA] SMS message reply | SMS should support replying to a received message. | xxx |
| Feature 4154 - [FEA] SMS - Recieve an SMS | The system shall be able to receive a newly delivered SMS | xxx |
| Feature 4155 - [FEA] SMS - Send an SMS | The user shall be able to send an SMS | xxx |
| Feature 4158 - [FEA] SMS - Save an SMS | The user shall be able to save an SMS | xxx |
| Feature 3021 - [FEA] SMS display number of characters once composing | SMS should support of displaying number of characters inputted and left to fit
to a single message while it is being composed. | xxx |
| Feature 3023 - [FEA] SMS message history | SMS should support message history of sent and received message. | xxx |
| Feature 4153 - [FEA] SMS - Create an SMS | The user shall be able to create a message for SMS | xxx |
| Feature 4157 - [FEA] SMS - View an SMS | The user shall be able to view an SMS | xxx |
| Feature 4156 - [FEA] SMS - Delete an SMS | The User shall be able to delete an SMS message. | xxx |
| Feature 3017 - [FEA] SMS multi-page messages | SMS should support to send messages that exceed the number of characters
supported by the current cellular network in a single message (e.g. GSM 160 characters) by providing the means to send such a message splitted to multiple messages (multi-page messages). | xxx |
| Feature 3018 - [FEA] SMS autostore message in creation | SMS should support storing last edited message automatically as a draft in a
provided folder. | xxx |
| xxx | xxx | xxx |
Feature Not To Be Tested
List of Not testable features can be found using this query: Not testable features
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
Handset UX QA Testing Frequency
Overall test sets and those definitions can be found here
Link to official milestones and definitions can be found here
Next picture illustrates test execution frequency for Handset UX QA team and is aligned with MM milestones. Please, click on picture and select full resolution.
Hardware Platforms
Supported hardware info: http://meego.com/devices/handset/handset-supported-hardware