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.
Just trying to figure out what others are using to test their database procedures / queries, etc. Are you using the new Visual Studio extensions, custom code, etc? I need to some how formulate some unit tests, but not quite sure how I am going to build the tests so that we can easily regression test the procedures.
You have lots of options–as you’ve already mentioned–but for true unit testing you always want to get as close to the actual unit under test as possible in order to avoid letting integration concerns intefere with your tests. For database objects, this means using the Visual Studio database unit test projects and writing SQL to unit test the database objects, or using some sort of 3rd party SQL-based testing framework like DBUnit.
In some cases you may want to use Linq-to-SQL to perform some database unit tests more concisely/easily than can be done in SQL, but this should be avoided unless absolutely necessary for true unit testing; Linq-to-SQL (and any other custom code) introduces integration issues and extra layers, and so if you encounter an error, you will first have to make sure it truly is an error in your database and not in your Linq-to-SQL database connection, C# code (for example), etc.