From bfa3d5af34937eef52dc4cfb22e831ff4a720fe8 Mon Sep 17 00:00:00 2001 From: juanpex Date: Mon, 27 Aug 2012 21:04:20 -0300 Subject: [PATCH] fix documentation testing of Selenium WebDriverWait According to the documentation of Selenium, WebDriverWait class has no timeout parameter and using the code fails. http://selenium.googlecode.com/svn/trunk/docs/api/java/org/openqa/selenium/support/ui/FluentWait.html#until%28com.google.common.base.Predicate%29 --- docs/topics/testing.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index 1f4c970d3e..c4c73733f5 100644 --- a/docs/topics/testing.txt +++ b/docs/topics/testing.txt @@ -2039,7 +2039,7 @@ out the `full reference`_ for more details. self.selenium.find_element_by_xpath('//input[@value="Log in"]').click() # Wait until the response is received WebDriverWait(self.selenium, timeout).until( - lambda driver: driver.find_element_by_tag_name('body'), timeout=10) + lambda driver: driver.find_element_by_tag_name('body')) The tricky thing here is that there's really no such thing as a "page load," especially in modern Web apps that generate HTML dynamically after the