We are working on the Load runner Ajax true client protocol scripting. The given flow is when we double click on a record , it will navigate to the new window. But while recording the script new window is not opening.
LoadRunner version – 12.60
How can I resolve the recording issue?
Navigating to new window (record and replay) is working absolutely fine in current latest version of Microfocus Loadrunner 2020 https://www.microfocus.com/en-us/products/loadrunner-professional/download
Related
My web app is working in a WebView of an IOS native application. There is a button on the top-left side of the page, and it will go back to the previous page after the button is clicked. So far so good, but recently many customers have upgraded their IOS to 14 Beta2 and now the back button doesn't work as expected.
I use the history.go(-1) to go back, but if the session history length is 2, it will execute the history.go(-1), but the page will not go back. The url also doesn't change. If the user continue to open new page, then it works again.
Does anyone have ideas of whats going on with it?
I meet the same problem. You can use setTimeout delay for a while when you use history.push，like this
setTimeout(() => {
history.push('xxx');
}, 100);
I am working on xpages project which I want to run in notes client browser not in the any othe browser because this application is not server based application , This application is kind of desktop applicationn with extension .nsf and can be run on notes clients.
In the first case I thoought it needs to hosted on server and then CSJS will work but it wont work that way also.
a simple alert("Hello World"); throws the error, 'An error occurred while updating some of the page. Not enough arguments [insIDE Window.alert] notes'
Is there any specific settings which I am missing in the applcation ?
I have tried the same in notes 10 , notes 9 , but the result is same.
Even partial refreshes workimg not expectedly .
link of location popup image I am trying to execute the automation scripts(Appium+Java+TestNG/Junit) on Amazon DeviceFarm but while executing, scripts were unable to perform any action((Access/Deny) on Location permission popup.Couldn't see any error logs in console. I have used normal click() operation as well as alert() function. Nothing works in this case.
Please help me.Below is the piece of code that I have tried..
WebDriverWait wait = new WebDriverWait(android, 5);
wait.until(ExpectedConditions.alertIsPresent());
driver.switchTo().alert().dismiss();
}catch(Throwable t) {
System.out.println("Not an alert popup or alert is not present..");
driver.findElement(By.id("idofthelocator")).click();
}
Unfortunately, cap.setCapability(AndroidMobileCapabilityType.AUTO_GRANT_PERMISSIONS, "true"); did not work for me as well. So, I tried finding the locators of the pop-up as usual and then click on same and it worked like a charm. Could you also try finding the locators and clicking on the button as required. Below code works in my case:
`//Location service pop up
#FindBy(id ="com.android.packageinstaller:id/dialog_container")
public WebElement locationPopup;
//Location service allow button
#FindBy(id = "com.android.packageinstaller:id/permission_allow_button")
public WebElement locationPopupAllowButton;
WebDriverWait wait = new WebDriverWait(driver, 20);
wait.until(ExpectedConditions.visibilityOf(locationPopup));
locationPopupAllowButton.click();`
Hope it helps :)
With Android Appium tests it should possible to dismiss permissions popups by setting the capability autoGrantPermission to true. This capability will evaluate the application for the permission it need and run and adb command to grant the app access. Here is the code in the Appium project that does that:
https://github.com/appium/appium-android-driver/blob/959e07d84dc9d09a11735872259ac87511d03b85/lib/android-helpers.js#L334
https://github.com/appium/appium-adb/blob/e6bdc234e7dcf61e0252aad3ac7ab47491fe3720/lib/tools/adb-commands.js#L186
Can you try this capability and let us know if that helps?
With iOS Appium tests the capability autoGrantPermission does NOT work with Appium version less then 1.9.1 because there's not way through Apple APIs to predict the permission necessary or accept them. A workaround is to either find the element manually by printing the page source and checking for it on the fly or use the following lines to take advantage of the selenium methods:
driver.switchTo().alert().accept();
driver.switchTo().alert().dismiss();
In the more recent versions of Appium changes were made to use the autoGrantPermission capability valid with iOS tests. Here is the PR for that request
https://github.com/appium/appium-xcuitest-driver/commit/f5267acab3bc9285161397fa19a8daf60ae0c6ae
Can you let us know which Appium version you're using in this case and provide some of the Appium server logs from the run in Device Farm and your local execution?
We have a requirement to open Google Chrome Browser from Internet Explorer 8. To do this, we are using JavaScript ActiveXobject with the following code.
Code Snippet:
var URL ="http://www.google.com"
var chromeCommand = "Chrome --app="+URL+" --allow-outdated-plugins";
var shell = new ActiveXObject("WScript.Shell");
shell.run(chromeCommand);
For this, we need to set Enable "Initialize and Script ActiveX Controls not Marked as Safe for Scripting" radio button from Tools->Internet Options->Security Tab->Trusted sites -> Custom Level ...
Is this enable setting will harm anything on security concerns?
Please let me either we can open Chrome browser in this way or not, or else any alternative to do this.
Will this code work for Linux OS Internet Explorer?
I have a multi-line Text field on a form CRM 2011 with update rollup 17. I have enabled the readonly property field with the following code:
Xrm.Page.ui.controls.get('description').setDisabled(false);
It works correctly in Internet Explorer but not in any other browsers. What's the problem?
It should work in other browsers as well as far as they are supporting CRM application. You should debug the Javascript in the browser that you are having issues in. Press F12 and in the console press start debugging when you load the page. It will give show you the errors in javascript and show you whether your javascript is even being loaded in the browser or not. Alternatively try Xrm.Page.getControl('description').setDisabled(false)
You can also write the following statement :
var description = document.getElementById("description");
if (description != null)
{
description.disabled=false;
}