The Problem Solver

Tell me and I will forget
Show me and I will remember
Involve me and I will understand
- Confucius -

Google Ads

This Blog

Syndication

Search

Tags

News





  • View Maurice De Beijer's profile on LinkedIn

Community

Email Notifications

Explore

Archives

Unit testing in Visual Studio 2005
One of the things I always disliked is that unit testing was only available in the enterprise VS2005 SKU, just like professional developers don't need or use unit testing. Yeah right, that is one of the hallmarks of a professional coder is you ask me. So I, amongst others, complained about this to Microsoft and it appears we have some influence because they have decided we are right Smile and the next version of Visual Studio will include unit testing in the professional SKU as well. Well what can I say other than a great big THANK YOU!
 
Hope I can blog more about stuff we are told this week but I am kind of doubting that as most, if not everything, of what hear will be under NDA.
 
Stay tuned for more though!
 
Published Sun, Mar 11 2007 18:16 by Maurice
Filed under: , , , , , ,

Comments

# re: Unit testing in Visual Studio 2005@ Tuesday, March 20, 2007 5:13 PM

In my experience, you're hardly missing out on much. NUnit (the free unit testing framework for .NET) still provides a better testing experience than the VSTS support.

The two places it does fall down are a lack of IDE integration, but that's cureable with TestDriven.NET, or just keeping NUnit running in the background - it's hardly heavy...

... and a lack of builtin coverage tools, but there's NCover for that purpose. Although, the usefulness of a coverage tool in test-driven development is fairly negligible - if its there, it's there because a test required it.

I use enterprise, and I still use NUnit. The `red/green bar` thing is critical for me.

--Chris

by chrisf