Ldtp Tutorial

Linux Desktop Testing Project - LDTP

Linux Desktop Testing Project – LDTPhttp://ldtp.freedesktop.org

Tutorial

http://ldtp.freedesktop.org

http://ldtp.freedesktop.org/



Copyright 2004 - 2007 Novell, Inc.Copyright 2008 Nagappan Alagappan

Permission is granted to copy, distribute and/or modify this documentunder the terms of the GNU Lesser General Public License, Version 2or any later version published by the Free Software Foundation;with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.A copy of the license is included in the section entitled "GNULesser General Public License".

You should have received a copy of the GNU GNU Lesser General PublicLicense along with this documentation; if not, write to theFree Software Foundation, Inc., 59 Temple Place - Suite 330,Boston, MA 02111-1307, USA.

Author Nagappan A <[email protected]>Contributors: Harsha <[email protected]> Premkumar J <[email protected]> Guofu Xu <[email protected]> Surendran M <[email protected]> Vamsi B <[email protected]>



mailto:[email protected]







Table of ContentsAbout LDTP..........................................................................................................................................5Audience................................................................................................................................................6About testing.........................................................................................................................................6

Why testing ?....................................................................................................................................6Why automation ?.............................................................................................................................6Complexity of GUI testing ?.............................................................................................................6What type of testing can be done using LDTP ?..............................................................................6Advantage of accessibility based testing..........................................................................................6Disadvantage of accessibility based testing......................................................................................6What applications can be tested ?.....................................................................................................6Supported platforms.........................................................................................................................6

LDTP Features......................................................................................................................................7Web / Contact........................................................................................................................................7

LDTP on web....................................................................................................................................7Development mailing list..................................................................................................................7Internet relay chatting – IRC............................................................................................................7

System requirements.............................................................................................................................8Disk space requirement.....................................................................................................................8Software requirements......................................................................................................................8

Install the following dependency packages.................................................................................8Optional packages........................................................................................................................8

Environment.....................................................................................................................................8Setup LDTP...........................................................................................................................................8

Download source from GIT..............................................................................................................8Download source in tar ball format..................................................................................................8Setup LDTP from source in Linux environment..............................................................................9Setup LDTP from binary..................................................................................................................9

Architecture...........................................................................................................................................9LDTP Overall Architecture..............................................................................................................9LDTP Internals.................................................................................................................................9

Server.........................................................................................................................................11Client Handler............................................................................................................................11Component Handler...................................................................................................................11Event Handler............................................................................................................................11Logger........................................................................................................................................12

LDTP conventions...............................................................................................................................12Appmap..........................................................................................................................................12Appmap convention........................................................................................................................12

How to Access UI Objects from LDTP scripts...................................................................................14Window name.................................................................................................................................14

Different window types..............................................................................................................15Glob pattern support..................................................................................................................15




Different ways of representing window name...........................................................................15Window name formats...............................................................................................................15

Example.................................................................................................................................15Object name....................................................................................................................................15

Label..........................................................................................................................................15Example.................................................................................................................................15

Label by / Label for (associated label).......................................................................................16Example.................................................................................................................................16

Object name with out label / associated label accessing via index............................................16Example.................................................................................................................................16

Object name with index.............................................................................................................16Example.................................................................................................................................16

Object name formats..................................................................................................................16Example.................................................................................................................................16

Accessibility library............................................................................................................................17Enabling accessibility..........................................................................................................................17Importing LDTP modules...................................................................................................................18

Example 1: ................................................................................................................................18Example 2:.................................................................................................................................18

Call a function to perform an operation..........................................................................................18LDTP API.......................................................................................................................................19

Using / Hacking LDTP........................................................................................................................19Identifying controls.........................................................................................................................19Push button.....................................................................................................................................20Menu item.......................................................................................................................................23Toggle button..................................................................................................................................24Text control.....................................................................................................................................25Table control...................................................................................................................................25Push button.....................................................................................................................................26Check box.......................................................................................................................................27Spin button......................................................................................................................................29Page tab...........................................................................................................................................30Check menu item............................................................................................................................30Radio menu item.............................................................................................................................32Combo box – Menu item................................................................................................................32Combo box – List item...................................................................................................................33Launch application..........................................................................................................................34GUI exist.........................................................................................................................................35Timeout...........................................................................................................................................35Re-Initialize LDTP.........................................................................................................................36Set context / Release context..........................................................................................................37Generate raw keyboard events........................................................................................................37Generate raw mouse events............................................................................................................38Application information..................................................................................................................38

Callback – On new window creation..................................................................................................39




Advantage.......................................................................................................................................39Example..........................................................................................................................................39Logging...........................................................................................................................................40

Example script.....................................................................................................................................41Script input Data XML file - Useful to maintain a generic script.......................................................42

What................................................................................................................................................42Why................................................................................................................................................42Advantages of using LDTP Data XML..........................................................................................42LDTP Data XML Tags...................................................................................................................42Syntax.............................................................................................................................................42Example..........................................................................................................................................42Sample XML File...........................................................................................................................43

Sequencing set of LDTP scripts using ldtprunner XML file...............................................................43What................................................................................................................................................43Why................................................................................................................................................43Advantages of using ldtprunner XML............................................................................................43ldtprunner Tags...............................................................................................................................43Sample LDTP runner XML file......................................................................................................44

How to execute LDTP scripts.............................................................................................................45Suggestions from LDTP team.............................................................................................................45How to operate LDTP from a remote system......................................................................................45

LDTP engine...................................................................................................................................45LDTP client....................................................................................................................................45

Troubleshooting LDTP........................................................................................................................46Sample LDTP script / runner XML / log XML...................................................................................47

LDTP runner input XML file.........................................................................................................47Test script........................................................................................................................................48XML Log file, On success..............................................................................................................48XML Log file, On failure...............................................................................................................48

Bibliography........................................................................................................................................49

