Hi Caolan,
Caolan McNamara wrote:
On Thu, 2006-10-12 at 09:05 +0200, Thorsten Ziehm wrote:
Hi Mathias,
Mathias Bauer wrote:
Code coverage is one thing (and it's only status quo!), code behavior
another. Does just switching on a11y support in the configuration
*without actually using it* really make the testing with the testtool
impossible? How does it hurt us?
It doesn't make the testing with TestTool impossible. But the
Accessibility Code isn't touched at testing. Therefore I talked about
the analysis of Code Coverage with the TestTool scripts.
If it will be possible to check the Accessibility functionality with
TestTool too, then the code coverage of all scripts will increase. But
as I heard, this isn't possible without using the Accessibility Tools.
Maybe something of interest here then might be dogtail which RedHat uses
for app GUI testing. It uses the a11y interface to traverse the apps GUI
elements, and so tests some a11y functionality as it goes by nature of
how it works.
http://people.redhat.com/zcerza/dogtail/
http://people.redhat.com/zcerza/dogtail/doc/apps/categories.html
The resources in my team are limited. Currently I do not see any chance
to work with dogtail to check with Valgrind the accessibility code.
Perhaps a team at RedHat can do this or somebody else from the community?
Regards,
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
