Back to issue list Export
Issue: 3e7eb3cf85967173a24e7287a22fc5b1538de9222343425284be42afd1c35b1e
Title:
Date: 2013-11-27 04:46:05
Reported_By: travisb
Seen_In_Build:
Severity: Blocker Critical Major Minor Trivial
Priority: 1 2 3 4 5
State: New Open Diagnosed Fixed Closed
Resolution: None Fixed Duplicate WontFix Invalid WorksForMe
Type: Bug Feature Regression
Owner: Unassigned travisb
Fix_By: Next_Release Eventually 1.0
Component: Documentation Test_Runner Integration UI Analyzer Vtty Stubs
Depends_On:
Dependent_Of:
Duplicate_Of:
Though we already get a total time taken for all the tests, that doesn't help you find the slow tests. Add timings on a per-test basis to provide this information.
It would also be useful if the timings could include how long the various setUp() methods and tearDown() methods take to run as well.
Though we already get a total time taken for all the tests, that doesn't help you find the slow tests. Add timings on a per-test basis to provide this information.
Date: 2013-11-27 04:50:58
User: travisb
It would also be useful if the timings could include how long the various setUp() methods and tearDown() methods take to run as well.