[Qt-interest] QDBusBridge, IAPoke: no enough info

[Görög Veronika]

Dear David,

Thank you again for your answers.

I have tried squish. It seems well, but it is a third party tool without
source code, what I don't like. And it is very expensive.

Do you know something about kdexecutor? Which is also a GUI testing tool for
Qt, but it is cheeper, and they give also the source code with the license.
I think it is cool. Because I am very curious how they solve this GUI
testing problem on linux, with qt.

Anyway, I try to understand the accessible plugin and D-Bus interface more
deeply. Because I think this is to best way in long term.

Just one more question: do you know the email address of harald (
http://labs.trolltech.com/blogs/author/harald/) ? Can I contact with him
directly?

Cheers,

Veronika
On Tue, Jan 13, 2009 at 7:10 PM, David Boddie <david.boddie at nokia.com>wrote:

> Görög Veronika wrote:
>
> > I am playing with this Qt D-Bus Accessibility Bridge with IAPoke.
> >
> > I have some questions:
> >
> > 1. Is there a forum or something according to using this Qt D-Bus
> > Accessibility Bridge?
>
> The only forum appears to be the one on the Labs site:
>
>  http://labs.trolltech.com/forums/forum/12
>
> > 2. I have tried to reach the widgets in the following example:
> > /examples/dialogs/tabdialog
> >
> > Which is a QDialog. But IAPoke does not show any widget in this
> > application. Is it a missing feature?
>
> Possibly. It seems that other QDialog-based examples fail to work with
> IAPoke and may not be registered with D-Bus at all.
>
> > 3. I have created an application to test the widgets in Qt with IAPoke.
> > And I try to call the shown methods.
> >
> > For example, if I call doAction with value -1 on a QPushButton, this
> > button
> > will be pushed. QTextEdit seems very cool, because in IAPoke there  are a
> > lot of callable methods: i.e.: EditableText - insertText
> >
> > That's cool. But how this works? I mean with the QLineEdit I don't find
> > such a method in IAPoke. What is the reason?
>
> It may well be the case that it doesn't expose the same interface. Looking
> through the source in src/plugins/accessible/widgets/simplewidgets.cpp it
> seems that its capabilities are more limited that those of QTextEdit.
>
> > What can I do to make this widgets more robust without using an adaptor?
>
> I'm not sure I understand what you mean. Are you asking what you can do to
> make QLineEdit and QDialog more accessible, or if there's a way to do this
> without the accessibility bridge?
>
> Accessibility support on Linux is more limited than I had originally
> thought, so there may not be much you can do to improve the situation using
> the current tools unless you start modifying the accessibility bridge or
> the
> built-in accessibility code (in src/plugins/accessible).
>
> I seem to recall that you wanted to use these features for user interface
> testing. Another option you would have for this is to try Squish
> (http://www.froglogic.com/). Otherwise, you could expose your own D-Bus
> interface to enable GUI testing. I realize that this doesn't help you with
> ldtp interoperability.
>
> Sorry I can't offer more useful advice. Maybe there are others reading who
> can suggest other, better ways to do what you want.
>
> David
> --
> David Boddie
> Senior Technical Writer
> Nokia, Qt Software
>
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20090114/f2304179/attachment.html