Home/ Questions/Q 105215
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T01:24:15+00:00

I am trying to start a new MVC project with tests and I thought

  • 0

I am trying to start a new MVC project with tests and I thought the best way to go would have 2 databases. 1 for testing against and 1 for when I run the app and use it (also test really as it’s not production yet).

For the test database I was thinking of putting create table scripts and fill data scripts within the test setup method and then deleting all this in the tear down method.

I am going to be using Linq to SQL though and I don’t think that will allow me to do this?

Will I have to just go the ADO route if I want to do it this way? Or should I just use a mock object and store data as an array or something?.

Any tips on best practices?

How did Jeff go about doing this for StackOveflow?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I checked out the link from tvanfosson and RikMigrations and after playing about with them I prefer the mocking datacontext method best. I realised I don’t need to create tables and drop them all the time.

    After a little more research I found Stephen Walther’s article http://stephenwalther.com/blog/archive/2008/08/17/asp-net-mvc-tip-33-unit-test-linq-to-sql.aspx which to me seems easier and more reliable.

    So I am going with this implementation.

    Thanks for the help.

    • 0