That looks reasonably elegant. I tried that, but I still get the error from comment 2. With the maliit-server.override approach I get a different crash:
File "/home/phablet/messaging-app/tests/autopilot/messaging_app/tests/test_messaging.py", line 102, in test_write_new_message
self.close_osk()
File "/home/phablet/messaging-app/tests/autopilot/messaging_app/tests/test_messaging.py", line 154, in close_osk
kb.dismiss()
File "/usr/lib/python2.7/dist-packages/ubuntu_keyboard/emulators/keyboard.py", line 170, in dismiss
self.keyboard.state.wait_for("HIDDEN")
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", line 234, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickItem.state failed: 'HIDDEN' != dbus.String(u'SHOWN', variant_level=1)
It's notable that for both approaches the application crashes the first time after running the test after restarting maliit, the second time it injects an additional "00" keyboard keys into the application, and only at the third time it actually starts functioning normally. That sounds like a bug in maliit itself, though.
> $ initctl set-env QT_LOAD_ TESTABILITY= 1 && start maliit-server
That looks reasonably elegant. I tried that, but I still get the error from comment 2. With the maliit- server. override approach I get a different crash:
File "/home/ phablet/ messaging- app/tests/ autopilot/ messaging_ app/tests/ test_messaging. py", line 102, in test_write_ new_message close_osk( ) phablet/ messaging- app/tests/ autopilot/ messaging_ app/tests/ test_messaging. py", line 154, in close_osk python2. 7/dist- packages/ ubuntu_ keyboard/ emulators/ keyboard. py", line 170, in dismiss keyboard. state.wait_ for("HIDDEN" ) python2. 7/dist- packages/ autopilot/ introspection/ dbus.py" , line 234, in wait_for u'SHOWN' , variant_level=1)
self.
File "/home/
kb.dismiss()
File "/usr/lib/
self.
File "/usr/lib/
failure_msg))
AssertionError: After 10.0 seconds test on QQuickItem.state failed: 'HIDDEN' != dbus.String(
It's notable that for both approaches the application crashes the first time after running the test after restarting maliit, the second time it injects an additional "00" keyboard keys into the application, and only at the third time it actually starts functioning normally. That sounds like a bug in maliit itself, though.