nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Please give one or two examples of how you would use this.

I have a little hesitation in giving this information to the test, since it
is actually info _about_ the test and separation of concerns seems to
call for it being part of the test runner or an addin rather than something
that the test itself reflects upon.

Charlie

On Tue, Mar 22, 2011 at 9:26 AM, Rechenelf <740304@xxxxxxxxxxxxxxxxxx> wrote:
> Public bug reported:
>
> In #611325 the introduced TestContext should also have performance information. I think the most important things are CPU cycles (not runtime!) and maximum of memory used by the last test.
> Perhaps num of used threads und their CPU cylcles and maximum stack size would be interested, too.
> A very good additional information would be, how often the test will be run and the number of the current run.
>
> Runtime ist not useful on current processors because can change the
> frequence. Since vista new functions are available for cpu cycles.
>
> Background: We make performance tests with nunit and the statistics.
>
> ** Affects: nunit-3.0
>     Importance: Undecided
>         Status: New
>
>
> ** Tags: testcontext
>
> --
> You received this bug notification because you are subscribed to NUnit
> Extended Testing Platform.
> https://bugs.launchpad.net/bugs/740304
>
> Title:
>  teardown performance memory
>

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/740304

Title:
  teardown performance memory

Status in NUnit Test Framework:
  New

Bug description:
  In #611325 the introduced TestContext should also have performance information. I think the most important things are CPU cycles (not runtime!) and maximum of memory used by the last test.
  Perhaps num of used threads und their CPU cylcles and maximum stack size would be interested, too.
  A very good additional information would be, how often the test will be run and the number of the current run.

  Runtime ist not useful on current processors because can change the
  frequence. Since vista new functions are available for cpu cycles.

  Background: We make performance tests with nunit and the statistics.