So, I have been using NCrunch for a while now, and I liked it so much I had to buy it and I am now trying to get my company to get it for every developer.

My only issue is that I am not sure exactly the best way to configure NCrunch to do what I want.

NCrunch is working flawlessly for unit tests. So, we turned it on for our integration tests, which go against a database, require a logged on user, and use a security class that is linked between the logged in user and the database.

The problem is that NCrunch likes to run each test in parallel, and that is bad for our set of unit tests due to the static security class and the fact that we attach a new copy of our test database for run through of the integration tests. MSTest handles this just fine because we set up some deployment items and it deploys the assembly and runs all tests in the assembly.

I was able to get NCrunch to work by adding an ExclusivelyUses property to all my integration tests so they do not interfere with each other. But, now I have to attach a new database and set up our security context for each individual test It would be much nicer if I could get to NCrunch to run all those tests in the assembly using the same database and security context. Is that possible?

Bob

That is exactly what I am trying to do.

All of my integration tests are in the same project/assembly, or at least I only want one security context spun up for each project/assembly. Currently, I have each unity test marked with the ExclusivelyUsesAttribute, but I will move that up to the assembly level to save typing and insure that no developer forgets to add it.

It sounds like, though, that since I have this configured like this already, NCrunch should already be behaving this way? I haven't checked in a while, let me analyse the situation.

Thanks for the response!