Meego Wiki
Views

Quality/TestSuite/Telepathy Test Plan

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Component Summary)
(→Feature to be Tested)
Line 63: Line 63:
|}
|}
-
'''Tablet 4- Feature not to be tested'''
+
'''Tablet 4 - extention module'''
{|border="2" cellspacing="0" cellpadding="4" width="100%"
{|border="2" cellspacing="0" cellpadding="4" width="100%"
Line 72: Line 72:
|-
|-
-
|Additional audio manager for specific HW codec, and 3G
+
|support farstream and streamengin
-
|Additional pulseaudio plugin for specific HW codecs, policy manager, 3G
+
|test cases should support farstream and streamengin to handle stream channel
|n/a
|n/a
-
|Here this component is for all the platform, and general core features of pulseaudio
+
|Here this component is for defferent the platform
-
 
+
|}
|}

Revision as of 05:08, 17 June 2011

Contents

Telepathy Test Plan

Component Summary

Telepathy is a flexible, modular communications framework that enables real-time communication via pluggable protocol backends. Telepathy is a communications service that can be accessed by many applications ("clients") simultaneously. This allows any application to access presence information, request a communications channel (potentially handled by another client), or collaborate contact-to-contact.Telepathy provides protocol backends for most popular protocols including: Jabber/XMPP/Google Talk/Jingle, link-local XMPP, SIP, MSN, Yahoo/AIM and IRC via a unified D-Bus API.

It also provides convenience libraries for GLib, Qt4 and Python to simplify using the API from applications.Telepathy exposes the available real-time communications capabilities of each protocol: presence, contact rosters, text chat, voice and video over IP, file transfer and Telepathy Tubes. Telepathy is modular. Each backend and client runs in a separate process, allowing for much greater security and resilience.

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 voice communication on gtalk Send/Answer gtalk voice call/request. ALL High
n/a voice communication on skype Send/Answer skype voice call/request. ALL High
n/a video communication on gtalk Send/Answer gtalk video call/request. ALL High
n/a video communication on skype Send/Answer skype video call/request. ALL High
n/a IM on gtalk Send/Receive gtalk IM. ALL High
n/a IM on skype Send/Receive skype IM. ALL High

Tablet 4 - extention module

Summary Detailed scenario Support Reasons
support farstream and streamengin test cases should support farstream and streamengin to handle stream channel n/a Here this component is for defferent the platform

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

Retrieved from "http://wiki.meego.com/Quality/TestSuite/Telepathy_Test_Plan"
Personal tools