Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am trying to start unit testing an MVC2 project, which uses the Entity Framework. When I run my “hello world” test, it fails saying this:
The specified named connection is
either not found in the configuration,
not intended to be used with the
EntityClient provider, or not valid.
How can I pass the connection data (which were generated by the Entity Framework and are in the main Web.config) to the testing project?
Thanks
Depending on what unit testing framework you use you could try adding an app.config to your test-project with the right settings for EF. This works with xUnit.Net and I’m pretty sure most other test-frameworks also support this.
For completeness I do need to warn you that tests that touch the database aren’t unit-tests but integration tests. Those are useful too but can become a hassle to maintain when your code changes. It’s usually a good idea to test small pieces of code in isolation, this gets around problems like you describe because you won’t need to access the database at all.