ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #08825
Programmatically unlocking Unity for testing
Hello all,
with autopkgtest now being able to run click tests on the phone [1]
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.
- Relying on external additional dependencies introduces another
point of potential breakage.
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?
Thanks for any insights!
Martin
[1] http://www.piware.de/2014/07/deb-click-schroot-lxc-qemu-phone-cloud-one-autopkgtest-to-rule-them-all/
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Follow ups