I believe the most immediate answer to "How should a test author declare that a particular test suite should only be run on a real phone?" is to take the approach that was discussed in Malta [1], and make user of the 'Classes' field [2]. Martin, please correct me if I'm wrong, but I believe 'Classes' replaced what was originally discussed as tags in that document.
Martin, Jean-Baptiste, Vincent, For this to work, the current britney service for proposed-migration will need to interpret this field and act accordingly. Does britney do this now? I'm looking to Martin to help define what these classes should be. For example, should we start with just 'phone' as that appears to the testbed for which these tests are being developed (this is my assumption)? But as Martin mentioned, we don't want to just encode specific platform information in the dep8 control file. From our current testing needs, 'phone' and 'desktop' are the two classes that first come to mind. [1] - https://docs.google.com/a/canonical.com/document/d/1igg8h3CpGshATwWd9nnLMiy_w5fEkvN0DqeDAIfGeQc/edit#heading=h.7sq2knmz5u2y [2] - http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.package-tests.rst;hb=HEAD Francis On Mon, Dec 8, 2014 at 12:08 PM, Julien Funk <[email protected]> wrote: > This is urgent and I hope to have a response today since a lot of > automation is blocked pending an answer. > > ~J > > On Sun, Dec 7, 2014 at 2:19 PM, Thomi Richards < > [email protected]> wrote: > >> Hi CI, >> >> >> We're starting to hit cases where a particular dep8 test suite can really >> only be run on an actual phone. We're encouraging development teams to >> express their tests in dep8, but we need some guidance from CI on how to >> declare hardware-type restrictions. >> >> How should a test author declare that a particular test suite should only >> be run on a real phone? >> >> My understanding is that all dep8 tests are run for packages uploaded to >> debian & ubuntu. I think it's reasonable to provide test authors with a way >> to not introduce broken tests.. >> >> >> Cheers, >> >> -- >> 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 > > -- Francis Ginther Canonical - Ubuntu Engineering - Continuous Integration Team
-- 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
