launchpad-dev team mailing list archive

[John Meinel <john@xxxxxxxxxxxxxxxxx>]

IIRC, there used to be a magic variable you could set (on the module?), and
unittest would then omit/stop the traceback at that point. I think there was
discussion about even having a function local magic variable. What mechanism
did testtools go with?

John
=:->
On Aug 15, 2011 8:23 AM, "Robert Collins" <robertc@xxxxxxxxxxxxxxxxx> wrote:
> On Mon, Aug 15, 2011 at 5:47 PM, Jeroen Vermeulen <jtv@xxxxxxxxxxxxx>
wrote:
>> Just throwing an idea out there for our maintenance squad(s), or whoever
>> might be interested:
>>
>> When a test assertion fails, wouldn't it be great if the traceback could
>> stop at the failed assertion?  Rarely if ever am I interested in the call
>> stack inside TestCase.assertEqual, a matcher, etc.
>
> The next release of testtools does this.
>
> _rob
>
> _______________________________________________
> Mailing list: https://launchpad.net/~launchpad-dev
> Post to : launchpad-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~launchpad-dev
> More help : https://help.launchpad.net/ListHelp