Repository navigation
unittest: display time used by each test case #48330
Description
| BPO | 4080 |
|---|---|
| Nosy | @rhettinger, @giampaolo, @ezio-melotti, @merwok, @voidspace |
| PRs | |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2008-10-08.20:28:15.274>
labels = ['tests', 'type-feature', 'library', '3.9']
title = 'unittest: display time used by each test case'
updated_at = <Date 2020-02-16.12:49:33.700>
user = 'https://bugs.python.org/pprokop'bugs.python.org fields:
activity = <Date 2020-02-16.12:49:33.700>
actor = 'giampaolo.rodola'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Tests']
creation = <Date 2008-10-08.20:28:15.274>
creator = 'pprokop'
dependencies = []
files = ['11751', '15332']
hgrepos = []
issue_num = 4080
keywords = ['patch']
message_count = 17.0
messages = ['74545', '87989', '95253', '109448', '110692', '110800', '110883', '154650', '154678', '154687', '154769', '154771', '154776', '155721', '176157', '337648', '362067']
nosy_count = 8.0
nosy_names = ['rhettinger', 'techtonik', 'giampaolo.rodola', 'ezio.melotti', 'eric.araujo', 'pprokop', 'michael.foord', 'piotr.dobrogost']
pr_nums = ['12271']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue4080'
versions = ['Python 3.9']
Activity
pprokop commentedon Oct 8, 2008
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?
voidspace commentedon May 17, 2009
Needs test and documentation. Otherwise looks good.
pprokop commentedon Nov 14, 2009
Repack of unittest was good idea. It is a patch against trunk, one test
case is provided and documentation update.
ezio-melotti commentedon Jul 7, 2010
The idea is interesting, but I would prefer to have a way to enable/disable this feature (and maybe even specify its format, e.g. the number of decimals). Moving the logic to an external function (possibly used as a decorator) might avoid some code duplication, but OTOH it would probably slow down the execution and the timing a little (I'm not sure that matters though).
BreamoreBoy commentedon Jul 18, 2010
Pawel, could you please provide an update wrt Ezio's comment on msg109448, thanks.
pprokop commentedon Jul 19, 2010
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
voidspace commentedon Jul 20, 2010
I am in the process of creating an extension mechanism for unittest which will make adding this sort of use case to unittest much easier. *Even* if it is added to the core it should be in the form of an extension (plugin) so please don't update the patch until this is in place.
piotrdobrogost commentedon Feb 29, 2012
@michael Foord
How is it going?
[-]pyunit - display time of each test case - patch[/-][+]unittest: display time of each test case[/+]rhettinger commentedon Mar 1, 2012
I think this would be a useful feature.
voidspace commentedon Mar 1, 2012
Yes, it would definitely be useful (as would a count of how far through the test run we are [27/129] style). Getting to completing (even for testing) the "extensible" unittest is something I will still do (and nose2 is being built off the prototype work I did), but isn't going to happen immediately - so it's not a good reason to hold up these improvements.
I'll be sprinting at PyCon and look at this issue then.
I'm keen to avoid proliferating command line parameters to the unittest test runner. Ezio - why would you want to disable this feature?
ezio-melotti commentedon Mar 2, 2012
Because it looks like line noise and doesn't provide an useful information in most of the cases (at least for me), see e.g.:
+ test_format (main.MyTestCase) ... [0.000612s] skipped 'not supported in this library version'
+ test_nothing (main.MyTestCase) ... [0.000486s] skipped 'demonstrating skipping'
+ test_windows_support (main.MyTestCase) ... [0.000090s] skipped 'requires Windows'
It might still be useful to find the slowest test(s), or for test suites that take a long time (so I'm not opposed to having it as an option that can be enabled if needed), but for most of the tests it will just show an almost meaningless fraction of second.
9 remaining items
giampaolo commentedon Feb 16, 2020
I updated the PR for Python 3.9. I think it's ready to be merged. Can someone involved in unittest take a look at it?
pythongh-48330: assert warning is emitted on unittest.TestResult with…
gh-48330: assert warning is emitted on unittest.TestResult with no ad…
pythongh-48330: assert warning is emitted on unittest.TestResult with…
00398: pythongh-48330: assert warning is emitted on unittest.TestResu…
gh-48330: address review comments to PR-12271 (#103209)
Merge branch 'main' into superopt
Merge branch 'superopt' into superopt_spec
hugovk commentedon Nov 27, 2023
Closing, the PR has been merged: #12271 👍