Make it easier to select an introspection type.

[Thomi Richards]

Currently autopilot can auto-detect the introspection type to use when launching applications if the application is a dynamically linked binary. The current mechanism for overriding this is by overriding a method in AUtopilotTestCase. This is cumbersome because:

1) It applies to all the applications launched within that test.
2) It's a lot of typing

Ideally we need a keyword parameter to launch_test_application that allows the user to specify the application type - the default value should be 'Auto'. This means we can then consolodate the code in bin/autopilot and the code in autopilot/testcase.py. We should probably keep the old mechanism as well, in case the user wants to specify the introspection type once, for all applications launched.

Don't forget to update the documentation, including the porting guide!

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:autopilot at revision 172, scheduled for release in autopilot, milestone 1.3

[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".