Forum Discussion
I have just tried it again and it has started working.. albeit with ambiguous recognition.
I since removed 'Full Name' and replaced with 'BaseURL' below:
This is because "FullName" value contains a reference to the concrete browser ("Firefox" in your case). And when you run another type of browser, it fails.
You can use wildcards and conditional name mapping to make your aliases more flexible to different application conditions.
- georgereynolds8 years agoOccasional Contributor
I did try using wildcards previously.
Note that it worked in Chrome, not firefox and changing the browser at the top of the keyword test, it still worked in Chrome, despite not having the wildcards in place and the namemapping making reference to firefox. I did try adding the wildcards and many combinations before my my initial post, so I don't think that isn't the cause of the issue - unless something is buggy with wildcards?
- georgereynolds8 years agoOccasional Contributor
On a slightly different modal, it times out trying to find the 'Yes' button and I get the 'Unable to find the object' option - which gives the possiblity of 'Point to the buttonYes on screen" - if I do this, then I get the below message -asking me to map it manually
- georgereynolds8 years agoOccasional Contributor
I've not been able to fix this - I rolled back to a build on the SVN where I wasn't getting this error and re-did all the fixes manually. It is now identifying these modals correctly. It's still a mystery to me why it failed.
Related Content
- 4 years agoGunacelan
- 3 years agonewbe
- 2 years agoIlakkk
- 3 years agovargirovic
Recent Discussions
- 2 hours agomarkos