Can an NUnit project load a separate *.config for each assembly that it loads?

Question

If so, how?

If not, what is the best workaround? Particularly, I'm trying to automate running unit tests in the GUI test runner on arbitrary developers' machines.

Answer 1

The best solution is to make the classes you want to unit test accept configuration settings in their constructors rather than read them from configuration files.

Make callers responsible for obtaining configuration data: decouple your classes from specific configuration sources and eliminate hidden dependencies in one fell swoop.