# from Michael Peters
# on Thursday 06 September 2007 01:49 pm:
>Ovid wrote:
>> Thanks for reminding me. Another bit of meta-information that
>> should be optionally supported in the TAP YAML output is "duration".
>> If one's comparing the behavior of a test suite over time, some
>> might find it beneficial to know that they've added 10% more tests
>> but increased the time it takes to run those tests by 300%. Of
>> course, this is a *very* sketchy metric and not one I would be too
>> keen on relying on, but some might value it.
>
>Smolder uses duration, but it does it by having the start time and end
> time. If we want to be able to package up a test runs results and
> send it somewhere else, it would be nice if we could get the original
> run time of the tests. Duration can be calculated from that.
What's that calculation look like? From what I've seen, we currently
only have the harness start/end times.
Maybe I'm unclear, but it sounds like something is going to break when
the archive is constructed of tests which were run in parallel and then
aggregated together.
If we're going to calculate duration, it needs to be per-test.
--Eric
--
Anyone who has the power to make you believe absurdities has the power
to make you commit injustices.
--Voltaire
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
