Postponed
Project:
Project Issue File Review
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Jun 2011 at 14:00 UTC
Updated:
25 Feb 2012 at 00:39 UTC
It just doesn't make any sense that we don't capture duration for test runs. This is not great performance information, but we should at least capture the information and make historical information available.
Now that we're on a *relatively* homogenous environment, the numbers might mean something. Really the averages are only a little useful. But I just don't think we can skip having them.
Comments
Comment #1
catchThis would be great to have, we can't rely on it, but even if it only catches issues that make test runs slow (or confirms testing performance improvements) that would be enough reason to do it.
Comment #2
rfayin reality this is probably a Simpletest issue first... which makes it a core issue first... Which probably means we should get something into simpletest quickly. I created #1205162: Simpletest should report test duration for individual tests and for the entire run in the Drupal 8 (simpletest) queue.
Comment #3
jthorson commentedPostponed pending #1205162: Simpletest should report test duration for individual tests and for the entire run.