split tests into headless and "all"

[Martin Mrazik]

I was talking with didrocks this morning about autopilot packaging and we would like to enable the tests during the distro build. The tests however need to be headless so we need to have two (easy) ways how to run:
1. headless tests
2. tests that require X
3. 1+2

The relevant IRC conversation:
<didrocks> oh? where is it (and can it run in headless mode?)
<mmrazik> I was talking with him about this as well
<didrocks> ah found, autopilot/tests/
<mmrazik> I was told some of the tests require X
<mmrazik> but I/thomi can probably disable that
<mmrazik> let me find the command thomi is using for running them
<didrocks> mmrazik: hum, ok, not required now, but would be nice to have a headless build and tests in the future
<didrocks> mmrazik: so that we can activate them on build
<didrocks> then, another target with both

[Thomi Richards (thomir-deactivatedaccount)]

I'm taking a different approach here - and splitting the tests into unit tests, which can be run thusly:

autopilot run autopilot.tests.unit

and functional tests, which can be run thusly:

autopilot run autopilot.tests.functional

This is a better classification than "headless", since we cannot run tests that have any external dependencies not in the Build-Requires field.

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:autopilot at revision 196, scheduled for release in autopilot, milestone 1.3.1

[Launchpad Janitor (janitor)]

This bug was fixed in the package autopilot - 1.3daily13.06.05-0ubuntu2

---------------
autopilot (1.3daily13.06.05-0ubuntu2) saucy; urgency=low

  * autopilot-touch only suggests python-ubuntu-platform-api for now.
    It's not in distro and we need that requirement to be fulfilled to
    have unity 7, 100 scopes and the touch stack to distro.
 -- Didier Roche <email address hidden> Fri, 07 Jun 2013 13:33:46 +0200

[Rolf Leggewie (r0lf)]

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".