Merge lp:~bfiller/dialer-app/fix-header-and-test into lp:dialer-app
Status: | Merged |
---|---|
Approved by: | Bill Filler |
Approved revision: | 91 |
Merged at revision: | 90 |
Proposed branch: | lp:~bfiller/dialer-app/fix-header-and-test |
Merge into: | lp:dialer-app |
Diff against target: |
31 lines (+7/-3) 2 files modified
src/qml/dialer-app.qml (+1/-1) tests/autopilot/dialer_app/tests/test_calls.py (+6/-2) |
To merge this branch: | bzr merge lp:~bfiller/dialer-app/fix-header-and-test |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Bill Filler (community) | Approve | ||
PS Jenkins bot | continuous-integration | Needs Fixing | |
Review via email: mp+203871@code.launchpad.net |
This proposal supersedes a proposal from 2014-01-29.
Commit message
o not pass the phone number as a parameter when pushing the live call view for an outgoing call. The correct value will be taken from the callManager. This fixes the problem of the header not updating when switching between multiple calls. Re-add try catch around autopilot test as the underlying mir/shell crash has not been fixed
Description of the change
Do not pass the phone number as a parameter when pushing the live call view for an outgoing call. The correct value will be taken from the callManager. This fixes the problem of the header not updating when switching between multiple calls. Re-add try catch around autopilot test as the underlying mir/shell crash has not been fixed
- Are there any related MPs required for this MP to build/function as expected? Please list.
no
- Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes)
yes
- Did you perform an exploratory manual test run of your code change and any related functionality on device or emulator?
yes
- Did you successfully run all tests found in your component's Test Plan (https:/ /wiki.ubuntu. com/Process/ Merges/ TestPlan/ dialer- app) on device or emulator?
yes
- If you changed the UI, was the change specified/approved by design?
not applicable - it is just a fix to a buggy behavior
- If you changed the packaging (debian), did you subscribe a core-dev to this MP?
not applicable - no packaging changes