Troubleshooting launch issues with xaml based apps using Coded UI Test

Jan 25, 2016Abhitej_MSFT

SummaryAI, from the source post

This post addresses a specific troubleshooting issue with launching XAML-based Windows Store apps using Coded UI Test in Windows 10. It explains that the automationID returned by the Coded UI Test engine has changed in Windows 10, causing a 'Package was not found' exception when using the XamlWindow.Launch() API. The post provides a workaround by stripping the 'tile-' prefix and '_b3rhdqcqv1gj2!App' postfix from the reported automationID to successfully launch the application.

Read the full post on devblogs.microsoft.com

More from the Coded UI Test Deprecation and Alternatives trail

Changes to Coded UI Test in Visual Studio 2019Apr 13, 2019
Coded UI Test Extensibility V2Dec 3, 2015
Coded UI testing support for Silverlight using Visual Studio 2013May 23, 2014
Test controllers are not visible or marked offline in MTM when multiple versions of MTM are installedMay 21, 2014
Using Coded UI to test XAML-based Windows Phone appsApr 4, 2014