Clients reading their surface position on screen
Thomi Richards
thomi.richards at canonical.com
Sun Aug 17 23:35:13 UTC 2014
On Fri, Aug 15, 2014 at 10:23 PM, Michał Sawicz <michal.sawicz at canonical.com
> wrote:
> Only reason I suggested the idea is that restarting unity8 would be a new
>> thing for all app tests, and maybe sending a dbus signal would be less
>> disruptive? But if Thomi things restarting is ok, then I'm happy.
>>
>
> We're already restarting unity with testability enabled before every test
> suite, to be able to reliably unlock the greeter (in automation that is, at
> home you need to unlock yourself :P).
Right, but that's handled outside the tests (i.e.- by CI infrastructure).
This would add a new requirement that unity8 *must* be restarted with
special options in *all* cases, any time you want to run an autopilot test.
I think that it's quite reasonable to get users to unlock the phone before
an AP test starts if the phone is on their desk, obviously CI needs a
different solution. I don't think it's reasonable to ask users to
_manually_ restart unity8 any time they want to run an AP test, so whatever
we do it should probably be automated.
I'm not sure what the best way to handle that is - you could propose a MP
to autopilot that does the restarting at the correct time, or you could
propose MPs to every test suite that we run on the phone.... there might be
some more options as well (am open to suggestions).
Personally, I think this is an absolutely crazy requirement, but that's
fine, since you'll be implementing the fix, and I'll send any fallout from
the decision to the mir team.
Cheers,
--
Thomi Richards
thomi.richards at canonical.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20140818/29aa9edd/attachment.html>
More information about the Mir-devel
mailing list