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,
Naysawn
We are happy to announce that the Orcas Pro Sku will contain a the majority of the unit testing bits
It was publically announced today on Naysawn Naderi's blog that Unit Testing will be in the Pro SKU of
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.
Really great news!
And I would love to see code coverage being added to Pro as well.
Naysawn Naderi has posted about Unit Testing Trickling into VS Pro:Due to popular demand we have decided...
Hop hop, c'est vraiment la période des grandes annonces dans l'équipe Team System! Après le rachat de
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!)
If you haven't heard the news yet, Visual Studio Unit Testing, which was only available in some Team
Naysawn Naderi wrote a post today stating that many of the unit test features in Team System will be
Visual Studioの単体テスト機能がProfessionalにまで拡大(Orcas)
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.
Due to popular demand, the unit testing features normally found only in Visual Studio Team System are
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.
Just to summarize some great new cool things that are happening in the team system space. First of all
Dobré zprávy se jenom hrnou, podle neoficiálních (teď již polooficiálních) informací bude ve VS "Orcas"