Supported configurations and platforms for coded UI tests and action recordings
Applies to: Visual Studio Visual Studio for Mac Visual Studio Code
The supported configurations and platforms for coded UI tests for Visual Studio Enterprise are listed in the following table. These configurations also apply to action recordings created by using Test Runner.
The coded UI test process must have the same privileges as the app under test.
Coded UI Test for automated UI-driven functional testing is deprecated. Visual Studio 2019 is the last version where Coded UI Test will be fully available. We recommend using Playwright for testing web apps and Appium with WinAppDriver for testing desktop and UWP apps. Consider Xamarin.UITest for testing iOS and Android apps using the NUnit test framework. To reduce the impact on users, some minimum support will still be available in Visual Studio 2022. In Visual Studio 2022, users can run existing CodedUI tests, but not record new tests because Coded UI Test Editor is not available.
- Visual Studio Enterprise
|Operating Systems||Windows 7
Windows Server 2008 R2
|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 or later versions.|
|.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.|
UI Synchronization is a feature where the playback is verified in the message queue of each control. If a control did not respond to the event that was sent to it, then the event is sent again.
|Platform||Level of Support|
|Windows Phone Apps||Only WinRT-XAML based Phone apps are supported.|
|UWP apps||Only XAML-based UWP apps are supported.|
|Universal Windows Apps||Only XAML-based Universal Windows Apps on Phone and Desktop are supported.|
|Edge||Recording of action steps or using the builder to view object properties is not supported. Tests can be played back on the Edge browser, using Visual Studio 2015 Update 2 and later versions by using the Coded UI cross browser testing extension.|
|Internet Explorer 8
Internet Explorer 9
Internet Explorer 10 Important: Internet Explorer 10 is only supported on the desktop.
Internet Explorer 11 Important: Internet Explorer 11 is only supported on the desktop.
- 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. Warning: 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. Warning: 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
|Recording of action steps is not supported. Coded UI Tests can be played back on Chrome and Firefox browsers with Visual Studio 2012 Update 4 or later. Go here for more details.|
For Visual Studio 2013 however, you can download the Microsoft Visual Studio 2013 coded UI test plugin for Silverlight from the Visual Studio Gallery.
|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 UITest framework for details of what features are supported.|
|Office Client Applications||Not supported.|
|Dynamics CRM web client||Fully supported.|
|Dynamics (Ax) 2012 client||Action recording and playback are partially supported. See Visual Studio 10 coded UI / action recordings support for Microsoft Dynamics for details.|
|Citrix/Terminal Services||We don't recommend recording actions on a terminal server. The recorder doesn't support running multiple instances at the same time.|
The support is to the extent accessibility is enabled for PowerBuilder controls.
Submit and view feedback for