mirrors/django
mirrors/django
0
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-11-29 22:56:46 +01:00
Code Issues Releases Wiki Activity

Edited testing.txt changes from [17283]

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17306 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2011-12-30 20:29:27 +00:00
parent 103890561b
commit 32ee74f89e
1 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/topics/testing.txt
View File

@ -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