About LDTPLinux Desktop Testing Project (LDTP) is aimed at producing high quality test automation framework and cutting-edge tools that can be used to test GNU/Linux Desktop and improve it. It uses the Accessibility libraries to poke through the application's user interface. The framework also has tools to record test-cases based on user-selection on the application. LDTP core framework uses Appmap (application map) and the recorded test-cases to test an application and gives the status of each test-case as output. As of now, LDTP can test any GNOME application which are accessibility enabled, Mozilla, Openoffice.org, any Java application (should have a UI based on swing) and KDE 4.0 applications based on QT 4.0 (based on the press releases by KDE).

We encourage you to join the project and help us to create robust, reliable and stable test tool / framework for Unix Desktops. Thanks to GNOME Accessibility team and Sun Microsystems Accessibility team for their great work and their continuous support !!!



http://www.kde.org/

http://sun.java.com/

http://www.mozilla.org/


AudienceIts assumed that the user of this document has little knowledge about UI controls in any GUI application, minimal Linux or Unix (Solaris / BSD flavor) knowledge.

About testing

Why testing ?Testing is a process to identify defects in a (software) system. For more information - http://en.wikipedia.org/wiki/Software_testing

Why automation ?Testing an application multiple times with same steps, automated process can do a better job.

Complexity of GUI testing ?• Identification of object in a window (push button, menu item)• Should be context sensitive (Window specific operation)• Handling of unexpected pop-up windows• Keeping the test script in sync with the UI changes• Failures has to be verified on each operation• Rendering of images / text in the display area

What type of testing can be done using LDTP ?LDTP can be used to test the functionality of any accessibility enabled application.

Advantage of accessibility based testing• Accessibility libraries provide applications property, state, its child items etc.• No need to work in toolkit (GTK, AWT, QT) level

Disadvantage of accessibility based testing• Application which are not accessibility enabled can't be tested

What applications can be tested ?As of now, LDTP can test any GNOME application which are accessibility enabled, Mozilla, Openoffice.org, any Java application (should have a UI based on swing) and KDE 4.0 applications based on QT 4.0 (based on the press releases by KDE).

Supported platforms• OpenSuSE• OpenSolaris



http://www.kde.org/

http://sun.java.com/

http://www.mozilla.org/

http://en.wikipedia.org/wiki/Software_testing


• Debian• Ubuntu• Fedora• FreeBSD• Embedded Platform (Palm Source / Access Company)

LDTP Features• LDTP concepts are derived from Software Automation Framework Support

• LDTP supports verification of actions performed (guiexist, verifystate, etc) - API Reference

• Writing test scripts are very easy, the script writer need not know about the object hierarchy

• CPU / Memory performance monitoring of application-under-test can be measured - Class pstats

• From the XML log, we can gather HTML report using XSLT

• Group based execution, which provides precise control on the flow of test-script execution - ldtprunner XML

• Scripts can be written as a reusable component and for that the data can be stored / retrieved in XML - Data XML

• Objects are identified both statically and dynamically

Web / Contact

LDTP on web● Website - http://ldtp.freedesktop.org● Source / Binary - http://ldtp.freedesktop.org/wiki/Download● API reference - http://ldtp.freedesktop.org/wiki/Docs● HOWTO - http://ldtp.freedesktop.org/wiki/HOWTO● FAQ - http://ldtp.freedesktop.org/wiki/FAQ

Development mailing listhttp://lists.freedesktop.org/mailman/listinfo/ldtp-dev

Internet relay chatting – IRC#ldtp of irc.freenod.net



http://lists.freedesktop.org/mailman/listinfo/ldtp-dev

http://ldtp.freedesktop.org/wiki/FAQ

http://ldtp.freedesktop.org/wiki/HOWTO

http://ldtp.freedesktop.org/wiki/Docs

http://ldtp.freedesktop.org/wiki/Download


http://gnomebangalore.org/ldtp/index.php/Remap

http://gnomebangalore.org/ldtp/index.php/Howto_generate_Application_map

http://ldtp.freedesktop.org/wiki/Data_20XML

http://ldtp.freedesktop.org/wiki/ldtprunner_20XML

http://lists.freedesktop.org/archives/ldtp-dev/2005-October/000031.html

http://ldtp.freedesktop.org/user-doc/processstatistics.html

http://ldtp.freedesktop.org/user-doc/processstatistics.html

http://ldtp.freedesktop.org/user-doc/index.html

http://safsdev.sourceforge.net/Default.htm


System requirements

Disk space requirementLess than 450 KB

Software requirements

Install the following dependency packages• cspi-1.0 and development library >= 1.2.0, glib-2.0 >= 2.2.0, gobject-2.0 >= 2.2.0• gail and development library• libgail and development library (or libgail-gnome based on your distribution) • python development library• libxml-2.0 >= 2.0.0 and development library

Note: Development packages are required, if you are planing to install LDTP from source.

Optional packages• Import tool of ImageMagick - To capture a screenshot • Python Imaging Library - Compare images, black out a region in an image • pystatgrab - CPU / Memory utilization monitoring library • Linux Test For X - LTFX, To operate on Window / Object which is not accessibility enabled

EnvironmentGNOME 2.10 or above / KDE 4.0 or above

Setup LDTP

Download source from GIT• check out source from GIT with the following command: 'git clone

git://anongit.freedesktop.org/git/ldtp/ldtp.git'.

• change to the source directory with the following command: 'cd ldtp'

Download source in tar ball format• If you can't access GIT, get the source tarball from http://ldtp.freedesktop.org/wiki/Download

• Extract and change to the source directory with the following command: 'cd ldtp-<version number>'




http://ldtp.freedesktop.org/wiki/GIT

http://sf.net/projects/ltfx

http://www.i-scream.org/pystatgrab

http://www.pythonware.com/products/pil

http://ldtp.freedesktop.org/wiki/ImageMagick

http://imagemagick.org/script/import.php


Setup LDTP from source in Linux environment• build with './autogen.sh --prefix=/usr; make' Assuming that all the above mentioned

development packages are installed. (If downloaded tarball, './configure --prefix=/usr; make')

• setup with 'make install' as the root user

Setup LDTP from binaryDownload latest RPM / Deb / Gentoo / Solaris package from http://ldtp.freedesktop.org/wiki/Download

Architecture

