Few tips on implementing a Coded UI Test Plugin Extension
Aug 17, 2012Tapas Sahoo [MSFT]
Summary
This post provides specific technical tips for implementing Coded UI Test plugin extensions, including setting ComVisibleAttribute, implementing caching mechanisms for property providers, limiting class hierarchy, avoiding live UITestControl property access in GetControlSupportLevel, using unique names for extension managers, avoiding specific implementation inside specialized class properties, and utilizing new extension proxy classes.
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