Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-1048

RemoteWebDriver ignores old configuration properties

XMLWordPrintable

    • Workaround Exists
    • Hide

      specify a capability instead, e.g.

      <property name=capabilityChromeBinary>/path/to/binary</property>
      Show
      specify a capability instead, e.g. <property name=capabilityChromeBinary> /path/to/binary </property>

      If you set up a Drone Webdriver with given capability, original configuration is completely ignored, e.g.:

      public void simpleWebdriverTest(@Drone RemoteWebDriver webdriver) {
        webdriver.get(contextPath.toString());

        webdriver.findElement(By.id("name")).sendKeys("Samuel");
        webdriver.findElement(By.id("email")).sendKeys("samuel@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);
    }

      <!-- 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>

      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.

              kpiwko Karel Piwko
              kpiwko Karel Piwko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: