How to Unit Test a missing .NET ConfigurationSection

Question

If I have code like this:

        public XALServiceConfiguration CreateInstance()
        {
            var config = ConfigurationManager.GetSection(ConfigurationSectionName) as XALServiceConfiguration;
            if (config == null)
                throw new ConfigurationErrorsException("Configuration element 'xalService' was not found or is not of correct type.");
            return config;
        }

How can I test that the exception is thrown if the section is missing from the configuration file ? For other tests, the configuration section needs to be in the config file, so I cannot actually remove it from the file.

I am using the Visual Studio 2008 Unit test framework.

Jon Skeet · Accepted Answer · 2008-11-25 07:27:37Z

2

I think the other answers so far have missed the point of your question, which is how to provoke the exception.

Using a static technique like this, you really can't easily do it - you'd have to have a way of injecting the particular configuration into your test. I seem to remember that the .NET configuration management isn't particularly amenable to this, but I think it can be done. I don't have easy MSDN access right now, but try to find some way of loading an instance of a configuration instead of accessing it just with static methods. I may be wrong - there may be no way of doing it.

Don't worry too much about 100% coverage - sometimes there are just conditions which are infeasible to test, unfortunately :(

answered Nov 25, 2008 at 7:27

Jon Skeet

1.5m893 gold badges9.3k silver badges9.3k bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Christian.K · Accepted Answer · 2008-11-25 07:54:06Z

2

You could run the testcase in a separate application domain. For such you can specify the configuration file to use, or even specify the configuration file as "bytes" (see AppDomainSetup Structure)

answered Nov 25, 2008 at 7:54

Christian.K

49.6k10 gold badges108 silver badges155 bronze badges

1 Comment

Jon Skeet Over a year ago

Nice. It's a pretty painful thing to do (and for a single test I'd probably not bother) but +1 for explaining how it can be done :)

tsimon · Accepted Answer · 2008-11-25 07:05:05Z

1

Just to make Slace's answer a bit more clear, it would look like this:

try {
  XALServiceConfiguration config = CreateInstance();
} catch (ConfigurationErrorsException cee) {
  Assert.Fail("Could not create XALServiceConfiguration: " + e.Message);
}

It's not great (as you are not explicitly testing the null situation. If you want to go to that step, you might have to create your own config loader and then test that against a different config with a known missing section.

answered Nov 25, 2008 at 7:05

tsimon

8,0202 gold badges34 silver badges44 bronze badges

Comments

Aaron Powell · Accepted Answer · 2008-11-25 06:57:54Z

0

You could just catch the exception in a try catch statment and do an Assert in the catch.

answered Nov 25, 2008 at 6:57

Aaron Powell

25.1k18 gold badges102 silver badges150 bronze badges

Comments

Ducati007 · Accepted Answer · 2013-03-22 07:43:00Z

0

This is a good implementation for testing Config sections http://www.codeproject.com/Articles/71843/Unit-Testing-your-App-config-and-ConfigurationSect

answered Mar 22, 2013 at 7:43

Ducati007

2751 gold badge5 silver badges15 bronze badges

Collectives™ on Stack Overflow

How to Unit Test a missing .NET ConfigurationSection

5 Answers 5

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related