I've asked Saviq for his experience but he also doesn't have recent experience now.
I seem to have a lot more failures on xenial but it might be real problems indicated. For now, I think this bug can be set as Incomplete, to be revisited when the phones can be investigated in more detail. It's very good to know that introspecting applications and interaction with them would seem to work on desktop with Qt 5.6. That means there's no huge problems at least to be expected, together with the fact that my UITK AP run on phone was okayish (maybe 75% pass). I'm attaching my unity8 autopilot log from Qt 5.5 (as opposed to using the Qt 5.6 PPA), which did have more trouble than UITK but I believe Unity 8 team will also look into that once phone can be tested. ** Attachment added: "unity8_autopilot_qt55.txt" https://bugs.launchpad.net/ubuntu/+source/autopilot-qt/+bug/1611733/+attachment/4721667/+files/unity8_autopilot_qt55.txt ** Changed in: autopilot-qt (Ubuntu) Importance: Critical => High ** Changed in: autopilot-qt (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1611733 Title: Autopilot does not fully work on xenial / Qt 5.5/ Mir Status in autopilot-qt package in Ubuntu: Incomplete Bug description: There is a problem with Autopilot and Qt 5.5 and newer on the phone (works somewhat better on desktop, maybe) that would need fixed if Autopilot is wanted to be continued to be used after the phone base switches from vivid to xenial. The introspection would probably need at least some changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-qt/+bug/1611733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
