Merge lp:~canonical-platform-qa/ubuntu-system-settings/main_window_objectName into lp:ubuntu-system-settings
| Status: | Merged |
|---|---|
| Approved by: | Ken VanDine on 2015-02-23 |
| Approved revision: | 1322 |
| Merged at revision: | 1333 |
| Proposed branch: | lp:~canonical-platform-qa/ubuntu-system-settings/main_window_objectName |
| Merge into: | lp:ubuntu-system-settings |
| Diff against target: |
238 lines (+78/-69) 3 files modified
src/qml/MainWindow.qml (+2/-2) tests/autopilot/ubuntu_system_settings/__init__.py (+25/-55) tests/autopilot/ubuntu_system_settings/tests/__init__.py (+51/-12) |
| To merge this branch: | bzr merge lp:~canonical-platform-qa/ubuntu-system-settings/main_window_objectName |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Jonas G. Drange (community) | Approve on 2015-02-23 | ||
| PS Jenkins bot | continuous-integration | Approve on 2015-02-20 | |
| Sebastien Bacher (community) | 2015-02-19 | Needs Information on 2015-02-19 | |
| Brendan Donegan (community) | Approve on 2015-02-19 | ||
|
Review via email:
|
|||
Commit Message
On the autopilot tests, select the main window by object name.
Added a proxy object for the application.
Cleaned up the launching methods.
Description of the Change
In order to test the integration between system settings and other applications, we need to assign a unique name to the MainWindow.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1318
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Brendan Donegan (brendan-donegan) wrote : | # |
LGTM but obviously the jenkins issues need to be fixed before merging
| Sebastien Bacher (seb128) wrote : | # |
That changeset seems to do more than changing the name of the mainview object, can you update the description/commit message to give some details?b
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1319
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1320
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1320
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1321
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:1322
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Leo Arias (elopio) wrote : | # |
I finally found my mistake that was causing errors in jenkins.
I added more info to the commit message, and this is ready for a new review.
| Jonas G. Drange (jonas-drange) wrote : | # |
Tests run fine on unity7 and 8, changes look good. If you have time you could maybe roughly explain ubuntuuitoolkit
WFM
| Leo Arias (elopio) wrote : | # |
> If you have time you could
> maybe roughly explain ubuntuuitoolkit
When autopilot returns a qml element with select single, what it returns is a default proxy object. What this default proxy does is to make it easier the access to qml properties and adds some handy things like waits and methods to inspect the element and its children.
We can extend the default proxy object with a custom proxy object. We link a custom proxy object to a specific QML component, so we can put in that object methods that will make it easier to write tests using that component. For example, a custom proxy object for a check box will have a method "check" and a method "uncheck" that will take care of moving the pointer to the right point and do the click.
We defined a class ubuntuuitoolkit
In here, we are using the toolkit base for the application proxy. The application has some properties that no other QML component has, so at some point we will probably make a specific base class for applications. For now, this one is good for everything.


FAILED: Continuous integration, rev:1317 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- ci/1984/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 1434 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- vivid-i386- ci/254 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 1271 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 1432 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 1432/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 18189
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/ubuntu- system- settings- ci/1984/ rebuild
http://