Quick & Dirty Compatibility

James Newkirk s Blog Quick amp Dirty Compatibility | Indoor Grills

James Newkirk s Blog Quick amp Dirty Compatibility | Indoor Grills — Mon, 01 Jun 2009 10:51:38 GMT

PingBack from http://indoorgrillsrecipes.info/story.php?id=4784

Ecco i link dati nel webcast di oggi su VSTS Team Developer

Lorenzo Barbieri @ UGIblogs! — Mon, 03 Apr 2006 23:37:58 GMT

Geek Notes 2004-06-24

Geek Noise — Thu, 24 Jun 2004 18:22:00 GMT

re: Quick & Dirty Compatibility

AT — Tue, 22 Jun 2004 13:34:00 GMT

Instead of commention out you can use

#ifdef VSNET
using Microsoft.VisualStudio.QualityTools.UnitTesting.Framework;
.....
#else
using NUnit.Framework
#endif

This way you will be able to work with both..
But as I've found - Microsoft Assert class is more powerfull. You can not get backward compatibility from Microsoft Assert to NUnit one.

As well you can use reverse code to use test classes generated by VS.NET in NUnit.
This sounds better becouse Microsoft attribute names are readable instead of SetUp and TearDown ;o)

#if VSNET
using Microsoft.VisualStudio.QualityTools.UnitTesting.Framework;
#else
using TestMethod = NUnit.Framework.TestAttribute;
using TestClass = NUnit.Framework.TestFixtureAttribute;
using TestInitialize = NUnit.Framework.SetUpAttribute;
using TestCleanup = NUnit.Framework.TearDownAttribute;
#endif

Convert existing NUnit test harnesses to VS Team System

Darrell Norton's Blog — Thu, 17 Jun 2004 17:42:00 GMT

Convert existing NUnit test harnesses to VS Team System

re: Quick & Dirty Compatibility

Mike — Thu, 17 Jun 2004 17:10:00 GMT

Thats nice and reassuring, but really why did they choose to deviate from the base Attributes that everyone has been using. If they wanted to add functionality they could have just extended those.

NUnit and VS Team System

Zinoblog — Thu, 17 Jun 2004 07:57:00 GMT

re: Quick & Dirty Compatibility

Simon Hodd — Thu, 17 Jun 2004 07:24:00 GMT

I used this method too (even throwing in an #ifdef so I can switch back and forth). But how do you handle the NUnit Ignore attribute?

James Newkirk on Quick

Rob Caron's Blog — Thu, 17 Jun 2004 04:03:00 GMT

re: Quick & Dirty Compatibility

Marc Clifton — Thu, 17 Jun 2004 01:55:00 GMT

Is there some reason Microsoft chose to implement brain dead unit testing?

What about http://aut.tigris.org/

What about http://www.codeproject.com/gen/design/autp5.asp

And why make unit testing available only for team test?