Merge lp:~canonical-platform-qa/unity8/edges_demo_test into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Albert Astals Cid on 2015-01-07 |
| Approved revision: | 1517 |
| Merged at revision: | 1545 |
| Proposed branch: | lp:~canonical-platform-qa/unity8/edges_demo_test |
| Merge into: | lp:unity8 |
| Diff against target: |
254 lines (+230/-0) 3 files modified
tests/autopilot/unity8/shell/emulators/edges_demo.py (+140/-0) tests/autopilot/unity8/shell/fixture_setup.py (+38/-0) tests/autopilot/unity8/shell/tests/test_edges_demo.py (+52/-0) |
| To merge this branch: | bzr merge lp:~canonical-platform-qa/unity8/edges_demo_test |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Approve on 2015-01-07 | |
| Albert Astals Cid (community) | 2014-12-16 | Approve on 2015-01-07 | |
|
Review via email:
|
|||
Commit Message
Added an autopilot test for the edges demo.
Description of the Change
We want to automate most of the sanity testing process, and this test is one of the easy ones that can be removed from the manual execution if we have a good high level test to confirm the demo works.
* Are there any related MPs required for this MP to build/function as expected? Please list.
There are no related MPs.
* Did you perform an exploratory manual test run of your code change and any related functionality?
Sort of. I ran the tests many times, in the device and desktop, with different starting conditions.
* Did you make sure that your branch does not contain spurious tags?
I did.
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
No packaging changes.
* If you changed the UI, has there been a design review?
No UI changes.
| Albert Astals Cid (aacid) wrote : | # |
Seems the test failed can you have a look? (Only at yours, i'll check the other ones)
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1515
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1516
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Leo Arias (elopio) wrote : | # |
Thanks for looking at it Albert. I was missing a import that loads the autopilot cache. Now the test passed.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:1516
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1517
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
No, it's only a test improvement. I checked the test succeeds
* Did CI run pass?
No, fails in an unrelated test and since this only adds a different test can't be the cause
* Did you make sure that the branch does not contain spurious tags?
Yes
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1517
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: 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:1517
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

FAILED: Continuous integration, rev:1515 /code.launchpad .net/~canonical -platform- qa/unity8/ edges_demo_ test/+merge/ 244889/ +edit-commit- message
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http:// jenkins. qa.ubuntu. com/job/ unity8- ci/5053/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 594 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- vivid/217 jenkins. qa.ubuntu. com/job/ unity8- vivid-amd64- ci/218 jenkins. qa.ubuntu. com/job/ unity8- vivid-i386- ci/218 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 511 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 592 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 592/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 16616
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/5053/ rebuild
http://