Forum Discussion
Presume you must be using the URL as an identification property for the page object?
If it is the only browser open during your test, you should be able to simply wildcard it out.
So instead of the property ID being "www.TEST.com" or "www.PROD.com" change it to "www.*.com". Or simply "*". Which means it would run on any site.
Or you could store it as a variable. Read it in from an INI file of some description. Include it in the input if you use data and/or keyword driven tests (that's what I do). If there is anything else in the deployment which changes, and can be accessed before starting the site, you could inspect that and use the result to determine the URL path to use.
Probably quite a few options.
- coffee8 years agoContributor
Thanks All.
I managed to do "Extended Find" , so I just skip the pageURL and I put all elements directly under Sys-Browser.
I also tried to wildcard the URL , www.*.com.
The problem with those solutions is TC tends to take much more time and the playback process becomes much much slower when I have heaps of open Chrome tabs. I think TC doesn't know in which tab does this web element sit and it needs to search in each and every tab. Sometimes it took 5 minutes just to find the box and it returns
Searching for the mapped object "WarningBox" took a long time. This happened because the sought-for object has the Extended Find attribute enabled, and the test engine searched for this object on all levels down the object hierarchy.
To speed up the search and improve the test performance, add more parent objects of this object to the Mapped Objects tree of Name Mapping.
Anyway, thanks for all the suggestions :smileyhappy:
Related Content
Recent Discussions
- 4 hours agoSubhraDas
- 23 hours agotramuntana