summaryrefslogtreecommitdiff
path: root/docs/topics/testing
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2014-03-24 11:42:56 -0400
committerTim Graham <timograham@gmail.com>2014-03-24 11:42:56 -0400
commit51c8045145b29fed604f716d4d17958aa803b5ea (patch)
tree3d3c1711832684134bf5bda967acdb4bf5cd09c0 /docs/topics/testing
parentec08d62a20f55cfdfb9fbd21d8bc5627c54337c7 (diff)
Removed versionadded/changed annotations for 1.6.
Diffstat (limited to 'docs/topics/testing')
-rw-r--r--docs/topics/testing/advanced.txt4
-rw-r--r--docs/topics/testing/overview.txt15
-rw-r--r--docs/topics/testing/tools.txt17
3 files changed, 3 insertions, 33 deletions
diff --git a/docs/topics/testing/advanced.txt b/docs/topics/testing/advanced.txt
index 1bd15bd1a6..cd71505d38 100644
--- a/docs/topics/testing/advanced.txt
+++ b/docs/topics/testing/advanced.txt
@@ -166,8 +166,6 @@ Advanced features of ``TransactionTestCase``
.. attribute:: TransactionTestCase.available_apps
- .. versionadded:: 1.6
-
.. warning::
This attribute is a private API. It may be changed or removed without
@@ -295,8 +293,6 @@ Defining a test runner
.. currentmodule:: django.test.runner
-.. versionadded:: 1.6
-
A test runner is a class defining a ``run_tests()`` method. Django ships
with a ``DiscoverRunner`` class that defines the default Django testing
behavior. This class defines the ``run_tests()`` entry point, plus a
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index 19fff1ed1c..30448e9db9 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -58,12 +58,6 @@ test utility is to find all the test cases (that is, subclasses of
:class:`unittest.TestCase`) in any file whose name begins with ``test``,
automatically build a test suite out of those test cases, and run that suite.
-.. versionchanged:: 1.6
-
- Previously, Django's default test runner only discovered tests in
- ``tests.py`` and ``models.py`` files within a Python package listed in
- :setting:`INSTALLED_APPS`.
-
For more details about :mod:`unittest`, see the Python documentation.
.. warning::
@@ -120,15 +114,6 @@ You can specify a custom filename pattern match using the ``-p`` (or
$ ./manage.py test --pattern="tests_*.py"
-.. versionchanged:: 1.6
-
- Previously, test labels were in the form ``applabel``,
- ``applabel.TestCase``, or ``applabel.TestCase.test_method``, rather than
- being true Python dotted paths, and tests could only be found within
- ``tests.py`` or ``models.py`` files within a Python package listed in
- :setting:`INSTALLED_APPS`. The ``--pattern`` option and file paths as test
- labels are new in 1.6.
-
If you press ``Ctrl-C`` while the tests are running, the test runner will
wait for the currently running test to complete and then exit gracefully.
During a graceful exit the test runner will output details of any test
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index a67675b268..f56cbee861 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -573,11 +573,6 @@ functionality like:
* Using the :attr:`~SimpleTestCase.client` :class:`~django.test.Client`.
* Custom test-time :attr:`URL maps <SimpleTestCase.urls>`.
-.. versionchanged:: 1.6
-
- The latter two features were moved from ``TransactionTestCase`` to
- ``SimpleTestCase`` in Django 1.6.
-
If you need any of the other more complex and heavyweight Django-specific
features like:
@@ -1281,8 +1276,6 @@ your test suite.
.. method:: SimpleTestCase.assertFormsetError(response, formset, form_index, field, errors, msg_prefix='')
- .. versionadded:: 1.6
-
Asserts that the ``formset`` raises the provided list of errors when
rendered.
@@ -1459,16 +1452,12 @@ your test suite.
By default, the comparison is also ordering dependent. If ``qs`` doesn't
provide an implicit ordering, you can set the ``ordered`` parameter to
``False``, which turns the comparison into a Python set comparison.
+ If the order is undefined (if the given ``qs`` isn't ordered and the
+ comparison is against more than one ordered values), a ``ValueError`` is
+ raised.
Output in case of error can be customized with the ``msg`` argument.
- .. versionchanged:: 1.6
-
- The method now checks for undefined order and raises ``ValueError``
- if undefined order is spotted. The ordering is seen as undefined if
- the given ``qs`` isn't ordered and the comparison is against more
- than one ordered values.
-
.. versionchanged:: 1.7
The method now accepts a ``msg`` parameter to allow customization of