Hi,
We test a wpf application which is running under .NET Framework 4.0. There are several elements in the visual tree (in tab pages), which are built from a child class of a custom control of us. During it's initialization, we set the automationid=classname of the specific child.
Now, I have two environments where I build and run testscases. On one machine, the classname and automationid property are available, on the other only the classname is set the automationid is empty.
Both machines have:
Same Version of the Testapplication
Ranorex: 3.0.0.11639
.NET: 4.0.30319.1
The machine which does not recognize the automationid is a 64Bit Windows 7 Workstation. I tried the 32bit and 64bit Version of Ranorex Spy. The machine which is working correctly is a 32Bit Windows Vista.
There are other elements, where the automationid is working perfectly.
Does anyone have an idea how to identify the problem?
Thanks
Andreas
AutomationID not recognized
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: AutomationID not recognized
Hi,
How to create a Snapshot
Regards,
Peter
Ranorex Team
Please can you post us two Ranorex Snapshots of the entire application to check the difference between them? One of the working and one of the not working application.andreas.tastler wrote:There are other elements, where the automationid is working perfectly.
Does anyone have an idea how to identify the problem?
How to create a Snapshot
Regards,
Peter
Ranorex Team
-
- Posts: 36
- Joined: Mon Sep 20, 2010 10:59 am
Re: AutomationID not recognized
Hi
There are two Snapshots in the attached zip file.
The one which is working is AutomationID_OK.rxsnp
The element I told you about is at
/form[@automationid='IsagClientMainForm']/tabpagelist[@automationid='tabMain']/tabpage/container/element[@automationid='dlgOrgeinheitSuchen']
Regards
Andreas
There are two Snapshots in the attached zip file.
The one which is working is AutomationID_OK.rxsnp
The element I told you about is at
/form[@automationid='IsagClientMainForm']/tabpagelist[@automationid='tabMain']/tabpage/container/element[@automationid='dlgOrgeinheitSuchen']
Regards
Andreas
You do not have the required permissions to view the files attached to this post.
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: AutomationID not recognized
Hi,
Thank you for the Snapshots.
It seems to be a bug in the UIAutomation Framework or in our WPF-Plug-In, we try to nail it down with our WPF specialist. But as workaround you can use the "classname" attribute for this element instead of the "automationid" attribute. This attribute should work for both systems. If this is a bug on our side we will fix this with a future release of Ranorex.
Regards,
Peter
Ranorex Team
Thank you for the Snapshots.
It seems to be a bug in the UIAutomation Framework or in our WPF-Plug-In, we try to nail it down with our WPF specialist. But as workaround you can use the "classname" attribute for this element instead of the "automationid" attribute. This attribute should work for both systems. If this is a bug on our side we will fix this with a future release of Ranorex.
Regards,
Peter
Ranorex Team
-
- Posts: 36
- Joined: Mon Sep 20, 2010 10:59 am
Re: AutomationID not recognized
Hi
Thank you for analyzing the snapshots. I have already used the classname to identify the elements. Since there were no other issues with the AutomationId, everything works fine for now.
Regards
Andreas
Thank you for analyzing the snapshots. I have already used the classname to identify the elements. Since there were no other issues with the AutomationId, everything works fine for now.
Regards
Andreas
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: AutomationID not recognized
Hi,
Fine that this workaround is okay for you. We will inform you about the outcome of our further analyzes.
Regards,
Peter
Ranorex Team
Fine that this workaround is okay for you. We will inform you about the outcome of our further analyzes.
Regards,
Peter
Ranorex Team