DBus Exception NoReply when running Telegram autopilot Logout test case on BQ Aquaris M10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
I am executing the following autopilot test case:
telegram.
On a BQ Aquaris M10 tablet and it fails with the Traceback below.
** NOTE: The testcase passes fine on a BQ Aquaris E4.5 device and the desktop.
Environment:
Desktop OS: Ubuntu 16.04
Branch: bzr branch lp:~cellsoftware/telegram-app/autopilotTest-3
M10 Tablet OS: Ubuntu 15.04 (OTA-13)
E4.5 phone OS: Ubuntu 15.04 (OTA-12)
Traceback (most recent call last):
File "/opt/click.
logout_
File "/usr/lib/
return self._select_
File "/usr/lib/
instances = self._select(
File "/usr/lib/
return self._execute_
File "/usr/lib/
getattr(self, '_id', None),
File "/usr/lib/
data = self.execute_
File "/usr/lib/
query.
File "/usr/lib/
return self._proxy_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
The problem lies when trying to interact with a Popup.Dialog with an object name set to 'logoutDialog'
My initial conviction was that you need to select the root object but it seems that you already are selecting on the root `app` instance. Can you please tell if the same bug is reproducible on desktop as well ? So that I can actually try to reproduce the issue ?