Won't Fix
Last Updated: 16 Oct 2017 08:26 by ADMIN
Created on: 07 Aug 2017 08:53
Type: Feature Request
Recorder does not identify the automationIDs in a custom WPF application when executing a recorded test
1. Start recording a test against it and click over the cells in grid. Note that the first step is recorded against an element relying on TextContent. Each next element relies on AutomationID. 

2. Run the test. 

Expected: To run successfully.

Actual: Only the first step is being successful since the automationIDs are not present in the DOM tree. 

Note: The application does generate the automationIDs when started. They are only not present in the recorder DOM tree before a click is performed. 

Sample app shared internally. 
Posted on: 16 Oct 2017 08:26

This behavior is due the fact that Test Studio uses AutiomationId's as primary filter in it's find logic. When custom Automation Ids are implemented finding the elements in the application is piece of cake. However for some reason in the GridView controls temporarily IDs are implemented which are used during the recording of the application as they are populated when a click event is performed. We from Test Studio have no control over this implementation and we cannot change the current way that the control is working.
In order to have this working properly you should either implement your own custom Automation Ids or modify the application  by adding the following line of code in the AppXaml.cs file in the Onstartup() method:
 AutomationManager.AutomationMode = AutomationMode.Disabled;

This will prevent the AutomatioIDs to be triggered in record mode and will force the recorder to generate find expressions based on text content or other filters.

Thank you for your understanding regarding this matter.

Best Regards,
Posted on: 07 Aug 2017 11:50
it is funny when telerik studio can't work with teleriks native controls.