Dieter Maurer wrote:
We use "pyUnit" extensively and are mostly satisfied.
There is one essential problem we hit more often: setting up
and tearing down can take excessive time.
Often, we are forced to abandon the test independence
and let a complete set of tests share the main part of the fixture.
"Grig" <[EMAIL PROTECTED]> writes on 28 Dec 2004 18:47:45 -0800:
> ...
> My own experience with pyUnit has been very satisfactory and for me
> personally pyUnitPerf scratches an itch.
We use "pyUnit" extensively and are mostly satisfied.
There is one essential
Roy Smith wrote:
"Grig" <[EMAIL PROTECTED]> wrote:
"Problem with porting patterns/api's from java straight to python is
that most of the outcome feels unpythonic. I'll not go about my own
feelings python vs. java here now, but I just want to point out that
there's already a rather large core of har
"Grig" <[EMAIL PROTECTED]> wrote:
> "Problem with porting patterns/api's from java straight to python is
> that most of the outcome feels unpythonic. I'll not go about my own
> feelings python vs. java here now, but I just want to point out that
> there's already a rather large core of hard-python
I just released a Python port of Mike Clark's JUnitPerf. I called it
pyUnitPerf and it's available at
http://sourceforge.net/projects/pyunitperf. It is in a very early stage
of development, but I think it's pretty usable (and useful) as it is.
I already received an interesting comm
