Changes between Version 110 and Version 111 of DeveloperGuidelinesTesting

Timestamp:

08/08/11 21:13:52 (13 years ago)

Author:

Mike A

Comment:

Added section on writing tests with simple examples of both methods

DeveloperGuidelinesTesting

@@ -69 +69 @@
  * simplification of integration testing (because all the parts are known to work, only interfaces between them need testing),
  * better system design by:
- ** easing refactoring (changes can be more rapidly verified not to create new bugs),
- ** promoting refactoring (dividing units into testable pieces also creates more reusable pieces),
- ** standing in for specification documents (i.e. describing by example what the code needs to do).
+   * easing refactoring (changes can be more rapidly verified not to create new bugs),
+   * promoting refactoring (dividing units into testable pieces also creates more reusable pieces),
+   * standing in for specification documents (i.e. describing by example what the code needs to do).
 
 Cons:
@@ -115 +115 @@
 '''Advice:'''
 
-One unittest.TestCase per unit (procedure, method or function). This makes test output easy to follow as it is what unittest expects. I.e. don't test several units in one TestCase.
-You can just use asserts instead of the cumbersome test.assertEquals etc. methods which often don't do what you need. nose can introspect the stack to make meaningful messages.
-Avoid inheritance trees with unittests as the unittest.TestCase isn't really designed for inheritance, more as a convenient place to put the tests.
-Break test methods up into smaller methods. Non-test code can be extracted out into external procedures/functions which are easier to reuse. 
-Read the nose documentation regarding writing tests: [http://readthedocs.org/docs/nose/en/latest/writing_tests.html]
-Read this too: [http://ivory.idyll.org/articles/nose-intro.html]
+* One unittest.TestCase per unit (procedure, method or function). This makes test output easy to follow as it is what unittest expects. I.e. don't test several units in one TestCase.
+* You can just use asserts instead of the cumbersome test.assertEquals etc. methods which often don't do what you need. nose can introspect the stack to make meaningful messages.
+* Avoid inheritance trees with unittests as the unittest.TestCase isn't really designed for inheritance, more as a convenient place to put the tests.
+* Break test methods up into smaller methods. Non-test code can be extracted out into external procedures/functions which are easier to reuse. 
+* Read the nose documentation regarding writing tests: [http://readthedocs.org/docs/nose/en/latest/writing_tests.html]
+* Read this too: [http://ivory.idyll.org/articles/nose-intro.html]
 
 === Examples ===