Closed Bug 1128952 Opened 5 years ago Closed 5 years ago

Use more precise actions when selecting values from the timepicker


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

Gonk (Firefox OS)
Not set


(Not tracked)



(Reporter: viorela, Assigned: viorela)



(2 files)

Test is failing on mozilla-central:

I've been able to reproduce the failure locally by running the automated test. It is failing constantly (repro rate: 5/5). It is not reproducible manually.
The failure is caused by the fact that '11' minutes alarm time is set when editing alarm, instead of '2' min. So the alarm will be triggered after 11 minutes. 
As we are waiting 60 seconds for the alarm to be triggered, the test is timing out.
This requires further investigation, and maybe some changes in the _flick_menu_up() method:

Traceback (most recent call last):
File "/var/jenkins/1/workspace/flame-kk-319.b2g-inbound.ui.functional.smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.8.7-py2.7.egg/marionette/", line 283, in run
File "/var/jenkins/1/workspace/flame-kk-319.b2g-inbound.ui.functional.smoke/tests/python/gaia-ui-tests/gaiatest/tests/functional/clock/", line 92, in test_clock_create_new_alarm
File "/var/jenkins/1/workspace/flame-kk-319.b2g-inbound.ui.functional.smoke/tests/python/gaia-ui-tests/gaiatest/apps/clock/regions/", line 24, in wait_for_alarm_to_trigger
File "/var/jenkins/1/workspace/flame-kk-319.b2g-inbound.ui.functional.smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.8.7-py2.7.egg/marionette/", line 143, in until
TimeoutException: TimeoutException: Timed out after 60.3 seconds

Device info:
Device firmware (base) 	L1TC100118D0
Device firmware (date) 	03 Feb 2015 03:09:31
Device firmware (incremental) 	eng.cltbld.20150203.060920
Device firmware (release) 	4.4.2
Device identifier 	flame
Gaia date 	03 Feb 2015 01:42:36
Gaia revision 	feb5c58c93d4
Gecko build 	20150203020617
Gecko revision 	519ac008276a
Gecko version 	38.0a1
Assignee: nobody → viorela.ioia
The test is still failing while I'm running it locally.
Dave, can we reset the time to 1:00 just before editing the alarm, or set the time alarm to '02'?
Flags: needinfo?(dave.hunt)
Summary: Investigate failure in → Use more precise actions when selecting values from the timepicker
QA Whiteboard: [fxosqa-auto-s9]
Flags: needinfo?(dave.hunt)
You need to log in before you can comment on or make changes to this bug.