Revision as of 03:32, 8 December 2010

MeeGo Graphics Test Plan

Component Summary

The graphics subsystem is composed of Xserver, Mesa, 2D driver (e.g. Xf86-video-intel) and Drm. It should provide the latest graphics h/w features, as well as meet requirement of UI framework (e.g. Clutter, Qt), Window Manager even applications.

Feature to be Tested

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

Table.1 Basic features

Table.1 MeeGo-1.1

Table.2 MeeGo-1.2

Feature not to be Tested

Bluez tests do not cover Drivers and Low Level BT Profiles

Test Strategy and Approach

Test is focused on Bluez user level profiles. Main goal is to ensure bluez stack can work well to comminucate with outside hardwares to implement different usages. All the commonly used BT profiles should be tested on different platforms either by GUI or by terminal commands.
For those low level profiles or Bluetooth drivers on platforms, there is no cover.

Test Methodology:

Bluez library provides many tools to do hardware BT connection. For example:
Nearly all the bluetooth test needs the first step: Bluetooth pairing. This can be done by simple-agent in bluez-test RPM.
BT Keyboard and BT mouse connection uses HID profile, which could be done by HID daemon. hidd --connect <Keyboard MAC> and hidd --search can help to connect keyboard and mouse.
For the profiles through OBEX, we write python scripts to call OBEX server APIs to transfer data.
For PANU, we setup a unbutu10.04 machine as BNEP server. PAN user could link to the BNEP after pairing with the ubuntu machine. When PANU needs log on to internet, the BNEP server will do ipforwarding from the bnap0 to eth0 (eth0 is connecting to outside).

Test Types:

Although the test points are classified by each profiles, we also do negative, performance and even stress test to the test points.

• Positive test must pass
• If the system has GUI (such as gnome-bluetooth-meego), some tests are validated through GUI following user experience.
• Negative and stress test will be especially run for FTP, for example:
  • Transfer the file to wrong target, or target memory is full
  • Transfer multiple files with small-size each
  • Transfer one big files with hundreds of MB
• Performance Test will also be cared when doing FTP test, file transfer speed should be mor than 10K. Or we will treat BT connection not stable.

Test level:

Current test level is API level. All cases are based on middleware usage, no dependency on how GUI is like.

Flexibility:

Nokia shares some test cases calling bluez-libs API in C language. Although those cases are not in our test strategy, we still try to use bluez-libs to enlarge our profile test scope if possible.

Test Automation

We will keep one PC as server machine for auto test, so automated cases are the profiles which can be used between two computers. Based on this strategy, we currently made FTP/OPP/PANU profiles test cases automated.
There is no low level profiles automated by us. Nokia share some codes in MWTS and BLTS to test RFCOMM and L2CAP profiles. But unfortunately, all their cases are semi-automatic in fact.
The test framework to run our auto cases is MCTS. Those cases are written by shell scripts, some utility tools (called by cases) are made by python. Before case running, a OBEXD-Server machine must be setup there and wait for obexd-client call. Detail information can be refered from the README file in MCTS:Bluez component. Git repository is http://gitorious.org/qa-tools/mcts

Test Design

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

Test Environment

Nearly all the bluez test cases need at least two devices. One is testing machine, the other may be some BT integrated device.
There are still some scripts needed for profile checking, since we do not depend on GUI APP.

Hardware Platforms

Tools

Some python scripts are used to check FTP/OPP/PBAP... functions in middleware (without GUI). They are from:

• bluez source code: bluez/test/simple-agent --- For bluetooth pairing
• bluez source code: bluez/test/test-network --- For PANU connection setup with BNEP (PAN Server)
• obexd source code: obexd-0.32/test/ftp-client --- For FTP send/get/browse checking

QA Contact

jingke.zhang@intel.com
zhaojuan.guo@intel.com (intern)

Developers

majid.awad@intel.com
qiang.z.zhang@intel.com

Referrences

BT Profile introduction: http://en.wikipedia.org/wiki/Bluetooth_profile
Bluez source and tool downloading: http://www.bluez.org
BIG offical webpage: http://www.bluetooth.org