Closed Bug 960744 Opened 12 years ago Closed 12 years ago

Intermittent test_calendar_new_event_appears_on_all_calendar_views.py test_calendar_new_event_appears_on_all_calendar_views.TestCalendar.test_that_new_event_appears_on_all_calendar_views | NoSuchElementException: Unable to locate element ...

Categories

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

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: Bebe)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

46 bytes, text/x-github-pull-request
zcampbell
: review+
Details | Review
https://tbpl.mozilla.org/php/getParsedLog.php?id=33116811&tree=Mozilla-Inbound b2g_ubuntu64_vm mozilla-inbound opt test gaia-ui-test on 2014-01-16 10:51:34 PST for push 544bdb194485 slave: tst-linux64-spot-391 11:00:17 INFO - test_that_new_event_appears_on_all_calendar_views (test_calendar_new_event_appears_on_all_calendar_views.TestCalendar) ... ERROR 11:00:17 INFO - ====================================================================== 11:00:17 INFO - ERROR: None 11:00:17 INFO - ---------------------------------------------------------------------- 11:00:17 INFO - Traceback (most recent call last): 11:00:17 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/marionette/marionette_test.py", line 143, in run 11:00:17 INFO - testMethod() 11:00:17 INFO - File "/builds/slave/test/gaia/tests/python/gaia-ui-tests/gaiatest/tests/functional/calendar/test_calendar_new_event_appears_on_all_calendar_views.py", line 37, in test_that_new_event_appears_on_all_calendar_views 11:00:17 INFO - self.assertIn(event_title, calendar.displayed_events_in_month_view(event_start_date_time)) 11:00:17 INFO - File "/builds/slave/test/gaia/tests/python/gaia-ui-tests/gaiatest/apps/calendar/app.py", line 55, in displayed_events_in_month_view 11:00:17 INFO - return self.marionette.find_element(*self._get_events_locator_in_month_view(date_time)).text 11:00:17 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/marionette/marionette.py", line 1116, in find_element 11:00:17 INFO - response = self._send_message('findElement', 'value', **kwargs) 11:00:17 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/marionette/marionette.py", line 593, in _send_message 11:00:17 INFO - self._handle_error(response) 11:00:17 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/marionette/marionette.py", line 614, in _handle_error 11:00:17 ERROR - raise NoSuchElementException(message=message, status=status, stacktrace=stacktrace) 11:00:17 ERROR - TEST-UNEXPECTED-FAIL | test_calendar_new_event_appears_on_all_calendar_views.py test_calendar_new_event_appears_on_all_calendar_views.TestCalendar.test_that_new_event_appears_on_all_calendar_views | NoSuchElementException: Unable to locate element: #event-list section.hour-11 div.events 11:00:17 INFO - ---------------------------------------------------------------------- 11:00:17 INFO - Ran 1 test in 28.996s 11:00:17 WARNING - FAILED (errors=1)
Looking at the source code here for the failure report we can see that the test run, from creation of the event to clicking submit covered over a new hour. This is because the expected condition is taken before the app is launched and the even added, which might take 10-15 seconds. We need a fix on this. <section id="months-day-view" data-date="Thu Jan 16 2014 00:00:00 GMT-0800 (PST)" class="active"> <section class="day-events" id="event-list"><section data-hour="12" class="hour hour-12 calendar-display calendar-id-local-first"><h4><span class="display-hour 12">12 PM</span></h4><div class="events"><section data-id="local-first-350e5538-5104-4b38-b41d-9c2e57dbd8eb-ef624ab4-acd8-4d16-a4d7-9a8300f9eef3" class="event calendar-id-local-first has-alarms calendar-display" style="height: 100%;"><div class="container calendar-id-local-first calendar-color"><h5>Event Title 11:59:58</h5><span class="details"><span class="location">Event Location 11:59:58</span></span></div></section></div></section></section> </section>
Priority: -- → P1
Attached file pull request
Attachment #8363692 - Flags: review?(zcampbell)
Attachment #8363692 - Flags: review?(viorela.ioia)
Attachment #8363692 - Flags: review?(bob.silverberg)
Attachment #8363692 - Flags: review?(andrei.hutusoru)
currently we expect that the new alarm time is current time + 1 hour and use locators based on that assumption. but if we run tests and the current time is x:59 then tit's a hight probability that the test will fail Updated the test to use the actual event hour in the tests
Assignee: nobody → florin.strugariu
Comment on attachment 8363692 [details] [review] pull request Looks ok! Thanks @bebef1987 for looking into this!
Attachment #8363692 - Flags: review?(andrei.hutusoru) → review+
Comment on attachment 8363692 [details] [review] pull request I ran this test multiple times and got no failure. It seems that the intermittent problem was fixed by your patch.
Attachment #8363692 - Flags: review?(viorela.ioia) → review+
(In reply to Viorela Ioia [:viorela] from comment #8) > Comment on attachment 8363692 [details] [review] > pull request > > I ran this test multiple times and got no failure. It seems that the > intermittent problem was fixed by your patch. Did you test it at the right time of day? Maybe even force the clock to be the time that might induce the failure?
Comment on attachment 8363692 [details] [review] pull request r-
Attachment #8363692 - Flags: review?(zcampbell) → review-
Attachment #8363692 - Flags: review?(bob.silverberg)
Attachment #8363692 - Flags: review-
Attachment #8363692 - Flags: review+
Comment on attachment 8363692 [details] [review] pull request r+, Bebe can you squash it now?
Attachment #8363692 - Flags: review+
zac done
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: