I have a very large VS solution with many projects, code files, and tests.

I just added a new class to remove an XML element from an WCF XML message. I then added, of course, a test to verify the removal of the XML element.

I start the test using "Debug selected test..."

The "working" icon (I guess that's what you would name at the top of the Tests window turns red.

So it appears NCrunch is working.

I wait for several minutes* then VS debug session is started and a breakpoint is hit in the test factory.

I'm able to step through the code.

* I'm trying to time how long it takes to get to the test factory but it's now taking over 5 minutes. NCrunch seems to be working but never getting to actually running the test.
(I closed Tests window, disabled NCrunch, reopened Tests, enabled. Appears to be working now. )

I'm guessing NCrunch, based on your comments in previous posts, builds the test data for all tests and then runs the selected test.

This long startup time is certainly increasing my dev time and I'm getting less done than usual.

Just wondering if you have suggestions to speed this up.

I have moved a lot of code to separate class libraries with their own Test projects.


Thanks, Ed