mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-23 01:25:58 +00:00
Code Issues 25 Releases Wiki Activity

Made instructions for shell launch in tutorial 5 more explicit.

Browse Source
This commit is contained in:
Devin Mork 2018-01-11 10:23:50 -06:00 committed by Tim Graham
parent 7d607127e3
commit 2e625095fe
1 changed files with 18 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/intro/tutorial05.txt
View File

@ -135,7 +135,13 @@ the ``Question`` was published within the last day (which is correct) but also i
the ``Question``’s ``pub_date`` field is in the future (which certainly isn't). the ``Question``’s ``pub_date`` field is in the future (which certainly isn't).
To check if the bug really exists, using the Admin create a question whose date To check if the bug really exists, using the Admin create a question whose date
lies in the future and check the method using the :djadmin:`shell`:: lies in the future and check the method using the :djadmin:`shell`:
.. console::
$ python manage.py shell
.. code-block:: pycon
>>> import datetime >>> import datetime
>>> from django.utils import timezone >>> from django.utils import timezone
@ -190,7 +196,9 @@ future. We then check the output of ``was_published_recently()`` - which
Running tests Running tests
------------- -------------
In the terminal, we can run our test:: In the terminal, we can run our test:
.. console::
$ python manage.py test polls $ python manage.py test polls
@ -215,7 +223,7 @@ and you'll see something like::
What happened is this: What happened is this:
* ``python manage.py test polls`` looked for tests in the ``polls`` application * ``manage.py test polls`` looked for tests in the ``polls`` application
* it found a subclass of the :class:`django.test.TestCase` class * it found a subclass of the :class:`django.test.TestCase` class
@ -335,7 +343,13 @@ or even in the :djadmin:`shell`.
We will start again with the :djadmin:`shell`, where we need to do a couple of We will start again with the :djadmin:`shell`, where we need to do a couple of
things that won't be necessary in ``tests.py``. The first is to set up the test things that won't be necessary in ``tests.py``. The first is to set up the test
environment in the :djadmin:`shell`:: environment in the :djadmin:`shell`:
.. console::
$ python manage.py shell
.. code-block:: pycon
>>> from django.test.utils import setup_test_environment >>> from django.test.utils import setup_test_environment
>>> setup_test_environment() >>> setup_test_environment()