LDTP Overall ArchitectureTest scripts uses LDTP API interface, which in-turn communicate to LDTP engine either by UNIX socket or by TCP socket. LDTP engine talks to Application under test (AUT) using AT-SPI library.

LDTP InternalsLDTP Clients can talk to LDTP engine with the set of LDTP Command Transfer Protocol (LDTPCTP) as defined in the Docs section. LDTP client wraps the LDTP Command Transfer Protcol based on the programming language (example: separate python client, maybe in future we can have Mono / Java / Perl based clients). Communication between the client and server takes place in XML format.

Most of LDTP ideas are implemented from http://safsdev.sf.net Most of the commands takes at-least 2 arguments. First argument will be context (window in which we want to operate) and the second argument will be component (object in which we want to operate, based on the current context).

Example: click ('*-gedit', 'btnNew') # Click operation will be performed on a window which is having *-gedit (regexp) and in that window object name 'New', which is of type 'push button'.



http://safsdev.sf.net/



ServerWhen a test script is started, the LDTP client will establish a connection with the LDTP engine using AF_UNIX / AF_INET.

Client HandlerWhen ever a command is executed from the script, the client frames the XML data and send it to the server. LDTP engine parses the command request from the client and invoke the respective Component Handler.

Component HandlerEach individual component handlers uses the AT-SPI libraries to communicate to the respective application. Based on the execution status, success or failure will be notified as a response (in XML format) to the client. In few cases the requested data from the respective component will be returned to the client, based on the request (example: gettextvalue).

Event HandlerFor unexpected windows (example: connection reset by peer /connection timed out dialogs) can be handled by registering a callback function and the respective callback function will be called, whenever




the registered window with the title appears and even this window could be based on regular expression.

LoggerLogs the execution status in XML format

LDTP conventions

Appmap'Appmap' [Application Map in short] is a text based representation of the GUI which is under testing. Each and every UI control viz., Button, Text Box etc., are represented using predefined conventions (which are listed in the table below) along with their parent UI object information. At runtime, a particular UI control is accessed by using the Appmap generated for the GUI under testing. For more details about Appmap refer http://safsdev.sourceforge.net/DataDrivenTestAutomationFrameworks.htm#TheApplicationMap

Appmap convention

Class keywords convention used in appmap ACCEL_LABEL

ALERT dlg ANIMATION

ARROW CALENDAR cal

CANVAS cnvs CHECK_BOX chk

CHECK_MENU_ITEM mnu COLOR_CHOOSER COLUMN_HEADER

COMBO_BOX cbo DATE_EDITOR

DESKTOP_ICON DESKTOP_FRAME frm

DIAL dial DIALOG dlg

DIRECTORY_PANE DRAWING_AREA dwg



http://safsdev.sourceforge.net/DataDrivenTestAutomationFrameworks.htm#TheApplicationMap


FILE_CHOOSER dlg FILLER flr

FONT_CHOOSER dlg FRAME frm

GLASS_PANE HTML_CONTAINER html

ICON ico IMAGE img

INTERNAL_FRAME LABEL lbl

LAYERED_PANE pane LIST lst

LIST_ITEM lsti MENU mnu

MENU_BAR mbar MENU_ITEM mnu

OPTION_PANE opan PAGE_TAB ptab

PAGE_TAB_LIST ptl PANEL pnl

PASSWORD_TEXT txt POPUP_MENU pop

PROGRESS_BAR pbar PUSH_BUTTON btn

RADIO_BUTTON rbtn RADIO_MENU_ITEM mnu

ROOT_PANE rpan ROW_HEADER rhdr SCROLL_BAR scbr

SCROLL_PANE scpn SEPARATOR sep

SLIDER sldr SPIN_BUTTON sbtn SPLIT_PANE splt




STATUS_BAR stat TABLE tbl

TABLE_CELL tbl TABLE_COLUMN_HEADER tch

TABLE_ROW_HEADER trh TEAROFF_MENU_ITEM tmi

TERMINAL term TEXT txt

TOGGLE_BUTTON tbtn TOOL_BAR tbar TOOL_TIP ttip

TREE tree TREE_TABLE ttbl UNKNOWN unk VIEWPORT view WINDOW dlg

EXTENDED HEADER hdr FOOTER foot

PARAGRAPH para RULER rul

APPLICATION app AUTOCOMPLETE txt CALENDARVIEW cal

CALENDAREVENT cal EDITBAR txt

ENTRY txt

How to Access UI Objects from LDTP scriptsTwo main entities to act on an object, window name, object name.

Window nameTo operate on a window, we need to know the window name (nothing but window title).




Different window types1. Frame (frm)2. Dialog (dlg)3. Alert (dlg)4. Font Chooser (dlg)5. File Chooser (dlg)6. Window (This type in general does not have any associated title, so we need to represent them

using index - dlg)

Glob pattern supportWindow name can be clubbed with glob patterns (* or ?)

Different ways of representing window name1. Window type and window title (Ex: 'frmUnsavedDocument1-gedit')2. Window title (Ex: 'Unsaved Document 1 - gedit')3. Window type, glob expression and partial window title (Ex: 'frm*-gedit')4. Glob pattern and partial window title (Ex: '*-gedit')5. Window type, partial window title and glob pattern (Ex: 'frmUnsavedDocument1*')6. Window type, window title and index (If two windows of same title exist at same time. Ex:

First window name 'dlgAppoinment', Second window name 'dlgAppoinment1')7. Window type and index (only if window does not have any accessible title, Ex: 'dlg0')

Window name formatsIf window label contains space or new line characters, they will be stripped.

Example1. 'Unsaved Document 1 – gedit', will be represented as 'UnsavedDocument1-gedit'2. 'Unsaved Document 1

- gedit', will be represented as 'UnsavedDocument1-gedit'

Object nameObject (the type of control in which we want to operate) can be identified either with a label or by an associated label.

LabelIn general menu / menu item / push button / toggle button type controls can be accessed through its label.

ExamplemnuFile (gedit menu)mnuNew (gedit menu item)




btnNew (gedit tool bar, push button)tbtnLocation (gedit Open File dialog, toggle bar control)

