Test Automation Suite getting Different IDs for Pega UI elements (SR-C66137)
We are trying to automate our functional testing through Ketalon automation suite. When we run the test scripts, each time the pega UI element IDs are generated differently. Ketalon is not able to get the same UI element ID for the pega fields. In our case worker portal, we have a navigation menu. Pega is generating the UI IDs for the navigation items differently each time when they are launched. Because of this, whatever the test scripts generated in the Katalon studio are not working as this studio runs the test based on only the UI IDs generated in the initial run. Steps to Reproduce Please read this article and let me what do you think - https://forum.katalon.com/discussion/2015/element-not-found-exception When I debug the view source, I noticed each time it is generating new xpath value, and that is causing element not found on the page when we run the automated suite. For LHN “Search” element, it generates following different values while running it multiple times. Katalon Studio utilize that value to find the html element on the screen. Please review, and let me know if you find any alternative solution to automate this flow/application. //*[@id="menu-1537368369212"]/li[2]/a/span[2] //*[@id="menu-1537368526859"]/li[2]/a/span[2] //*[@id="menu-1537368659131"]/li[2]/a/span[2] 1.Open your page using Chrome. 2.Right-click on your desired test object -> choose Inspect Element. 3.In Chrome's Elements tab, right-click on the focused object, choose Copy -> Copy XPath. 4.Open your test object in Katalon, modify xpath property with the copied value.
We are trying to automate our functional testing through Ketalon automation suite. When we run the test scripts, each time the pega UI element IDs are generated differently. Ketalon is not able to get the same UI element ID for the pega fields. In our case worker portal, we have a navigation menu. Pega is generating the UI IDs for the navigation items differently each time when they are launched. Because of this, whatever the test scripts generated in the Katalon studio are not working as this studio runs the test based on only the UI IDs generated in the initial run. Steps to Reproduce Please read this article and let me what do you think - https://forum.katalon.com/discussion/2015/element-not-found-exception When I debug the view source, I noticed each time it is generating new xpath value, and that is causing element not found on the page when we run the automated suite. For LHN “Search” element, it generates following different values while running it multiple times. Katalon Studio utilize that value to find the html element on the screen. Please review, and let me know if you find any alternative solution to automate this flow/application. //*[@id="menu-1537368369212"]/li[2]/a/span[2] //*[@id="menu-1537368526859"]/li[2]/a/span[2] //*[@id="menu-1537368659131"]/li[2]/a/span[2] 1.Open your page using Chrome. 2.Right-click on your desired test object -> choose Inspect Element. 3.In Chrome's Elements tab, right-click on the focused object, choose Copy -> Copy XPath. 4.Open your test object in Katalon, modify xpath property with the copied value.
***Edited by Moderator Marissa to update SR Details***
Cisco
US
Hello grona,
Thank you for responding. are these match rules from Katalon studio?
Sorry, I do not have much idea on that tool. just checking. if that is something from Katalon, I can inform my team to remove the element ID from the match rules in katalon. please confirm. Thank you!