Re: [Pyunit-interest] Modifications to PyUnit

[Stephen P. <ste...@ya...>]

Nathan R Heagy wrote:
> 
> The only reason I put it in the Constructor for TestSuite is because
> this is where I thought I found it in JUnit. That's it.

I think there are good arguments on both sides. I suspect that the best
place for such code depends upon how often TestSuite is likely to get
subclassed.

> >3.) There are complications with reloading modules -- see the recent
> >discussions on the list between Shae and myself. To reload the test
> >module is not enough to ensure that the tested module is reloaded too.
> 
> That is true. It's something I'll be working on for sure. I do have a few
> ideas though. My background is in perl, so I'm not sure how easy or 
> natural this would be in python:

Off hand response: "At least as easy as in perl."  <grin>

> [backticks etc.]

This is probably not the simplest way to do things. Looks like some
smart combination of __import__ and the 'imp' and 'rexec' modules is the
simplest* solution, but hardly the most obvious.

* Note: simplicity is here measured in lines of code and maintainability

The CGI test runner idea is a cool one. Talk about a cross-platform GUI!
Perhaps even a test server based on the standard library's
BaseHTTPServer would be interesting; any way that could be used to embed
testing capabilities in a larger environment is inherently interesting.
I know some Zope people are crying out for that kind of embedded test
functionality.

Best wishes,

-Steve

_____________________________________________
Steve Purcell,  Technical Director, Inkontact
Get in touch at http://www.inkontact.com/