Wed Mar 8 20:46:26 2006
Ticket #2 (Closed: fixed)
implement profiler plugin
| Priority: | normal | Reporter: | jpellerin |
|---|---|---|---|
| Severity: | normal | Assigned to: | jpellerin |
| Component: | nose:plugin:profile | Status: | closed |
| Version: | 0.9a1 | Resolution: | fixed |
| Milestone: | 0.9a1 | Keywords: | enhancement |
Description by jpellerin:
Plugin should be a Watcher that outputs a profiler report after test run. Possibly exclude test packages from report, have a --profile-package argument (like coverage plugin).
Changelog
Wed Mar 8 20:46:54 2006: Modified by jpellerin
- status changed from new to assigned
Fri Mar 17 21:26:37 2006: Modified by jpellerin
- milestone cleared
- version changed from 0.9a1 to 1.0
Fri Mar 17 21:28:03 2006: Modified by jpellerin
- milestone set to 1.0
Thu Mar 23 21:23:22 2006: Modified by jpellerin
- milestone changed from 1.0 to 0.9a1
- version changed from 1.0 to 0.9a1
Thu Mar 23 22:10:11 2006: Modified by jpellerin
- resolution set to fixed
- status changed from assigned to closed
Basic implementation in [13]
This is going to be a bit more difficult than I had anticipated. For hotshot to work, it has to wrap at least the initial runtests call -- and really, to focus the profiling on the code being tested and not on nose itself, the profiler runcall() method ought to be used to wrap only individual test cases runTest() calls. Not sure how to do that without horrible monkeypatching, so kicking this plugin to 1.0.