From bdcfd1e221f996699522295207a0138522f3ada6 Mon Sep 17 00:00:00 2001 From: Jens Rantil Date: Sun, 10 Jun 2012 18:53:37 +0200 Subject: [PATCH] Minor spelling fix --- docs/writing/tests.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/writing/tests.rst b/docs/writing/tests.rst index 717d26e..0a8479d 100644 --- 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 - 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. ``square()`` or even ``sqr()`` is ok in running code, but in testing code you would has names such as ``test_square_of_number_2()``, -- 1.8.0.2