On Wed, Apr 23, 2008 at 05:22:29PM -0300, Sidnei da Silva wrote: > Can't you start a plain-old unittests module and stick your test in > there? Is there any rule that says you cannot create a plain-old test > module if the project you are fixing the bug in uses doctests?
I'll probably do that (since I sort of took over the maintainership of zope.testing a while ago). The point of my message was not to whine about the state of zope.testing, but to present a new argument against the current fashion of using plain-text narrative doctests for everything. These are very fine when you initially write them, but a pain when you come back a year later and need to modify them. Trying to kill two birds with one stone (i.e. have narrative doctests serve both as documentation and as the test suite) doesn't seem to work: * users complain about boring corner cases and irrelevant test fixtures in what they expected to be documentation * programmers complain about narratives being too hard to modify Marius Gedminas -- You can't spell evil without vi.
Description: Digital signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )