Would it be wise to have DEP-8 tests that rely on real hardware being available? If it's fine then we could take that approach and I can write some tests in phablet-tools itself. But still, at least some of the issues we found were not caused by changes in phablet-tools, but for example by changes in adb, so I would primarily like to have a job running such tests on the image we produce. If this still isn't clear we could have a quick hangout to sort out the details.
On Tue, Sep 23, 2014 at 5:56 PM, Paul Larson <[email protected]> wrote: > Correct me if I'm wrong Brendan, but I think you're actually looking for > it to install the latest image on a phone, add a silo (ppa), and run > autopilot tests against that ppa correct? If that's the case, I don't think > we have the infrastructure to do this yet, but isn't there a way we can > hook tests in for phablet-tools as part of pre-merge testing? > > On Tue, Sep 23, 2014 at 6:20 AM, Evan Dandrea <[email protected]> > wrote: > >> Could this not be done as a DEP-8 test? What's preventing us from >> adding debian/tests to the phablet-tools package with code to do >> everything Brendan describes as part of proposed-migration. >> >> I realise this wouldn't catch the problem before it was committed, but >> we could work on getting this run as part of pre-merge testing as a >> second phase. >> > >
-- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
