Using NUnit CPU is very large - How to resolve?

For numerous unrelated projects, the use of the NUnit processor often ends by about 50%, even when I don't run my tests. From the other information I read, this is more likely to be related to my code than to Nunit.

Does anyone know how I can isolate problems in my code that will cause this and fix them?

thanks

+4
source share
1 answer

I have the same problem, and it seems to have a fairly consistent effect on only one test project that performs integration testing (calling web services, checking content via HTTP, etc.). I am very careful to get rid of network objects (using using(...){ } ), so I don’t quite understand why NUnit should continue to use 90% of the processor days after the test is completed, and all objects used during testing should to be deleted.

It is really strange that when running the test, NUnit uses no more than 10% -50% CPU. This is only after the test has finished loading the processor and constantly remains at the level of 80% -100% forever. This is really weird. Rebooting or closing the test project (File> Close) does not help either. NUnit itself must be closed.

+1
source

All Articles