Merge lp:~chris.gagnon/ubuntu-system-settings/barebones-autopilot-emulator-for-updates-page into lp:ubuntu-system-settings
Status: | Work in progress |
---|---|
Proposed branch: | lp:~chris.gagnon/ubuntu-system-settings/barebones-autopilot-emulator-for-updates-page |
Merge into: | lp:ubuntu-system-settings |
Diff against target: |
444 lines (+224/-73) 5 files modified
plugins/system-update/PageComponent.qml (+2/-0) tests/autopilot/ubuntu_system_settings/emulators.py (+155/-0) tests/autopilot/ubuntu_system_settings/tests/__init__.py (+61/-58) tests/autopilot/ubuntu_system_settings/tests/test_about.py (+0/-1) tests/autopilot/ubuntu_system_settings/tests/test_system_updates.py (+6/-14) |
To merge this branch: | bzr merge lp:~chris.gagnon/ubuntu-system-settings/barebones-autopilot-emulator-for-updates-page |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sebastien Bacher (community) | Needs Fixing | ||
PS Jenkins bot | continuous-integration | Approve | |
Review via email: mp+210036@code.launchpad.net |
Commit message
barebones emulator for system updates page, add objectNames that were needed for testing
Description of the change
I am trying to use the updates page in the system settings app to do upgrade testing for images that have not been released.
We use a custom proxy object/autopilot emulator in the autopilot tests so all projects can reuse the custom proxy objects.
This will be used to save time when there are changes made to the system-settings app, as we will not have also make changes to all the tests that might check or use something in system-settings with autopilot.
To test the changes there should be an in memory backend that changes the state of the updates page.
There should also be a mock update that does not reboot the phone.
Unmerged revisions
- 641. By Chris Gagnon
-
barebones start on emulator for system-settings
- 640. By Chris Gagnon
-
add objectNames, create emulator for system updates
PASSED: Continuous integration, rev:641 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- ci/685/ jenkins. qa.ubuntu. com/job/ generic- mediumtests- trusty/ 3763 jenkins. qa.ubuntu. com/job/ generic- mediumtests- trusty- touch/3351 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- trusty- amd64-ci/ 201 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- trusty- armhf-ci/ 189 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- trusty- i386-ci/ 188 jenkins. qa.ubuntu. com/job/ autopilot- testrunner- otto-trusty/ 3309 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- amd64/3771 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- amd64/3771/ artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- armhf/3353 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- trusty- armhf/3353/ artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ generic- mediumtests- runner- mako/5722 s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 4597
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/ubuntu- system- settings- ci/685/ rebuild
http://