I am trying to launch a website from Playwright, the browser is set to desktop chrome. But I am getting an error message saying the website is not reachable. I can able to launch the website manually and when I try to launch the site on other browsers like safari, Firefox or iPhone it is launching successfully from Playwright. Has anyone experienced similar issue. I have been trying solution for long time but I couldn't find anything useful. Kindly help me on this.
Thanks in advance!!
I am expecting the site to launch successfully from the Playwright using Desktop Chrome browser. Sometime the site is launching successfully but when I try to perform any actions the site is again unreachable
Related
When I download a TWA built like this project (https://github.com/GoogleChromeLabs/svgomg-twa) on Chromebooks it only launches the URL inside the Chrome browser and not as a standalone webview. If I install as a PWA then it runs correctly inside a standalone browser. The website is also not cached while running from the TWA unlike the PWA
Has anyone managed to get a TWA running correctly on Chromebooks?
It's not supported yet. Support for Trusted Web Activity in Chrome OS is coming in Chrome 86.
I have been executing automation scripts for last 6 months without any issues. Suddenly chrome browser shows captcha screen and shows message that please confirm are you human ?.
Below that it states 2 points 1.JavaScript might be disabled 2. your cookies are not supported .I enabled both of the Java script and cookies but no luck.
I tried to execute older version of chrome browser also but I am getting same captcha screen in the older version of browser too.
The good thing is that I am not getting captcha screen in Firefox and edge browser. I am getting it only in the chrome browser.
May I know if chrome has introduced any functionality like if we execute automation scripts and it shows captcha screen because why I am getting this doubt that firefox and edge is not showing captcha screen.
I have a weird problem going on with a Selenium test. I have an internal company website that I'm writing a Selenium test for and am getting a 404 error ONLY with the browser instance that Selenium opens up. It doesn't matter if its Chrome or Firefox, I still get the 404.
To prove its only with the browser instance that Selenium opens I have run my test in debug mode, paused it when the browser launches and then manually executed the test case within that browser instance and I always get a 404.
Now, if I open a normal Chrome or Firefox browser instance outside of Selenium I can manually execute the test case just fine.
Manual execution of the test case in Chrome Incognito also works.
What am I missing here?
Apparently something else needs to be loaded with in the browser but I have no idea what. Any help would be greatly appreciated.
I found that we had a redirect problem on our server, however it still doesn't make sense as to why it failed in WebDriver but not in a normal browser. Either way, its resolved.
I am using browserstack to test some devices, like IE. However I need to set up local testing so I can test my site localhost:3000
I have logged in to browserstack in Chrome and installed the extension. I click on the extension IE11 link. It takes me to a IE11 on Windows 8 virtual machine.
I type localhost:3000 into IE but it doesn't seem to work.
Then I click the Settings cog and click resolve all URLs through my network.
Still it doesn't seem to work for me.
Looks like the setup was fine in Browserstack, I just forgot that in IE11 I need to use http://localhost:3000 as it doesn't automatically resolve the protocol http silly mistake :)
My web app uses IndexedDB and I'm testing on SauceLabs. Some months back my tests ran but now they block on a browser dialog that says "http://gbserver3.cs.unc.edu/" wants to: store files on this device", with an Allow button.
This is Win7 and Chrome or Firefox. Likely others too.
How can I dismiss or prevent this dialog?
Update: I have discovered that if I don't ask for quota I don't get the popup and my tests succeed. I'd still like to learn how to get rid of that dialog.
we are using Nightwatch.js in our project and we were facing the same issue.
What actually did the trick was using --unlimited-storage switch when launching the browser.
(List of other command line switches for Chromium can be found here)