Jason Zander has announced the availability of Visual Studio 2010 RC for MSDN subscribers – here.
The changes in Coded UI Test are
- Specialized classes (HtmEdit, WinWindow, WpfButton etc) have been added to the product. (Previously these classes were auto-generated in the UserControls file. This file will no longer be added to the Coded UI Test Project.) Please note that this is a breaking change.
- Multiple UI Maps are now supported. Previously a Coded UI Test Project could have only one UI Map file. Now we allow addition of multiple UI Maps to enable test projects to scale up to real world applications. Also, this will enable multiple UI automation engineers to work simultaneously on the test project without running into merge conflicts.
- Start -> Search action filters – If you launch the application under test by typing its name in the Start -> Search box, the actions will be aggregated to an ApplicationUnderTest.Launch action. This greatly enhances the resilience of the test and you can now record this on Win7 or Vista and playback your recording on XP or Win2K3.
- WPF DateTimePicker/MonthCalendar controls are now supported.
- SharePoint Support has been enhanced – SharePoint 2007 is now fully supported except where it interacts with Office applications like Excel/InfoPath.
- TFS Work Item Picker has been enhanced to allow selection of only valid test cases. When you choose a manual test case to generate code from, the experience now lets you look at test case work item types and filter on those that have automation strip associated with them.
- Waiters – New APIs have been added to support Waiters in playback. These help your test code be faster and more resilient by getting rid of the sleep APIs in the test code where you don’t know how long you need to wait for a control.
- Playback.EncryptText API has been added to enable users to encrypt text that can be set on a password field
- Extensibility APIs have enhanced usability and richer documentation.
- New Plugins can now be created by extending existing Plugins.
See the full list of changes in Testing tools in RC – here
Steps to upgrade an existing Coded UI Test Project to VS 2010 RC
1. Launch the Visual Studio Command Prompt
2. Run the following script
UITestUpgrade.exe <name of folder(s) to upgrade>
– This upgrade tool will fix all the changes listed below.
– All the folders under the specified folder(s) is searched recursively and all projects under it upgraded.
– Multiple folders may be specified, separated by comma.
– If a project is under source control, the upgrade tool will check it out of source control and make changes.
– A backup folder is created and all contents of the specified folder copied to it before making changes.
The list of changes are as follows:
1. UserControls.cs file has been removed. All specialized classes (HtmlButton, WinEdit, WpfCheckbox etc) are now part of the product.
2. ‘Internet Explorer Server’ control used to be part of the UI Control hierarchy for Html Controls. This has been removed to enable better support for extensibility.
3. For searching a Browser Window, exact name match will be used.
4. The names of properties (e.g: DisplayText of a HtmlButton) previously used to be in a separate class hierarchy (e.g: HtmlProperties.Button.DisplayText). This has now been modified to be part of the definition of each specialized class. Therefore, HtmlButton.PropertyNames.DisplayText will now give the name of the DisplayText property of HtmlButton.
5. Classes which did not have any additional property on them will now be treated as a Custom class. e.g: HtmlForm will now be treated as a HtmlCustom and its TagName property will be set to ‘Form’. WinForms controls which don’t have additional properties will be treated as a WinControl. WPF controls which don’t have additional properties will be treated as a WPFControl.