Author: russellm
Date: 2010-01-18 17:49:20 -0600 (Mon, 18 Jan 2010)
New Revision: 12259
Modified:
django/trunk/docs/topics/testing.txt
Log:
Updated the docs around test runners to encourage the use of **kwargs in the
test runner constructor.
Modified: django/trunk/docs/topics/testing.txt
===================================================================
--- django/trunk/docs/topics/testing.txt 2010-01-18 21:49:13 UTC (rev
12258)
+++ django/trunk/docs/topics/testing.txt 2010-01-18 23:49:20 UTC (rev
12259)
@@ -1269,7 +1269,7 @@
plus a selection of other methods that are used to by ``run_tests()`` to
set up, execute and tear down the test suite.
-.. class:: DjangoTestSuiteRunner(verbosity=1, interactive=True, failfast=True)
+.. class:: DjangoTestSuiteRunner(verbosity=1, interactive=True, failfast=True,
**kwargs)
``verbosity`` determines the amount of notification and debug information
that will be printed to the console; ``0`` is no output, ``1`` is normal
@@ -1284,6 +1284,12 @@
If ``failfast`` is ``True``, the test suite will stop running after the
first test failure is detected.
+ Django will, from time to time, extend the capabilities of
+ the test runner by adding new arguments. The ``**kwargs`` declaration
+ allows for this expansion. If you subclass ``DjangoTestSuiteRunner`` or
+ write your own test runner, ensure accept and handle the ``**kwargs``
+ parameter.
+
.. method:: DjangoTestSuiteRunner.run_tests(test_labels, extra_tests=[])
Run the test suite.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
