j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
On Mon, Feb 27, 2012 at 5:31 PM, Michael Foord email@example.com wrote:
On 27 February 2012 23:23, Mark Janssen firstname.lastname@example.org wrote:
On Mon, Feb 27, 2012 at 3:59 PM, Michael Foord email@example.com: >
As well as fundamental problems, the particular implementation of doctest suffers from these potentially resolvable problems:
Execution of an individual testing section continues after a failure. So a single failure results in the reporting of potentially many failures.
Hmm, perhaps I don't understand you. doctest reports how many failures occur, without blocking on any single failure.
Right. But you typically group a bunch of actions into a single "test". If a doctest fails in an early action then every line after that will probably fail - a single test failure will cause multiple reported failures.
The problem of being dependent on order of unorderable types (actually
very difficult to solve).
Well, a crude solution is just to lift any output text that denotes an non-ordered type and pass it through an "eval" operation.
Not a general solution - not all reprs are reversible (in fact very few are as a proportion of all objects).