Re: GNOME's testing strategy for GUIs

["Nagappan A" <nagappan gmail com>]

Hi Will,

* We have the recording framework using pyatspi / orca-atspi. So, this works on older systems (GNOME >= 2.14) too, where orca-atspi worked. With this, Evolution QA team was able to automate more than 100 different test cases and they are using it in their local testing environment.
* Currently the LDTP team is working on OO LDTP, which many users have requested.
* LDTP API manual is available online. It has more than 150 ready to use API.
* LDTP tutorial is available online to start with automation.
* As part of Google Summer of Code 2006, under GNOME project, Prashanth Mohan developed LDTP scripts and delivered them to GNOME.
* As part of Google Summer of Code 2007, under Mozilla project, Hari Shankar developed LDTP scripts and delivered them to Mozilla.
* As part of GHOP 2007, Joshua developed LDTP scripts and delivered to GNOME community.

LDTP team is ready to implement what ever the features required by GNOME community.

Thanks
Nagappan

On Thu, Feb 14, 2008 at 10:42 AM, Willie Walker <William Walker sun com> wrote:

Hi All:

I might be opening a big can of worms with this question, and I
apologize if someone is already working in this space and I just don't
know it.

What is the automated testing strategy for GUIs in GNOME?  Is there a
well defined way to create a 'make test' target and have it do the right
thing?

I know of LDTP and Dogtail, and the build brigade folks were trying
something at one time.  Orca has its regression test harness as well.
But, I know of no unifying test strategy for GNOME.  Are people working
in this space?  If not, does the community have an interest in seeing
something like this emerge?

Will


_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

-- 
Linux Desktop (GUI Application) Testing Project - http://ldtp.freedesktop.org
http://nagappanal.blogspot.com