Re: [Pyunit-interest] Modifications to PyUnit
Brought to you by:
purcell
From: Nathan R H. <na...@he...> - 2000-06-04 07:36:14
|
>Hi Nathan, > >The GUI looks cool; thanks for sending it in. I have a few comments >overall, which may or may not help you: Thanks for the quick response! >1.) The ability to create a TestSuite instance from a TestCase class >containing conventionally named methods is actually already provided by >the outboard function 'unittest.makeSuite()'. I think I prefer this to >altering the TestSuite constructor. 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. >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: Execute a new instance of the TestResult as a seperate program and parse the results. In perl I would use backticks to do this. Then the main problem is keeping track of current working directories and program location. The other possibility I'm looking at is creating a CGI version with a HTML form GUI. This is what I did with php, and it worked quite well. Nathan R Heagy . . . . . . . . . . . . . . Blow Your Beef Away http://cowcomics.com |