Autopilot for mobile devices planning

Registered by Martin Mrazik on 2013-02-28

What we need in autopilot (and all the flavors such as qt/gtk) to support testing on the mobile/convergent platforms.

Blueprint information

Status:
Started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Autopilot Hackers
Definition:
Approved
Series goal:
Accepted for raring
Implementation:
Started
Milestone target:
milestone icon ubuntu-13.04-month-5
Started by
Martin Mrazik on 2013-03-19

Related branches

Sprints

Whiteboard

Acceptance criteria:
The following exists after march:
 - list of features we need to support mobile and desktop (tagging form-factor specific test-cases; support new technologies such as QML properly, etc)

(?)

Work Items

Work items:
[mrazik] write best practices in the autopilot docs for how to write qml apps so they are easy to test with autopilot (e.g. objectnames for your objects): TODO
look into mir backend that might eventually replace surfaceflinger: TODO
[autopilot] make autopilot documentation better: DONE
[mzanetti] write some tests for signal monitoring in autopilot/autopilot-qt: TODO

Work items for ubuntu-13.04-month-5:
[autopilot] create backlog for autopilot features: DONE
[thomir-deactivatedaccount] input stack needs to be refactored (mixing high level gestures with low level touch events): DONE
[veebers] common interface for getting display configuration (resolution, DPI, ): INPROGRESS
[mzanetti] get data for memory consumption when adding objectNames into the qml code: DONE

Work items for ubuntu-13.04-month-6:
process management backend with nice interface (we need to be careful about backwards compatibility): TODO
[thomir-deactivatedaccount] certain autopilot tests are only relevant on certain form factors (?decorators): DONE