Hi Caolan,
the Automated Testing Team by Sun tried with TestTool to identify a code
coverage with their test scripts. They ran the tests with accessibility
enabled or disabled on the system. The result in our environment was the
same.
Perhaps you find an other way. But the testing team thought, that the
Accessibility code is only activated, when the connection is over the
Accessibility tools/bridges or what ever, but it isn't activated only by
enabling it in the system.
So we cannot help here for Valgrind testing when Accessiblity is
activated in the system.
Thorsten
Caolan McNamara wrote:
On Wed, 2006-10-11 at 14:54 +0200, Nikolai Pretzell wrote:
Hi,
regarding the Valgrind Tasks
(http://wiki.services.openoffice.org/wiki/ValgrindTasks) somebody
(Caolan?) asked some time ago, if we could do something like this for
accessability features.
I have contacted the people creating the automatic tests we use, and the
answer is unfortunately: No, with the current tools this is not
possible. Accessability features trigger the Office via third party
tools and the TestTool can not catch the signals in the Office caused
from third party applications, therefore there are no automatic test
scripts we could use with Valgrind.
Not sure if we're talking about exactly the same thing, but maybe I just
don't understand the current valgrind test harness. I didn't really mean
to actually test a11y features specifically, I just mean that when
running OOo under valgrind on e.g. linux that gnome's a11y is enabled,
which triggers OOo's a11y to be enabled and the various OOo a11y objects
created during normal operations. i.e. not poking OOo directly with any
external a11y tools.
C.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
