Question

2
Replies
62
Views
 Michael Fu (MichaelF2091)
IBM

IBM
CN
MichaelF2091 Member since 2017 9 posts
IBM
Posted: August 8, 2017
Last activity: August 14, 2017
Posted: 8 Aug 2017 22:50 EDT
Last activity: 14 Aug 2017 1:09 EDT
Closed

How to migrate automation tool from test environment to production environment

There is a same web application deployed in both test environment and production environment,and now I have to develop automation tool based on the web application in test environment firstly because of the limitation of production environment.

The issue i met is that it didn't work after migrating automation tool developed in test environment to production environment via changing the start page property of web.os ,like the URL of production is http://XXXX.com while test's is http://test.XXXX.com,I saw most elements are mismatched.It means i should interrogate the elements again,Is there any solution can fixed this issue?after all the web application is same.

Any help will be appreciated.

System Administration Installation and Deployment
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Posted: 9 Aug 2017 8:23 EDT
Michael Chandler (chanm1)
PEGA
Lead System Architect, Robotics
Pegasystems Inc.
US

Some controls, web pages in particular, use a URL match rule.  It is not uncommon to have different URLs for a test verses production environment as you start.  To handle this condition you will need to modify the URL match rules to match both URLs.  In your example you use http://XXXX.com and http://test.XXXX.com.   You could change the URL match rule to only match on XXXX.com with Mode set to EndsWith.  The rule would then match the XXXX.com in both URLs.


A lot of times a web page can be uniquely identified using only the Title match rule.  If this is the case for your application you could delete the URL match rules.