kennethreitz/python-guide
1
0
Fork 0
mirror of https://github.com/kennethreitz/python-guide.git synced 2026-06-05 23:00:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Minor spelling fix

Browse Source
This commit is contained in:
Jens Rantil
2012-06-10 18:53:37 +02:00
parent 911865980b
commit bdcfd1e221
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/writing/tests.rst
+1 -1
View File
@@ -47,7 +47,7 @@ Some general rules of testing:
catching test are among the most valuable piece of code in your project. 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 - Use long and descriptive names for testing functions. The style guide here is
slighlty different than that of running code, where short names are often slightly different than that of running code, where short names are often
preferred. The reason is testing functions are never called explicitely. preferred. The reason is testing functions are never called explicitely.
``square()`` or even ``sqr()`` is ok in running code, but in testing code you ``square()`` or even ``sqr()`` is ok in running code, but in testing code you
would has names such as ``test_square_of_number_2()``, would has names such as ``test_square_of_number_2()``,