Some autopilot test rely on the list index position of a returned 'select_many'

[Christopher Lee]

The returned list of a select_many in autopilot 1.4 has no guaranteed order of position for objects returned by select_many.

Some tests/helper methods rely on this (i.e. self.select_many("example")[1]) and expect it to return the intended object.

[Olivier Tilloy (osomon)]

The autopilot documentation for select_many (http://unity.ubuntu.com/autopilot/api/introspection.html#autopilot.introspection.dbus.DBusIntrospectionObject.select_many) doesn’t mention that the order is not guaranteed. Could that be a bug in autopilot itself, or does the documentation need updating?

[Christopher Lee (veebers)]

Hi Olivier

The autopilot documentation needs to be updated, so it's a bug in that sense :-)
I'll file a bug against autopilot for the documentation and follow it up.

[Olivier Tilloy (osomon)]

@Chris, I already filed bug #1248267 to track the issue in the documentation.

[Pat McGowan (pat-mcgowan)]

What is needed within the gallery-app project?

[Olivier Tilloy (osomon)]

In gallery-app, we need to go through all the calls to select_many(…) in the autopilot tests, and for the tests that assume a given order, fix them. One example of such an unreliable test is:

    def first_media_in_grid_view(self):
        grid_view = self.grid_view()
        return grid_view.select_many("OrganicItemInteraction")[0]