Vladimir, Thanks for the Dogtail tip! It looks like in addition to doing automated testing of GUI in general, the a11y underpinning should facilitate a more systematic assessment of Accessibility and support for Assistive Technologies as implemented on the Linux builds. But that testing should be of benefit to Windows and OSX Accessibility as well. Assuring Accessibility and support for Assistive Technologies has not had much effort on the automated test case front--it has been hit or miss by hand with big gaps in the QA process.
Stuart ________________________________________ From: libreoffice-qa on behalf of Vladimir Benes [[email protected]] Sent: Wednesday, March 13, 2013 10:17 AM To: [email protected] Subject: [Libreoffice-qa] GUI automation Hi all, we were discussing recently how to improve testing of LO's GUI. We found out that situation if more than bad. There are several options how to approach this. The first is LDTP [1] and the other one (in my opinion far better) is Dogtail [2]. If LO uses standard gtk widgets so they're a11y friendly we can easily access them. This works for accessing menu items, dialogs and so on. For comparing visual things like pictures, font alignment, etc there is Sikuli [3] framework actively developed at MIT that can be used for this. Is there anything where we can start or at least help with? What I would expect is at least some priority one functionality that should be covered first or so. any ideas? Vladimir [1] http://ldtp.freedesktop.org/wiki [2] https://fedorahosted.org/dogtail/ [3] http://www.sikuli.org/ _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: [email protected] Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
