Revision as of 06:34, 8 December 2010 (view source) Zhengkui (Talk | contribs) (→Table.5 Feature/Case mapping) ← Older edit		Revision as of 03:09, 9 December 2010 (view source) Shaofeng (Talk | contribs) (→Test Environment) Newer edit →
Line 104:		Line 104:
	== Test Environment ==		== Test Environment ==
-	It's OK to run the cases without UI home or Window manager, because our test target is graphics lib/stack only.	+	=== General Environment Setup ===
		+	* Netbooks/Nettops/Notebooks meego platform or other platform with the geoclue package.
-	=== Table.6 Hardware Platforms ===	+	=== Extra Environment Setup  ===
-	{| cellspacing="0" border="1"	+	* Check geoclue pypsy provider DBUS services.
-	! ''Test Platforms''	+	'' $ ls /usr/share/dbus-1/services | grep org.freedesktop.Geoclue.Providers ''<br/>
-	! ''Graphics h/w''	+	Below services should be printed on screen:<br/>
-	! ''Priority''	+	org.freedesktop.Geoclue.Providers.Hostip.service
-	|-	+
-	|''Pinetrail Netbook: EeePC 1005 HA''|| ''intel Pineview'' || ''P1''	+	* Directly connect to Internet without proxy
-	|-	+	* Export DISPLAY variable if run test in text-mode console.
-	|''Handset: Avaa''|| ''PVR SGX535'' || ''P1''	+
-	|}	+
	=== Tools ===		=== Tools ===

---

Revision as of 03:09, 9 December 2010

Contents 1 MeeGo Graphics Test Plan 1.1 Component Summary 1.2 Feature to be Tested 1.2.1 Table.1 Basic features 1.2.2 Table.2 MeeGo-1.1 1.2.3 Table.3 MeeGo-1.2 1.3 Table.4 Feature not to be Tested 1.4 Test Strategy and Approach 1.5 Table.5 Feature/Lib/Case mapping 1.5.1 Test Automation 1.6 Test Design 1.7 Test Environment 1.7.1 General Environment Setup 1.7.2 Extra Environment Setup 1.7.3 Tools 1.8 QA Contact 1.9 Distrobution 1.10 Referrences

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/a	Input	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
X11	libX11 libXdamage libXcomposite libXrandr libXrender libXv	blts-x11
OpenGL ES2.0	libEGL libGLESv2	blts-opengles2-perf
OpenVG	libEGL libOpenVG	mcts-openvg-tests
Display	libXrandr	mcts-display-tests
Input	libX11	blts-input-devices
Video	libXv	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

General Environment Setup

• Netbooks/Nettops/Notebooks meego platform or other platform with the geoclue package.

Extra Environment Setup

• Check geoclue pypsy provider DBUS services.

$ ls /usr/share/dbus-1/services | grep org.freedesktop.Geoclue.Providers
Below services should be printed on screen:
org.freedesktop.Geoclue.Providers.Hostip.service

• Directly connect to Internet without proxy
• Export DISPLAY variable if run test in text-mode console.

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