Merge lp://staging/~brendan-donegan/ubuntu-power-tests/tc-powermeter-07 into lp://staging/ubuntu-power-tests

PASSED: Continuous integration, rev:10
http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-ci/12/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-amd64-ci/12
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-armhf-ci/12
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-i386-ci/12

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-power-tests-ci/12/rebuild

I think I may not have captured it well in the card, but the intent of this test is for wifi to be on but unassociated to any network. We'll need functionality to disassociate the network for the test, then reassociate it as part of the preparation. I'll see if I can get that working.

So I started working on a branch for tc-powermeter-06 that included changes to the path for the prepare script. My combined 06/07 branch is here:
lp:~nuclearbob/ubuntu-power-tests/flight-mode-test-with-adt-command
That will run both tests, but the tc-powermeter-07 script as written doesn't do what we actually want; it should unassociate wifi, and the prepare-device script should make an attempt to reassociate it. I'm not sure if it makes more sense to just run phablet-network separately (that's probably easier than doing it on the device.) Chris is going to look at it, and I'll be checking over it before I EOD.

Max, I don't know if this is what you're looking for, but there is a helper used in the sanity wizard test to remove existing wi-fi connections before the test and restore them after:

http://bazaar.launchpad.net/~canonical-platform-qa/ubuntu-sanity-tests/trunk/view/head:/ubuntu_sanity_tests/helpers/testbed.py#L53

It sounds like the implementation would need to be split between the test which removes the connection and prepare-device script which restores it. Could be of use though.

You can always expect me to find a bug in anything

PASSED: Continuous integration, rev:13
http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-ci/15/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-amd64-ci/15
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-armhf-ci/15
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-power-tests-vivid-i386-ci/15

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-power-tests-ci/15/rebuild

What we'll actually need for this is for the test to disassociate wifi and for the preparation script to reassociate it. As such, I'm not sure of the best way to pass the network in question to the preparation script, since that will be running after a reboot, and will need to be able to run when this test hasn't run. Maybe as part of the provisioning process, we write the network name to a file, and the preparation script can read it from there?

Are you sure? Isn't it fine as long as the test leaves the system in the same state it was in prior to the test?

I've created a new branch (dependent on this one) which will remove existing networks in tc-powermeter-07, and restore them in prepare-device. See here:

https://code.launchpad.net/~canonical-platform-qa/ubuntu-power-tests/backup-restore-network/+merge/259099

I think this addresses the problem. It would just assume that a network is already setup on the device, and the saved network details would persist after reboot, so they can be easily restored.

Let me know what you think.