While I think you already got an answer to your immediate question, I think that this sounds interesting and perhaps something that could be integrated with the application startup testing that QA is setting up. Would be nice to have a screenshot there, and perhaps invalidate results based on it.
Ted On Sat, 2014-06-07 at 11:40 +0100, Alan Pope wrote: > In short, what's the replacement for programmatically terminating > click package based applications? > > Some months back I used upstart-app-stop, but that no longer works. I > tried "stop <app_id>" but that also doesn't work. Is the process for > programmatically stopping apps documented. > > The context is that I have a script on my pc which starts every app on > the device one by one. It waits a few seconds then takes a screenshot. > It analyses the picture to see if the app actually started (is the > screen all black or all white - which are often indicators the app > failed to start) and logs the results. > > Now previously I used to use upstart-app-stop to kill off each app > after taking the screenshot, before moving on to the next one. So I > need to know what is the new way to stop apps for this script to > function. > > As an aside, of course I could just start each app in turn and leave > it running, and let our application lifecycle reap the old ones - I > guess it would be a good test of that :) > > Cheers, > -- > Alan Pope > Engineering Manager > > Canonical - Product Strategy > +44 (0) 7973 620 164 > alan.p...@canonical.com > http://ubuntu.com/ >
signature.asc
Description: This is a digitally signed message part
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
