Comment 6 for bug 495049

Hi Charlie,

Purposed is to add TestResult.xml time to HTML.

The bug starts with the time of the run but by my mistake I thought
you talk about duration of each unit test. Sorry for that. So as I
wrote before (in Bug 491484) this Bug #495049 can be closed.

Br,
Milan.

On Sat, Dec 12, 2009 at 3:00 AM, Charlie Poole <email address hidden> wrote:
> I'm confused... the bug description starts talking about listing the time of the run and then adds comments about test duration.
> Is the purpose of this bug to add test duration or to add the current time to the reports?
>
> In future, it will be helpful to limit bug reports to discussing one
> thing. For example, if you had a question about the implementation of
> the current time request, they you would add it as a comment to that
> bug, not to a new one!
>
> Please don't make a new request! Just clarify what you want from this
> one.
>
> --
> HTML report should have unit-test duration column released or bug ?
> https://bugs.launchpad.net/bugs/495049
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in NUnit Test Result Reporting: New
>
> Bug description:
>
> Although already discussed under here under
>
> "HTML Reports should contain the time of the run
> NUnit-Results Bugs Bug #490869"
>
> and released I did not found mention feature in release nunit-results-1.1-bin.zip, in what version is it released ?
>
>
> Hi Uniters,
>
> as tester I would need one more information written in HTML Report files and that is duration of every NUnit test. There are attributes which can be used for testing if test case took more than X second but I would need not just end result PASS FAIL (smaller or bigger than some time) but in order to track bug-fixes and its influence on the performance for every test (for those having noting to do with performance too) I would need one more column in the HTML report where would be written how much time unit test took.
> That information is already present in the TestResult.xml (there is some "time" written for every test, right?) so just extracting it and writing to HTML should not takes too much time (for those familiar with NUnit-Results) but it would bring one new FEATURE and much better tester experience.
> Althought some unit tests are not impotrant to be fast it is good to know how much they took so later just by looking at time needed some unit tests to be executed can be found some problematic functions/test.
>
>
>
> Best regards,
> Milan.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/nunit-results/+bug/495049/+subscribe
>