Skip to content


Minor wording correction and changed some code-block tags to be python #305

merged 1 commit into from

3 participants


No description provided.

@kennethreitz kennethreitz merged commit b432c73 into kennethreitz:master

Looks like I messed up and accidentally specified some code blocks as console where they should have been python (corrected in this PR). Oops. Nice catch, @Duta.

@Duta Duta deleted the unknown repository branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
This page is out of date. Refresh to see the latest.
Showing with 6 additions and 6 deletions.
  1. +6 −6 docs/writing/tests.rst
12 docs/writing/tests.rst
@@ -44,7 +44,7 @@ Some general rules of testing:
- The first step when you are debugging your code is to write a new test
pinpointing the bug. While it is not always possible to do, those bug
- catching test are among the most valuable piece of code in your project.
+ catching test are among the most valuable pieces of code in your project.
- Use long and descriptive names for testing functions. The style guide here is
slightly different than that of running code, where short names are often
@@ -150,7 +150,7 @@ Despite being a fully-featured and extensible test tool, it boasts a simple
syntax. Creating a test suite is as easy as writing a module with a couple of
-.. code-block:: console
+.. code-block:: python
# content of
def func(x):
@@ -181,8 +181,8 @@ and then running the `py.test` command AssertionError
========================= 1 failed in 0.02 seconds =========================
-far less work than would be required for the equivalent functionality with the
-unittest module!
+is far less work than would be required for the equivalent functionality with
+the unittest module!
`py.test <>`_
@@ -262,7 +262,7 @@ make assertions about how they have been used.
For example, you can monkey patch a method
-.. code-block:: console
+.. code-block:: python
from mock import MagicMock
thing = ProductionClass()
@@ -275,7 +275,7 @@ To mock classes or objects in a module under test, use the ``patch`` decorator.
In the example below, an external search system is replaced with a mock that
always returns the same result (but only for the duration of the test).
-.. code-block:: console
+.. code-block:: python
def mock_search(self):
class MockSearchQuerySet(SearchQuerySet):
Something went wrong with that request. Please try again.