Closed
Bug 1128952
Opened 10 years ago
Closed 10 years ago
Use more precise actions when selecting values from the timepicker
Categories
(Firefox OS Graveyard :: Gaia::UI Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: viorela, Assigned: viorela)
Details
Attachments
(2 files)
Test test_clock_create_new_alarm.py is failing on mozilla-central: http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-central.ui.functional.smoke/329/HTML_Report/ 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: https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/apps/system/regions/time_picker.py#L59 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/marionette_test.py", line 283, in run testMethod() File "/var/jenkins/1/workspace/flame-kk-319.b2g-inbound.ui.functional.smoke/tests/python/gaia-ui-tests/gaiatest/tests/functional/clock/test_clock_create_new_alarm.py", line 92, in test_clock_create_new_alarm self.alarm_alert.wait_for_alarm_to_trigger() File "/var/jenkins/1/workspace/flame-kk-319.b2g-inbound.ui.functional.smoke/tests/python/gaia-ui-tests/gaiatest/apps/clock/regions/alarm_alert.py", line 24, in wait_for_alarm_to_trigger expected.element_present(*self._alarm_frame_locator)) 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/wait.py", line 143, in until cause=last_exc) 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 | ||
Updated•10 years ago
|
Assignee: nobody → viorela.ioia
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•10 years ago
|
||
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)
Comment 3•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Summary: Investigate failure in test_clock_create_new_alarm.py → Use more precise actions when selecting values from the timepicker
Updated•10 years ago
|
Attachment #8559871 -
Flags: review+
Comment 4•10 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/59f71e42d4137f194ca50709497f6e3706dad10a
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
QA Whiteboard: [fxosqa-auto-s9]
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(dave.hunt)
You need to log in
before you can comment on or make changes to this bug.
Description
•