Merge lp:~canonical-platform-qa/ubuntu-keyboard/fix_base_class into lp:ubuntu-keyboard
Status: | Merged |
---|---|
Approved by: | Michael Sheldon |
Approved revision: | 360 |
Merged at revision: | 365 |
Proposed branch: | lp:~canonical-platform-qa/ubuntu-keyboard/fix_base_class |
Merge into: | lp:ubuntu-keyboard |
Diff against target: |
129 lines (+15/-19) 4 files modified
tests/autopilot/ubuntu_keyboard/emulators/__init__.py (+1/-7) tests/autopilot/ubuntu_keyboard/emulators/key.py (+5/-5) tests/autopilot/ubuntu_keyboard/emulators/keyboard.py (+3/-3) tests/autopilot/ubuntu_keyboard/emulators/keypad.py (+6/-4) |
To merge this branch: | bzr merge lp:~canonical-platform-qa/ubuntu-keyboard/fix_base_class |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michael Sheldon (community) | Approve | ||
PS Jenkins bot | continuous-integration | Needs Fixing | |
Review via email: mp+257644@code.launchpad.net |
Commit message
Use the base class from the toolkit in autopilot tests.
Description of the change
Autopilot is currently designed to have a single proxy object base, so we started finding some problems when we integrated tests from multiple projects for the sanity suite. We are working on making autopilot smarter, but in order to be able to change the design without breaking any tests we need this change.
And in this case, it makes sense to use the proxy object from the toolkit, because the one defined for this project was empty.
Are there any related MPs required for this MP to build/function as expected? Please list.
No MPs required.
Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes)
It is.
Did you perform an exploratory manual test run of your code change and any related functionality on device or emulator?
Just made sure that the tests are still passing.
Did you successfully run all tests found in your component's Test Plan (https:/
Only changes to automated tests, so no need to run the test plan.
If you changed the UI, was the change specified/approved by design?
No UI changes.
If you changed UI labels, did you update the pot file?
No UI changes.
If you changed the packaging (debian), did you add a core-dev as a reviewer to this MP?
No packaging changes.
FAILED: Continuous integration, rev:359 jenkins. qa.ubuntu. com/job/ ubuntu- keyboard- ci/587/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 2497 jenkins. qa.ubuntu. com/job/ ubuntu- keyboard- vivid-amd64- ci/88 jenkins. qa.ubuntu. com/job/ ubuntu- keyboard- vivid-armhf- ci/88 jenkins. qa.ubuntu. com/job/ ubuntu- keyboard- vivid-armhf- ci/88/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ ubuntu- keyboard- vivid-i386- ci/88 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 2165 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 2495 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 2495/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 19984
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/ubuntu- keyboard- ci/587/ rebuild
http://