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.
Test Type and Approach
Core UX components are tested in different test sets:
- Sanity Test Set
- Contains BAT test cases of Core UX components.
- Basic Feature Test Set
- Contains basic feature (Functional) test cases for every testable feature of Core UX components.
- Extended Feature Test Set
- Contains bunch of well selected test cases of Core UX components to deeply verify functionality of every delivered features.
- System Functional Test Set
- Contains test cases of Core UX components that interacting and collaborating with other components to support a system usage.
Test Set Guideline: http://wiki.meego.com/Quality/TestSetGuideline
Test Design
Home Screen
- Test Points
- Check home screen, application launcher, system UI layout.
- Open/close application launcher
- Launch/close application from application launcher or quick launch bar
- Switch between running applications with home screen
- Gestures and Touch Interactions (Tap, Long press, Drag, Flick, Double tap, Pinch)
- Security setting (lock/unlock screen)
- System notification handle and interaction with home screen or running applications
Theme
- Test Points
- Check home and key applications default theme
- Update theme to check if it could take effect
- Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)
System UI
- Test Points
- Check System UI layout. For instance, if correct date/time appears.
- Check if drop down menu is shown by dragging system UI, and be able to close.
- Check toggle switch On/Off button could enable/disable Gps, WiFi, 3G, Bluetooth, Airplane connectivity.
- Check if corresponding connectivity status appears on system UI when enable Gps, WiFi, 3G, Bluetooth, Airplane.
- 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 (TBD).
L10n Supporting
- Test Points: to check if following items in target locale could be displayed correctly
- 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 feature request. All MTF sub-features depend on *Core OS features*. These test cases covered several feature points from UX.
- Lack of system UI feature request or UI design wireframe.
Test Environment
Hardware Platforms
Tools
- bluetooth devices, wlan devices, wireless AP
QA Contact
References