991700 - [v1.3] Fix test_dialer_airplane_mode.TestDialerAirplaneMode on v1.3

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::UI Tests, defect)

Description

[[:AndreiH]]

Attachment: screen.png

Test test_dialer_airplane_mode.TestDialerAirplaneMode is failing when trying to make a call.
Tapping on call, but it's not actually dialing.
This is not reproducible manually.

Traceback (most recent call last):
  File "/var/jenkins/workspace/b2g.hamachi.mozilla-b2g28_v1_3.ui/.env/local/lib/python2.7/site-packages/marionette_client-0.7.1-py2.7.egg/marionette/marionette_test.py", line 143, in run
    testMethod()
  File "/var/jenkins/workspace/b2g.hamachi.mozilla-b2g28_v1_3.ui/tests/python/gaia-ui-tests/gaiatest/tests/functional/dialer/test_dialer_airplane_mode.py", line 31, in test_dialer_airplane_mode
    phone.wait_for_confirmation_dialog()
  File "/var/jenkins/workspace/b2g.hamachi.mozilla-b2g28_v1_3.ui/tests/python/gaia-ui-tests/gaiatest/apps/phone/app.py", line 51, in wait_for_confirmation_dialog
    self.wait_for_element_displayed(*self._dialog_locator)
  File "/var/jenkins/workspace/b2g.hamachi.mozilla-b2g28_v1_3.ui/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 71, in wait_for_element_displayed
    raise TimeoutException('Element %s present but not displayed before timeout' % locator)
TimeoutException: Element confirmation-message present but not displayed before timeout

Comment 1

[[:AndreiH]]

this should be an easy fix in our automated test

Comment 2

[Viorela Ioia [:viorela]]

This test still fails in the latest build. 
Device: Hamachi
Gaia      0a7a50129995f080c1df4d807a2334701701e8ed
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/e3fca8c23e1d
BuildID   20140408004002
Version   28.0
ro.build.version.incremental=eng.tclxa.20131223.163538
ro.build.date=Mon Dec 23 16:36:04 CST 2013

I ran the test several times locally and it failed intermittently. The test fails when trying to tap the Call button. I tapped the button manually afterwards and it didn't work. I attached a logcat of the issue and also a video that shows how the Call button behaves after the test fails. I was not able to reproduce this failure manually entirely. 
Bob, can you, please, take a look at this?

Comment 3

[Viorela Ioia [:viorela]]

Attachment: logcat

Comment 4

[Viorela Ioia [:viorela]]

Attachment: video.3gp

Comment 5

[Viorela Ioia [:viorela]]

I'll still investigate this.

Comment 6

[Robert Chira [:RobertC]]

This issue is still reproduced in latest v1.3 build:
Gaia      03340f9b00343512066ab0dceca1641ef9a5374c
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/0b0822ffdbf8
BuildID   20140415004003
Version   28.0
ro.build.version.incremental=eng.tclxa.20131223.163538
ro.build.date=Mon Dec 23 16:36:04 CST 2013

I cannot replicate the issue manually and it fails in approximately 10% of the runns on my local device.

I looked in the page source at the call button element when the test failed and couldn't see anything different from the usual behaviour.

Possible steps to reproduce (steps from the automated test):
1. go to settings and enable airplane mode
2. open phone app
3. type phone number
4. tap call button

Expected result:
A warning message should be displayed

Actual result:
No message is displayed and the call button is unresponsive, manually tapping the call button after the test fails still doesn't work.

Comment 7

[Jason Smith [:jsmith]]

From what I can tell, the manual testing analysis already happened here, so no need to flag qawanted here.

Comment 8

[Zac C (:zac)]

Automation on v1.3 is over.