How do I diagnose test errors?

[Martin Geisler]

"Peter Arrenbrecht" <peter.arrenbrecht at gmail.com> writes:

> On Thu, Jun 5, 2008 at 10:45 AM, Martin Geisler <mg at daimi.au.dk> wrote:
>> "Peter Arrenbrecht" <peter.arrenbrecht at gmail.com> writes:
>>
>>> Having a way to cite actual tested input and output in documentation
>>> would be great! (See http://arrenbrecht.ch/jcite/ for my take on
>>> this for Java.)
>>
>> I looked at the examples on your page -- is this not similar to the
>> standard doctest module in Python?
>>
>>  http://docs.python.org/lib/module-doctest.html
>
> Yes, I believe so, although I don't know how doctest handles setup
> code you don't want to cite, highlighting, etc.

No, there is no support for highlighting and such.

> And AFAIK doctest does not alert you to changed output (meaning you
> should inspect surrounding text for whether it is still accurate).

Checking the output against known good output is the whole idea of
doctest -- if something changes you get an error with the actual and
expected output shown.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.