Touch hardware validation framework

Registered by Sergio Schvezov on 2013-11-06

Discuss framework to validate new devices

Blueprint information

Status:
Not started
Approver:
Michael Frey
Priority:
Undefined
Drafter:
Sergio Schvezov
Direction:
Needs approval
Assignee:
Sergio Schvezov
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Opens to close
=========

Should we integrate with plainbox?
If integrating with plainbox, how do we integrate with the framework and still allow porters to run just the hw validation part?
How do we deliver the framework to the target devices? i.e.; click
Should we run with a host connected or completely isolated? Host connected would be interesting for porting/dev phase;
If integrating with plainbox, what's the ETA and do we need to create an interim small runner?

Should we think of extending to device testing in the future? Contrary to just hardware validation.

PlainBox links
========

Docs: http://plainbox.readthedocs.org/en/latest/index.html
Code: lp:checkbox
IRC: #checkbox

Meeting notes
=========

Tests:
 * In general, all tests should be automated, but we may need some manual tests
  * CTS is fully automated, run from the host

Packaging
 * 1 click package with everything, or several click packages

Docs:
 * http://plainbox.readthedocs.org/en/latest/index.html
Code:
* code.launchpad.net/checkbox
 Work items
[ara] provide docs to write new providers
[zyga] provide example on how to create provider
[sergiusens] work with zyga to create a click package out of this
[sergiusens] write test plan to divide and conquer on tests
[sergiusens] define minimal requirements for running the tests
[sergiusens] write in better recover tools to do better forensics when porting.
[sergiusens] write about apparmor enablement tests
[zyga] provide information on how to use resources.
[sergiusens] write documentation on how to contribute
[sergiusens] create jenkins job that builds click 'CTS'
[zyga] list tests we can reuse

(?)

Work Items

Work items:
[zyga] Provide documentation links for plainbox: DONE
[zyga] Show how the 'plainbox startprovider' works and how to use it: DONE
XUnit exporter format implementation for plainbox: TODO
[ara] provide docs to write new providers: TODO
[zyga] provide example on how to create provider: DONE
[sergiusens] work with zyga to create a click package out of this: TODO
[zyga] list tests we can reuse: TODO
[sergiusens] identify lp account for zyga and assign work-items appropriatly: DONE
[sergiusens] write in better recover tools to do better forensics when porting: TODO
[sergiusens] write about apparmor enablement tests: TODO
[zyga] provide information on how to use resources: TODO
[sergiusens] write documentation on how to contribute: TODO

Work items for ubuntu-13.12:
[sergiusens] write egl tests: INPROGRESS

Work items for ubuntu-14.01:
[sergiusens] create jenkins job that builds click 'CTS': INPROGRESS
[sergiusens] write test plan and iterate on test plan with stakeholders: TODO
[sergiusens] divide and conquer on tests: create follow up workitems/blueprints with clear owners that plans out the individual test development/integration tasks: TODO
[sergiusens] define minimal requirements for running the tests: TODO