mirror of
https://github.com/django/django.git
synced 2024-12-23 01:25:58 +00:00
Rewrote 'Test with warnings enabled' section of docs/topics/testing.txt from [14019] to be clearer
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14033 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
bca8aed419
commit
40777cb533
@ -311,11 +311,11 @@ be reported, and any test databases created by the run will not be destroyed.
|
||||
|
||||
.. admonition:: Test with warnings enabled
|
||||
|
||||
It is a good idea to run your tests with ``python -Wall manage.py
|
||||
test``. This will allow you to catch any deprecation warnings that
|
||||
might be in your code. Django (as well as many other libraries) use
|
||||
warnings to flag when features are deprecated. It can also flag
|
||||
areas in your code that are not strictly wrong, but may benefit
|
||||
It's a good idea to run your tests with Python warnings enabled:
|
||||
``python -Wall manage.py test``. The ``-Wall`` flag tells Python to
|
||||
display deprecation warnings. Django, like many other Python libraries,
|
||||
uses these warnings to flag when features are going away. It also might
|
||||
flag areas in your code that aren't strictly wrong but could benefit
|
||||
from a better implementation.
|
||||
|
||||
Running tests outside the test runner
|
||||
|
Loading…
Reference in New Issue
Block a user