Hi, thanks for the suggestions!

I'll make a note about adding an option to pin all tests in the current file. NCrunch currently isn't scope aware within editor windows - so this is probably the closest I can get at the moment and it seems like a really good idea.

NCrunch does actually have the capability to pin unexecuted tests. You'll notice that after you write a new test and the project is built, a faded green 'arrow' will appear next to the first line of the test. This arrow can be used to perform context sensitive actions against the test in the same way as any executed line of code (i.e. pinning, ignoring, etc).

The key problem here I think you're experiencing is that because your project takes so long to build with NCrunch, you won't see the green arrow until a good 30 seconds after you've finished authoring the test stub and the project is actually able to compile. NCrunch doesn't make use of a metadata model in the same way as refactoring tools do - it instead relies on the output from the build process in order to find tests. This makes it impossible to locate a test without first completing a build.

As such, I'd like to learn a bit more about what may be contributing to your high build times and see if there are options to solve this. Reducing build times is a major long term goal of NCrunch and 30 seconds is definitely longer than I'd feel comfortable when working on a project myself. How long does this project usually take to build without NCrunch? Do you notice a significant improvement in performance if you turn off the 'Instrument output assembly' option for the project?


Cheers,

Remco