Media subsystem plays an important role in Handset usage model. The media software stack in MeeGo is divided into 3 layers briefly. Upper level applications include Music/Photo/Video/camera application (camera application don't cover in MeeGo 1.1 release). Middleware libraries include audio server(Pulseaudio), audio library(ALSA), audio/video decoder library (Gstreamer), Gstreamer plugin, QT-mobility, Tracker etc. Low level includes kernel modules or drivers such as Intel SST audio driver, V4l2 etc.
Our testing for handset 1.1 releases focus on upper layer application. And take advantage of shell command or script to validate the middleware or driver status just for bug root cause purpose.
The relevant media format & codecs tested is focusing on the free license file format & codecs. For example: ogg format, theora video, vorbis audio, bmp, jpg, png, gif, wav etc.
|Feature Name||Feature Description||Vertical||Priority||Comments|
|Audio||*Audio playback |
*Audio play control
*Artist/Album/Song Navigation & Playback
*Play Queue generation
*Shuffle and repeat
|Handset||P1||The design input: UI design 27 Jul 2010 version and feature bugs: http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Features&query_format=advanced&component=Audio%20Player&product=MeeGo%20Handset%20Features|
|Photo||*Basic photo viewer functionality |
*Photo album organization
*Photo mainipulation via popup menu
|Handset||P1||The design input: UI design 28 Jul 2010 version and feature bugs: http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Features&query_format=advanced&component=Photo%20viewer&product=MeeGo%20Handset%20Features|
|Video||*Basic video playback|
*Video play control
*Video file mainipulation via popup menu
*Video files filtering & search
*Switch between different category
|Handset||P1||The design input: UI design 28 Jul 2010 version and feature bugs: http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Features&query_format=advanced&component=Video%20player&product=MeeGo%20Handset%20Features|
Low level drivers will be not tested unless we need to perform the bug isolation. middleware level like media framework(gstreamer) or tracker, qt-mobility, pulseaudio testing will not cover in this test plan.
See Bug 150 - pulseaudio not work on CDK & Aava
See Bug 5712 - Video playback is not working
We will cover the media features via Music/Photo/Video application testing. Most of media usage models will be covered by this type of testing.
Make sure user have comfortable usage experience like there no stuttering and no frame drop during video playback, no scratchy when playback audio and etc. There is no dedicate cases designed for it specially, it will be covered by normal usage testing.
We will test boundary, negative input value and error input. Also some negative scenarios will be covered, such as playback non-media files or un-supported media file.
Media is one type of resource intensive application (memory, cpu load) and user may put long time on one application like watch movie. So we test media apps' stability under long time run to make sure there is no crash etc.
Test focus is for I18N mechanism in media application. Generally, we set another language environment (ex. Chinese Simplified) instead of default English environment and check the change of media application. Notes: only Chinese Simplified Translation will be covered by QA, for other languages, they will be covered by other teams.
Performance testing will be covered by performance test separately.
For some low level testing such as pulseaudio, we may use pulseaudio compatible sample applications to cover the police config setting for typical usage models.
In MeeGo 1.1 release, video player test points includes: