diff options
| author | Julien Phalip <jphalip@gmail.com> | 2012-02-15 17:33:51 +0000 |
|---|---|---|
| committer | Julien Phalip <jphalip@gmail.com> | 2012-02-15 17:33:51 +0000 |
| commit | 41256d2341b8ecf4c4987e6acc3d84aafe2674c8 (patch) | |
| tree | 56810a3fe0c87ec0b0fb096024847c401746acaf /docs/topics | |
| parent | 2000f375cde88358cdc66f775f4de14df1234f72 (diff) | |
Fixed #17652 -- Removed all mentions to Windmill from the docs as that project doesn't integrate well with Django at this time.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17524 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/testing.txt | 19 |
1 files changed, 9 insertions, 10 deletions
diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index a9c8635024..ef6fb3c9b3 100644 --- a/docs/topics/testing.txt +++ b/docs/topics/testing.txt @@ -581,16 +581,16 @@ Some of the things you can do with the test client are: * Test that a given request is rendered by a given Django template, with a template context that contains certain values. -Note that the test client is not intended to be a replacement for Windmill_, -Selenium_, or other "in-browser" frameworks. Django's test client has -a different focus. In short: +Note that the test client is not intended to be a replacement for Selenium_ or +other "in-browser" frameworks. Django's test client has a different focus. In +short: * Use Django's test client to establish that the correct view is being called and that the view is collecting the correct context data. -* Use in-browser frameworks such as Windmill_ and Selenium_ to test *rendered* - HTML and the *behavior* of Web pages, namely JavaScript functionality. Django - also provides special support for those frameworks; see the section on +* Use in-browser frameworks like Selenium_ to test *rendered* HTML and the + *behavior* of Web pages, namely JavaScript functionality. Django also + provides special support for those frameworks; see the section on :class:`~django.test.LiveServerTestCase` for more details. A comprehensive test suite should use a combination of both test types. @@ -1840,9 +1840,9 @@ Live test server :class:`~django.test.TransactionTestCase` with one extra feature: it launches a live Django server in the background on setup, and shuts it down on teardown. This allows the use of automated test clients other than the -:ref:`Django dummy client <test-client>` such as, for example, the Selenium_ or -Windmill_ clients, to execute a series of functional tests inside a browser and -simulate a real user's actions. +:ref:`Django dummy client <test-client>` such as, for example, the Selenium_ +client, to execute a series of functional tests inside a browser and simulate a +real user's actions. By default the live server's address is `'localhost:8081'` and the full URL can be accessed during the tests with ``self.live_server_url``. If you'd like @@ -1928,7 +1928,6 @@ case you do not have Firefox installed or wish to use another browser. The example above is just a tiny fraction of what the Selenium client can do; check out the `full reference`_ for more details. -.. _Windmill: http://www.getwindmill.com/ .. _Selenium: http://seleniumhq.org/ .. _selenium package: http://pypi.python.org/pypi/selenium .. _full reference: http://readthedocs.org/docs/selenium-python/en/latest/api.html |