Getting Started with SQL Server Database Unit Testing in SSDT

re: Getting Started with SQL Server Database Unit Testing in SSDT

Ded Medved — Thu, 16 May 2013 20:46:30 GMT

When is the custom static rules and custom refactoring support going to arrive in SSDT/VS2012.

I've made quite an investment of time and effort with these features in VS2010. I'd hate to think I can't carry it forwards into SQL Server 2012.

re: Getting Started with SQL Server Database Unit Testing in SSDT

Jonathan Burr — Fri, 15 Mar 2013 21:52:01 GMT

Is the Test > Windows > Test Explorer window (see below) available in VS Professional with SSDT 2012? I am able to get as far as defining test conditions but can't get to your next step. I am not sure that VS Professional has Test View or Test Explorer. Thanks

re: Getting Started with SQL Server Database Unit Testing in SSDT

Simon — Wed, 20 Feb 2013 09:54:50 GMT

This all works fine and when asked to to create a new test project when you create yuour first unit test create a the test project at the solution level. Which again all works well.

However if I try and move the test project into a more appropriate solution folder (i.e. 'UnitTests'). I then get an error when I try to add anew test, it states:

System.ArgumentException

Project with name Solution1.Server.UnitTest doesn't exist in solution

at Microsoft.VisualStudio.Data.Tools.Package.SharedUtilities.VsUtilities.GetProjectFromSolution(String projectName)

at Microsoft.VisualStudio.Data.Tools.Package.UnitTesting.UI.SqlUnitTestWizard.TryEnsureCorrectProjectImportsAndReferences(String projectName, String fileBeingOpened)

at Microsoft.VisualStudio.Data.Tools.Package.UI.DataPackage.OnIdle()

at Microsoft.VisualStudio.Data.Tools.Package.Project.VsPkgIdleProcessingComponent.FDoIdle(UInt32 grfidlef)

I have tried making the namesapces the same, as well as adding references but nonthing seems to fix this?

re: Getting Started with SQL Server Database Unit Testing in SSDT

Paul Arnold — Wed, 30 Jan 2013 17:05:53 GMT

Has anyone managed to get automatic deployment of projects working with the SSDT Unit tests when using composite projects?

re: Getting Started with SQL Server Database Unit Testing in SSDT

Bill Gibson MSFT — Sun, 06 Jan 2013 16:52:49 GMT

Hi Mikah, assuming that you are following the instructions above and using a VS Pro or higher edition, then the template should be visible. If you have Premium or Ultimate, then in VS 2010 SQL Server Unit Test template should be visible in the Add New Test dialog alongside the existing Database Unit Test - if this applies to you, do you see the old template?

Try running VS from the command line using the following, which will reset the default templates.

VS 2012 -> C:\>"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe" /ResetSettings

VS 2010 -> C:\>"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /ResetSettings

If this doesn't work then please describe the problem on the forum (link below), including a full description of the environment (edition and versions of VS and SSDT) and the steps you're using and what you see, and we'll try and resolve it with you.

Forum: social.msdn.microsoft.com/.../threads

re: Getting Started with SQL Server Database Unit Testing in SSDT

Mikah Trent — Sun, 30 Dec 2012 16:28:56 GMT

I am not finding the SQL Server Unit Test template. I have VS 2010, SSDT 2010, VS 2012, and SSDT 2012 and have not found the template anywhere. Any thoughts?

Thanks for the article!

re: Getting Started with SQL Server Database Unit Testing in SSDT

Bill Gibson MSFT — Mon, 17 Dec 2012 19:38:45 GMT

Denis, VS 2012 Pro is all you need in order to use SQL Server unit testing in SSDT. Obviously the Premium and Ultimate editions have many great features, but they are not specifically leveraged or required by SSDT.

re: Getting Started with SQL Server Database Unit Testing in SSDT

Denis Cilliers — Mon, 17 Dec 2012 14:09:39 GMT

Wow great idea, will try this out asap, and let you know how it goes.

Would you recommend the Premium edition of VS 2012 or would Pro do fine?