Meego Wiki
Views

Quality/TestSuite/MeeGo Graphics Test Plan

From MeeGo wiki
< Quality | TestSuite(Difference between revisions)
Jump to: navigation, search
(Undo revision 23800 by Shaofeng (Talk))
 
(3 intermediate revisions not shown)
Line 66: Line 66:
All the above features would be tested. You can get the latest cases from http://gitorious.org/qa-tools/mcts. <br>
All the above features would be tested. You can get the latest cases from http://gitorious.org/qa-tools/mcts. <br>
-
== Table.5 Feature/Case mapping ==
+
== Table.5 Feature/Lib/Case mapping ==
{| cellspacing="0" border="1"
{| cellspacing="0" border="1"
! ''FEA name''
! ''FEA name''
Line 94: Line 94:
<u>''Test level:  ''</u>
<u>''Test level:  ''</u>
-
All the cases are API level and inplemented with C language. <br>
+
All the cases are API level and inplemented with C language. Table.5 shows the target lib too. <br>
-
 
+
-
<u>''Flexibility:''</u>
+
-
 
+
-
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. <br>
+
=== Test Automation ===
=== 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. <br>
+
All the cases tracked in mcts should be automatic. How to build/run cases, pls refer to README of every testing package.
-
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. <br>
+
-
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 Design ==
Line 110: Line 104:
== Test Environment ==
== 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. <br>
+
It's OK to run the cases without UI home or Window manager, because our test target is graphics lib/stack only.
-
There are still some scripts needed for profile checking, since we do not depend on GUI APP.  
+
-
=== Hardware Platforms ===
+
=== Table.6 Hardware Platforms ===
{| cellspacing="0" border="1"
{| cellspacing="0" border="1"
! ''Test Platforms''
! ''Test Platforms''
-
! ''Networking''
+
! ''Graphics h/w''
-
! ''Other Devices''
+
! ''Priority''
! ''Priority''
|-
|-
-
|''Pinetrail Netbook: Acer NAV50''|| ''LAN, Wifi, BT'' || ''BT headset (Dell DH200), BT Keyboard (Dell)...'' || ''P1''
+
|''Pinetrail Netbook: EeePC 1005 HA''|| ''intel Pineview'' || ''P1''  
-
|-
+
-
|''Diamondville Netbook: EeePC 1005 HA''|| ''LAN, Wifi, BT'' || ''BT headset (Dell DH200), BT Keyboard (Dell)...'' || ''P2''  
+
|-
|-
-
|''Handset: Avaa''|| ''USB, BT-dongle (BT2.0+EDR)'' || ''BT headset (Dell DH200), BT Keyboard (Dell)...'' || ''P1''  
+
|''Handset: Avaa''|| ''PVR SGX535'' || ''P1''  
|}
|}
=== Tools ===
=== Tools ===
-
Some python scripts are used to check FTP/OPP/PBAP... functions in middleware (without GUI). They are from:<br>
+
N/A
-
* 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 ==
== QA Contact ==
-
jingke.zhang@intel.com<br>
+
kui.zheng@intel.com<br>
-
zhaojuan.guo@intel.com (intern)
+
xuetingx.jin@intel.com (intern)
-
== Developers ==
+
== Distrobution ==
-
majid.awad@intel.com <br>
+
peng.li@intel.com <br>
-
qiang.z.zhang@intel.com <br>
+
== Referrences ==
== Referrences ==
-
BT Profile introduction: http://en.wikipedia.org/wiki/Bluetooth_profile<br>
+
Xorg Fundation: http://www.x.org/wiki/<br>
-
Bluez source and tool downloading: http://www.bluez.org<br>
+
Intel Linux Graphics: http://intellinuxgraphics.org/index.html<br>
-
BIG offical webpage: http://www.bluetooth.org
+
MCTS QA-tools: http://gitorious.org/qa-tools/mcts

Latest revision as of 03:10, 9 December 2010

Contents

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

FEA ID Feature summary Feature description and Test points Platform Priority
n/a X11 * Xserver should work well with Mesa, 2D driver and other components.
* Many X extensions should be supported, including Xrender, Xcomposite, Xdamage, Xrandr adn so on. 		ALL Major
n/a OpenGL ES 2.0 Should support OpenGL ES 2.0 ALL Major
n/a OpenVG Should support OpenVG ALL Major
n/a Display * Should support Single/Multi display
* Mode setting
* Rotation setting 		ALL Major
n/aInput Should support proper event for input devices (i.e. multi-touch) in X ALL Major
n/a Video Should support XVideo and libVA ALL n/a

Table.2 MeeGo-1.1

FEA ID Feature summary Feature description and Test points Platform Priority
4877 [FEA] Provide libOpenVG and libOpenVGU packages OpenVG is supported ALL Major

Table.3 MeeGo-1.2

FEA ID Feature summary Test points Platform Priority
7614 [FEA] Multiple output (HDMI) support from Graphics and Window manager * HDMI output is supported by graphics driver;
* Multiple display is supported by Window Manager 		HDMI platform Major

Table.4 Feature not to be Tested

Summary Detail scenario Support Reasons
OpenGL OpenGL ES2.0 would be the default 3D backend n/a OpenGL not be supported by SGX540 h/w

Test Strategy and Approach

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

Table.5 Feature/Lib/Case mapping

FEA name Target Lib Test suite package name
X11libX11 libXdamage libXcomposite libXrandr libXrender libXvblts-x11
OpenGL ES2.0libEGL libGLESv2blts-opengles2-perf
OpenVGlibEGL libOpenVGmcts-openvg-tests
DisplaylibXrandrmcts-display-tests
InputlibX11blts-input-devices
VideolibXv blts-xvideo

Test Types:

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

  • Function test: All.
  • Performance test: OpenGL ES2.0, OpenVG, Xrender.

Test level:

All the cases are API level and inplemented with C language. 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

It's OK to run the cases without UI home or Window manager, because our test target is graphics lib/stack only.

Table.6 Hardware Platforms

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

Tools

N/A

QA Contact

kui.zheng@intel.com
xuetingx.jin@intel.com (intern)

Distrobution

peng.li@intel.com

Referrences

Xorg Fundation: http://www.x.org/wiki/
Intel Linux Graphics: http://intellinuxgraphics.org/index.html
MCTS QA-tools: http://gitorious.org/qa-tools/mcts

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