[IPython-dev] How to organize test code

Fernando Perez fperez.net at gmail.com
Tue Jun 12 15:34:18 EDT 2012

On Tue, Jun 12, 2012 at 12:23 PM, Jörgen Stenarson
<jorgen.stenarson at kroywen.se> wrote:
> What do you think about rewriting this using a class and proper
> setUp/tearDown methods instead?

Sure!  To reiterate: a lot of our testing machinery is messy because
it was written in a desperate effort early on to get *some* testing
going, and IPython isn't the easiest beast to test (because you
basically are bootstrapping a 'vm inside a vm' for many practical
purposes).  So we cut quite a few corners just so that we'd have any
testing at all.

Any and all testing simplifications and cleanups are now welcome and a
good idea, even if they include completely shedding some of the old
stuff.  We're not emotionally attached to any of that code, as long as
we get solid test coverage, all punches are fair to throw :)



More information about the IPython-dev mailing list