Phablet Tools

Merge lp://qastaging/~sergiusens/phablet-tools/emu_prov into lp://qastaging/phablet-tools

emu_prov
Merge into trunk

Proposed by Sergio Schvezov on 2014-02-20

Status:	Needs review
Proposed branch:	lp://qastaging/~sergiusens/phablet-tools/emu_prov
Merge into:	lp://qastaging/phablet-tools
Prerequisite:	lp://qastaging/~doanac/phablet-tools/autopilot-args
Diff against target:	80 lines (+27/-4) 3 files modified click-buddy (+1/-0) phablet-click-test-setup (+15/-2) phablet-config (+11/-2)
To merge this branch:	bzr merge lp://qastaging/~sergiusens/phablet-tools/emu_prov
Related bugs:	Link a bug report

Reviewer	Review Type	Date Requested	Status
Nicholas Skaggs (community)		2014-02-20	Needs Fixing on 2014-03-07
PS Jenkins bot	continuous-integration		Approve on 2014-02-20
Andy Doan		2014-02-20	Pending
Ubuntu Phablet Team		2014-02-20	Pending
Review via email: mp+207440@code.qastaging.launchpad.net

Commit message

Adding emulator (and future ap) provisioning; in the future this would only work if the tests are py3.

Description of the change

Tested from the branch like
PATH=$PWD:$PATH click-buddy --dir ~/source/apps/clock/trunk --provision
PATH=$PWD:$PATH phablet-test-run -o $(mktemp -d) -f xml ubuntu_clock_app

Revision history for this message

PS Jenkins bot (ps-jenkins) wrote on 2014-02-20:

PASSED: Continuous integration, rev:244
http://jenkins.qa.ubuntu.com/job/phablet-tools-ci/279/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/phablet-tools-trusty-amd64-ci/51
    SUCCESS: http://jenkins.qa.ubuntu.com/job/phablet-tools-trusty-armhf-ci/51
    SUCCESS: http://jenkins.qa.ubuntu.com/job/phablet-tools-trusty-i386-ci/51

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/phablet-tools-ci/279/rebuild

review: Approve (continuous-integration)

Revision history for this message

Nicholas Skaggs (nskaggs) wrote on 2014-03-07:

Works fine, but I would like to see a one option added to click-buddy:

1) Support to skip the phablet-config autopilot --setup step; in the case where we already have pulled things, we don't need to do it again. Heck, I'm not even sure the step should be on by default. The first time you run tests from your project it's needed, but after you don't need it. I suppose having it default means it will do the right thing for new folks, but I'd like to be able to skip it at least.. Just makes me want to adb push even more if it takes too long . . .

In addition;

2) Potentially provision and push tests only; don't push the click package. I might want to test using the pre-installed click, but with my newer tests. This is really a corner case, and not important or critical. I wouldn't hold up this merge for it :-)

review: Needs Fixing