ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #08829
Re: Programmatically unlocking Unity for testing
On miércoles 2 de julio de 2014 04h'44:59 ART, Martin Pitt wrote:
Hello all,
with autopkgtest now being able to run click tests on the phone [1]
Thanks for doing this :-)
I'd like to fine-tune the ADB setup script to require less manual
action.
One outstanding issue is to unlock Unity before starting a test. I
know the unity8-autopilot package ships a
/usr/share/unity8/unlock-device script; the setup script could
certainly download/unpack that package and run the script, but that's
ugly in several ways:
- The script reboots the phone; surely there is a way to unlock Unity
without having to do that? This adds a whole minute to
each test run, and also destroys any other runtime setup that might
have been done before.
I bet you just need to restart unity (for introspection) and not the whole
device and you can probably get away with that if you boot with the
testability flag on for the whole session (and if you decide to proceed on
this course of action, I would also add it as a flashing option for
devices).
Currently the status quo is to flag stuff in /userdata/.[action] and have
an upstart job that checks on it and does the right thing.
- Relying on external additional dependencies introduces another
point of potential breakage.
+1, there have been three attempts to get this into phablet-tools without
success to remove this dependency.
Isn't there something easier which doesn't require all that, like
changing a configuration value and simply restarting unity itself, or
sending Unity a D-BUS call?
I proposed this once and was told it could be a security issue. Now that
split greeter isn't landing; not sure it's that much of a problem.
References