I have a test written with intern that worked fine on Firefox and Chrome until recently - possibly until a recent upgrade of intern. The following code correctly tabbed to an element on the screen that can be focussed, and when actioned with the [Space] key would cause a script event to trigger.
.keys(specialKeys.Tab)
.keys(specialKeys["Space"])
.end()
If I do this activity manually in either browser it works fine.
Now when I run this sequence of commands it works fine in Firefox, but not in Chrome. I have tried forcing an update of both Chrome and ChromeDriver and running again. This has not fixed the problem.
Does anybody have any ideas as to why this is occurring?
I'm using intern 1.7, Chrome 34.0.1847.137 and ChromeDriver 2.10.0. If there is a particular sequence of npm commands that gives a reliable and stable installation when one of the afore mentioned components upgrades that would be very useful.
This is a known issue with Chrome 34, caused by keyboard focus being stuck on the address bar. It is not a bug in Intern. More information can be found at https://code.google.com/p/chromedriver/issues/detail?id=762.
Related
I have a problem with chromium when I run my tests through the puppeteer.
What happens is that my tests require the microphone to be enabled the moment I log in to the application, even after adding:
'--use-fake-ui-for-media-stream', '--no-sandbox', '--disable-setuid-sandbox'] : ['--use-fake-ui-for-media-stream'
Before working normally, after changing the machine it stopped working and I don't know if it is related to the version of the chromium that is started:
This is the version of chromium when testing starts:
Version 77.0.3844.0
And my version of the puppeteer is:
```"puppeteer": "^1.19.0"````
Has anyone ever experienced this? If so, how do I update the chromium?
Thanks,
I am having trouble debugging my web project using the Chrome Browser. I can only use IE to do my debugging. I did some "googling" to resolve this problem, and came across a few Microsoft threads that said to update to the latest version of VS2017, which I did. I use version 15.9.13 and Visual Studio 2017 tells me I am "up to date" when I check for further updates.
When I first updated VS 2017, it started working, and I could debug using Chrome (finally!). But now it has stopped working again.
I saw in other threads where people suggested deleting the .vs folder, which I did, but had no luck with that.
Google Chrome is up to date at Version 75.0.3770.100
I debug and run my application as "Administrator" so that shouldn't be the problem either. I also close all browsers before running the debugger, so Chrome isn't running elsewhere when I try to debug.
Is there any explanation why Chrome cannot launch when using debugger? I would really like to use Chrome because of it's superior "dev tools" and inspection tools. Any suggestions? Was sad to have it working only one day.
Having configured the same environment like yours(VS version and Chrome version) but can't reproduce the issue.I would think if something is broken in VS or maybe third-party extension is the causes this issue.
Please try:
VS repair and a reinstall of Chrome(don't forget to backup the bookmarks)
Uninstall or disable third-party vs extensions, this won't take effect until restart vs
Navigate to %LocalAppData%\Microsoft\VisualStudio\15.xxx directory, delete all ComponentModelCache folders in all 15.xxx folders.
Open your project in vs, changed the target browser from Chrome to IE. Then F5 and wait until it is finish. Stop it and change the browser back to Chrome. After that the error disappeared.
Also, create a new asp.net web app and debug it with Chrome browser to check if the issue persists. Hope it helps.
I have inherited a JMeter performance testing script. There is a chromedriver section and an HTTPSampler section. The httpsampler section works fine. The chromedriver section runs into a problem. When I run it chrome pops up like this:
It does not move forward with any of the steps in the plan after that. Up until recently I've also been seeing the error
Error communicating with the remote browser. It may have died.
I am not seeing this now, so I don't know if it's just a difference in how the test is running or what.
The person I inherited this from was running it on a mac and did not get any of these problems. I saw it run with no errors at the same time I was getting them.
One solution I found was to add the --test-type flag to chromedriver. Unfortunately I cannot find a way to add that argument when running it through JMeter. I've tried adding both --test-type and -test-type to the end of the path to chromedriver.exe, but that did not work.
Does anyone have a solution for this?
The error might be due to conflict in chrome driver version. Please install the latest version of ChromeDriver from this link.
Latest version of Chrome Driver supports the browser version v56-58.
I updated my windows 8.1 to windows 10 recently. Everything is fine except for Chrome. Chrome opens and crashes. How many times I reinstall, the problem remains the same. Do I need to wait for chrome update or is there a solution for this problem? Thanks.
run "cmd" as Administrator (search "cmd", right mouse-click, run as Administrator)
type "netsh.exe winsock reset", then reboot computer
After the reboot chrome started to work for me again. I found that in some forum and i just tried it out, since running in windows 8 compatibility modus did not work for me. Neither Chrome Canary (unstable chrome), which was constantly crashing.
Good luck.
I have been facing the same issue from past few days(almost a month). Following helped me to get my chrome work well...
Close chrome.
Open Windows Explorer and go to following folder path: %USERPROFILE%\AppData\Local\Google\Chrome\User Data
Delete the file named “Local State” in that path
Also rename a folder named "Default" to "Default.old"
Thats it your chrome works well.
Happy browsing.
List item
You can find more details in the follwing link. http://www.kitwall.com/wallalert/45d3hx4u6xwh22ckvxz35ayw5/=014ggvbnq6j5x
Have not been able to use Chrome (Version 42.0.2311.90 (64-bit)) as a neo4j browser client after upgrading to the latest XCode / Command Tools in MacOS Yosemite 10.10.3 . Safari is working fine though. Is there an easy way to pinpoint to the actual problem? I'm using Neo4j 2.2.1
The following is a screenshot from the JavaScript console showing the errors:
mostly load resource errors and an uncaught error failing to instatiate module neo4jApp .
It works fine under Safari. It also works in a Chrome Incognito Window. Partially resetting settings is a trial and error exercise. While resetting all chrome settings finally solved the initial problem, I wonder if there is a better way and not having to lose all other user settings in Chrome.
I encountered the same exact issue today with Chromium 43.0.2357.81 (64-bit) and Neo4j 2.2.1. Clearing the cache and refreshing http://localhost:7474/browser/ wasn't working for me (javascript errors). What did work for me, was going to http://localhost:7474/webadmin/ which asked me to re-authenticate. After logging in, the Neo4j browser site loaded.