Question

I have an ASP.NET MVC project that I would like to unit test. Most of the functions rely on a call to our database, who’s connection string is defined as:

connStr.ProviderConnectionString = Web.Configuration.WebConfigurationManager.ConnectionStrings("ApplicationServices").ConnectionString

Is there some way to easily test this without making each unit test fire off the dev server with:

 <TestMethod(), _
 HostType("ASP.NET"), _
 AspNetDevelopmentServerHost("C:\Users\tyler.HQ\Development\LateralSports\Dev\Dev\Site", "/"), _
 UrlToTest("http://localhost:57110/")> _

Using the HostType allows the unit tests to run, but it is super slow.

Is there some configuration parameter I can swap around?

Thanks

Answer 1

You really should find a better way to get at the connection string. Options include:

• Use the normal System.Configuration.ConfigurationManager rather than whatever that thing is.
• Use dependency injection to abstract it away.
• Avoid the DB in unit tests entirely — it is a bit of an infrastructure concern after all.