HTML report should have unit-test duration column released or bug ?

[Milan]

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.

[Charlie Poole (charlie.poole)]

The bug fix for 490869 was released in NUnit-Results 1.1. The bugs covered by a release are shown with the milestone, in this case at
  https://launchpad.net/nunit-results/+milestone/1.1

The fix changed from using the current date to using the current date and time. I agree that using the run datetime from the xml file makes much more sense.

[Milan (milan-vukoslavcevic)]

Hi Charlie,

here I was thinking of having list of all test cases(not in Index.html
there should be just Test Classes names and links to html with the
class test names) and duration of each in milliseconds like:

AdditionTest() PASS 0.23sec
SubstrTest() PASS 0.11sec
DBWrite() FAIL 2.45sec

so it is not about displaying test time of starting or ending test but
displaying duration of each unit test. Could this be consider as a new
FEATURE ? It would be extrem usefull/easy to have it since all info
are already in Result.xml file.

regards,
Milan.

On Thu, Dec 10, 2009 at 11:34 PM, Charlie Poole <email address hidden> wrote:
> The bug fix for 490869 was released in NUnit-Results 1.1. The bugs covered by a release are shown with the milestone, in this case at
>  https://launchpad.net/nunit-results/+milestone/1.1
>
> The fix changed from using the current date to using the current date
> and time. I agree that using the run datetime from the xml file makes
> much more sense.
>
>
> ** Tags added: easy
>
> --
> 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
>

[Charlie Poole (charlie.poole)]

Please don't pile new requests on top of one simple bug. If you need to ask for something new, add a new request or modify a *related* request. This seems to be a detail for your separate request about having a third level of detail (methods) in the reports.

Also, we should not use the bug list for discussions or Q&A - that's what the nunit-discuss forum is for. It is frequented by a large number of people who use and work on NUnit.

If you need more help in how to use the bug system, that's also a topic for nunit-discuss.

[Milan (milan-vukoslavcevic)]

Ok Charlie,

should I report having a list of all unit cases names with duration of each test as new Feature request ?

regards,
Milan.

[Charlie Poole (charlie.poole)]

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.

[Milan (milan-vukoslavcevic)]

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
>