Social Networking Test Plan
Component Summary
This test plan is for MeeGo 1.1 HandSet Social networking application.
- Social Networking is an application that allows the user to fetch web services by setting up corresponding user accounts.
Feature to be Tested
| Feature Name
| Detailed Feature Description
| Comments
|
Social Networking
- Bug 5875 - [FEA] Need to add social networking to MeeGo
|
- Social networking main window UI, layout and button response check
- Launch/close social networking application
- Set up social networking accounts (last.fm and twitter)
- last.fm context menu (View on Last.fm, Remove from timeline)
- Status update and Refresh
- Settings for last.fm and twitter.com
- Individual update for last.fm and twitter.com
- Post new twitter status
- Twitter context menu (Reply, Retweet, View on twitter.com, Remove from timeline)
|
- No detailed social networking feature request in featurezilla.
- Twitter web service is blocked in China.
|
Feature not to be Tested
- 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, widget could work fine each other and with other features from user perspective.
Test Type and Approach
- Functional test: to check each function works as expected at the "unit" level. Such as open/close application, switch to home screen by tapping home button, lock/unlock screen, etc.
- Negative test: negative test will be involved in functional test to check how it works if an unexpected input is given. E.g. give an input out of range.
- Stress test: it involves testing beyond normal operational capacity and work under high workload. For instance, input long strings for text entry, repeated operations on open/close application, switch between home screen with application, switch between different running applications. About duration, we define some generic operations which run a period of time continuously.
- I18N/L10N testing: test focus is for I18N mechanism in applet. Generally, we set another language environment (ex. Chinese Simplified) instead of default English environment and check if the change applied to whole home screen and widgets. Notes: only Chinese Simplified Translation will be covered by QA. For other languages, they will be covered by other teams.
Test Design
Home Screen
- Test Method
- UI layout check
- Functionality check
- Test Points
- UI layout check
- Check home screen, application launcher, system UI layout.
- Functionality check
- 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 Method
- UI layout check
- Functionality check
- Test Points
- UI layout check
- Home and key applications default theme
- Functionality check
- Update theme to check if it could take effect
- Check orientation effect (Portrait, Landscape, 90/180/270 degrees clockwise)
System UI
- Test Method
- UI layout check
- Functionality check
- Test Points
- UI layout check
- Check System UI layout. For instance, if correct date/time appears.
- Functionality check
- 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).
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
- Aava DV1 and DV2
- Moorestown QS CDK with NEC PMIC
Tools
- bluetooth devices, wlan devices, network simulators, sim simulators, wireless AP
QA Contact