I'm running automated test scripts using webdriver.io. Issue is, the code stopped running after updating the chromedriver to 100.0.4896.60 which is recommended for chrome browser v100 that is currently installed. It was working fine in all the previous versions (v93 thru v99). Im getting the data;; screen and I dont see any errors on the terminal (VS Code)
I wont be able to upgrade or downgrade the browser versions. Could anyone help?
It was a case of access issues with DevTools of chrome. After getting proper access the issue is resolved.
Related
I'm using PhpStorm in Ubuntu 18.041 and facing a serious problem.
I've tried several configurations (JavaScript, PHP remote) with Chrome and Firefox but none of them is starting the browser. I do not get any error message, the browser window just do not appear.
The service desk helped me to solve this issue. It seems that the installation was not completed correctly. I started PHPStorm from the shell and it lead me again trough the initial configuration. Since that is is working normally.
Today i've attempted to start dev environment, as usual and got this alert:
Nothing seems to be changed. One thing I've noticed is that chrome started asking for update today. The error has shown up before i've restarted chrome and updated it. But still, i assume, there were some critical changes introduced and begun breaking things once again. Anyone got/solved it already?
OS X 10.11.6
Chrome 57.0.2987.133
Looks like a Parallels issue, do you have Chrome installed on a Windows VM on your Mac using Parallels?
If so, removing Chrome from Windows to see if the problem still persists might be the first test.
My theory is that RN is trying to launch Chrome but it's locating the one inside of the VM instead of the app on OSX.
I am facing below stack of errors with my selenium tests which are passed yesterday. I am facing issue only when running tests in chrome browser. For rest of the browsers the tests are running perfect. i tried updating the chrome version to latest. And even updated selenium jars to latest versions.
Any fix with out changing the existing framework please?
I tried most of the fixes available in stackoverflow. Still no luck.
My Computer auto updated chrome browser at some point.
So I got the previous version chrome web driver.
I got rid of all the errors in the screenshot and able to run tests succesfully
I am trying to run a test using chrome, but when the browser launches the test fails and I see the below error.
org.openqa.selenium.WebDriverException: unknown error: unable to
discover open window in chrome
I am using the most recent versions of selenium and chrome driver
Webdriver - 2.46
Chrome driver - 2.16
Chrome browser - 43
This error only occurs when running the tests on my local machine. If I run these tests on a grid VM, chrome will open without any issues and the test will run. The grid VM and my local machine have the exact same versions of chrome, chrome driver, and webdriver.
What can I look for on my local machine to resolve the issue? I've tried to reinstall chrome, but that didn't help.
I have observed inconsistent behavior using the Web Developer extension (Chris Pederick) in Google Chrome on these different machines:
My PC running Windows 7 Home Premium 64-bit
A VirturalBox Virtual Machine (VM) running Ubuntu 12 on my PC
A VM running a updated, fresh install of Windows 7 Home Premium 64-bit on my PC
I have the same version of Google Chrome and Web Developer installed on all these machines. However, for some reason, Web Developer does not work as expected on my PC. It works perfectly on the Ubuntu VM and the Windows VM.
On my PC, about 95% of the time the Custom Tools functions (Validate CSS, Validate HTML, etc.) in Web Developer do nothing when clicked (they should open new tabs to the W3C validators).
I have uninstalled and reinstalled Google Chrome on my PC several times. I have even manually gone through the file system and registry to completely remove all traces of Google Chrome before reinstalling. Nothing I've attempted so far has corrected this problem.
Of course, due to Google's 'field trials', all these machines have slightly different variations (as reported by chrome://version), but I would doubt that is the source of the problem.
Any ideas or suggestions?
OK, here's a possible clue...
It has baffled me why this problem NEVER occurs in my virtual machine (VM); only on the host. Same version of OS, Chrome, and Web Developer installed on both. May have discovered why.
My standard settings for VMs is to use only one CPU. As a test, I changed the VM to use two CPUs. BOOM! I can reproduce the problem on my VM. Change back to one CPU - can not reproduce the problem.
Does this suggest a problem with threading in Chrome?