Performance starting NUnit Gui
Bug #991930 reported by
Rechenelf
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NUnit Framework |
Triaged
|
Wishlist
|
Unassigned |
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.
tags: | added: gui |
Changed in nunit-3.0: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in nunit-3.0: | |
status: | Won't Fix → Triaged |
tags: | added: github |
To post a comment you must log in.
"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