On 11/14/06, Carl Friedrich Bolz <[EMAIL PROTECTED]> wrote: > Pierre Rouleau wrote: > > ---------- Forwarded message ---------- > > From: Pierre Rouleau <[EMAIL PROTECTED]> > > Date: Nov 14, 2006 4:18 PM > > Subject: Re: [py-dev] Speed of py.test compared to unittest > > To: Maciek Fija�kowski <[EMAIL PROTECTED]> > > > > > > On 11/14/06, Maciek Fija�kowski <[EMAIL PROTECTED]> wrote: > >> Sure. Please do. > >> > > Oh, also, as far as startup time is concerned, even though the startup > > time might be constant, a larger startup time will mask differences in > > execution time of the code under test. Since a unit test system > > should optimally be used during development, a startup time close to 0 > > will show timing impact of the code being tested as it is being > > modified. And this might be useful during development (even though > > you might want to measure performance of the module being developed > > using other tools). > > I am not quite sure I buy that argument since py.test tells you the time > that the test itself took (if you use the -v argument) or that all tests > together take (at the end of each test run). As far as I remember, these > times don't include any startup times. Yes, wall clock time of the whole > test run is quite a bad measure, but you don't have to use it anyway. > > Cheers, > > Carl Friedrich > I didn't realize that the time of *each* test is shown when the -v option is used. Thanks for pointing that out.
P.R. _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
