UbuntuMobileEdition
|
Size: 5194
Comment:
|
← Revision 33 as of 2008-10-08 17:54:02 ⇥
Size: 3481
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(Testing/Cases/Header)]] | ## page was copied from Testing/Cases/Ubuntu-Netbook-Remix ## page was copied from Testing/Cases/UMEdesktop <<Include(Testing/Cases/Header)>> |
| Line 3: | Line 5: |
| ||<tablestyle="float:right; font-size: 0.9em; background:#F1F1ED;margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>>[[https://wiki.ubuntu.com/Testing/Cases/UNRinstall?action=AttachFile&do=get&target=UNR.png|{{https://wiki.ubuntu.com/Testing/Cases/UNRinstall?action=AttachFile&do=get&target=UNR.png}}]]<<BR>><<TableOfContents(2)>>|| | |
| Line 5: | Line 8: |
| This is a comprehensive test case suite designed to confirm compliance with all project requirements. Most of these tests can be performed on mobile hardware or in Xnest/Xephyr on a development machine. | Welcome to the Ubuntu Mobile Edition testing wiki. The pages linked within are designed to guide you through the process of setting up an environment, testing the features, and reporting bugs. As always, feel free to update these pages with any clarifications/additional information that you find useful along the way. Happy Hunting. |
| Line 7: | Line 10: |
| == Environment Setup == | = Getting Started = |
| Line 9: | Line 12: |
| === Xephyr === | == Environment == The first part of preparation, is to get a working environment up and running. There are a couple different ways. To learn more about getting your environment up and running visit:<<BR>> [[https://wiki.ubuntu.com/Testing/Cases/UbuntuMobileinstall| Environment Setup]] |
| Line 11: | Line 16: |
| * Download the latest project tarball from the [http://cdimage.ubuntu.com/moblin/hardy/menlow : Build Area] * Launch Moblin Image Creator application * File -> Load Project -> Browse to .tar.bz2 * Select project in ''Platform Projects'' window in MIC interface. * Select target in ''Targets'' window in MIC interface. * Click the Terminal button in the ''Targets'' section. * Inside the target terminal type: # ume-xephyr-start [[BR]] this script does the following: # apt-get install xserver-xephyr |
== Test Cases == |
| Line 22: | Line 18: |
| # export DISPLAY=:0 | This is a comprehensive test case suite designed to confirm compliance with all project requirements. Most of these tests can be performed on mobile hardware or in KVM on a development machine. |
| Line 24: | Line 20: |
| # /etc/init.d/dbus start | The cases have been split into three categories; Basic Feature, Advanced Feature, and Compliance Testing. |
| Line 26: | Line 22: |
| # xinit /etc/X11/xinit/xinitrc -- /usr/bin/Xephyr :2 -host-cursor -screen 1024x600x32 -dpi 96 -ac | === Basic Feature Testing === |
| Line 28: | Line 24: |
| '''You should now have a working environment''' | The Basic Feature set are designed to cover the main applications included with Ubuntu Mobile Edition. They should be run as often as possible to ensure all baseline functionality is working.<<BR>> [[https://wiki.ubuntu.com/Testing/Cases/UbuntuMobile-basic| Basic Functionality Testing]] |
| Line 30: | Line 27: |
| === Device === * Download the latest image from the [http://cdimage.ubuntu.com/moblin/hardy/ : Build Area] |
=== Advanced Feature Testing === Advanced feature testing covers functionality that is hidden or not used as often as the basic feature set. These cases often require advanced knowledge of the underlying system or access to system resources that are not commonly used.<<BR>> [[https://wiki.ubuntu.com/Testing/Cases/UbuntuMobile-advanced-features| Advanced Feature Testing]] |
| Line 33: | Line 31: |
| * Insert ''' Empty ''' USB thumbdrive. * Open Moblin Image Creator and go to: Tools -> Write USB Image * Browse to the *.img file you retrieved from the Build Area and create the image to thumbdrive * Insert thumbdrive into MID device and restart the device. '' be sure you have downloaded the correct build for the chipset in your test device '' '''You should now have a working environment''' = Test Cases = == Basic Feature Testing == Basic feature testing covers the features that the user of the software will see on a daily basis. Defects in this area of functionality will be noticed immediately by the user. It is vital that this area of testing is performed as often as possible and by as many people as possible. === Core Applications and Plug-ins === [https://wiki.ubuntu.com/Testing/Cases/UMEdesktop-apps : Cases] * Include an MID-optimized browser * Include an MID-optimized media player * Include Flash Movie Player, comparable to Adobe Flash Player version 9 * Include Adobe Acrobat Reader * Include a Java Run-time Environment * Media player plug-in * IM / Chat * Standalone Email client supporting * Video conferencing * Office document viewer * Games * Camera application * RSS reader * Clock * Calculator * PIM * Remote desktop client * E-book reader === System Configuration & Utilities === [https://wiki.ubuntu.com/Testing/Cases/UMEdesktop-config : Cases] * Software update mechanism tailored for MID * Power Management * Network Manager * Touchscreen calibration * Screen brightness * User theming customization * Font size / screen size * Hardware button configuration * Volume Controls * System Information * Date & Time settings === Codec Support === [https://wiki.ubuntu.com/Testing/Cases/UMEdesktop-codec : Cases] * MPEG-3 (MP3) Support * Windows Media Audio (WMA) Support * Ogg Theora (ogg) Support * Real Audio Support * Musepack Support * FLAC Support * WMV 9 Support * Real Video Support * Ogg Theora (ogg) Support * MPEG-4 Support * AVI Support * Xvid media format Support * Apple Quicktime containers (MOV) Support * DivX media format (version; 3, 4, 5 and 6) Support * Flash video 7/8/9 (swf) Support * Ogg media (ogm) Support * Real Media (Ram, ra and rpm) Support * JPEG decode * BMP decode * GIF decode * PNG decode * JPEG encode * BMP encode * GIF encode * PNG encode * Real Helix DRM Support * WM DRM Support * OMA DRM v2.0 Support === Device Drivers === [https://wiki.ubuntu.com/Testing/Cases/UMEdesktop-drivers : Cases] * WLAN Support * WiMax Support * WWAN Support * SDIO Support * Touchscreen Support * GPS Support * BlueTooth Support * Graphics – support x.org 7.1 or newer plus x11 2d driver, mesa 3d driver, agpgart kernel module, DRM kernel module and kernel frame buffer driver * Video Decode Acceleration * USB Client Support * Poulsbo chipset support (PCI IDs) * HD Audio – kernel patch to support chipset and ALSA codec driver * USB Camera Support |
=== Compliance Testing === Compliance testing ensures that Ubuntu Mobile Edition conforms to all project requirements. These include basic system versioning to the inclusion of licensing information in the delivered builds. Compliance is important to the success of Ubuntu Mobile Edition and is a vital requirement for many of companies implementing it.<<BR>> [[https://wiki.ubuntu.com/Testing/Cases/UbuntuMobile-compliance| Compliance Testing]] |
| Line 200: | Line 36: |
| == Advanced Feature Testing == Advanced feature testing covers functionality that is hidden or not used as often as the basic feature set. These cases often require advanced knowledge of the underlying system or access to system resouces that are not commonly used. |
== Reporting Bugs == |
| Line 203: | Line 38: |
| [https://wiki.ubuntu.com/Testing/Cases/UMEdesktop-advanced-features : Advanced Feature Testing] | All bugs discovered in Ubuntu Mobile Edition should be logged against the main project:<<BR>> [[https://bugs.launchpad.net/ubuntu-mobile| Ubuntu Mobile Edition]] There is some information that, when included, can make the triage team and developers work much easier. Please paste the following template into your bug reports submitted against UNR, and try to provide as much of the information as you can. {{{ Build Version/Date: Environment used for testing: Summary: |
| Line 206: | Line 50: |
| == Compliance Testing == Compliance testing ensures that UME conforms to all project requirements. These include basic system versioning to the inclusion of licensing information in the delivered builds. Compliance is important to the success of UME and is a vital requirement for many of companies implementing UME. |
Steps to Reproduce: |
| Line 210: | Line 53: |
| [https://wiki.ubuntu.com/Testing/Cases/UMEdesktop-compliance : Compliance Testing] | Expected result: |
| Line 213: | Line 56: |
| Actual result:}}} == Summary == Thank you for your interest in Ubuntu Mobile Edition testing. We hope you decide to contribute to the project. As always, if you have any questions or comments, feel free to visit the mobile team over on ''Freenode #ubuntu-mobile''. |
Contents |
Introduction
Welcome to the Ubuntu Mobile Edition testing wiki. The pages linked within are designed to guide you through the process of setting up an environment, testing the features, and reporting bugs. As always, feel free to update these pages with any clarifications/additional information that you find useful along the way. Happy Hunting.
Getting Started
Environment
The first part of preparation, is to get a working environment up and running. There are a couple different ways. To learn more about getting your environment up and running visit:
Environment Setup
Test Cases
This is a comprehensive test case suite designed to confirm compliance with all project requirements. Most of these tests can be performed on mobile hardware or in KVM on a development machine.
The cases have been split into three categories; Basic Feature, Advanced Feature, and Compliance Testing.
Basic Feature Testing
The Basic Feature set are designed to cover the main applications included with Ubuntu Mobile Edition. They should be run as often as possible to ensure all baseline functionality is working.
Basic Functionality Testing
Advanced Feature Testing
Advanced feature testing covers functionality that is hidden or not used as often as the basic feature set. These cases often require advanced knowledge of the underlying system or access to system resources that are not commonly used.
Advanced Feature Testing
Compliance Testing
Compliance testing ensures that Ubuntu Mobile Edition conforms to all project requirements. These include basic system versioning to the inclusion of licensing information in the delivered builds. Compliance is important to the success of Ubuntu Mobile Edition and is a vital requirement for many of companies implementing it.
Compliance Testing
Reporting Bugs
All bugs discovered in Ubuntu Mobile Edition should be logged against the main project:
Ubuntu Mobile Edition
There is some information that, when included, can make the triage team and developers work much easier. Please paste the following template into your bug reports submitted against UNR, and try to provide as much of the information as you can.
Build Version/Date: Environment used for testing: Summary: Steps to Reproduce: Expected result: Actual result:
Summary
Thank you for your interest in Ubuntu Mobile Edition testing. We hope you decide to contribute to the project. As always, if you have any questions or comments, feel free to visit the mobile team over on Freenode #ubuntu-mobile.
Testing/Cases/UbuntuMobileEdition (last edited 2008-10-08 17:54:02 by bismuth)