git://git.eng.unimelb.edu.au
/
python-guide.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
9118659
)
Minor spelling fix
author
Jens Rantil
<jens.rantil@gmail.com>
Sun, 10 Jun 2012 16:53:37 +0000
(18:53 +0200)
committer
Jens Rantil
<jens.rantil@gmail.com>
Sun, 10 Jun 2012 16:53:37 +0000
(18:53 +0200)
docs/writing/tests.rst
patch
|
blob
|
history
diff --git
a/docs/writing/tests.rst
b/docs/writing/tests.rst
index
717d26e
..
0a8479d
100644
(file)
--- a/
docs/writing/tests.rst
+++ b/
docs/writing/tests.rst
@@
-47,7
+47,7
@@
Some general rules of testing:
catching test are among the most valuable piece of code in your project.
- Use long and descriptive names for testing functions. The style guide here is
catching test are among the most valuable piece of code in your project.
- Use long and descriptive names for testing functions. The style guide here is
- sligh
lt
y different than that of running code, where short names are often
+ sligh
tl
y different than that of running code, where short names are often
preferred. The reason is testing functions are never called explicitely.
``square()`` or even ``sqr()`` is ok in running code, but in testing code you
would has names such as ``test_square_of_number_2()``,
preferred. The reason is testing functions are never called explicitely.
``square()`` or even ``sqr()`` is ok in running code, but in testing code you
would has names such as ``test_square_of_number_2()``,