GTK3 doesn't play nicely with ldtp and so we need a better way to test it. There is a new at-spi2-core with a pyatspi2 set of python bindings.
Investigate what it will take to make this work on GTK3.
Determine which widgets in GTK3 do not work on ldtp
Try to get pyatspi2 to work on those widgets
Investigate if pyatspi2 can click a spoke selector for initial-setup
Once it is determined how pyatspi2 works, figure out a way to
Make it work with the original code (pyatspi)
Add an xmlrpc server to allow clojure code to call it
Benefits
Currently, some widgets in GTK3 either don't work, or don't work all the time with the old pyatspi bindings. There is therefore no way to test certain features of the GUI
Concerns
This is a lot of work and for what gain? Furthermore, the old pyatspi and pyatspi2 bindings are incompatible with each other. That would mean that we would effectively have to write something like ldtp but on top of the new pyatspi2 instead.
Rationale
GTK3 doesn't play nicely with ldtp and so we need a better way to test it. There is a new at-spi2-core with a pyatspi2 set of python bindings.
Investigate what it will take to make this work on GTK3.
Benefits
Currently, some widgets in GTK3 either don't work, or don't work all the time with the old pyatspi bindings. There is therefore no way to test certain features of the GUI
Concerns
This is a lot of work and for what gain? Furthermore, the old pyatspi and pyatspi2 bindings are incompatible with each other. That would mean that we would effectively have to write something like ldtp but on top of the new pyatspi2 instead.