nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

"Thousands" is really not a lot of tests, unless you mean "hundreds of
thousands." So, if it's only a few thousand, you should look to the
nature of the tests themselves - for example, how you generate data for
the tests - for a solution.

For NUnit 3.0, we will move to loading on a separate thread, which
should show some improvement. We also expect to implement dynamic test
cases, where the data is only generated when the test is executed and
not at the time of loading.

Both of those changes are out of scope for NUnit 2.x, so i'm redirecting
this bug to the 3.0 project.

Charlie

** Project changed: nunitv2 => nunit-3.0

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/991930

Title:
  Performance starting NUnit Gui

Status in NUnit Test Framework:
  New

Bug description:
  NUnit 2.5.10 Gui Runner

  We are having a lot of tests, some thousands. The gui needs a long time to start, much longer than the test you want to run. I guess that the large amount at all and the large amount of calculated testcases may be responsible for that.
  Solution: Run through the expanded pathes, not all possible. Make the other ones when they are expanded by the user or the user decides to run the tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/991930/+subscriptions