5

I have a component that reads some configuration from the standard .NET configuration (app.config) file.

when I run unit tests (NUnit) for this component (using TD.NET), i noticed that the configuration file is not read.

Upon inspection of AppDomain.CurrentDomain.SetupInformation.ConfigurationFile

I have noticed that its' value is set to C:\Users\ltal\AppData\Local\Temp\tmp6D2F.tmp (some temp random locaiton).

Is there a reason for why this is happening? (Is it NUnit or TD.NET's fault?)

I suppose i could set this SetupInformation object myself for the sake of the test, haven't tried yet, but still wondering why is it being created like that and not as default.

lysergic-acid
  • 19,570
  • 21
  • 109
  • 218

2 Answers2

3

  • To workaround this, you can create an app.config in your unit test project. This will then be called in place of the main app.config by your unit tests. You can then change values in that app.config in your unit tests making it easier to test different values and configurations i.e. you can setup your test app.config with certain values before running your test.

    ConfigurationManager.AppSettings[""] = "";

  • Another option might be to place settings in the Settings.setting file of your main project. You do not have to change anything in your unit test project then. Some links about the difference between settings and app.config - MSDN forums, StackOverflow, User Settings - MSDN

  • And of course a third option would be to remove the dependency on the app.config from your component by introducing an interface and inject the dependency into the component making it easy to mock it out and unit test.

Community
  • 1
  • 1
Peter Kelly
  • 14,253
  • 6
  • 54
  • 63
  • What is the difference between Settings and configuration? do you have a link regarding that? what should go where.. ? – lysergic-acid May 18 '11 at 15:44
  • Settings file is saved off to a location under C:\Documents and Settings and is typically used for user specific settings (such as background colors) that you want to change during runtime and possibly persist app upgrades. I would usually store things like connection strings in the App.Config file. Edited to include links. – Peter Kelly May 18 '11 at 15:50
1

By default the .NET runtime looks in the working directory of the AppDomain, which is being managed by NUnit in the temp location.

This link offers two solutions about how to get config files picked up:

http://blogs.msdn.com/b/josealmeida/archive/2004/05/31/loading-config-files-in-nunit.aspx

Basically, they need to live in the testing directory.

Adam Houldsworth
  • 63,413
  • 11
  • 150
  • 187