I am automating a simple login script through Browserstack using Selenium.
The script I have written works on chrome windows, chrome mac os, and Android Samsung. However, when I run the script through apple iPhone 11 or mac os safari I get an error message saying can not locate
driver.findElement(By.xpath("//*[contains(text(),'Log in')]")).click();
Apart from the device, I am automating nothing else changes.
What is the fix for this?
If the test returned "cannot find element" on the device, I'll recommend changing the element locator strategy.
You could otherwise also try to inspect the app against the same browser manually via Live: https://live.browserstack.com/
This could help you narrow down if the element locator is correct.
Related
When i have checked the cypress latest version of 12.5.1 it is suggested to use the playwright-webkit where the safari browser is using the webkit engine it seems. here I need to simulate real time safari browser execution. Is there any way to do this?
I have tried to execute the playwright-webkit but unluckily it is not even open the URL and webkit is not working properly and if we switch to chrome or another browser it is working fine. but my request is to execute in safari the most.
Guys I need help to run the robot using Selenium. When trying to run the browser it opens very quickly and closes, I can't access the amazon website. I have already updated the chromedriver to the compatible version of my browser but I still get the InvalidArgumentException message: Message: invalid argument showing the browser screen in white.
obs: I've already reinstalled the drivers for the versions I have of firefox and chrome but I still can't run.
enter image description here
enter image description here
I tried to run the robot and I couldn't because the error message is displayed
InvalidArgumentException: Message: invalid argument
Did you specify the browser and web-url arguments?
like:
open browser https://www.amazon.com/ chrome
I just updated to TestCafe v1.18.0 and I followed the upgrade guide. I am able to run tests against Chrome and Firefox, as the system correctly prompted me if I wanted to let TestCafe control these, but this is not happening for Safari, so I am unable to test against it. I don't see any way to manually add an entry in the Automation tab either.
Automation Tab entry for TestCafe Browser Tools
Edit: I managed to add it using the remote option for TestCafe and pasting the URL into Safari, but even after that, npx testcafe safari is unable to launch Safari. I'm using an M1 Mac and macOS Monterey 12.0.1
TestCafe 1.18.0 does have the Safari-related issue. It has already been fixed. Please update TestCafe to v1.18.1.
Can I run headless safari browser via windows?
I did not tried it yet but it's just I wanted to check if it's possible. If anyone have what all I need.
The short answer to this is no. The reason for this is an issue with Safari specifically, not Selenium. You can find an explanation on this relevant GitHub issue opened under the Selenium repo: https://github.com/SeleniumHQ/selenium/issues/5985
The GitHub issue is marked as closed by the Selenium developers, because Safari application itself does not support headless mode.
I have problem as following. I use a Titanium Studio, build: 3.1.1.201306112235 with SDK 3.1.1 GA (on Windows 7). When I try to run example app as "Mobile Web Preview in Browser", then I saw mobile app in my Firefox (version 21.0) but any actions associated with 'clicks' don't work. Furthermore when I try run the same app in Chrome I see the same behaviour. Only in Internet Explorer app works properly (version 10). Do you have idea why apps from Titanium don't work properly? If you would like to get some more logs just ask.
EDIT: I provide remote access, and reopen page by Firefox in the same version on my colleague's laptop. Then in here browser everything works well. So i have question which settings, on my browser can "freezing" titanium application. Javascript is running, so I don't have idea, what is bad in my configuration.
This sounds like you are making web service calls to a remote host, which violates the same-origin-policy built into recent versions of chrome.
Try opening up chrome with this policy disabled:
chrome.exe --disable-web-security