touch-packages team mailing list archive

[Leo Arias <leo.arias@xxxxxxxxxxxxx>]

I agree with zombie that unit tests are needed. Ideally, you would find
a nice way to fake the OSK and trigger the events it is supposed to
trigger.

About the autopilot tests, I think we have everything we need now. We
need to extend get_keyboard with:

if model == touch:
    if maliit is not running with testability:
       restart malit with testability
    return ubuntu_keyboard.emulators.keyboard.Keyboard()
else:
    return input.Keyboard.create()

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1428114

Title:
  Need OSK input device on phones

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428114/+subscriptions