20 messages in org.gnome.desktop-devel-listRe: GNOME's testing strategy for GUIs
FromSent OnAttachments
Willie WalkerFeb 14, 2008 10:42 am 
Nickolay V. ShmyrevFeb 14, 2008 10:53 am 
Brad TaylorFeb 14, 2008 11:08 am 
John StowersFeb 14, 2008 1:18 pm 
Brad TaylorFeb 14, 2008 1:25 pm 
John StowersFeb 14, 2008 1:34 pm 
David BolterFeb 14, 2008 1:56 pm 
David BolterFeb 14, 2008 1:58 pm 
Nagappan AFeb 14, 2008 9:48 pm 
Vincent UntzFeb 15, 2008 6:09 am 
Emmanuel FleuryFeb 15, 2008 6:33 am 
Nagappan AFeb 15, 2008 7:03 am 
Willie WalkerFeb 15, 2008 8:40 am 
David BolterFeb 16, 2008 9:41 am 
Willie WalkerFeb 16, 2008 1:50 pm 
Luis VillaFeb 16, 2008 2:00 pm 
Luis VillaFeb 17, 2008 5:20 am 
APIFeb 20, 2008 8:12 am 
Qi-Bo Paul MeiFeb 20, 2008 2:00 pm.Other
Nagappan AFeb 22, 2008 9:51 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: GNOME's testing strategy for GUIsActions...
From:Brad Taylor (br@getcoded.net)
Date:Feb 14, 2008 11:08:52 am
List:org.gnome.desktop-devel-list

Hi Willie,

First off, in the spirit of full disclosure, I should mention that I work for Medsphere, the company who backs the development of the GPL testing tool, Strongwind[1].

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.

Ken VanDine and I met at SCALE this last week and discussed some plans regarding automated testing in GNOME. We identified a few rough spots:

* Many tools are available for automated testing, and GNOME needs to annoint one with holy gnome pee so that it will become an acceptable dependency for development. Whether this is LDTP, Dogtail, Strongwind, or others, a clear decision needs to be made so that people can go forth with creating tests.

Having a mix of testing tools in use will only make it more difficult for folks to contribute to, and maintain a large body of tests.

* Someone needs to step up and write good, thorough documentation for developing tests. To my knowledge, no current testing tool has this.

* A culture of automated testing needs to be developed and fostered inside of GNOME so that maintainers feel real benefit in maintaining a high-quality test library. Maintenance is not a trivial thing.

* Distributions who already have automated tests for GNOME applications need to have a place to contribute and maintain these tests _publicly_, and have them shared by all. This was made clear in discussions with folks at this year's GNOME Summit.

Obviously, there is a lot of work that needs to be done, but these challenges are by no means insurmountable.

The first thing that needs to come into the picture are good docs. I've commited myself to contribute a Gnome Journal article on writing Strongwind tests as a first start into this field.

Cheers,

-Brad