MeeGo 1.2.0 IVI Software Update Test Plan
Test Objective
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
- the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
- the health of 1.2.0 release distribution after system update
- validate whether relative bugs are fixed by update patch
- explore regression issues when system is with updated software
Feature to be Tested
- MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
- MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
- New features or bug fixings introduced by updated packages
- Functionality and reliability in resulting upgraded system function
- Performance of MeeGo 1.2.0 update release
Test Strategy and Approach
Test Approach
- Install/Update system in various ways as below:
- Install 1.2.0 update release build directly to get latest software stuff
- system Upgrade from 1.2.0 final release
- Validate the system with below criteria:
- Software update can be previewed and easily completed via command line (zypper, pkcon).
- New functions of latest build works
- Unchanged functions are not broken
- No regression on performance and reliability of whole system
Test Cycle
- Sanity Testing
- Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
- QA will do sanity testing when new update repo/build is ready and cover:
- XFCE sanity testing
- Middleware components sanity testing
- IVI drivers sanity testing
- Bug verification and regression testing
- System Function Testing
- QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo
Test Design
Checkpoints
Note: checkpoint in bold means it is also a sanity test point.
| Category
| Checkpoints
|
| System Overall
|
- [Startup] Liveboot/boot from local disk
- [Installation] Installer/Installer-shell launch and launch time
- [Installation] Installation in text mode and system start up(installer removal)
- [Installation] Installation in GUI mode and system start up(installer removal)
- [Peripherals] USB/SD auto-mounter/read/write
- [AppManager] Zypper install/update/debuginfo-install/source-install default repo configuration
- [AppManager] pkcon install/update
- [Settings] date&time settings
- [Settings] system build ID
- [Pnp] Cold boot time
- [Pnp] Powertop log analysis, Cn state, avg resident, Wakeup times
- [Stability] Shutdown and Reboot system 10 times without failure or crash
- [Stability] Use multiple applications
|
| Hardware Adaptation
|
- ML7213 drivers
- EG20T drivers
- touch screen
- Ethernet
- Wifi
- snd card
- onboard MMC
- removable MMC/USB
- USB HID/hub/LAN/BT dangle
- dmesg
|
| Graphics Driver(EMGD)
|
- System Startup with EMGD enabled
- startx from console
- Switch between X/console
- Desktop rendering
- GUI installer rendering
- Check basic 3D application glxgears can be run successfully
- Single(LVDS) display
|
| Connectivity/Communication
|
- Ethernet connection/disconnection/file transfer(proxy)
- Wifi scan/connection/disconnection
- Bluetooth pairing/connection(A2DP, HFP)
|
| Multimedia
|
- aplay/arecord
- paplay/parec
- gstreamer play audio/video
|
| XFCE desktop
|
- Desktop render
- XFCE menu view
- app launch/close/switch
|
Test Environment
Hardware
- Crossville/Lapis
- CRB = Brookville + ICM(Intel® Atom™ CPU E6XX Series + LAPIS ML7213 IOH)
- BIOS: AMI 4.6.3.7/0ABXJ 0.03
- Display: 7’’ LVDS
- Hard drive: SATA SSD 8G
- Crown Bay
- Crown Bay CRB = Shell Bay Fab2(Intel® EG20T IOH) + Little Bay REV D(Intel® Atom™ CPU E6XX Series)
- BIOS: AMI 4.6.3.7, Project 0ABTN 0.20
- Display = 13’’ LVDS
- Hard drive: SATA HD 160G
- wifi card: Intel wifi link 5100
Test Repos
- MeeGo 1.2.0 Release Repo
- MeeGo 1.2.0 Update Repo
QA Contact
Test Report
- Sanity Test Report
- Milestone Test Report
Referrences