[Zope] Debugging doctests
tseaver at palladion.com
Fri Feb 24 10:38:18 EST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Stephan Richter wrote:
> On Thursday 23 February 2006 14:16, Chris McDonough wrote:
>> (e.g. high-
>>level overview of purpose, how to install it, what other packages it
>>depends upon, which versions of Python/Zope it works with, who is
>>responsible for maintaining the package, where to report bugs, and so
>>on). I suppose this is really a packaging issue, but it would be
>>nice if more packages in the zope namespace package were treated as
>>"islands" like this that could be installed separately from Zope
> The ZSCP tries to exactly capture this information and provide it via its
> So, I take it that you are a second voter in favor of not requiring all tests
> to be doctests.
Count me as another. Doctests are fine for many cases, but they suck
for doing "coverage" / "edge case" testing, which are the "valuable"
unit tests for my applications.
I would note that the usefulness of a doctest as documentation is
inversely proportional to the amount of "setup noise" the test requires.
Tres Seaver +1 202-558-7113 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Zope