summaryrefslogtreecommitdiff
path: root/docs/topics/testing/overview.txt
diff options
context:
space:
mode:
authorSergey Fedoseev <fedoseev.sergey@gmail.com>2019-11-25 20:28:47 +0500
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2019-11-26 14:45:15 +0100
commitc2a8a69b729749ede9b366a5791ea60b51a6dfa0 (patch)
treecee3c735de8002d62338d8bdb54d855842a37552 /docs/topics/testing/overview.txt
parent7873d3757d3075d36cf68771bf4f584ba3386e37 (diff)
[2.2.x] Used :ticket: role in all tickets links.
Backport of abc51d44afcb8482c64c0bb8c1022f11e7eb2bbb from master.
Diffstat (limited to 'docs/topics/testing/overview.txt')
-rw-r--r--docs/topics/testing/overview.txt4
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index 1eea7ead22..3b07ed42c6 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -275,9 +275,7 @@ setting.
Caches are not cleared after each test, and running "manage.py test fooapp" can
insert data from the tests into the cache of a live system if you run your
tests in production because, unlike databases, a separate "test cache" is not
-used. This behavior `may change`_ in the future.
-
-.. _may change: https://code.djangoproject.com/ticket/11505
+used. This behavior :ticket:`may change <11505>` in the future.
Understanding the test output
-----------------------------