diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2011-12-30 20:29:27 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2011-12-30 20:29:27 +0000 |
| commit | 32ee74f89edd88fb37ca223b1e146eebe8fb6c1b (patch) | |
| tree | 8cfee739e79d681963de5b3cf43092782e605175 /docs | |
| parent | 103890561be52a074ef30c08d4ecc2d98066c259 (diff) | |
Edited testing.txt changes from [17283]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17306 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/testing.txt | 27 |
1 files changed, 13 insertions, 14 deletions
diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index 3c25577400..5eef2dc092 100644 --- a/docs/topics/testing.txt +++ b/docs/topics/testing.txt @@ -1870,16 +1870,16 @@ out the `full reference`_ for more details. When using an in-memory SQLite database to run the tests, the same database connection will be shared by two threads in parallel: the thread in which - the live server is run, and the thread in which the test case is run. It is + the live server is run and the thread in which the test case is run. It's important to prevent simultaneous database queries via this shared - connection by the two threads as that may sometimes cause the tests to - randomly fail. So you need to ensure that the two threads do not access the + connection by the two threads, as that may sometimes randomly cause the + tests to fail. So you need to ensure that the two threads don't access the database at the same time. In particular, this means that in some cases - (for example just after clicking a link or submitting a form) you might + (for example, just after clicking a link or submitting a form), you might need to check that a response is received by Selenium and that the next - page is loaded before proceeding further with the execution of the tests. - This can be achieved, for example, by making Selenium wait until the - `<body>` HTML tag is found in the response (requires Selenium > 2.13): + page is loaded before proceeding with further test execution. + Do this, for example, by making Selenium wait until the `<body>` HTML tag + is found in the response (requires Selenium > 2.13): .. code-block:: python @@ -1891,13 +1891,12 @@ out the `full reference`_ for more details. WebDriverWait(self.selenium, timeout).until( lambda driver: driver.find_element_by_tag_name('body'), timeout=10) - The difficult point is that there really is no such thing as a "page load", - especially in modern Web apps that have dynamically-generated page - components that do not exist in the HTML initially received from the - server. So simply checking for the presence of the `<body>` tag in the - response might not necessarily be appropriate for all use cases. Please - refer to the `Selenium FAQ`_ and the `Selenium documentation`_ for more - information on this topic. + 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 + server generates the initial document. So, simply checking for the presence + of `<body>` in the response might not necessarily be appropriate for all + use cases. Please refer to the `Selenium FAQ`_ and + `Selenium documentation`_ for more information. .. _Selenium FAQ: http://code.google.com/p/selenium/wiki/FrequentlyAskedQuestions#Q:_WebDriver_fails_to_find_elements_/_Does_not_block_on_page_loa .. _Selenium documentation: http://seleniumhq.org/docs/04_webdriver_advanced.html#explicit-waits |