(→Feature not to be Tested) |
(categorise, cut toplevel heading, wikify table formatting) |
||
| (4 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | |||
==Component Summary== | ==Component Summary== | ||
* '''Email Client ''' | * '''Email Client ''' | ||
| Line 7: | Line 6: | ||
==Feature to be Tested== | ==Feature to be Tested== | ||
| - | All testable features coming to MeeGo 1.1 HandSet UX | + | All testable features coming to MeeGo 1.1 HandSet UX Email will be covered in this test plan. |
| - | + | {| class="wikitable" | |
| - | + | |+ Email Features to be tested | |
| - | + | |- | |
!|Feature Name | !|Feature Name | ||
!|Feature Description | !|Feature Description | ||
| Line 84: | Line 83: | ||
==Feature not to be Tested== | ==Feature not to be Tested== | ||
| - | List of features that are not tested in this test plan | + | |
| - | + | {| class="wikitable" | |
| + | |+ List of features that are not tested in this test plan | ||
| + | |- | ||
!|Feature Name | !|Feature Name | ||
!|Feature Description | !|Feature Description | ||
| Line 127: | Line 128: | ||
==Test Strategy and Approach== | ==Test Strategy and Approach== | ||
In general, the email client test applies Black-Box test methods and refers to feature implementations to guide test design. Email client application will be tested from different levels below: | In general, the email client test applies Black-Box test methods and refers to feature implementations to guide test design. Email client application will be tested from different levels below: | ||
| - | * GUI testing | + | * GUI testing |
| + | ** Cover UI testing | ||
| + | ** Better interaction with touch screen | ||
| + | ** Common UI operation | ||
| + | ** i18n | ||
| - | * Functional testing | + | * Functional testing |
| + | ** Email account setup | ||
| + | ** POP3/IMAP/SMTP email protocol support | ||
| + | ** Email send/receive/replay/replay all/compose/forward/cc/bcc/attachment/view | ||
| + | ** Messaging list | ||
| + | ** Html/text email format support | ||
| + | ** Email sort | ||
| + | ** Move/delete/save email | ||
| + | ** Search email | ||
| + | ** Different email account settings like signature,email mail content and size limitation, push mail setting | ||
| - | * Stress testing | + | * Stress testing |
| + | ** Launch application multi times | ||
| + | ** Send/receive big attchment | ||
| + | ** Receive large amount of email | ||
| + | ** Repeat send/receive in short time | ||
| - | * Negative Test | + | * Negative Test |
| + | ** Wrong email account setting | ||
| + | ** Long email subject | ||
| + | ** Special character in email subject | ||
| + | ** Send email to invalid email address | ||
| + | ** Network disconnect during send/receive email | ||
==Test Design== | ==Test Design== | ||
| Line 216: | Line 239: | ||
** Check that the folder view reflects the new account | ** Check that the folder view reflects the new account | ||
* Contextual menu - CAP | * Contextual menu - CAP | ||
| - | ** Check that the contextual panel contains the following items – reply, forward, discard | + | ** Check that the contextual panel contains the following items – reply, forward, discard) |
** Check that the contextual menu contains reply all when the message contains CC recipients and doesn't when the message doesn't not contain cc recipients | ** Check that the contextual menu contains reply all when the message contains CC recipients and doesn't when the message doesn't not contain cc recipients | ||
** Check that the contextual menu contains “move” menu item only appears if there are more than one folder | ** Check that the contextual menu contains “move” menu item only appears if there are more than one folder | ||
| Line 337: | Line 360: | ||
** Check that selecting cancel returns to the message compose view | ** Check that selecting cancel returns to the message compose view | ||
** Check that suspecting back transitions back to the “type” pop-up | ** Check that suspecting back transitions back to the “type” pop-up | ||
| - | |||
| - | |||
| - | |||
| - | |||
===Address book (TBD) === | ===Address book (TBD) === | ||
| Line 351: | Line 370: | ||
==QA Contact== | ==QA Contact== | ||
* [mailto:yi.fu@intel.com Fu Yi] | * [mailto:yi.fu@intel.com Fu Yi] | ||
| + | |||
| + | [[Category:QA]] | ||
| + | [[Category:Meego-1.1]] | ||
Contents |
This test plan is for MeeGo 1.1 HandSet UX Email application.
The email client depends on QT messaging framework. The Qt Messaging Framework, QMF, consists of a C++ library and daemon server process that can be used to build email clients, and more generally software that interacts with email and mail servers.
All testable features coming to MeeGo 1.1 HandSet UX Email will be covered in this test plan.
| Feature Name | Feature Description | Vertical | Priority | Comments |
|---|---|---|---|---|
| POP3/IMAP/SMTP protocol support |
| Handset | P1 | The design input: UI design 17 Aug 2010 version and feature bugs: Meego 1.1 Email features |
| Email operation | Check popular email operation support
| Handset | P1 | The design input: UI design 17 Aug 2010 version and feature bugs: Meego 1.1 Email features |
| Email full view |
| Handset | P1 | The design input: UI design 17 Aug 2010 version and feature bugs: Meego 1.1 Email features |
| Email client generate UI |
| Handset | P1 | The design input: UI design 17 Aug 2010 version and feature bugs: Meego 1.1 Email features |
| Email attachment support |
| Handset | P1 | The design input: UI design 17 Aug 2010 version and feature bugs: Meego 1.1 Email features |
| TBD: address book/contact management |
TBD | The design input: UI design 17 Aug 2010 version and feature bugs: Meego 1.1 Email features | ||
| I18N & L10N |
| Handset | P1 | The design input: UI design 17 Aug 2010 version and feature bugs: Meego 1.1 Email features |
| Feature Name | Feature Description | Vertical | Priority | Comments |
|---|---|---|---|---|
| Email backend service features |
|
| ||
| Email features don't be supported in meego 1.1 release |
|
|
In general, the email client test applies Black-Box test methods and refers to feature implementations to guide test design. Email client application will be tested from different levels below:
delete