Automation script impact post Pega 8 upgrade
Hello,
We are planning to upgrade existing application that runs on 7.1.9 to 8.2.3. We are currently evaluating and estimating this. On One aspect we are a bit clueless that how this upgrade is gonna impact the test automation scripts.
Automation testing is performed through selenium script in our application. Our test engineers would like to clarify the below points for which we seek the support of community. The below quesrions are valid for as is upgrade only.
- Does Pega introduce/exclude any iframe in 8.2.3 version compared to 7.1.9 which would be inherited in Perform/Review harness.
- Application behavioral/performance/response time change in terms of page load wait time.
- DOM structure change which leads to changes of x-path for existing web elements.
- Any major UI architecture changes (apart from mentioned in point 1) which could lead to change in page element type.
- Any java script/ajax call that could dynamically change the property & attribute of web elements.
Any clue/experience/lesson learn on the above points would be helpful for us
Thanks
Sayak
MUFG Pension & Market Services
IN
I will try to answer posted questions as below
- Does Pega introduce/exclude any iframe in 8.2.3 version compared to 7.1.9 which would be inherited in Perform/Review harness. FC: iframes are still available unless you are using COSMOS UI. values (tag/name/index) might be changed after upgrade.
- Application behavioral/performance/response time change in terms of page load wait time. FC: Can't be sured as it's completly depends on the infrastruce you have used and application functionality. But according to my experience performance shouldn't be downgrade but it should improve in new versions of Pega.
- DOM structure change which leads to changes of x-path for existing web elements. FC: Yes, you can expect and consider refactoring of most of the xpaths.
- Any major UI architecture changes (apart from mentioned in point 1) which could lead to change in page element type.
- Any java script/ajax call that could dynamically change the property & attribute of web elements.
One thing cannot be changed even after upgrade is unique test ID which is provided to each rule in Pega. Which is available in each rule as a form of Test ID and this will result in DOM structure as data-test-id value. Ask your development team to make a habbit of providing unique test id and while wrtiting automation scripts please use data-test-id as dynamic xpath.
I will try to answer posted questions as below
- Does Pega introduce/exclude any iframe in 8.2.3 version compared to 7.1.9 which would be inherited in Perform/Review harness. FC: iframes are still available unless you are using COSMOS UI. values (tag/name/index) might be changed after upgrade.
- Application behavioral/performance/response time change in terms of page load wait time. FC: Can't be sured as it's completly depends on the infrastruce you have used and application functionality. But according to my experience performance shouldn't be downgrade but it should improve in new versions of Pega.
- DOM structure change which leads to changes of x-path for existing web elements. FC: Yes, you can expect and consider refactoring of most of the xpaths.
- Any major UI architecture changes (apart from mentioned in point 1) which could lead to change in page element type.
- Any java script/ajax call that could dynamically change the property & attribute of web elements.
One thing cannot be changed even after upgrade is unique test ID which is provided to each rule in Pega. Which is available in each rule as a form of Test ID and this will result in DOM structure as data-test-id value. Ask your development team to make a habbit of providing unique test id and while wrtiting automation scripts please use data-test-id as dynamic xpath.
I hope it answers your questions.