Label by / Label for (associated label)In general text / tables / check box / radio button / spin button / combo box controls can be accessed using the associated label only.

ExampletxtLocation (gedit Open File dialog, text control)tblFiles (gedit Open File dialog, table control)cboSearchfor (gedit Find dialog, combo box control)chkMatchcase (gedit Find dialog, check box control)sbtnRightmarginatcolumn (gedit Preferences dialog, spin button control)

Object name with out label / associated label accessing via indexIf a control does not have any label or associated label, then it can be accessed using index.

Exampletxt0 (gedit text rendering region)ptl0 (gedit Preferences dialog, page tab list control)ptl0 (In gedit when more than one files are opened, a page tab list control will be available)

Object name with indexIn some cases, a control type can be present in multiple places in the same window and chances that it may have same label too in that case, the first control can be accessed just with the default notation, but the second control and further can be accessed with the format control type, label or associated label and index starting from 1.

ExamplebtnAdd – First push button control with label AddbtnAdd1 – Second push button control with label AddbtnAdd2 – Third push button control with label Add

Object name formatsIf object label or associated label contains space, dot, colon, under score or new line characters, they will be stripped.

Example'Search for:' will be represented as 'Searchfor'

'File name 'a_txt' already exist.Replace' will be represented as 'Filename'atxt'alreadyexistReplace'.




Accessibility libraryLDTP uses accessibility libraries (at-spi) available in GNOME environment. Using accessibility we can get the information about application and its current state (property). We can be able to poke through each layer in any application, if and only if, the application is accessibility enabled.

Enabling accessibilityIn gnome-control-center, open Assistive Technology.

Drawing 2: Screenshot of Assisstive technology preferences dialog

Importing LDTP modules• from ldtp import *

from ldtputils import *

Reason why we do importing based on the above format instead of 'import ldtp' is, if we do the first one, we can just directly use all the ldtp functions just by calling their name. If we import the module as 'import ldtp', then we need to call the corresponding function as ldtp.<function


Drawing 1: Assistive technology preferences under GNOME control center



name>

Example 1:

from ldtp import *

selectmenuitem ('*-gedit', 'mnuFile;mnuNew')

Example 2:

import ldtp

ldtp.selectmenuitem ('*-gedit', 'mnuFile;mnuNew')

Call a function to perform an operationLDTP generally operates on the given object in a particular window.

To select a menu item, you need to call selectmenuitem function. For example, to select open menu item in gedit application, call the below function

• selectmenuitem ('frmUnsavedDocument1-gedit', 'mnuFile;mnuOpen')

When you call the above a new dialog box will be poped up, you can verify whether the window is opened or not either by guiexist or by waittillguiexist

• guiexist function immediately returns either 1 (window exist) or 0 (window does not exist) waittillguiexist waits for the window to appear. Wait time out is by default 30 seconds. This default time out can be either increased on decreased using GUI_TIMEOUT

If you want to operate on a push button in a window, you need to call click function:

To press 'Cancel' button in a GTK Open File Selector dialog

• click ('dlgOpenFile', 'btnCancel')

When you do the above operation the GTK File selector dialog disappears. To verify whether the window actually quits or not use waittillguinotexist function

If you modify any opened file in gedit, the window title will be modified. To continue operating on the window you need to change your context of operation. Reason: As you are aware that LDTP works based on individual window, the context of window will be changed, when the title changes. To over come this use setcontext function and when you don't require them use releasecontext

Edit your current opened file using:

• settextvalue ('frmUnsavedDocument1-gedit', 'txt0', 'Testing editing')

This will change the window title. Note, before doing the above operation, title will be 'Unsaved Document 1 - gedit' and after editing the title will look like '*Unsaved Document 1 - gedit'. To further operate on the same window, use

• setcontext ('Unsaved Document 1 - gedit', '*Unsaved Document 1 - gedit')



http://ldtp.freedesktop.org/wiki/releasecontext

http://ldtp.freedesktop.org/wiki/setcontext

http://ldtp.freedesktop.org/wiki/waittillguinotexist

http://ldtp.freedesktop.org/wiki/click

http://ldtp.freedesktop.org/wiki/waittillguiexist

http://ldtp.freedesktop.org/wiki/guiexist

http://ldtp.freedesktop.org/wiki/selectmenuitem


So that you can continue using the same window name, for example:

• selectmenuitem ('frmUnsavedDocument1-gedit', 'mnuFile;mnuSaveAs')

The above function will invoke the GTK save dialog box

If any of the action releated functions (example: selectmenuitem, click, settextvalue) fail, an exception is raised. It has to be handled by the program to either continue operating on execution or just halt.

LDTP API• Refer LDTP API page for list of implemented LDTP API's

Using / Hacking LDTP

Identifying controlsTo operate on a window, first thing we need to know is the window title.

In the following picture you could notice red colored eclipse mark is the window title.

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> guiexist ('*-gedit')1>>> guiexist ('frmUnsavedDocument1-gedit')1>>> guiexist ('frmUnsavedDocument1-*')1>>> guiexist ('frm*-gedit')



http://ldtp.freedesktop.org/user-doc/index.html


1>>> guiexist ('Unsaved Document 1 - gedit')1>>>

Push buttonTo operate on an object inside gedit window, we need to know the object information.

To click on open push button in gedit tool bar control, we need to use click API with window name as first argument and object name as second argument. The above command does the click operation. Informations to be gathered are Window name (Unsaved Document 1 – gedit) and push button control (Open).

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> click ('*-gedit', 'btnOpen')1>>>

Menu itemTo select a menu item under a menu in a window we need to use selectmenuitem API.

Informations to be gathered: Window name (Unsaved Document 1 – gedit), menu control (File), menu item control (New).

Incase of menu, we handle them in hierarchy. So, to access 'New' menu item, we need 'File' menu control too.




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> selectmenuitem ('*-gedit', 'mnuFile;mnuNew')1>>>

Toggle buttonTo operate on a toggle button with a click action, information required are window name (Open Files...) toggle button control (Type a file name).




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> click ('dlgOpenFiles...', 'tbtnTypeafilename')1>>>

