What’s new in Test and Lab Management in VS 2010 Beta 2
Visual Studio 2010 Beta 2 is now live, and we have updated the Beta2 landing page to point to the publicly available downloads. Early reaction from our MSDN customers and MVPs has been very positive. The Beta 2 release is also a “go-live” release – that it, the product is ready enough that we are licensing the product for developing and deploying production applications. You can read more about what it means to go-live from Jeff Beehler’s post on the topic.
In my product team, we are actively working with a set of customers who have chosen to go-live with our Test and Lab Management Products. Please post a comment on this blog if you are interested in going live with the VS 2010 Beta 2 product.
In this post I want to highlight the changes that you will see in Beta 2, focusing on the Test and Lab Management capabilities.
One of the most significant changes is on the packing front. We have finalized the SKU structure for the VS 2010 release, and it is a marked simplification from the many different SKUs we had in VS 2008 which made the buying decision quite complex. With the 2010 release, we are moving to a simple nested-model of capabilities which you can think of as three variants – good, better, and best. The picture below shows the three variants.
![clip_image002[6]](https://msdntnarchive.z22.web.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_msdn/amit_chatterjee/WindowsLiveWriter/WhatsnewinTestandLabManagementinVS2010Be_CAE1/clip_image002%5B6%5D.jpg "clip_image002[6]")
At the lowest level you have the good – the VS 2010 Professional SKU with or without MSDN. These are the tools for basic development tasks. The “better” is the VS 2010 Premium SKU which offers a complete toolset that allows developers to deliver scalable, high quality applications. Finally, the “best” builds upon this theme and provides a comprehensive suite of application lifecycle management tools for teams. The next diagram below gives you a sense of how the capabilities build up from the good to the best. I have marked off those feature sets that are targeted for testers (or valuable for testers) with red boxes.
There are some additional products in the VS 2010 family that are shown below – these are particularly important for testers. The Visual Studio Test Elements SKU is essential for anyone engaging in test case management or manual test execution in the development cycle. All of the functionality of this SKU, by the way, is also included in the VS 2010 Ultimate SKU as well. The Lab Management product enables teams to configure and manage virtual lab environments. All of these capabilities are of course built on top of the Team Foundation Server product.
A high level diagram which shows were the features land in the different client side SKUs is shown below
In the backdrop of the above changes in the SKU and packaging, let me now tell you about the key changes you will see in the Test and Lab Management products in Beta 2 that are new or improved over the functionality we had in the Beta 1 release.
The table below shows all of the features and capabilities for our Test product that is new or changed in Beta 2
![clip_image009[5]](https://msdntnarchive.z22.web.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_msdn/amit_chatterjee/WindowsLiveWriter/WhatsnewinTestandLabManagementinVS2010Be_CAE1/clip_image009%5B5%5D.png "clip_image009[5]")
The next table shows the improvements in the Lab Management product for Beta 2
![clip_image010[5]](https://msdntnarchive.z22.web.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_msdn/amit_chatterjee/WindowsLiveWriter/WhatsnewinTestandLabManagementinVS2010Be_CAE1/clip_image010%5B5%5D.png "clip_image010[5]")
You will see a lot of blog activity from team members soon, as they talk about their favorite features and scenarios. I will complete this post with a set of screen shots from the Beta 2 builds.
![clip_image012[6]](https://msdntnarchive.z22.web.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_msdn/amit_chatterjee/WindowsLiveWriter/WhatsnewinTestandLabManagementinVS2010Be_CAE1/clip_image012%5B6%5D.jpg "clip_image012[6]")
A view of the plan activity center showing the hierarchy of suites and test cases in a suite
![clip_image014[6]](https://msdntnarchive.z22.web.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_msdn/amit_chatterjee/WindowsLiveWriter/WhatsnewinTestandLabManagementinVS2010Be_CAE1/clip_image014%5B6%5D.jpg "clip_image014[6]")
Test Plan properties showing various settings and results overview
![clip_image016[6]](https://msdntnarchive.z22.web.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_msdn/amit_chatterjee/WindowsLiveWriter/WhatsnewinTestandLabManagementinVS2010Be_CAE1/clip_image016%5B6%5D.jpg "clip_image016[6]")
Test Results from a Data Driven Test
![clip_image018[5]](https://msdntnarchive.z22.web.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_msdn/amit_chatterjee/WindowsLiveWriter/WhatsnewinTestandLabManagementinVS2010Be_CAE1/clip_image018%5B5%5D.jpg "clip_image018[5]")
The Lab Activity center showing Lab Environments in various states
Releasing Beta 2 is a very significant milestone for us. We are now in the home stretch for the product, and are ready for you to go live with this release. I look forward to you deploying the products in your teams, and will be happy to answer any questions and clarification you may have.
I will be back soon with future posts on value props and scenarios we are enabling with this release.
Comments
- Anonymous
December 02, 2009
What are the changes in the Coded UI Test Builder? I installed Beta 2 and it does not recognize any of the tests I've built in Beta 1. I also created a Coded UI Test in Beta 2, which it also does not recognize.Previously, tests I was recording were generating code in the RecordedMethods.cs file and now it is generating the code in the UIMap.Designer.cs file? I have many tests and I would like to avoid reconfiguring every one of them if possible. I am running tests directly through VSTS. - Anonymous
December 07, 2009
You can find "What's new in Coded UI Test for Beta2" in Anutthara's blog.http://blogs.msdn.com/anutthara/archive/2009/10/25/what-s-new-for-testers-doing-ui-automation-in-vs-2010-beta2.aspxWhen a Coded UI Test project created in Beta1 is migrated to Beta2, there will be compilation errors because two properties [WinProperties.Common.TabIndex & HtmlProperties.Common.RelativePosition] have been removed.The following steps can be used to fix the problems.Open the Coded UI Test ProjectOpen UserControls.cs Delete "TabIndex" property from WinControl class & "RelativePosition" property from HtmlControl class 4. Remove all refereces of these two properties from the solution 5. Search for "WinProperties.Common.TabIndex" & "HtmlProperties.Common.RelativePosition" in RecordedMethods & CodedUITest file 6. Search for the strings "WinProperties.Common.TabIndex" & "HtmlProperties.Common.RelativePosition" Remove all references of these properties. Launch Coded UI Test Builder and click "Generate Code" button. Close the Coded UI Test Builder. Rebuild the solution Please upgrade the projects to Beta2 using the steps above.