Closed Bug 1198620 Opened 10 years ago Closed 9 years ago

"NoSuchElementException: Unable to locate element: reportButton" in test_safe_browsing_warning_pages.py

Categories

(Testing :: Firefox UI Tests, defect)

43 Branch
All
Windows XP
defect
Not set
normal

Tracking

(firefox43 fixed)

RESOLVED FIXED
Tracking Status
firefox43 --- fixed

People

(Reporter: whimboo, Unassigned)

References

Details

(Whiteboard: [failure][fixed by bug 1201715])

Maybe a page load is not done successfully here so the button cannot be found? It would need some investigation. Here the stack: Traceback (most recent call last): File "c:\jenkins\workspace\mozilla-aurora_remote\venv\lib\site-packages\marionette\marionette_test.py", line 296, in run testMethod() File "c:\jenkins\workspace\mozilla-aurora_remote\venv\Lib\site-packages\firefox_ui_tests\remote\security\test_safe_browsing_warning_pages.py", line 58, in test_warning_pages self.check_report_button(unsafe_page) File "c:\jenkins\workspace\mozilla-aurora_remote\venv\Lib\site-packages\firefox_ui_tests\remote\security\test_safe_browsing_warning_pages.py", line 81, in check_report_button button = self.marionette.find_element(By.ID, "reportButton") File "c:\jenkins\workspace\mozilla-aurora_remote\venv\lib\site-packages\marionette_driver\marionette.py", line 1599, in find_element response = self._send_message('findElement', 'value', **kwargs) File "c:\jenkins\workspace\mozilla-aurora_remote\venv\lib\site-packages\marionette_driver\decorators.py", line 36, in _ return func(*args, **kwargs) File "c:\jenkins\workspace\mozilla-aurora_remote\venv\lib\site-packages\marionette_driver\marionette.py", line 725, in _send_message self._handle_error(response) File "c:\jenkins\workspace\mozilla-aurora_remote\venv\lib\site-packages\marionette_driver\marionette.py", line 761, in _handle_error raise errors.lookup(status)(message, stacktrace=stacktrace) NoSuchElementException: NoSuchElementException: Unable to locate element: reportButton
Depends on: 1201715
No failure over the last couple days since bug 1201715 was fixed. So it looks like this bug is also fixed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [failure] → [failure][fixed by bug 1201715]
Product: Mozilla QA → Testing
You need to log in before you can comment on or make changes to this bug.