Text controlTo set a text value in a text box, information like window name (Open Files...), text controls associated label (Location:) and the actual text to be placed (Class1.cs).

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> settextvalue ('dlgOpenFiles...', 'txtLocation', 'Class1.cs')1>>>

Table controlTo select a row from the table of GTK open file selector, we need to collect information like, Window name (Open Files...), table name (Files – circled with blue color), row to be selected (Class1.cs).




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> selectrow('dlgOpenFiles...', 'tblFiles', 'Class1.cs')1>>>

Push buttonAfter selecting the file name, to open the file contents, we need to click on Open push button control. For doing this operation we need to gather informations like Window name (Open Files...), push button label name (Open).




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> click ('dlgOpenFiles...', 'btnOpen')1>>>

Check boxTo click on a check box control, we need to collect informations like window name (gedit Preferences), check box associated label name (Display line numbers).

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> click ('dlggeditPreferences', 'chkDisplaylinenumbers')1>>>




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> check ('dlggeditPreferences', 'chkEnabletextwrapping')1>>>

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *




>>> uncheck ('dlggeditPreferences', 'chkDisplaylinenumbers')1>>>

Spin buttonTo operate on a spin button, we need to collect information like Window name (gedit Preferences), spin button control name (Right margin at column).

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> getvalue('dlggeditPreferences', 'sbtnRightmarginatcolumn')80.0>>> setvalue('dlggeditPreferences', 'sbtnRightmarginatcolumn', '81')1>>> setvalue('dlggeditPreferences', 'sbtnRightmarginatcolumn', '80')1>>>

Page tabTo operate on a page tab list, we need to collect information like window name (gedit Preferences), page tab list name (ptl0 in this case, as there are no label or associated label with this page tab list control), page tab name or index starting from 0.

nags@nags:~> python




Python 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> gettabcount ('dlggeditPreferences', 'ptl0')5L>>> selecttabindex ('dlggeditPreferences', 'ptl0', 2)1>>> selecttab ('dlggeditPreferences', 'ptl0', 'Editor')1>>>

Check menu itemTo operate on check menu item, we need to gather information like window name (Unsaved Document 1 – gedit), menu name (View), check menu item name (Side Pane).

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> selectmenuitem ('*-gedit', 'mnuView;mnuSidePane')1>>> menuuncheck('*-gedit', 'mnuView;mnuSidePane')1>>>




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> menucheck('*-gedit', 'mnuView;mnuStatusbar')1>>>

Radio menu itemTo operate on a radio menu item control, we need to gather informations like window name (Unsaved Document 1 – gedit), menu name (Documents), menu item name (Class1.cs – assuming that Class1.cs is currently opened).

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> selectmenuitem ('*-gedit', 'mnuDocuments;mnuClass1.cs')1




>>> menucheck ('*-gedit', 'mnuDocuments;mnuClass1.cs')1>>>

Combo box – Menu itemTo select a menu item under a combo box, we need to gather informations like window name (Open Files...), combo box name (Character Coding), menu item name (Current Locale).







nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> comboselect ('dlgOpenFiles...', 'cboCharacterCoding', 'Current Locale (UTF-8)')1>>>

Combo box – List itemTo operate on list item under a combo box control, we need to gather informations like window name (Find), Combo box control name (Search for), list item existing content or list item index or new item name (OdbcMetaDataCollectionName.cs)




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> settextvalue('dlgFind', 'cboSearchfor', 'OdbcMetaDataCollectionNames.cs'')1>>>

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2




Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> comboselect('dlgFind', 'cboSearchfor', 'OdbcMetaDataCollectionNames.cs')1>>>

Launch applicationApplication to be tested can be launched using LDTP API launchapp.

launchapp takes an optional argument, to set the environment variable GTK_MODULES and GNOME_ACCESSIBILITY and then invoke the respective application. When accessibility is not enabled by default in gnome-control-center, this is the preferred way of launching application.

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> launchapp ('gedit', env = 1)1>>>

Example 1launchapp ('gedit')

Example 2launchapp ('gedit', env = 1)

GUI existTo check a GUI (window) exist, you can use this guiexist API. Also it has different flavors like waittillguiexist, waittillguinotexist.

● guiexist function checks whether the given window exists or not. If exist returns 1, else returns 0.

● waittillguiexist function will wait for the given window to appear. If appeared returns 1, else returns 0. Difference between guiexist and waittillguiexist is, guiexist returns immediately, but waittillguiexist will wait for a max of 30 seconds for a window to appear. Note: On doing some operation, if the expected result is, a window will be pop-ed up, then it is recommended to use waittillguiexist, instead of wait or sleep. Reason: wait or sleep will wait till the time period, but waittillguiexist, will return immediately once the window appears.

● waittillguinotexist function will wait for the given window to close. If closed returns 1, else returns 0. waittillguinotexist will wait for a max of 30 seconds for a window to close. Note: On doing some operation, if the expected result is, an existing window will be closed, then it is




recommended to use waittillguinotexist, instead of wait or sleep. Reason: wait or sleep will wait till the time period, but waittillguinotexist, will return immediately once the window closed.

TimeoutGUI timeout

GUI timeout, is the default timeout settings used, by waittillguiexist and waittillguinotexist functions. This function will wait for the specified number of seconds, for the window to either appear or disappear. Default timeout period is 30 seconds.

This default timeout period that can be modified:

● By setting the environment variable GUI_TIMEOUT to whatever seconds.● By passing a value to guiTimeOut argument of waittillguiexist or waittillguinotexist functions.● By calling guitimeout function.● When invoking LDTP engine, use -g option.

Example 1export GUI_TIMEOUT=30

Example 2waittillguiexist ('*-gedit', guiTimeOut=30)waittillguinotexist ('dlgOpenFiles...', guiTimeOut=30)

Example 3guitimeout (30)

Example 4ldtp -g 30

OBJ timeout

OBJ timeout, is the default timeout settings used, internally. This function will wait for the specified number of seconds, for the object inside a window to appear. Default timeout period is 5 seconds.

This default timeout period that can be modified:

● By setting the environment variable OBJ_TIMEOUT to whatever seconds.● By calling objtimeout function.● When invoking LDTP engine, use -o option.

Example 1export OBJ_TIMEOUT=5




Example 2objtimeout (5)

Example 3ldtp -o 5

Re-Initialize LDTPWhen we open a new window in few applications, the windows accessibility informations are not updated, due to bug in the respective application (for example, Firefox 1.x or nautilus with GNOME 2.8). If we close the at-spi handle and re-open it, we will be able to get the accessibility information. That's where reinitldtp api will be useful.

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> launchapp ('firefox') # Firefox 1.51>>> waittillguiexist ('*-MozillaFirefox')1>>> selectmenuitem ('*-MozillaFirefox', 'mnuEdit;mnuPreferences')1>>> reinitldtp ()1>>> waittillguiexist ('Preferences')1

Set context / Release contextIn some cases, the complete window title changes at run-time, setcontext can be used for such scenarios. For example, In Evolution application, the mail composer window's title changes dynamically, when the subject is typed. So, to access the window, after changing the subject, we need to change the window name (context name) for the consecutive calls. To over come this, we can use setcontext API and the rest of the call to the composer window can just have the same context name as the one before changing the subject.

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> selectmenuitem ('*-Evolution', 'mnuFile;mnuNew;mnuMailMessage')1>>> waittillguiexist ('frmComposeMessage')




1>>> settextvalue ('frmComposeMessage', 'txtTo', '[email protected]')1>>> settextvalue ('frmComposeMessage', 'txtSubject', 'Testing set context')1>>> setcontext ('Compose Message', 'Testing set context')1>>> settextvalue ('frmComposeMessage', 'txt0', 'Body of the mail')1

Generate raw keyboard eventsIn some cases, the window we are trying to operate may not be accessibility enabled or we may need to generate non-printable keys (ALT, CTRL, ENTER, BACKSPACE, ESC, F1-F12, SHIFT, CAPS LOCK, TAB, PAGE UP, PAGE DOWN, HOME, END, RIGHT / LEFT / UP / DOWN ARROW KEYS, INS, DEL). We can use generatekeyevent function or enterstring function to simulate the key events, as if the user typed. Note: All the non-printable characters will be enclosed with in angular brackets.Example 1<ctrl>lwww.google.co.in<enter>Example 2<alt><f1>Example 3<control>s

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> launchapp ('gedit')1>>> waittillguiexist ('*-gedit')1>>> enterstring ('<alt><tab>')1>>> enterstring ('*-gedit', 'txt0', '<caps>Testing enterstring API<enter>')1>>> generatekeyevent ('<alt><tab>')1

Generate raw mouse eventsTo generate raw mouse events of different types like, b1c, b1d, b2c, b2d, b3c, b3d, X and Y of screen co-ordinates has to be provided. Here b is button, c is single click, d is double click.




nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> generatemouseevent (100, 200) # Default is b1c1>>> generatemouseevent (100, 200, 'b1d')1

Application informationOn calling getapplist, will get all the accessibility application name that are currently running. To get window list for which the application map's are gathered and stored in local cache, use getwindowlist. To get all the object list under a window, use getobjectlist API. To get a list of properties available under an object, use getobjectinfo. To get the property of an object, use getobjectproperty.

nags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> getapplist ()[u'gnome-session', u'gnome-power-manager', u'gnome-settings-daemon', u'Libbonoboui-Gtk-Module-init-info', u'nautilus', u'GnomeApplicationBrowser', u'/usr/lib/zen-updater/ZenUpdater.exe', u'gaim', u'gtk-window-decorator', u'gedit', u'xchat', u'gnome-panel', u'gnome-volume-manager', u'resapplet', u'nm-applet', u'soffice.bin']>>> getwindowlist ()[u'frmUnsavedDocument1-gedit']>>> getobjectlist ('*-gedit')...>>> getobjectinfo ('*-gedit', 'btnNew')[u'child_index', u'class', u'description', u'parent', u'label']>>> getobjectproperty ('*-gedit', 'btnNew', 'class')'New'

Callback – On new window creationRegister a callback event, when a window with given title is created. Glob type pattern can be given as title name.

AdvantageUnexpected window can be easily handled using this. For example, the password dialog box of Evolution, connection reset by peer dialog, application crash dialog, etc.




Example from ldtp import * import threading callbackRunning = threading.Event () callbackRunning.clear () callbackState = threading.Event () callbackState.clear () def cb (): callbackState.set () waittillguiexist ('dlgReplace') click ('dlgReplace', 'btnClose') callbackState.clear () callbackRunning.set () print 'callbackend' onwindowcreate ('Replace', cb) click ('*gedit', 'btnReplace') click ('*gedit', 'btnOpen') waittillguiexist ('dlgOpenFiles...') click ('dlgOpenFiles...', 'btnClose') if callbackState.isSet (): print 'Waiting for callback to complete' callbackRunning.wait () print 'callbackset' print 'test end'

Color codingLight yellow – Thread creationLight green – Callback definitionRed – Callback registrationMagenta – General operation, which will invoke a windowLight blue – Wait for callback to complete, if invoked.

Loggingnags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> log ('test script', 'teststart')1>>> log ('test script', 'debug')1>>> log ('test script', 'warning')




1>>> log ('test script', 'error')1>>> log ('test script', 'cause')1>>> log ('test script', 'commend')1>>> log ('group scripts', 'groupstart')1>>> log ('group scripts', 'groupstatus')1>>> log ('group scripts', 'groupend')1>>> log ('category scripts', 'categorystart')1>>> log ('category scripts', 'categorystatus')1>>> log ('category scripts', 'categoryend')1>>> log ('test script', 'pass')1>>> log ('test script', 'fail')1>>> log ('test script', 'testend')1>>>

Example scriptfrom ldtp import *from ldtputils import *

try:logMsg = 'Open a file in gedit'log (logMsg, 'teststart')launchapp ('gedit')if waittillguiexist ('*-gedit') == 0:

raise LdtpExecutionError ('Gedit window does not exist')selectmenuitem ('*-gedit', 'mnuFile;mnuOpen')if waittillguiexist ('dlgOpenFiles') == 0:

raise LdtpExecutionError ('Open Files dialog does not exist')dataXml = LdtpDataFileParser (datafilename)fileName = dataXml.gettagvalue ('filename')selectrow ('dlgOpenFiles...', 'tblFiles', fileName [0])click ('dlgOpenFiles...', 'btnOpen')




if waittillguinotexist ('dlgOpenFiles') == 0:raise LdtpExecutionError ('Open Files dialog still exist')

log (logMsg, 'pass')log (logMsg, 'testend')

except LdtpExecutionError, msg:log (msg, 'cause')log (logMsg, 'fail')log (logMsg, 'testend')raise LdtpExecutionError (logMsg)

NOTE: With the recent changes in LDTP logging module, if the log file is not used, by default a new file will be created in /tmp/ldtp-$USER/log-mm-dd-yyyy-hh-mm.xml file and on each failure a screenshot will be placed in the same directory or the specified directory through startlog function call.

Script input Data XML file - Useful to maintain a generic script

WhatXML file contains input data required by the script at run-time.

WhyScripts can be written generically and the data's required can be taken from this XML file.

Advantages of using LDTP Data XML• Technically its a good practice to separate script and data. Reason behind this is re-usability

• Scripts will be written just once, based on the need we can just populate the data XML

• In some cases for doing regression testing we will just have one script and multiple data files

• Reason for XML format is, its easy to parse

LDTP Data XML TagsWe have the following tags in Data XML

• data - The complete XML are tagged under this <data> and </data> tag

• <user defined tags> - User defined tags with user defined values. These user defined tags can appear multiple times. If you use LDTP utils XML parser, the values from the user defined tags are returned as a list. So, you can use it with its index. The list index starts from 0.

SyntaxLdtpDataFileParser ('[XML Filename]')

LdtpDataFileParser class takes Data XML filename as an optional argument. This class also provides 2




functions.● *setfilename ('[XML Filename]'). If the class does not takes an argument, then this function

should be used● * gettagvalue ('tag name'). Get the value of the given tag.

ExampleExample 1

addr_book = LdtpDataFileParser ()addr_book.setfilename ('evolution-ab.xml')addr_book.gettagvalue ('AddressbookType')

Example 2addr_book = LdtpDataFileParser ('evolution-ab.xml')addr_book.gettagvalue ('AddressbookType')

Sample XML File <data> <AddressbookType>On This Computer<AddressbookType>

<AddressbookName>LDTP-AB</AddressbookName> </data>

Sequencing set of LDTP scripts using ldtprunner XML file

WhatXML file to group relevant scripts and respective data files under a group and execute them in one go.

WhyIt will be useful, if we could group all the relevant test-case into one group and start executing them. If one of the test scripts fails under a group, then the execution of remaining scripts can be ignored.

Advantages of using ldtprunner XML• Group set of related test-scripts into one category

• In a group if the current executing script fails, then rest of the scripts in the current group will be skipped and ldtprunner will start executing the next group

• Each individual scripts can take optional Data XML file as an argument

• Same script can be called multiple times with different Data XML file

• Scripts can be grouped in any sequence. Based on the sequence, scripts will be executed.






ldtprunner TagsWe have the following tags in ldtprunner XML

• ldtp - The complete XML are tagged under this <ldtp> and </ldtp> tag

• logfileoverwrite # - Value 0 (append to existing log file, if its already available) or 1 (Truncate the existing file, if its already available and write the data from 0)

• logfile - File name, where the log file has to be written. Log files are generated in XML format. Its preferred to give absolute path for the log file

• appmapfile # - Optinal application map file name. This option is available only for backward compatibility. We recommend not to use this option

• category # - A category can contain one or more group(s). All the group entries in a category will be executed in sequence. This feature was requested by Palm Source.

• group - A group can contain one or more scripts. All the scripts in a group will be executed in sequence. The purpose of group is, if one of the script fails, then the whole group is skipped

• testcaseid - One testcase id per group, if available will be logged as part of log file

• comment - Comments about the script, will not be logged in the log file

• script - Script contains one script file name and optional data file name

• name - Script file name

• data # - Data file name (Data file content will be in XML format - Data XML)

Note: # marked are optional fields

Following are the list of recommendations when generating ldtprunner XML

• Select the log file to initialize in ldtprunner XML

• Select log file overwrite option

Sample LDTP runner XML file <?xml version="1.0"?> <ldtp> <logfileoverwrite>1</logfileoverwrite> <logfile>evolutionexecutionstatus.xml</logfile> <group> <testcaseid>test-001</testcaseid> <comment>testing script test1.py and test3.py</comment> <script> <name>test1.py</name> <data>test1.xml</data> </script> <script>





<name>test3.py</name> <data>test3.xml</data> </script> </group> <group> <script> <name>test7.py</name> <data>test2.xml</data> </script> </group> </ldtp>

Color codeGreen – LDTP runner XML tagLight blue – Log fileMagenta – Group 1Pale yellow – Group 2

How to execute LDTP scriptsMake sure that you have the following files in current working directory

• You need to have test scripts to be executed • You can have Data XML - Optional • You can have ldtprunner XML - Optional• Make sure ldtp, ldtprunner, ltfx (optional), digwin (optional), ldtprecord (optional) are installed

Invoking LDTP runner XML

$ ldtprunner <ldtprunner XML>Example

ldtprunner test-runner.xml

Invoking python script $ python <script file name.py>Example

python gedit.py

Suggestions from LDTP team• When a new window is expected after an operation, we suggest to use waittillguiexist and on some

operation, if a window is expected to close we suggest to use waittillguinotexist. In both cases, the time-out period is 30 seconds. This value can be modified – refer LDTP API reference.

• Use data XML file, the data XML file can be produced with different data and the script can be written once.



http://ldtp.freedesktop.org/wiki/ldtprunner_20XML



How to operate LDTP from a remote system

LDTP engineFollow one of the options to start LDTP engine (ldtp binary) in the remote boxOption 1$ldtp -sOption 2$ ldtp -p <port number to start> # Default port number is 23456

LDTP clientFollow one of the options in the client side to communicate to LDTP engineOption 1export LDTP_SERVER_ADDR=host-name or ip addressexport LDTP_SERVER_PORT=<port number to communicate, as mentioned in LDTP engine>python <script file name>.py or ldtprunner test-runner.xmlOption 2export LDTP_SERVER_ADDR=host-name or ip addresspython <script file name>.py or ldtprunner test-runner.xml # This will use default port number.

Troubleshooting LDTPIn-case, if you want to see whats happening on executing some LDTP commands, follow the steps

In a terminal

$ export LDTP_DEBUG=2 # If bash shell$ ldtpClient packet len: 82i = 0Data read 82, packet-len = 82, bytes read = 82, data: <?xml version="1.0"?><REQUEST><ACTION>124</ACTION><ID>MainThread124</ID></REQUEST>PACKET LENGTH: 0Received packet [<?xml version="1.0"?><REQUEST><ACTION>124</ACTION><ID>MainThread124</ID></REQUEST>] through 15Node: ACTIONaction_name: 124Node: IDrequest_id: MainThread124Command: 124Accessible application name: ThunderbirdAccessible application name: gnome-panelAccessible application name: xchatAccessible application name: nm-applet




Accessible application name: nautilusAccessible application name: gaimAccessible application name: acroreadAccessible application name: soffice.binAccessible application name: gtk-window-decoratorAccessible application name: geditLIST: <?xml version="1.0" encoding="utf-8"?><OBJECTLIST><OBJECT>nautilus</OBJECT><OBJECT>gaim</OBJECT><OBJECT>gtk-window-decorator</OBJECT><OBJECT>gedit</OBJECT><OBJECT>xchat</OBJECT><OBJECT>gnome-panel</OBJECT><OBJECT>Thunderbird</OBJECT><OBJECT>nm-applet</OBJECT><OBJECT>soffice.bin</OBJECT><OBJECT>acroread</OBJECT></OBJECTLIST>resp_len = 117Sending..538Response packet: <?xml version="1.0" encoding="utf-8"?><RESPONSE><ID>MainThread124</ID><STATUS><CODE>0</CODE><MESSAGE>Successfully completed</MESSAGE></STATUS><DATA><LENGTH>325</LENGTH><VALUE><![CDATA[<?xml version="1.0" encoding="utf-8"?><OBJECTLIST><OBJECT>nautilus</OBJECT><OBJECT>gaim</OBJECT><OBJECT>gtk-window-decorator</OBJECT><OBJECT>gedit</OBJECT><OBJECT>xchat</OBJECT><OBJECT>gnome-panel</OBJECT><OBJECT>Thunderbird</OBJECT><OBJECT>nm-applet</OBJECT><OBJECT>soffice.bin</OBJECT><OBJECT>acroread</OBJECT></OBJECTLIST>]]></VALUE></DATA></RESPONSE>Msg:Bytes sent: 542

In another terminal

$ export LDTP_DEBUG=2 # If bashnags@nags:~> pythonPython 2.5 (r25:51908, Nov 25 2006, 15:39:45)[GCC 4.1.2 20061115 (prerelease) (SUSE Linux)] on linux2Type "help", "copyright", "credits" or "license" for more information.>>> from ldtp import *>>> getapplist()124 ( )Send packet <?xml version="1.0"?><REQUEST><ACTION>124</ACTION><ID>MainThread124</ID></REQUEST>Received packet size 538Received response Packet <?xml version="1.0" encoding="utf-8"?><RESPONSE><ID>MainThread124</ID><STATUS><CODE>0</CODE><MESSAGE>Successfully completed</MESSAGE></STATUS><DATA><LENGTH>325</LENGTH><VALUE><!




[CDATA[<?xml version="1.0" encoding="utf-8"?><OBJECTLIST><OBJECT>nautilus</OBJECT><OBJECT>gaim</OBJECT><OBJECT>gtk-window-decorator</OBJECT><OBJECT>gedit</OBJECT><OBJECT>xchat</OBJECT><OBJECT>gnome-panel</OBJECT><OBJECT>Thunderbird</OBJECT><OBJECT>nm-applet</OBJECT><OBJECT>soffice.bin</OBJECT><OBJECT>acroread</OBJECT></OBJECTLIST>]]></VALUE></DATA></RESPONSE>[u'nautilus', u'gaim', u'gtk-window-decorator', u'gedit', u'xchat', u'gnome-panel', u'Thunderbird', u'nm-applet', u'soffice.bin', u'acroread']>>>

Sample LDTP script / runner XML / log XML

LDTP runner input XML file<?xml version='1.0' encoding='utf-8'?><ldtp>

<category><name>category1</name><group>

<name>group1</name><script>

<name>file1.py</name></script>

</group></category>

</ldtp>

Test scriptfrom ldtp import *try: log ('launch gedit','teststart') launchapp ('gedit') if waittillguiexist ('*-gedit') == 0: raise LdtpExcecutionError ('Gedit window does not exist') log ('launch gedit', 'pass')except LdtpExecutionError, msg: log (msg, 'cause') log ('lauch gedit', 'fail') log ('launch gedit', 'testend')




raise LdtpExecutionError ('launch gedit failed')log ('launch gedit','testend')

XML Log file, On success<?xml version='1.0' encoding='utf-8'?><ldtp>

<category name="category1"><group name="group1">

<script name="launch-gedit.py"><test name="launch gedit"></test>

</script><pass>1</pass>

</group></category>

</ldtp>

XML Log file, On failure<?xml version='1.0' encoding='utf-8'?><ldtp>

<category name="category1"><group name="group1">

<script name="launch-gedit.py"><test name="launch gedit">

<cause>window does not exist</cause></test>

</script><pass>0</pass>

</group></category>

</ldtp>

Bibliographyhttp://en.wikipedia.org/wiki/Software_testinghttp://safsdev.sf.net



http://safsdev.sf.net/

http://en.wikipedia.org/wiki/