<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d13405220\x26blogName\x3dPavan+Podila\x27s+Blog\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://pavanpodila.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://pavanpodila.blogspot.com/\x26vt\x3d-3240902251102105728', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Saturday, June 11, 2005

Will Team System 2005 render NUnit useless?

Previously the most widely used tool for Unit testing with C# was NUnit. However with the introduction of the Team System 2005 by Microsoft, TDD has become tigthly integrated. It is now possible to do a wide variety of tasks:

  1. Point and click Test stub creation
  2. Visualize the code coverage
  3. Integrated Test Manager (TestRunner)
  4. Custom test list creation
  5. Both Manual and Automated testing support
  6. .... probably some more that I have missed
With such an integration, I wonder if any C# developer would continue using NUnit. Probably only to support the existing tests. But any new development will most probably use the Team System tools. The testing tools already look promising and they should only get better by the November 7 release of Visual Studio 2005.