[TIP] pytest-2.0: asserts++, unittest++, reporting++, config++, docs++

Phlip phlip2005 at gmail.com
Fri Nov 26 18:02:42 PST 2010


On Fri, Nov 26, 2010 at 3:31 PM, holger krekel <holger at merlinux.eu> wrote:

> It comes from Python frame objects. And yes, you can use "py.test -l" to show
> local variables. Or "--pdb" to start an interactive debugger.  If there were a
> web interface you could probably click on it and see variable names and values
> :)

Then why can't the diagnostic reflector use them? I thought you
implied the reflector had to re-evaluate them. (That's how both
assert{ 2.0 } and Wrong do it, in Ruby, with less reflection support.)

> Heh, i am often debugging failing tests :)

I debug them as often as possible via git reset --hard HEAD. My
favoritest git command EVAR!



More information about the testing-in-python mailing list