Polymer Web Component Tester / Selenium Delayed

Question

We are trying to run a web component tester, but it continues to stop at the Selenium step.

When I ran wct -l chrome --verbose

I get the following

 hook: prepare hook: prepare:selenium hook done: prepare:selenium Starting Selenium server for local browsers 11:47:46.357 INFO - Launching a standalone server Setting system property webdriver.chrome.driver to C:\Users\<user>\AppData\Roaming\npm\node_modules\web-component-tester\node_modules\wct-local\node_modules\selenium-standalone\.selenium\chromedriver\2.13-x64-chromedriver Setting system property webdriver.ie.driver to C:\Users\<user>\AppData\Roaming\npm\node_modules\web-component-tester\node_modules\wct-local\node_modules\selenium-standalone\.selenium\iedriver\2.44.0-x64-IEDriverServer.exe 11:47:46.809 INFO - Java: Oracle Corporation 25.31-b07 11:47:46.809 INFO - OS: Windows 7 6.1 x86 11:47:46.872 INFO - v2.44.0, with Core v2.44.0. Built from revision 76d78cf 11:47:47.669 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:11655/wd/hub 11:47:47.669 INFO - Version Jetty/5.1.x 11:47:47.685 INFO - Started HttpContext[/selenium-server,/selenium-server] 11:47:47.919 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@3c1e69 11:47:47.919 INFO - Started HttpContext[/wd,/wd] 11:47:47.919 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver] 11:47:47.919 INFO - Started HttpContext[/,/] 11:47:47.935 INFO - Started SocketListener on 0.0.0.0:11655 11:47:47.935 INFO - Started org.openqa.jetty.jetty.Server@11bc7ed 

Then, after a few minutes of stall,

 hook done: prepare with error: [Error: Unable to connect to selenium] Error: Unable to connect to selenium 

Running the same tests from a browser works without problems.

While he hanged himself, we can still connect through the browser to http://127.0.0.1:11655/wd/hub

I tried google but not much luck.

What things can go wrong or how can I debug this further?

Answer 1

One of the node modules does not use Internet Explorer proxy values.

In environment variables create a new

• Name: no_proxy
• Value: localhost, 127.0.0.1

Remember to restart the shell session after applying

Answer 2

I had the same problem and was related to setting up a proxy server for my organization. When I left my network and connected via the Internet, I was able to run tests through selenium. At the moment, I have not yet been able to find a way to configure the proxy server. I worked on a Mac. You may need to try a typical installation on the Internet and check.