[issue4080] unittest: display time used by each test case

2012-03-02 Thread Pawel Prokop

Pawel Prokop  added the comment:

I agree with Ezio, 
this feature should have an option to enable/disable.

Anyway, I use it in different way.

Since 2008, I've used this feature for performance comparision, whether some 
implementation changes in application code did not slow down application. Tests 
run after each commit. I compare execution time of particular test before and 
after commit.

With additional scripts, I create metrics and charts using gnuplot to visualize 
how execution time of each test changed during the development.
I can ensure the performance stability of the application.

--

___
Python tracker 
<http://bugs.python.org/issue4080>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue4080] pyunit - display time of each test case - patch

2010-07-19 Thread Pawel Prokop

Pawel Prokop  added the comment:

I think that a delay time of calling a decorator is not important, because this 
should be constant in each test execution, so no matter.
I shall be able to provide a patch in few days.
Thanks

--

___
Python tracker 
<http://bugs.python.org/issue4080>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue4080] pyunit - display time of each test case - patch

2009-11-14 Thread Pawel Prokop

Pawel Prokop  added the comment:

Repack of unittest was good idea. It is a patch against trunk, one test
case is provided and documentation update.

--
Added file: http://bugs.python.org/file15332/unittest_runTime.patch

___
Python tracker 
<http://bugs.python.org/issue4080>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue4080] pyunit - display time of each test case - patch

2008-10-08 Thread Pawel Prokop

New submission from Pawel Prokop <[EMAIL PROTECTED]>:

I've needed to measure each unit test running time
to measure the performance changing of each functionality
that every test case tests.
Latest version of pyunit has only displayed summary running time of the
suite, so I've implemented small enhancement to unittest.py that 
(in verbose mode) shows time of each test case run.
Maybe that would be usefull for anybody else?

--
components: None
files: pyunit_time.patch
keywords: patch
messages: 74545
nosy: pprokop
severity: normal
status: open
title: pyunit - display time of each test case - patch
type: feature request
versions: 3rd party
Added file: http://bugs.python.org/file11751/pyunit_time.patch

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4080>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com