I'm seeing this error a lot:

SetUp : System.Configuration.ConfigurationErrorsException : The configuration file has been changed by another program.

followed by a path to a .config.ncrunchconfig file.

I'm getting the above error when ncrunch runs a lot of tests (eg when forcing re-run all or when ncrunch determines that the code I've changes potentially affects a lot of tests). Configuring ncrunch to not run my tests threaded reduces the error count but doesn't remove it completely. We have paid licenses for ncrunch based on our usage during the beta time period.

I'd REALLY appreciate this getting sorted out. My current project has around 3800 tests and the only resolution to this is to manually run the failing tests (sometimes I can run groups of 4-8 without issue, but still, if you have a hundred or so that are all failing for this reason, it's a bit of a PITA. This is a project I've inherited, and I have a feeling that there are some test assemblies that are referencing each other for shared functionality and perhaps the build process is modifying one of the assemblies after the tests for it have already kicked off? Just taking a stab in the dark here.

Hi

First of all, thanks for the response. I kind of forgot I posted this and came back here to post the problem again :/

To answer your questions:
1) I think so -- though I've only tried this once.
2) I get errors, but not as many
4) No
3) I have plenty of stack traces; they all quite similar, and now that I've read your answer, I think I know what was going on. We use Habanero to map our business objects and our tests spin up the required Habanero stuff at initialisation of each fixture. The default configuration storage for Habanero is, as far as I can tell, a file -- and the messages I'm getting back point at that file being the application config file. Creating a completely substituted settings manager using NSubstitute and making sure that's in use for every test fixture has resolved the issue.

I don't have any really good suggestions, but it would be nice if this error was a little easier to figure out: the error which comes back is that the .ncrunchconfig file has changed, not the app.config, so it seems as if NCrunch is getting lost; it's not immediately obvious that the problem is with tests themselves. It's especially difficult when working with a codebase you aren't familiar with. So perhaps can you add some messaging to that effect to the thrown exception? And also perhaps don't throw if the more recent file is actually unchanged (I know, this won't be trivial to solve) -- I'm actually quite sure that the file generated each time would have been the same.

Thanks again for replying (: