Rx Path has changed to everything being an element
Posted: Mon Sep 23, 2013 4:04 pm
I am using Ranorex 3.3.3 and have been for some time. I recorded some scripts a few months ago on this version of Ranorex and have run them several times without problems.
Recently I went back to the machine and attempted to run the same scripts with the same version of Ranorex but the scripts fail. It seems that many Rx Paths have changed from using correct control names (e.g. window) to using element in all cases. Plus there appears to be an extra level of "element" required in the new paths.
When I use the Rx Spy (32 or 64 bit) I can see this problem.
The problem manifests in many areas of the repository not just one section e.g. trees and listitems are now owned by windows such as "element[@class='WTL_OutlookSplitterWindow']/element[@class='WTL_OutlookSplitterWindow']/element[@class='ATL:00537DE8']/element/element[@class='ATL:00535F68']/container/element/element/element/list/listitem[@accessiblerole='ListItem']"
which used to be
"window[@class= ...]/Window[@class= ...] ..." etc.
For another example an item which used to work as
container[@controlname='parametersGroup']/table/row[@accessiblename='Row 0']/cell[@accessiblename='Parameter Value Row 0']
Now appears as
element[@controlname='parametersGroup']/element[@controlname='parametersGrid']/table/row[@accessiblename='Row 0']/cell[@accessiblename='Parameter Value Row 0']
Our programmers have made no changes in this area. They have NOT added ParametersGrid, for example.
However, we do now install the two Visual Studio SP1 items (x86 and x64) and also XML 6.0 SP1 x64 libraries.
Can someone tell me what to look for to get my existing scripts working with the correct object types again?
Have I unknowingly switched on some strange flag? I have not edited any path weights or preferences on the project that I can remember.
Recently I went back to the machine and attempted to run the same scripts with the same version of Ranorex but the scripts fail. It seems that many Rx Paths have changed from using correct control names (e.g. window) to using element in all cases. Plus there appears to be an extra level of "element" required in the new paths.
When I use the Rx Spy (32 or 64 bit) I can see this problem.
The problem manifests in many areas of the repository not just one section e.g. trees and listitems are now owned by windows such as "element[@class='WTL_OutlookSplitterWindow']/element[@class='WTL_OutlookSplitterWindow']/element[@class='ATL:00537DE8']/element/element[@class='ATL:00535F68']/container/element/element/element/list/listitem[@accessiblerole='ListItem']"
which used to be
"window[@class= ...]/Window[@class= ...] ..." etc.
For another example an item which used to work as
container[@controlname='parametersGroup']/table/row[@accessiblename='Row 0']/cell[@accessiblename='Parameter Value Row 0']
Now appears as
element[@controlname='parametersGroup']/element[@controlname='parametersGrid']/table/row[@accessiblename='Row 0']/cell[@accessiblename='Parameter Value Row 0']
Our programmers have made no changes in this area. They have NOT added ParametersGrid, for example.
However, we do now install the two Visual Studio SP1 items (x86 and x64) and also XML 6.0 SP1 x64 libraries.
Can someone tell me what to look for to get my existing scripts working with the correct object types again?
Have I unknowingly switched on some strange flag? I have not edited any path weights or preferences on the project that I can remember.