(Difference between revisions)
|
|
| Line 195: |
Line 195: |
| | ==QA Contact== | | ==QA Contact== |
| | * [mailto:cathy.li@intel.com Cathy Li] | | * [mailto:cathy.li@intel.com Cathy Li] |
| - |
| |
| - | ==References==
| |
| - | * [http://moblin.intel.com/wiki/UX_Application_Test_Design_Method Application Test Design Method]
| |
| - | * [http://moblin.intel.com/wiki/Handset_Test_Design_Guideline Handset Test Design Guideline]
| |
| - | * [http://moblin.intel.com/wiki/Handset_Test_Usage_Matrix Handset Test Usage Matrix]
| |
Revision as of 03:30, 3 December 2010
Core UX Test Plan
Component Summary
This test plan is for MeeGo HandSet Core UX. MeeGo handset Core UX is composed of whole home screen, theme style and engine, as well as system UI.
- Home Screen is the central point of access to all the applications and contents on your device, it's the first screen you see when you switch on your device. All interactive operations between users and MeeGo functionality is handled by Home Screen.
- Theme provides device orientation, object hierarchy and mode styling, which is required by any MTF application.
- System UI supports run time status (connectivity, battery status, volume status), date&time and notifications appearing on top bar of home screen.
Feature to be Tested
| Feature Name
| Detailed Feature Description
| Comments
|
Home:
- Feature 2680 - [FEA] Meego touch framework
| MeeGo Touch UI Framework, including
- Common UI components
- Application lifecycle management
- Application layouting
- Multitouch event handling including basic gestures, at least pan, flick/swipe, pinch
- Theme & style system
- OpenGL shader effects API
- Application service framework
- Localization & Internationalization extensions
| The feature is for UI Infrastructure, which related with home screen behaviors. All these sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
|
Theme:
- Feature 2685 - [FEA] MeeGo Theme and style engine
| Theme & style system for MeeGo Handset and Touch based devices should support:
- Styling based on Device Orientation
- Styling based on Object hierarchy and Objects
- Styling based on Mode
|
|
| System UI |
Run time status (connectivity, battery status), date&time, notifications appearing on system UI, and its drop down menu.
| No feature request for system UI
|
I18n and L10n:
- Feature 9254 - [FEA] [I18N] DUIHome shall be internationalized according to the dependencies listed in Core Master 5068
| This includes such items as:
- 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
|
|
Feature not to be Tested
| Feature Name
| Feature Description
| Comments
|
|
|
|
|
- Translation for other languages except Chinese Simplified will not be covered in Handset Core UX Test Plan.
Test Strategy and Approach
Test Strategy
- Test from UI: to check home screen, application launcher, system UI layout, theme and functionalities work correctly from UI. E.g, check if application is able to be launched to home screen with full screen; if could switch application to home screen by clicking home button; if correct runtime status (battery, networking) appears on system UI etc.
- Usage Model test: to check if running application, home screen, system UI could work fine from user perspective.
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, system UI etc.
- Stress and Negative testing to ensure the stability and robust of the Core UX.
Test Design
According to the usage modal, characteristics and application features, the check points of each features were defined. Test design tables are drafted below, and which will become the base to design test cases.
| Feature Category
| Feature ID-description
| Test Points
| Collaboration
| Conditions
|
| Home Screen
| 2680 - [FEA] Meego touch framework
|
- Check Home Screen layout
- Display selected applications icon in quick launch bar
- Display apps icons with label in application launcher
- Grid of apps layout, arrange order left to right
- Portrait and Landscape layout
- Navigate to view all apps in application launcher
- Launch/close applications
- Open/close application launcher
- Animation of launch application
- Lock/unlock screen
- Running applications switch with home screen
- Navigation to view all running applications
- Tap running application to maximize app window
- Tap to launch apps already run
|
- Theme
- System UI
- Key Applications
|
- Orientation (landscape and portrait view)
- Gesture: tap, swipe, tap and hold (long press)
|
| Theme
| 2685 - [FEA] MeeGo Theme and style engine
|
- Check home theme, no red/white/black block appearing
- Check key applications default theme, no red/white/black block appearing
- Check system UI (including notifications) theme, no red/white/black block appearing
- Update theme to check if it could take effect (TBD)
|
- Home
- System UI
- Key applications
|
|
| System UI
|
| Check System UI display and layout:
- System UI displays on the top of the screen
- Check icons (battery, network, roaming status, GPS, BT, time) display on system UI in idle screen
- Check if drop down menu is shown by dragging system UI, and is able to close.
- Check toggle switch On/Off button could enable/disable Gps, WiFi, 3G, Bluetooth, Airplane connectivity.
- Check whether correct battery status displays when charging and not charging.
- Check if notification appears on system UI.
- Check if setting could be invoked by tapping settings button.
- Check if volume value could be adjusted.
|
- Network (Bluetooth, wireless, 2G/2.5G/3G/4G)
- Clock to set Date/time
- Dialer/SMS
- Email
- Sound settings
- Notifications:
- new email
- missed call
- new SMS
|
- Network connection:
- Bluetooth on/off
- Wireless connected/disconnected/scanning
- 2G/2.5G/3G/4G
- GPS active/inactive
- Charge/uncharged battery
- Gesture: tap, swipe
|
| I18n and L10n
|
| Check text internationalization support on home screen, application launcher, System UI:
- 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
Check the Chinese language localization support on home screen, application launcher, System UI:
- Application name and icon
- Button label and its icon
- Window title
- Text message
- Date, time, number format
- Help message
- Embedded link
|
|
|
Risk and Dependency
- Lack of home screen features. All MTF sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
- Lack of system UI features.
Test Environment
Hardware Platforms
Tools
- bluetooth devices, wlan devices, wireless AP
QA Contact