Changes between Initial Version and Version 1 of Ticket #26048


Ignore:
Timestamp:
Jan 6, 2016, 6:50:14 PM (9 years ago)
Author:
Tim Graham
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26048 – Description

    initial v1  
    1 From the selenium docs, "Dependent on several factors, including the OS/Browser combination, WebDriver may or may not wait for the page to load. In some circumstances, WebDriver may return control before the page has finished, or even started, loading. To ensure robustness, you need to wait for the element(s) to exist in the page using Explicit and Implicit Waits."
     1From the selenium docs, "Dependent on several factors, including the OS/Browser combination, WebDriver may or may not wait for the page to load. In some circumstances, WebDriver may return control before the page has finished, or even started, loading. To ensure robustness, you need to wait for the element(s) to exist in the page using [http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp#explicit-and-implicit-waits-reference Explicit and Implicit Waits]."
    22
    33Currently, we have a collection of [https://github.com/django/django/blob/7f7553dd30534d606c84952a3f6dcb64b396ce37/django/contrib/admin/tests.py#L49-L120 wait_for*] methods to accomplish this. The idea is to switch our code to call `self.selenium.implicitly_wait(10)` after initializing `self.selenium` which should allow us to remove many of these waiting calls.
Back to Top