Meego Wiki
Views

Quality/MeeGo1.2HandSetUXTestPlanforConnectivityUI

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Hardware Platforms)
(→Strategy and Approach)
Line 47: Line 47:
Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
 +
 +
== Handset UX QA Testing Frequency ==
 +
 +
Overall test sets and those definitions can be found http://wiki.meego.com/Quality/TestSetGuideline
 +
 +
Link to official milestones and definitions can be found http://wiki.meego.com/Release_Engineering/Milestones
 +
 +
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.
 +
 +
[[File:MeeGoReleaseTimeline_Test_Execution.JPG|600px]]
=== Hardware Platforms ===
=== Hardware Platforms ===

Revision as of 17:40, 30 November 2010

Contents

MeeGo 1.2 HandSet UX Test Plan for Connectivity UI

Component Summary

This test plan is for MeeGo 1.2 HandSet UX Connectivity UI.

Feature To Be Tested

All testable features coming to MeeGo 1.2 HandSet UX Connectivity UI features will be covered in this test plan.

  • Connectivity UI Features to be tested are summarized as below:
Feature Name Description Comments
Feature 9251 - [FEA] [I18N]The Connectivity UI app shall be internationalized according to the dependencies listed in Core Master 5068.
  • Unicode support
  • All translatable strings are externalized
  • UI adaptability to longer and shorter strings than English
  • Ability to accept, display, sort, search, copy, paste, and print accented and double-byte characters
  • No concatenation of translatable strings
  • Support for the POR languages: en_US, en_GB, fr, de, es, it, fi, sv, pl, ru,nl, pt_BR, ja, ko, zh_TW, zh_CN
xxx
xxx xxx xxx

Feature Not To Be Tested

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

There are no features that are not tested.

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

Handset UX QA Testing Frequency

Overall test sets and those definitions can be found http://wiki.meego.com/Quality/TestSetGuideline

Link to official milestones and definitions can be found http://wiki.meego.com/Release_Engineering/Milestones

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.

MeeGoReleaseTimeline Test Execution.JPG

Hardware Platforms

Supported hardware info: http://meego.com/devices/handset/handset-supported-hardware

QA Contact

Retrieved from "http://wiki.meego.com/Quality/MeeGo1.2HandSetUXTestPlanforConnectivityUI"
Personal tools