Coded UI Test Extension for 3rd party controls - the basics explained
Oct 28, 2011Shubhra Maji MSFT
Summary
This post details the four levels of implementing Coded UI Test support for third-party controls: Level 1 (Basic Record and Playback) allows for element identification and basic property validation; Level 2 (Rich Property Validation) enables assertions on custom properties; Level 3 (Code Generation) allows for specialized classes and more readable auto-generated test code; and Level 4 (Intent Aware Actions) aggregates actions for more accurate recording based on control behavior. Implementing these levels requires extending the Technology Abstraction Layer (TAL), PropertyProvider, and ActionFilter.
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