Currently although it may look as though we have an OSK in Autopilot tests running on phones, keyboard input emits synthetic events. This makes testing of particular behavior involving pre-edit text impossible to test. We don't have unit tests for this either because maliit is very hard to spawn, so we essentially never run any of the tests for it.
def get_keyboard():
"""Return the keyboard device."""
# TODO return the OSK if we are on the phone. --elopio - 2014-01-13
return input.Keyboard.create()
As per my understanding we should have an input device that talks to maliit using introspection (accessibility?), which is the way tests run in ubuntu-keyboard, but those aren't right now re-usable by other projects.
Currently although it may look as though we have an OSK in Autopilot tests running on phones, keyboard input emits synthetic events. This makes testing of particular behavior involving pre-edit text impossible to test. We don't have unit tests for this either because maliit is very hard to spawn, so we essentially never run any of the tests for it.
def get_keyboard(): create( )
"""Return the keyboard device."""
# TODO return the OSK if we are on the phone. --elopio - 2014-01-13
return input.Keyboard.
As per my understanding we should have an input device that talks to maliit using introspection (accessibility?), which is the way tests run in ubuntu-keyboard, but those aren't right now re-usable by other projects.