Am 17.04.2010, 03:41 Uhr, schrieb Tres Seaver <>:

> The trickier testing bits we would re-write as super thorough, no
> shortcuts-taken unit tests:  one testcase class per class (or API
> function) under test, at least one method per class-under-test method,
> with more preferred to get all code paths / preconditions covered.  The
> goal here would be to comment out the doctests from the test_suites and
> get the code to 100% coverage using pure unit tests.  Meanwhile, the
> doctests would be refactored into the Sphinx documentation, losing all
> the bits which obscure their intent as documentation.

I'm all for this but in the past I have struggled mightily (this could be  
an ironic use of the word ;-) with unit tests for views. Is this

1) Because I've overlooked something?

2) Because views depend on too many things, setting up test cases is a lot  
of work?

3) Because it's not been done a lot in the past?

Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmholtzstr. 20
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to