Meego Wiki
Views

Quality/Meego Handset SyncUI TestPlan v1.2

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Created page with "=SyncUI Test Plan= ==History== {| class="wikitable" border="1" |- style="background-color:#538ED5;font-weight:bold;font-style:Italic;text-decoration:underline;color:#FFFFFF" a…")
(→Test Strategy and Approach)
Line 99: Line 99:
* Stress test on stability and repentance
* Stress test on stability and repentance
-
'''[http://moblin.intel.com/wiki/MeeGo_QA/Tablet/1.1/TestDesignGuideline Test Design Guideline ]and [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method test method]:'''
+
'''[http://moblin.intel.com/wiki/MeeGo_QA/Tablet/1.1/TestDesignGuideline Test Design Guideline ]and [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Test method]:'''
* Mostly based on UI experience and own functionality. For more details about these methods, please see references section.
* Mostly based on UI experience and own functionality. For more details about these methods, please see references section.

Revision as of 06:16, 6 December 2010

Contents

SyncUI Test Plan

History

Date Modification
11/30/2010 Initial Draft

Summary

SyncUI UI provide end-users with all the sync services for meego handset.

File:SyncUI Arch.png

Features to be Tested

  • The features listed here are all from MeeGo handset featurezilla, the test will cover all these features with required priority, as well as generic features of both functional and GUI, e.g. i18/l10n.
  • Considering SyncUI directly interact with end-users, fully testing strategy is applied, and testing covers functions, GUI, as well as basic user experience evaluation. Each feature is firstly validate with at least one basic test case to check key its key/high-priority function points within the key/common usage contexts from the standpoints of end-users. In addition to basic test set, extended test set are designed to further validate feature against function points of lower priority and common-less usage contexts.
ID Summary Description
5462 [FEA] SyncUI - Visibility of an ongoing synchronization The user shall be able to see an ongoing synchronization in a form of indicator icon or in a separate central location/application displaying ongoing data or application level transfers.
5463 [FEA] SyncUI - Information about last synchronization The user shall be able to see outcome of previous synchronization. The presented information includes added/modified/problematic entries from the previous synchronization.
5464 [FEA] SyncUI - Manual synchronization The user shall be able to manually start synchronization towards the selected destination.
5465 [FEA] SyncUI - Stopping synchronization The user shall be able to manually stop an ongoing synchronization.
5466 [FEA] SyncUI - Setting interval The user shall be able to define the interval for a scheduled synchronization. The interval options offered for the user are daily, twice a day, every hour and every 5, 15, 30 minutes.
5467 [FEA] SyncUI - Data types The solution shall support contacts, calendar and notes entries for synchronization.
5468 [FEA] SyncUI - Destinations The solution shall support the following online destinations: Google contacts, Scheduleworld.com and Mobical.net. These destinations may be included and/or pre-configured.
5469 [FEA] SyncUI - Setting destinations The user shall be able to enable and disable destinations for synchronization.
5470 [FEA] SyncUI - Setting data types for destinations The user shall be able to select the data types synchronized towards a destination.
5471 [FEA] SyncUI - User account for destinations The solution shall be able to utilize the Accounts/SSO for retrieving account specific to a destination.
5472 [FEA] SyncUI - MeeGo device to MeeGo device synchronization The solution shall support MeeGo device to MeeGo device synchronization over Bluetooth.

Feature not to be Tested

  • Performance testing is covered by Performance test plan.

Test Strategy and Approach

Based on the direction, following areas will be tested with high priority:

  • UI experience and functionality test, interaction with touch screen, common UI operation etc. It also includes i18n/l10n test.
  • Functionality verification, collaboration with other applications and with related devices

We will also cover the following functionality test:

  • Relative UI changes in HOME screen(mainly for panel settings), Status Bar, My tablet panel etc.
  • Stress test on stability and repentance

Test Design Guideline and Test method:

  • Mostly based on UI experience and own functionality. For more details about these methods, please see references section.

Test automation:

  • It will base on general auto testing framework. The test method and tools will align with overall automation test: Test Automation

Test case leverage:

  • We will re-use some common test cases for other platform.

Test Design

Test design is based on Test Design Guideline. According to the usage modal, characteristics and application features, the check points and priority of each media application were defined. Test design tables are drafted below, and which will become the base to design test cases.

Feature ID Test Point Conditions Collaborations Comments
       

Test Environment

  • Hardware Platforms

Target test platforms, networking environment, peripherals, test and measurement equipment, and etc

Test Platform Networking Other
nCDK WLAN/3G/BT  
  • Tools

N/A

QA Contact

Qin, Mu qin.mu@intel.com

Developers


Referrences

  • Test Design Guideline

http://moblin.intel.com/wiki/MeeGo_QA/Tablet/1.1/TestDesignGuideline

  • Application Test Design Method

http://moblin.intel.com/wiki/UX_Application_Test_Design_Method

  • Developer’s web:

TBD

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