[
https://issues.jboss.org/browse/ARQ-1048?page=com.atlassian.jira.plugin.s...
]
Karel Piwko updated ARQ-1048:
-----------------------------
Description:
If you set up a Drone Webdriver with given capability, original configuration is
completely ignored, e.g.:
{code:java}
public void simpleWebdriverTest(@Drone RemoteWebDriver webdriver) {
webdriver.get(contextPath.toString());
webdriver.findElement(By.id("name")).sendKeys("Samuel");
webdriver.findElement(By.id("email")).sendKeys("samuel(a)vimes.dw");
webdriver.findElement(By.id("phoneNumber")).sendKeys("1234567890");
webdriver.findElement(By.id("register")).submit();
// FIXME with Graphene, you can wait for a request
Assert.assertTrue(true);
}
{code}
{code:xml}
<!-- configuration for WebDrivers -->
<extension qualifier="webdriver">
<property
name="browserCapabilities">${browser:chrome}</property>
<property
name="firefoxBinary">/opt/firefox-9.0.1/firefox-bin</property>
<property
name="chromeBinary">/opt/google/chrome/chrome</property>
<property name="chromeSwitches">--user-data-dir=/tmp
--disable-web-security</property>
</extension>
{code}
Both chromeBinary and chromeSwitches are ignored. If you use @Drone ChromeDriver instead,
you get proper capabilities setup.
This means that a mapping between capabilities and Arquillian properties has to be
improved.
was:
If you set up a Drone Webdriver with given capability, original configuration is
completely ignored, e.g.:
{code:java}
public void simpleWebdriverTest(@Drone RemoteWebDriver webdriver) {
webdriver.get(contextPath.toString());
webdriver.findElement(By.id("name")).sendKeys("Samuel");
webdriver.findElement(By.id("email")).sendKeys("samuel(a)vimes.dw");
webdriver.findElement(By.id("phoneNumber")).sendKeys("1234567890");
webdriver.findElement(By.id("register")).submit();
// FIXME with Graphene, you can wait for a request
Assert.assertTrue(true);
}
{code}
{code:xml}
<!-- configuration for WebDrivers -->
<extension qualifier="webdriver">
<property
name="browserCapabilities">${browser:chrome}</property>
<property
name="firefoxBinary">/opt/firefox-9.0.1/firefox-bin</property>
<property
name="chromeBinary">/opt/google/chrome/chrome</property>
<property name="chromeSwitches">--user-data-dir=/tmp
--disable-web-security</property>
</extension>
{code:xml}
Both chromeBinary and chromeSwitches are ignored. If you use @Drone ChromeDriver instead,
you get proper capabilities setup.
This means that a mapping between capabilities and Arquillian properties has to be
improved.
RemoteWebDriver ignores old configuration properties
----------------------------------------------------
Key: ARQ-1048
URL:
https://issues.jboss.org/browse/ARQ-1048
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Drone
Affects Versions: drone_1.1.0.CR2
Reporter: Karel Piwko
Assignee: Karel Piwko
Fix For: drone_1.2.0.next
If you set up a Drone Webdriver with given capability, original configuration is
completely ignored, e.g.:
{code:java}
public void simpleWebdriverTest(@Drone RemoteWebDriver webdriver) {
webdriver.get(contextPath.toString());
webdriver.findElement(By.id("name")).sendKeys("Samuel");
webdriver.findElement(By.id("email")).sendKeys("samuel(a)vimes.dw");
webdriver.findElement(By.id("phoneNumber")).sendKeys("1234567890");
webdriver.findElement(By.id("register")).submit();
// FIXME with Graphene, you can wait for a request
Assert.assertTrue(true);
}
{code}
{code:xml}
<!-- configuration for WebDrivers -->
<extension qualifier="webdriver">
<property
name="browserCapabilities">${browser:chrome}</property>
<property
name="firefoxBinary">/opt/firefox-9.0.1/firefox-bin</property>
<property
name="chromeBinary">/opt/google/chrome/chrome</property>
<property name="chromeSwitches">--user-data-dir=/tmp
--disable-web-security</property>
</extension>
{code}
Both chromeBinary and chromeSwitches are ignored. If you use @Drone ChromeDriver instead,
you get proper capabilities setup.
This means that a mapping between capabilities and Arquillian properties has to be
improved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira