Hi, some parts of your email were cut for the sake of brevity...
On Wed, Dec 10, 2014 at 9:04 PM, Steve Langasek < [email protected]> wrote: > > I think that provides most of the guidance we need. excellent... > The only thing I'm > still not sure about is the "fail gracefully" part. All of the interfaces > invoked by our tests are things that, under DEP8, would be declared as > dependencies of the tests (AIUI), and there's no interface for querying the > key bit that will make the test work (i.e., "is the recovery partition set > up to upgrade us, and does this device support rebooting into recovery > mode?"). So for the time being I don't think we can be very graceful. > This is where I think your situation is probably unique amongst people writing test suites. I still think we need some guidance from CI here - how should we write test suites that target the physical device like this? To my mind, the easiest thing to do is run these on the host machine (this could similarly be configured via a test class), and give the test suite a command to connect to it's allocated device. Thoughts? -- Thomi Richards [email protected]
-- 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
