Contents 1 Telepathy Test Plan 1.1 Component Summary 1.2 Feature to be Tested 1.2.1 Test Strategy and Approach 1.3 Test Design 1.4 Test Environment 1.5 QA Contact 1.6 Distribution Contact 1.7 Reference

Telepathy Test Plan

Component Summary

Telepathy is designed to provide a group of interface to develop VoIP/IM by using gtalk/skype/SIP service, which provides account managment to help application login/logout to gtalk/skype/sip service, provides channel handling to bind stream to audio/video to playing receiving data from other pointends. Using Telepathy, developer can integrate gtalk/skype/SIP service to a uniform enviroment and send IM/Voice Call/Video Call to the other account which register in different services.

Feature to be Tested

Features to be tested are made of basic features + accepted features of MeeGO-1.1/MeeGo-1.2.

Tablet 1 - Basic Features

FEA ID	Feature summary	Feature description and Test points	Platform	Priority
n/a	Extensible plugin architecture	Extensible plugin architecture by loading dynamic loadable modules	ALL	High
n/a	Module autoloading	Module autoloading	ALL	High
n/a	Support for more than one sink/source	Support for more than one sink/source	ALL	High
n/a	Good low latency behaviour	Good low latency behaviour	ALL	High
n/a	asynchronous API	Completely asynchronous C API, complemented by two synchronous variants for simple use in synchronous applications	ALL	High
n/a	synchronize multiple playback streams	Ability to fully synchronize multiple playback streams	ALL	High

Tablet 2 – Meego 1.1

FEA ID	Feature summary	Feature description and Test points	Platform	Priority
7163	[FEA] PulseAudio Modules support	There shall be PulseAudio modules for music, recording and voice calling.	ALL	High

Tablet 3 – Meego 1.2

FEA ID	Feature summary	Feature description and Test points	Platform	Priority
7164	[FEA] PulseAudio Audio Path	Audio path shall be available for music, recording and voice calling in target HW.	ALL	High

Tablet 4- Feature not to be tested

Summary	Detailed scenario	Support	Reasons
Additional audio manager for specific HW codec, and 3G	Additional pulseaudio plugin for specific HW codecs, policy manager, 3G	n/a	Here this component is for all the platform, and general core features of pulseaudio

Test Strategy and Approach

All the above features would be tested. You can get the latest cases from http://gitorious.org/qa-tools/mcts.

Tablet 5 – Feature/Lib/Case mapping

FEA name	Target lib	Testsuite name
Pulseaudio	libpulse	mcts-pulseaudio-tests

Test Types:

Most of cases are auto cases and provide function and performance testing.

• Function test: All.
• Stress test

Test level:

All the cases are API level and implemented with C language, and encapsulated by shell script. Table.5 shows the target lib too.

Test Automation

All the cases tracked in mcts should be automatic. How to build/run cases, pls refer to README of every testing package.

Test Design

Test points are written in Tested Feature Tables.
Test method is introduced in Test Strategy and Approach section.

Test Environment

Hardware Platforms

Test Platforms	h/w	Priority
Pinetrail Netbook: EeePC 1005 HA	intel Pineview	P1
Handset: Avaa	PVR SGX535	P1

Tools

n/a

QA Contact

Zhang Zhiqiang

Distribution Contact

peng.li@intel.com

Reference

Pulseaudio official site: http://www.pulseaudio.org/

MCTS QA-tools: http://gitorious.org/qa-tools/mcts