Update NameMapping from QA URL to production URL

[david-beltran]

We've been working on a revamp of our billing site. I've been building tests in TestComplete in the QA environment. The QA and production URLs are different. I've been going through the tests to re-map objects on a test-by-test basis, but that's a very tedious process. I have gone into NameMapping, clicked on the page in question, and updated the URL. After running the test again TestComplete is not seeing the objects and giving me errors in the log. Is there a different way to update the URL for all of the objects at the same time? Or is there possibly a better way to go through the name mapping process to avoid this in the future?

[tvklovesu · Accepted solution]

You really no need to re-map all the objects in the namemapping. All you need to do is use wildcard in the page url

For ex

http://dev-mysite.com/login.html

change the url as follows

http://*-mysite.com/login.html

This way if the url matches with the one you specified above then the object will be identified

[rraghvani]

If the domain name is slightly different, then it's best to use wildcards as described by @tvklovesu. Otherwise, an alternative approach is to use either

• Use variable values and pass this to the command line which sets URL
• Read from an .ini file and set URL

[david-beltran]

Thank you both. That appears to be working properly. I was using my wildcards in the wrong spots to match.