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:Nickolay V. Shmyrev (nshm@yandex.ru)
Date:Feb 14, 2008 10:53:48 am
List:org.gnome.desktop-devel-list

В Чтв, 14/02/2008 в 13:42 -0500, Willie Walker пишет:

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?

Well, there is gnome-test-specs package, partially outdated:

svn.gnome.org/viewcvs/gnome-test-specs

during GHOP Joshua Henderson wrote amazing set of tests with ldtp for testcases mentions, now they are committed in gnome-tests-specs

Individual packages like evince or gedit also have test specification, there are evolution dogtail scripts. Some amount is committed in jhbuild which has jhbuild test command, not quite used now.

So the minor problem is either to collect all tests in a single place like jhbuild or gnome-test-specs or include them into individual packages. There must be a whole desktop testing suite as well too.

There are few much more important problems with tests:

1) They are slow, it's hard to wait so long 2) They don't really test anything at least now. GUI testing is rather complicated subject, I'm not sure how it can be done properly. I haven't seen any good article on GUI testing yet.