-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to connect to remote Selenium server #234
Comments
This was referenced Mar 29, 2014
klieber
added a commit
to klieber/jasmine-maven-plugin
that referenced
this issue
Sep 16, 2020
closes searls#234 closes searls#235
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
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
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
How can I use a Selenium server that runs in another machine?
The docs for
serverHostname
mention this possibility brieflyAlso, it seems that some work in this direction was done by @johnomalley in 4974ccc. He added a
<remoteWebDriverUrl>
parameter -- which was later reverted.The text was updated successfully, but these errors were encountered: