[py-dev] Gitting rid of "(inconsistently failed then succeeded)" ?
Carl Friedrich Bolz
cfbolz at gmx.de
Mon May 4 23:46:38 CEST 2009
Brian Dorsey wrote:
> On Tue, Apr 28, 2009 at 6:03 AM, Laura Creighton <lac at openend.se> wrote:
>> In a message of Tue, 28 Apr 2009 13:40:36 +0200, holger krekel writes:
>>> E: AssertionError: (assertion failed, but when it was re-run for
>>> printing intermediate values, it did not fail. Suggestions:
>>> compute assert expression before the assert or use --nomagic)
>> Looks great to me. :)
> Quick thanks to Philippe for bringing this up and to everyone else for
> taking the time to carefully work on this error message. It seems like
> a small thing, but having a good error message in places like this is
> the difference between taking a moment or two to change a test vs.
> hitting a wall with py.test and maybe giving up entirely.
I agree. I actually had to explain this to students during the exercises
for our lectures once or twice, so a clear error message should
definitely improve things.
More information about the Pytest-dev