ubuntu-phone team mailing list archive

[Iain Lane <laney@xxxxxxxxxx>]

Hi,

There's something up with the autopilot tests for
ubuntu-system-settings.

There's a set of fairly basic tests which check for the presence of
various objects on the main screen. Those work. But any tests which
involve clicking on any component—for example to go into a screen or to
type in the search box—don't work.

All of the tests pass on desktop.

The output is below. Install ubuntu-system-settings-autpilot on the
device and run that command.

Anyone got any clues?

phablet@ubuntu-phablet:~$ autopilot run ubuntu_system_settings.tests.test_search.SearchTestCases.test_search
Loading tests from: /usr/lib/python2.7/dist-packages

Tests running...
======================================================================
FAIL: ubuntu_system_settings.tests.test_search.SearchTestCases.test_search
----------------------------------------------------------------------
Traceback (most recent call last):
_StringException: Empty attachments:
  process-stdout

process-return-code: {{{-15}}}
[ … ]

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/ubuntu_system_settings/tests/test_search.py", line 44, in test_search
    self.assertThat(background, Equals(None))
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 412, in assertThat
    raise MismatchError(matchee, matcher, mismatch, verbose)
MismatchError: None != <autopilot.introspection.dbus.EntryComponent object at 0x1767b30>


Ran 1 test in 6.019s
FAILED (failures=1)

-- 
Iain Lane                                  [ iain@xxxxxxxxxxxxxxxxxxx ]
Debian Developer                                   [ laney@xxxxxxxxxx ]
Ubuntu Developer                                   [ laney@xxxxxxxxxx ]

Attachment: signature.asc
Description: Digital signature