Selenium interacting with Pega UI. Unable to consistently interact with elements
Hi, we are interacting with Pega UI using Selenium and Java for the purposes of automation .
In building a simple script we have correctly identified the elements either by ID or by Xpath. We then send values to be stored into a text box and then move onto the next element
During run-time the results are inconsistent as sometimes values to be stored in one field are then stored into another one. Or sometimes the value flashes up briefly on the screen and then seems to be cleared by something else. Reset by Javascript?
My research indicates that Pega is ajax intensive and it is that activity that is interrupting the Selenium script during runtime. The solution seems to be either putting in messy sleep commands or building a helper class that tries to force the value to be inserted into the field. Neither of these are ideal.
When we try and incorporate a class that is supposed to wait for Ajax interaction to complete it still fails to work. I've included the example below. Is the reason that this solution does not work down to the setting of the Pega-Rules pzPegaSUT. Currently ours is set to false. Will setting it to true allow us to check for background Ajax to be complete before interacting with an element in a consistent manner?
Are there any other impacts of setting this value? Or is there a better solution other then leaving sleep commands in the code? One other poster indicated he had a solution then decided to not share it with the community?
Hi, we are interacting with Pega UI using Selenium and Java for the purposes of automation .
In building a simple script we have correctly identified the elements either by ID or by Xpath. We then send values to be stored into a text box and then move onto the next element
During run-time the results are inconsistent as sometimes values to be stored in one field are then stored into another one. Or sometimes the value flashes up briefly on the screen and then seems to be cleared by something else. Reset by Javascript?
My research indicates that Pega is ajax intensive and it is that activity that is interrupting the Selenium script during runtime. The solution seems to be either putting in messy sleep commands or building a helper class that tries to force the value to be inserted into the field. Neither of these are ideal.
When we try and incorporate a class that is supposed to wait for Ajax interaction to complete it still fails to work. I've included the example below. Is the reason that this solution does not work down to the setting of the Pega-Rules pzPegaSUT. Currently ours is set to false. Will setting it to true allow us to check for background Ajax to be complete before interacting with an element in a consistent manner?
Are there any other impacts of setting this value? Or is there a better solution other then leaving sleep commands in the code? One other poster indicated he had a solution then decided to not share it with the community?
public static void waitForJQueryLoad() {
//Wait for jQuery to load
ExpectedCondition<Boolean> jQueryLoad = driver -> ((Long) ((JavascriptExecutor) jsWaitDriver)
.executeScript("return jQuery.active") == 0);
//Get JQuery is Ready
boolean jqueryReady = (Boolean) jsExec.executeScript("return jQuery.active==0");
//Wait JQuery until it is Ready!
if(!jqueryReady) {
System.out.println("JQuery is NOT Ready!");
//Wait for jQuery to load
jsWait.until(jQueryLoad);
} else {
System.out.println("JQuery is Ready!");
}
}
Accepted Solution
Transport NSW
AU
Based on the original question and the first response it looks like the Pega Internal Implementation of the Ajax counter works provided you are logged on as an authorised user.
IE Anon User of Pega based HTML forms will not be able to make use of this. For these scenarios a java helper class to deal with the various element types would be required. IE Retries if values are being cleared etc
Our Java implementation for our Selenium test case is below. Anyone implementing the below will need to play around based on the number of ajax calls that are being made for your implementation.
public static void waitForAjax(WebDriver driver) throws InterruptedException { System.out.println("Entering Helper");
driver.switchTo().defaultContent();
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
Thread.sleep(100);
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
Based on the original question and the first response it looks like the Pega Internal Implementation of the Ajax counter works provided you are logged on as an authorised user.
IE Anon User of Pega based HTML forms will not be able to make use of this. For these scenarios a java helper class to deal with the various element types would be required. IE Retries if values are being cleared etc
Our Java implementation for our Selenium test case is below. Anyone implementing the below will need to play around based on the number of ajax calls that are being made for your implementation.
public static void waitForAjax(WebDriver driver) throws InterruptedException { System.out.println("Entering Helper");
driver.switchTo().defaultContent();
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
Thread.sleep(100);
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
String Counter = driver.findElement(By.xpath("//div[@class='documentstatetracker']")).getAttribute("data-state-ajax-counter");
System.out.println("Ajax Counter " + Counter);
System.out.println("Coming out of helper");
Pegasystems Inc.
IN
Hi Darren,
I think we can go ahead with setting Pega-RULES pzPegaSUT to true.
There is less likelihood of any other impact on functionality.
Please refer https://collaborate.pega.com/discussion/what-ajax-framework-or-library-used-pega-7
Thanks,
Ujjwal
Transport NSW
AU
We have made this suggested change but still we can't see the Ajax state and the select element behaviour remains inconsistent because of the running processes.
Transport NSW
AU
Actually the change "does work" but as we use a non developer login credential it didn't let us see the value. When you actually login as a developer the value does appear via the Designer Studio. See below
<div class="document-statetracker" data-state-doc-counter="3" data-state-doc-status="ready" data-state-ajax-counter="21" data-state-ajax-status="none" data-state-script-status="none"></div>
I assume we must ask our developers to grant permissions to all users?
Or is the implementation restricted to to the back end user?
Accepted Solution
Transport NSW
AU
Based on the original question and the first response it looks like the Pega Internal Implementation of the Ajax counter works provided you are logged on as an authorised user.
IE Anon User of Pega based HTML forms will not be able to make use of this. For these scenarios a java helper class to deal with the various element types would be required. IE Retries if values are being cleared etc
Our Java implementation for our Selenium test case is below. Anyone implementing the below will need to play around based on the number of ajax calls that are being made for your implementation.
public static void waitForAjax(WebDriver driver) throws InterruptedException { System.out.println("Entering Helper");
driver.switchTo().defaultContent();
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
Thread.sleep(100);
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
Based on the original question and the first response it looks like the Pega Internal Implementation of the Ajax counter works provided you are logged on as an authorised user.
IE Anon User of Pega based HTML forms will not be able to make use of this. For these scenarios a java helper class to deal with the various element types would be required. IE Retries if values are being cleared etc
Our Java implementation for our Selenium test case is below. Anyone implementing the below will need to play around based on the number of ajax calls that are being made for your implementation.
public static void waitForAjax(WebDriver driver) throws InterruptedException { System.out.println("Entering Helper");
driver.switchTo().defaultContent();
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
Thread.sleep(100);
new WebDriverWait(driver,10).until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='document-statetracker' and @data-state-ajax-status='none']")));
String Counter = driver.findElement(By.xpath("//div[@class='documentstatetracker']")).getAttribute("data-state-ajax-counter");
System.out.println("Ajax Counter " + Counter);
System.out.println("Coming out of helper");