Supported Configurations and Platforms for Coded UI Tests and Action Recordings

Operating Systems

Windows 7

Windows Server 2008 R2

Windows 8

32-bit / 64-bit Support

32-bit Windows that is running 32-bit Microsoft Test Manager can test 32-bit applications.

64-bit Windows that is running 32-bit Microsoft Test Manager can test 32-bit WOW Applications that have UI Synchronization.n.

64-bit Windows that is running 32-bit Microsoft Test Manager can test 64-bit Windows Forms and WPF Applications that do not have UI Synchronization.

Architecture

x86 and x64

Note
Internet Explorer is not supported in 64-bit mode except when running under Windows 8.

.NET

.NET 2.0, 3.0, 3.5, 4 and 4.5.

Note
Microsoft Test Manager and Visual Studio will both require .NET 4 to operate. However, applications developed by using the listed .NET versions are supported.

Windows Store Apps

Not supported

Internet Explorer 8

Internet Explorer 9

Internet Explorer 10

Caution
Internet Explorer 10 on the desktop is only supported.

Fully supported.

• Support for HTML5 in Internet Explorer 9 and Internet Explorer 10: Coded UI tests support record, playback, and validation of the HTML5 controls: Audio, Video, ProgressBar and Slider. For more information, see Using HTML5 Controls in Coded UI Tests.

  Caution

  If you create a coded UI tests in Internet Explorer 10, it might not run using Internet Explorer 9 or Internet Explorer 8. This is because Internet Explorer 10 includes HTML5 controls such as Audio, Video, ProgressBar, and Slider. These HTML5 controls are not recognized by Internet Explorer 9, or Internet Explorer 8. Likewise, your coded UI test using Internet Explorer 9 might include some HTML5 controls that also will not be recognized by Internet Explorer 8.

• Support for Internet Explorer 10 Spell Checking: Internet Explorer 10 includes spell checking capabilities for all text boxes. This allows you to choose from a list of suggested corrections. Coded UI Test will ignore user actions like selecting an alternative spelling suggestion. Only the final text typed into the text box will be recorded.

  The following actions are recorded for coded UI test that use the spell checking control: Add to Dictionary, Copy, Select All, Add To Dictionary, and Ignore.

• Support for 64-bit Internet Explorer running under Windows 8: Previously, 64-bit versions of Internet Explorer were not supported for recording and playback. With Windows 8 and Visual Studio 2012, coded UI tests have been enabled for 64-bit versions of Internet Explorer.

  Caution
  64-bit support for Internet Explorer applies only when you are running Windows 8 or later.

• Support for Pinned Sites in Internet Explorer 9: In Internet Explorer 9, pinned sites were introduced. With Pinned Sites, you can get to your favorite sites directly from the Windows taskbar—without having to open Internet Explorer first. Coded UI tests can now generate intent-aware actions on pinned sites. For more information about pinned sites, see Pinned Sites.

• Support for Internet Explorer 9 Semantic Tags: Internet Explorer 9 introduced the following semantic tags: section, nav, article, aside, hgroup, header, footer, figure, figcaption and mark. Coded UI tests ignore all of these semantic tags while recording. You can add assertions on these tags using the Coded UI Test Builder. You can use the navigation dial in the Coded UI Test Builder to navigate to any of these elements and view their properties.

• Seamless Handling of White Space Characters between Versions of Internet Explorer: There are differences in the handling of white space characters between Internet Explorer 8, Internet Explorer 9, and Internet Explorer 10. Coded UI Test handles these differences seamlessly. Therefore, a coded UI test created in Internet Explorer 8 for example, will play back successfully in Internet Explorer 9 and Internet Explorer 10.

• The Notification Area of Internet Explorer Are Now Recorded With the “Continue on Error” Attribute Set: All actions on the Notification Area of Internet Explorer are now recorded with the “Continue on Error” attribute set. If the notification bar does not appear during playback, the actions on it will be ignored and coded UI test will continue with the next action.

Windows Forms and WPF third party controls

Fully supported.

To enable third party controls in Windows Forms and WPF applications, you must add references and code. For more information, see Enable Coded UI Testing of Your Controls.

Internet Explorer 6

Internet Explorer 7

Not supported.

Chrome

Firefox

The latest versions of Chrome and Firefox browsers are supported with Visual Studio 2012.1 update or later.

Opera

Safari

Not supported.

Silverlight

Not supported.

Note
The plug-in included in Visual Studio 2010 feature pack 2 is no longer part of the product. However, additional information is available on MSDN blogs and the Visual Gallery Q&A. For more information, see Microsoft Visual Studio UI Test Plugin for Silverlight

Flash/Java

Not supported.

Windows Forms 2.0 and later

Fully supported.

Note
NetFx controls are fully supported, but not all third-party controls are supported.

WPF 3.5 and later

Fully supported.

Note   NetFx controls are fully supported, but not all third-party controls are supported.

Windows Win32

May work with some known issues, but not officially supported.

MFC

Partially supported. See the following Microsoft Web site for details of what features are supported.

SharePoint

Fully supported.

Office Client Applications

Not supported.

Dynamics CRM web client

Fully supported.

Dynamics (Ax) 2012 client

Action recording and playback are partially supported. See the following Microsoft Web site for details.

SAP

Not supported.

Citrix/Terminal Services

Partially supported.

Note
It is recommended that you run Visual Studio or Microsoft Test Manager in your terminal session.

PowerBuilder

Partially supported.

The support is to the extent accessibility is enabled for PowerBuilder controls.