Hello,<br><br><div><span class="gmail_quote">On 3/5/07, <b class="gmail_sendername">Andrew Bennetts</b> <<a href="mailto:andrew-tip@puzzling.org">andrew-tip@puzzling.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>The other good use is as testable *documentation*, with the emphasis on<br>documentation. If a doctest file is primarily there to provide test coverage,<br>rather than explaining how to use something, then in my experience it's probably
<br>in the wrong format.</blockquote><div><br>
This has been my experience as well. <br>
<br>
Personally, I rarely view 'doctests' as tests; any executable code I put into
docstrings is meant to be a part of documentation. Of course, it nice
that doctest/nose can make sure these code samples never get out of sync
with the code but these samlple are no substitute for extensive test suite.<br>
<br>
All my 'real' tests are separate python modules, written for nose/unittest framework.<br>
</div><br>
Max.<br>
<br></div><br>