Merge lp:~azzar1/unity/fix-979686 into lp:unity
Proposed by
Andrea Azzarone
Status: | Merged |
---|---|
Approved by: | Andrea Azzarone |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2412 |
Proposed branch: | lp:~azzar1/unity/fix-979686 |
Merge into: | lp:unity |
Diff against target: |
104 lines (+37/-7) 3 files modified
dash/PlacesGroup.cpp (+10/-7) tests/autopilot/unity/emulators/dash.py (+4/-0) tests/autopilot/unity/tests/test_dash.py (+23/-0) |
To merge this branch: | bzr merge lp:~azzar1/unity/fix-979686 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Thomi Richards (community) | Approve | ||
Review via email: mp+109075@code.launchpad.net |
Commit message
Fix inconsistent hover/highlight
Description of the change
== Problem ==
Dash: Inconsistent hover/highlight
== Fix ==
Expand the HeaderView.
== Test ==
AP test added. The test doesn't work for me because self.dash.
To post a comment you must log in.
Hi,
The test works and passes for me on my machine. However, i'd appreciate it if you could change your test a little bit:
First, please replace "should" in your docstring to "must". eaderTests, self).setUp() reveal_ file_lens( ) get_current_ lens()
56 + def setUp(self):
57 + super(CategoryH
58 + self.dash.
59 + self.lens = self.dash.
These lines of code don't belong in setUp(). They're not setting up the test environment for the test - they're part of the test execution. I'd be happy if you wanted to change the reveal_foo_lens methods to return the revealed lens, so this is one line instead of two. I'd also be happy if you wanted to put these lines of code into a separate method and call it from the start of your test.
Also, if this test fails, you will be leaving the dash open. Can you please add a :
self.addCleanup (self.dash. ensure_ hidden) right after you reveal the application lens please? If your test passes, this is a no-op, so it's quite safe.
Finally, is there a way we can make this test leave the lens in the same state as it found it? Can we un-expand the category header as well? Maybe add a second assert, so we know that clicking in that spot will bot expand and collapse the category header? What do you think?
Cheers,