1026403 - [Flame[v2.1] test_setup_and_send_active_sync_email is intermittently failing

Status: RESOLVED FIXED

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

Description

[[:AndreiH]]

Attachment: download.png

The last fail occurred in:

http://selenium.qa.mtv2.mozilla.com:8080/view/B2G%20Flame/job/b2g.flame.mozilla-central.ui.smoketest/73/HTML_Report/

Traceback (most recent call last):
  File "/var/jenkins/workspace/b2g.flame.mozilla-central.ui.smoketest/.env/local/lib/python2.7/site-packages/marionette_client-0.7.9-py2.7.egg/marionette/marionette_test.py", line 170, in run
    testMethod()
  File "/var/jenkins/workspace/b2g.flame.mozilla-central.ui.smoketest/tests/python/gaia-ui-tests/gaiatest/tests/functional/email/test_setup_and_send_active_sync_email.py", line 30, in test_setup_and_send_active_sync_email
    self.email.setup_active_sync_email(self.account)
  File "/var/jenkins/workspace/b2g.flame.mozilla-central.ui.smoketest/tests/python/gaia-ui-tests/gaiatest/apps/email/app.py", line 78, in setup_active_sync_email
    setup.check_for_emails_interval('20000')
  File "/var/jenkins/workspace/b2g.flame.mozilla-central.ui.smoketest/tests/python/gaia-ui-tests/gaiatest/apps/email/regions/setup.py", line 160, in check_for_emails_interval
    self.select('Every 5 minutes')
  File "/var/jenkins/workspace/b2g.flame.mozilla-central.ui.smoketest/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 98, in select
    self.wait_for_element_not_displayed(*_close_button_locator)
  File "/var/jenkins/workspace/b2g.flame.mozilla-central.ui.smoketest/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 48, in wait_for_element_not_displayed
    lambda m: not m.find_element(by, locator).is_displayed())
  File "/var/jenkins/workspace/b2g.flame.mozilla-central.ui.smoketest/.env/local/lib/python2.7/site-packages/marionette_client-0.7.9-py2.7.egg/marionette/wait.py", line 143, in until
    cause=last_exc)
TimeoutException: TimeoutException: Timed out after 20.1 seconds

Comment 1

[[:AndreiH]]

This needs more investigation

Comment 2

[[:AndreiH]]

Attachment: VIDdeo.3gp

This video explains why this is failing.
Tapping on ok is done to quickly.

At these steps: https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/apps/base.py#L93

Comment 3

[Zac C (:zac)]

Weird, that's usually quite stable..
Put a wait for <li> to == selected ?

Comment 4

[[:AndreiH]]

We can use something like this for this test Zac, but there are a lot of other tests that use the "select" method that maybe don't have the "selected" attribute .

Should we ask the devs for some improvement?

Comment 5

[Zac C (:zac)]

It's a global/shared feature in the System app so I shouldn't think you'll regress anything by adding that wait in there.

Comment 6

[[:AndreiH]]

Attachment: 2014-06-17-15-07-11.png

After some more investigation I see that when the test fails, the keyboards is still displayed. (see the screenshot)

Comment 7

[[:AndreiH]]

Attachment: PR https://github.com/mozilla-b2g/gaia/pull/20614

Comment 8

[Florin Strugariu [:Bebe]]

Should that be visible?

Comment 9

[[:AndreiH]]

That should not be visible, after tapping on next https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/apps/email/app.py#L76

Comment 10

[Florin Strugariu [:Bebe]]

Comment on attachment 8441328 [details] [review]
PR https://github.com/mozilla-b2g/gaia/pull/20614

I tried to reproduce this but I couldn't

I could reproduce it if we run automated tests multiple times

It looks like somehow the keyboard suggestions take a little longer to load and we go to the next step and don't wait for the keyboard to dismiss this makes the keyboard visible over the screen  

The patch prevents this to happen

Comment 11

[Zac C (:zac)]

Comment on attachment 8441328 [details] [review]
PR https://github.com/mozilla-b2g/gaia/pull/20614

r+

Comment 12

[Zac C (:zac)]

Merged:
https://github.com/mozilla-b2g/gaia/commit/2cb9af38a933d531aaf27ffc19910f17e5931d2d