Guidelines on improving performance of Coded UI Test playback

This post provides guidelines on improving the performance of Coded UI Test playback. It details techniques such as extending auto-generated search hierarchies, making use of PlaybackSettings, using MaxDepth to restrict search sub-trees, giving precedence to window search properties over accessibility properties, utilizing NextSibling for faster searches, and employing the AlwaysSearch configuration option. It also offers scenario-specific guidelines for form filling using the CopyPastedText property, preferring SelectedItems over SelectedIndices for large lists, expanding all nodes in a TreeView control, being cautious about Items property usage, comparing WinList, WinTable, and WinTree, and using the Exists property. Additionally, it provides debugging tips for performance issues by analyzing warning and error messages in logs.
More from the Coded UI Test Deprecation and Alternatives trail
- Changes to Coded UI Test in Visual Studio 2019
- Troubleshooting launch issues with xaml based apps using Coded UI Test
- Coded UI Test Extensibility V2
- Coded UI testing support for Silverlight using Visual Studio 2013
- Test controllers are not visible or marked offline in MTM when multiple versions of MTM are installed