Re-script for object identification, how to avoid
Posted: Wed Apr 08, 2015 12:19 am
Hi Team,
When I earlier recorded Upload.exe(demo app), ranorex 5.2 identified the elements (such as buttons) with @accessiblename and it worked fine.
Now I have used the project on another computer, here the script when run, didn’t identify the element. When analysed with Ranorex spy, I see the elements no longer have @accessiblename, and hence I had to rescript with @controlname identifier to make this work.
My question are:
1) Why Ranorex didn’t use @controlname when I recorded it earlier (due to weightage?).
2) Can application such as upload.exe expose different identifiers when executed from different PC / Operating systems? What is the safe bet.
I the below screen shot, I have changed @accessiblename to @controlname (along with correct values) for StartFileUpload and ProgressBar and about to fix ResetUI and Close.
When I earlier recorded Upload.exe(demo app), ranorex 5.2 identified the elements (such as buttons) with @accessiblename and it worked fine.
Now I have used the project on another computer, here the script when run, didn’t identify the element. When analysed with Ranorex spy, I see the elements no longer have @accessiblename, and hence I had to rescript with @controlname identifier to make this work.
My question are:
1) Why Ranorex didn’t use @controlname when I recorded it earlier (due to weightage?).
2) Can application such as upload.exe expose different identifiers when executed from different PC / Operating systems? What is the safe bet.
I the below screen shot, I have changed @accessiblename to @controlname (along with correct values) for StartFileUpload and ProgressBar and about to fix ResetUI and Close.