Cannot make it work with RemoteWebDriver and Docker #349
Comments
klieber
added a commit
to klieber/jasmine-maven-plugin
that referenced
this issue
Sep 16, 2020
Example usage:
```xml
<plugin>
<groupId>com.github.searls</groupId>
<artifactId>jasmine-maven-plugin</artifactId>
<version>${jasmine-maven-plugin.version}</version>
<executions>
<execution>
<goals>
<goal>test</goal>
</goals>
</execution>
</executions>
<configuration>
<serverHostname>${accessibleHostname}</serverHostname>
<webDriverClassName>org.openqa.selenium.remote.RemoteWebDriver</webDriverClassName>
<webDriverCapabilities>
<webDriverCapability>
<name>browserName</name>
<value>chrome</value>
</webDriverCapability>
<webDriverCapability>
<name>goog:chromeOptions</name>
<value implementation="org.openqa.selenium.chrome.ChromeOptions">
<headless>true</headless>
</value>
</webDriverCapability>
</webDriverCapabilities>
</configuration>
</plugin>
```
closes searls#234
closes searls#235
closes searls#349
|
This will be fixed in the <plugin>
<groupId>com.github.searls</groupId>
<artifactId>jasmine-maven-plugin</artifactId>
<version>${jasmine-maven-plugin.version}</version>
<executions>
<execution>
<goals>
<goal>test</goal>
</goals>
</execution>
</executions>
<configuration>
<serverHostname>${accessibleHostname}</serverHostname>
<webDriverClassName>org.openqa.selenium.remote.RemoteWebDriver</webDriverClassName>
<webDriverCapabilities>
<webDriverCapability>
<name>browserName</name>
<value>chrome</value>
</webDriverCapability>
<webDriverCapability>
<name>goog:chromeOptions</name>
<value implementation="org.openqa.selenium.chrome.ChromeOptions">
<headless>true</headless>
</value>
</webDriverCapability>
</webDriverCapabilities>
<!-- If your remote server is not running at http://localhost:4444/wd/hub then you can use this parameter to configure the right location -->
<!-- <remoteWebDriverUrl>http://localhost:4444/wd/hub</remoteWebDriverUrl> -->
</configuration>
</plugin> |
klieber
added a commit
to klieber/jasmine-maven-plugin
that referenced
this issue
Sep 16, 2020
Example usage:
```xml
<plugin>
<groupId>com.github.searls</groupId>
<artifactId>jasmine-maven-plugin</artifactId>
<version>${jasmine-maven-plugin.version}</version>
<executions>
<execution>
<goals>
<goal>test</goal>
</goals>
</execution>
</executions>
<configuration>
<serverHostname>${accessibleHostname}</serverHostname>
<webDriverClassName>org.openqa.selenium.remote.RemoteWebDriver</webDriverClassName>
<webDriverCapabilities>
<webDriverCapability>
<name>browserName</name>
<value>chrome</value>
</webDriverCapability>
<webDriverCapability>
<name>goog:chromeOptions</name>
<value implementation="org.openqa.selenium.chrome.ChromeOptions">
<headless>true</headless>
</value>
</webDriverCapability>
</webDriverCapabilities>
<!-- If your remote server is not running at http://localhost:4444/wd/hub then you can use this parameter to configure the right location -->
<!-- <remoteWebDriverUrl>http://localhost:4444/wd/hub</remoteWebDriverUrl> -->
</configuration>
</plugin>
```
closes searls#234
closes searls#235
closes searls#349
|
that's awesome, thanks a lot @klieber 👍 |
|
@klieber I've just noticed that you released 3.0-beta-01 (https://github.com/searls/jasmine-maven-plugin/releases). I've tested it and it still fails for me with the same error as before... Here's what I have:
And I get:
And on the selenium side (in the docker container): So the issue is still this Would you have any idea of what could be wrong? Thank you very much. |
|
@klieber kind ping about the message above. |
|
Hi @klieber I reproduce the same issue as @vmassol. I've been able to put a breakpoint on this specific line: https://github.com/searls/jasmine-maven-plugin/blob/master/src/main/java/com/github/searls/jasmine/runner/SpecRunnerExecutor.java#L69 that's where the problem occurs: for some reason the command is not accepted and makes everything crashing. |
klieber
added a commit
to klieber/jasmine-maven-plugin
that referenced
this issue
Aug 24, 2022
Example usage:
```xml
<plugin>
<groupId>com.github.searls</groupId>
<artifactId>jasmine-maven-plugin</artifactId>
<version>${jasmine-maven-plugin.version}</version>
<executions>
<execution>
<goals>
<goal>test</goal>
</goals>
</execution>
</executions>
<configuration>
<serverHostname>${accessibleHostname}</serverHostname>
<webDriverClassName>org.openqa.selenium.remote.RemoteWebDriver</webDriverClassName>
<webDriverCapabilities>
<webDriverCapability>
<name>browserName</name>
<value>chrome</value>
</webDriverCapability>
<webDriverCapability>
<name>goog:chromeOptions</name>
<value implementation="org.openqa.selenium.chrome.ChromeOptions">
<headless>true</headless>
</value>
</webDriverCapability>
</webDriverCapabilities>
<!-- If your remote server is not running at http://localhost:4444/wd/hub then you can use this parameter to configure the right location -->
<!-- <remoteWebDriverUrl>http://localhost:4444/wd/hub</remoteWebDriverUrl> -->
</configuration>
</plugin>
```
closes searls#234
closes searls#235
closes searls#349
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
I admit that the issue could well be outside of the jasmine plugin but I cannot figure it and I'd need some hep, at least to debug it.
So I'm trying to do the following:
docker run --privileged -p 4444:4444 -p 5900:5900 -v /dev/shm:/dev/shm selenium/standalone-chrome-debug.The docker image starts well and I can see that jasmine, through WebDriverManager, succeeds in creating an instance of the webdriver class:
And on the jasmine side (client side):
Some notes:
[SEVERE]: bind() failed: Cannot assign requested address (99)is not a problem. It usually means that ipv6 is not enabled in docker but chrome falls back to listening to ipv4.org.openqa.selenium.WebDriverException: unknown error: net::ERR_CONNECTION_REFUSED. All I can see from the stack trace is that it comes from the interaction with the webdriver at:driver.get(runnerUrl.toString());(in SpecRunnerExecutor.java).If you have any idea how to debug this, it would be awesome!
Thanks a lot
The text was updated successfully, but these errors were encountered: