Unit Testing Trickling into Pro!

Due to popular demand we have decided to add the majority of the unit testing features of Team System to the Pro Sku of Visual Studio.  With the release of Orcas, the support for authoring, generating and running unit tests, will become available to the users of the Pro Sku of Visual Studio. Pro customers will also take advantage of the some of the unit testing improvements we have added into Orcas, specifically generating for generics, performance improvements, the ability to unit test devices and better IDE integration (I’ll try my best to blog on the details soon). We are in general very open to the concept of trickling down other functionality introduced in Team System into other Skus over time, so please let us know if you feel that other items should trickle down as well. Keeping this pattern keeps us on our toes to ensure that we are always adding high value features higher up the stack. We love hearing your feedback and take your suggestions very seriously (I’m not just saying this - I have been continually surprised at how much time is spent on user’s feedback).


Again, we are very excited about the trickle down as we hope that it will introduce the concept of unit testing to the average .Net developer.  Our team hopes that every developer will see the major benefits of unit testing and will regularly author and execute the tests throughout the product life cycle.    


To the beta users: you may notice that a few pieces of the unit testing puzzle is missing from the Pro Versions of Beta 1 – specifically, authoring test lists, remotely executing tests and generating code coverage results.  We have been debating if some of these features should also trickle down and would be very interested in your feedback.  For example, the ability to author test lists has been excluded from the Pro Sku since many felt that its chief benefit comes to those which author test lists and run them as a part of a Build Verification Test prior to checking code into Team Foundation Server. Some, however feel that it is still convenient to organize tests in a list regardless of check-ins.  How do you feel? Does the test list editor (formerly called Test Manager) belong in Pro?  


Happy Unit Testing,


Comments (34)

  1. We are happy to announce that the Orcas Pro Sku will contain a the majority of the unit testing bits

  2. It was publically announced today on Naysawn Naderi’s blog that Unit Testing will be in the Pro SKU of

  3. Kevin Daly says:

    This is great news.

    I would say that the test list editor *does* belong in Pro.

    It’s useful to anyone who wants to manage their testing in a methodical way, irrespecitive of whether they’re using TFS.

    Getting these toos as widely distributed as possible will help to raise the quality of code overall, which in turn will help to promote the .NET Framwork and Visual Studio.

  4. stranger4u says:

    Really great news!

    And I would love to see code coverage being added to Pro as well.

  5. Naysawn Naderi has posted about Unit Testing Trickling into VS Pro:Due to popular demand we have decided…

  6. Hop hop, c’est vraiment la période des grandes annonces dans l’équipe Team System! Après le rachat de

  7. joejoejoe says:

    Test manager and coverage should both be included, and hopefully in a way that both encourages thier use and makes them easy to use (testdriven.net!)

  8. Rob Caron says:

    If you haven’t heard the news yet, Visual Studio Unit Testing, which was only available in some Team

  9. Buck Hodges says:

    Naysawn Naderi wrote a post today stating that many of the unit test features in Team System will be

  10. Visual Studioの単体テスト機能がProfessionalにまで拡大(Orcas)

  11. bendono@hotmail.com says:

    It’s nice that Pro will finally have unit testing. However, it really belongs in all versions, most importantly Express.

    Express targets learners and hobbyist. Very few beginners learn about unit tests until long after becoming proficient. This is backwards. It needs to be learned and integrated in the coding style at the very beginning.

    Of course there are alternatives. However, many, especially beginners, will not use them if they are not already available. Some of this is probably due to lack of awareness; some of it is probably due to lack of integration.

    So while I applaud your decision to include them in Pro, I really do not think it is enough. Note that your competition, such as Eclipse, includes integrated JUnit support in all versions (free). Perhaps Microsoft will reconsider it again post-Orcas.

  12. Due to popular demand, the unit testing features normally found only in Visual Studio Team System are

  13. prulifson says:

    Yes! Add the test list editor to VS Pro. The VSTS 2005 pattern where a developer has to purchase both Tester and Developer team editions to edit lists of tests is a major barrier adopting MS unit tests.

  14. Just to summarize some great new cool things that are happening in the team system space. First of all

  15. Dobré zprávy se jenom hrnou, podle neoficiálních (teď již polooficiálních) informací bude ve VS "Orcas"

  16. TSHAK says:

    +1 to everything that Brad Wilson said. The Visual Studio unit testing framework (MSTest) is moving into…

  17. According to Naysawn Naderi , VSTS PM for Developer Oriented Testing, "the majority of the unit testing

  18. Check out this blog post Due to popular demand we have decided to add the majority of the unit testing

  19. J.D. Meier on New Video: What Is – New in Team Foundation Server Source Control and New Video: What Is…

  20. On my TDD presentation in Microsoft I had last week I couldn’t resist to spending last 10 minutes of

  21. PeterBlomqvist says:

    Great news!

    I have to agree with the previous persons that has commented, it is vital to have the ability to manage your tests in a structured fashion since they tend to grow quickly in a mid to large size project.

    It’s a problem to justify the cost of having to purchase both the dev and test edition of VSTS to do this. So please add the complete package and not only the test parts.

  22. Dave Bost says:

    In another example of Microsoft listening to it’s customers, it was recently announced that the Unit

  23. поддержка юниттестов в Pro версии VS Orcas

  24. A ferramenta de unit testing antes exclusiva de algumas versões do VSTS será incluída na versão VS Pro

  25. technorabble says:

    I would suggest trickling the Code Analysis functions over to Architect edition.  Architects do/assist with code reviews in many environments, and these tools are critical to that role.  In addition the current group of Architect tools is pretty uhmm immature compared to the developer and test tools.

  26. Avec la prochaine version de Visual Studio (orcas), les fonctionnalités de tests unitaires seront inclus

  27. Doug Seven says:

    The best decision ever was recently made…the decision to move the most of the Visual Studio Team System

  28. 在 Orcas, 將 VS 2005 中只有 VSTS 才有的 unit test 放到 VS Pro 中了, 對於使用 VS Pro 開發程式的 developer, 往後做 unit test 就方便了.

  29. I’m at least a month late in linking to this, but if you’ve been paying very little attention it might

  30. ChrisDoesDev.com says:

    I would like to place a vote for adding code coverage into the Pro version.  At present, I use NUnit, and NCoverage.  It seems to me that providing test functionality without adding coverage information is providing half of the solution.



  31. 在 Orcas, 將 VS 2005 中只有 VSTS 才有的 unit test 放到 VS Pro 中了, 對於使用 VS Pro 開發程式的 developer, 往後做 unit test 就方便了

  32. On my TDD presentation in Microsoft I had last week I couldn't resist to spending last 10 minutes

  33. jeremy.wiebe says:

    I’ve read alot about the unit testing improvements coming in VS2008.  One of them being "performance improvements".  What I’ve found difficult is a good explanation of _what_ these performance improvements are.

    For example, does it run the tests on multiple threads?  What were some of the existing performance issues that are now solved?

  34. Geek Noise says:

    Unit Testing Makes it into VS-Pro (Finally)

Skip to main content