Contents 1 MeeGo Software Management and Package Update Test Plan 1.1 Component Summary 1.2 Feature to be Tested 1.3 Feature not to be Tested 1.4 Test Strategy and Approach 1.5 Test Strategy and Approach 1.6 Test Design 1.6.1 Test Points 1.6.2 Collaboration 1.6.3 Conditions 1.7 Test Environment 1.7.1 Network 1.7.2 Hardware Platforms 1.7.3 Tools 1.8 QA Contact 1.9 Developers 1.10 References

MeeGo Software Management and Package Update Test Plan

Component Summary

Software Installation and Update is an important way for system function expansion, stability enhancement and issue fix. The Mechanism of software installation and update decide the MeeGo system's security and the complexity of user operation. Software Installation and Update application currently contains 2 components:

• Package Manager: Manage all packages; user uses it to install or remove packages; it can auto resolve packages' dependency and make a security check for packages' signature and integrity.
• System Update: Update those obsolete package in system or OS update .It provides an easy and fast way to fix old packages' issue or enhance system function and stability for users.

Feature to be Tested

The features listed here are all from Package management feature zilla, OS update(and software management) test will cove all these features with required priority, at the same time, the test will also cover other features which are not listed in this table, such as package management GUI, CLI, i18/l10n etc.

Feature ID	Feature	Feature Set	Comments
			.

Feature not to be Tested

• Independent applcations functionalities testing: Packages/Applictaions installation/update/remove are in package management test scope, but their own functionalities are out of this component's test coverage;
• System update will only update from default distribution repos, unconfirmed new OS update will not in this scope;

Test Strategy and Approach

Test Strategy and Approach

Isolate logical function testing from GUI testing: Software manager and system update are to be validated from two perspectives, logic function testing and GUI testing. The former focuses on features’ functionalities, while the later dedicates to UI visual appearance and user interaction. As the characteristic of event driven application, there are multiple event paths can reach the same function. Although separated from GUI layer, logic function testing is still achieved by go through one of equivalent event paths in GUI navigation, leaving most of event paths being covered in GUI testing.

Focus on features new implemented or customized for MeeGo system: The basic idea is to validate the MeeGo Software manager and system update functions from the end users’ perspective. Test efforts will mostly be taken on the features new implemented or customized for MeeGo system.

Software manager Test Strategy: Besides the MeeGo distribution repositories, QA package repository server will also be setup to simulate scenarios of package installation and updating. Below scenarios will be covered.

• Network protocols of package repository server: HTTP/HTTPS/FTP
• Publish new packages.
• Publish upgrade version of installed package.
• exception handler

System update test strategy: Test system update from the end users' perspective, check the user private setting and data remains after the updating of system, this test simulates tow user updating scene: update system day by day and once update from final release image to the latest status.

Package security installation test strategy: Packages security installation depends on MeeGo's signature validation mechanism, both of released repository and released packages have MeeGo's official signature. Set up various signature package and repository to simulate a real situation.

Test automation:

• OS update need tester manually check update status, and need also check whether it can workable after update process, so it's hard to automation the test like other GUI or midware components;
• Pakcage management automation need more investigation. [TBD]

Test case leverage:

• MeeGo table software management and update will re-use some common test cases from netbook ones, these cases are independent of tablet specific implementations.

Test Design

Test Points

Package management and OS update test will from end user side, follow the test design guideline and application test design method, and refer to other similar dirtibution OS like fedora, then get the following test point:

Feature Set	Test Point
Package management repos	Repo files Default repo files stays in right folder Default repo can work while using them to install packages Customized repository Add a customized repo, check whether package manager could detect it Install pakcages from customized repo and check whether it can work
System/OS update GUI	GUI layout and navigation Patches updating Search updated patches Install patches Patches auto check Update notification Enable default built-in repo Check whether there is notification while repos have some updates Update preferences Set and check update interval Set and check update types
System/OS update from CLI	OS update searching and reviewing pkcon search zypper search OS update and recovery pkcon upgrade zypper dist-update ...
System/OS update effect	Private date remains unchanged User configuration data for system Application private data, for example private data from browser, media applications System can be recovered System sanity
Package Manager GUI and functionality	GUI layout and navigation Check buttons' layout Check UI theme Package searching and reviewing Search a specific package and check results Package installation and removing Install a package from UI Package list refresh Refresh list and check the changes Software catalogs Enable repos and check whether they can work Disable repos and check whether they can work Software log viewer Desktop Files Check these application desk files from home screen or other place
Package Manager command line	Package searching and reviewing pkcon search zypper search Package installation and removing pkcon/zypper remove Package updating and recovery pkcon dist-update zypper Package status Synchronization pkcon refresh zypper refresh
Package manager signature validation	Packages and repository signature validate Install a package without signature, and check the behavior of pakcage manager
I18N & L10N	All text strings in softeare manager and system update UI should be internationalized Chinese Simplified Translation

Collaboration

Mainly for the conditions that the application will meet, mainly introduced by platform characteristic. For example, devices may in different wireless environment, users may use different input methods to write, etc.

Item ID	Name	Details	Comments
1	Virtual Keyboard	Input strings via virtual keyboard	.
2	Home screen	Launch pakcage management UI applications from home/panel screen	.

Conditions

Mainly for the conditions that the application will meet, maily introduced by platform characteristic. For example, devices may in different wireless environment, users may use different input methods to write, etc.

Item ID	Name	Details	Comments
1	Touch framework supported devices	Test devices need support touch framework	.
2	Wired network	Connects to wired network: Using proxy Without proxy	.
3	Wireless network	Connects to wireless network: Using proxy Without proxy	.
4	Landscape and portrait views	Change screen orientation to get different views: Landscape view with proper window size Portrait view with proper windows size	.
5	Power state	The state may include: idle sleep resume	.
6	Touch and gesture	MeeGo Touch Framework gestures Additional gestures support if there are	.

Test Environment

Network

• Internal network uses proxy to access repos
• Access repos directly without any proxy

Hardware Platforms

• Wired network
• Wireless network
• Oak Trail platform

Tools

• Customized repo server
• Refer to MeeGo netbook OS

QA Contact

• huajun.li@intel.com

Developers

References

• Softerware managemetn and system update features on feature zilla

Package management and update features

• MeeGo Core Test Plan

http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan