Merge lp:~mterry/unity8/robustify-testEdgeDemoOverlay into lp:unity8
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Albert Astals Cid | ||||
Approved revision: | 512 | ||||
Merged at revision: | 512 | ||||
Proposed branch: | lp:~mterry/unity8/robustify-testEdgeDemoOverlay | ||||
Merge into: | lp:unity8 | ||||
Diff against target: |
27 lines (+4/-2) 2 files modified
Components/EdgeDemoOverlay.qml (+2/-0) tests/qmltests/Components/tst_EdgeDemoOverlay.qml (+2/-2) |
||||
To merge this branch: | bzr merge lp:~mterry/unity8/robustify-testEdgeDemoOverlay | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Approve | |
Albert Astals Cid (community) | Approve | ||
Review via email:
|
Commit message
Make EdgeDemoOverlay test more reliable by testing for what we really care about, not an indirect indicator of it.
Description of the change
Make EdgeDemoOverlay test more reliable by testing for what we really care about, not an indirect indicator of it.
Turns out that tryCompare(obj, "prop", 1.0) will possibly return successfully at values like 0.999992, before other qml bindings on that property would consider it to be at value 1.0. So it's not wise to tryCompare on a value, expecting that a successful return will mean related qml bindings will have triggered at the same time.
The EdgeDemoOverlay qmltest was relying on just such an indirect test. Fixed to test what we really care about.
Robust++ :-)