Use upstart/upstart-app-launch to launch and monitor application under test

This bug is currently causing failures in the gallery-app tests in the touch_custom suite (as the environment is not being properly setup)

This is currently waiting on gir bindings to the upstart app launch libary.
Tedg is building these for us.

On Tue, Jan 7, 2014 at 12:23 PM, Thomi Richards
<email address hidden>wrote:

> ** Changed in: autopilot
> Assignee: (unassigned) => Thomi Richards (thomir)
>
> ** Changed in: autopilot
> Status: Confirmed => In Progress
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1263182
>
> Title:
> Use upstart/upstart-app-launch to launch and monitor application under
> test
>
> Status in Autopilot:
> In Progress
> Status in The Sevilerow project:
> Confirmed
>
> Bug description:
> On the phone and tablet, all apps are launched and managed by the
> upstart-app-launch utility, which is based on upstart.
>
> This utility ensures that each application has a correct environment
> to run in, configures application confinement and communicates the
> launch to shell so shell knows not to reject a rogue application.
> Since users are using this to launch apps, I think autopilot should do
> so too.
>
> Instead the hacky solution autopilot is relying on is the
> --desktop_file_hint parameter, which is error prone:
> https://bugs.launchpad.net/unity-mir/+bug/1262982
> and I have a goal to remove support for that parameter entirely.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/autopilot/+bug/1263182/+subscriptions
>

--
Thomi Richards
<email address hidden>

I think this released branch takes care of this:
https://code.launchpad.net/~thomir/autopilot/trunk-upstart-support
but maybe Thomi can confirm that.

mark won't fix in Savilerow since it's been fixed in Autopilot.