Pierre Rouleau wrote: >Hi all! > >I'v just started looking into py.test. I really like it: it's easier >to use and requires less boiler plate code than unittest. Thanks! > >However, i found that it runs much slower than unittest (at least >under some conditions). I was expecting a slowdown because of >py.test's nature, but I get results that are 10 to 30 times slower. > >I ran a test of a simple application that converts roman numeral to >integer and vice versa (taken from Mike Pilgrim's >http://diveintopython.org/ ). >In a test that checks all 4999 possible numbers, unittest performs in >about 125 mSeconds, while py.test takes about 3.8 seconds. That's 30 >times slower. >The unittest and py.test driven scripts perform the same tests. > >Is this what I should expect? > >I am running Python 2.4.3 on Win32 machine with py-dist revision 34574 >(the latest) from svn. > >Thanks, > >Pierre Rouleau >_______________________________________________ >py-dev mailing list >py-dev@codespeak.net >http://codespeak.net/mailman/listinfo/py-dev > > I would be happy to run some performance tests on my machine and profiling as well. Please send to me some details (how to access the code ie.). Please also note that a lot of time from that 3.8s is startup time (I guess it's not too much pain to just allow it to be about 2s).
_______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
