[arquillian-issues] [JBoss JIRA] (ARQ-1075) Problem with Drone when configuring WebDriver via Capabilities interface

[Katie Miller (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Katie Miller updated ARQ-1075:
------------------------------

    Description: 
According to the release highlights at http://planet.jboss.org/post/arquillian_drone_extension_1_1_0_cr1_released, Drone should now have the capability to configure WebDriver using the Capabilities interface. However, when attempted, a NullPointerException is thrown by the TypedWebDriverConfiguration class, which attempts to run the code {code}new DesiredCapabilities(TypedWebDriverConfiguration.this.capabilityMap){code} on the class variable 'capabilityMap', which does not seem to be initialised anywhere. This occurs both in version 1.1.0.CR1 of the Drone WebDriver extension and version 1.1.0.CR2. As a result, it does not seem possible to configure a WebDriver this way.

Note that in order to use version 1.1.0.CR1/2 of the WebDriver extension, the artifact 'arquillian-drone-webdriver' must be declared as a Maven dependency. If only 'arquillian-drone-webdriver-depchain' is declared as a dependency, the version of 'arquillian-drone-webdriver' used is one older than 1.1.0.CR1, even if the version given for the depchain is 1.1.0.CR1 or higher.



  was:
According to the release highlights at http://planet.jboss.org/post/arquillian_drone_extension_1_1_0_cr1_released), Drone should now have the capability to configure WebDriver using the Capabilities interface. However, when attempted, a NullPointerException is thrown by the TypedWebDriverConfiguration class, which attempts to run the code {code}new DesiredCapabilities(TypedWebDriverConfiguration.this.capabilityMap){code} on the class variable 'capabilityMap', which does not seem to be initialised anywhere. This occurs both in version 1.1.0.CR1 of the Drone WebDriver extension and version 1.1.0.CR2. As a result, it does not seem possible to configure a WebDriver this way.

Note that in order to use version 1.1.0.CR1/2 of the WebDriver extension, the artifact 'arquillian-drone-webdriver' must be declared as a Maven dependency. If only 'arquillian-drone-webdriver-depchain' is declared as a dependency, the version of 'arquillian-drone-webdriver' used is one older than 1.1.0.CR1, even if the version given for the depchain is 1.1.0.CR1 or higher.




    
> Problem with Drone when configuring WebDriver via Capabilities interface
> ------------------------------------------------------------------------
>
>                 Key: ARQ-1075
>                 URL: https://issues.jboss.org/browse/ARQ-1075
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Drone
>    Affects Versions: drone_1.1.0.CR1, drone_1.1.0.CR2
>         Environment: Running on Fedora, using OpenJDK7 and JBoss AS 7 as a container. Tried with Drone 1.1.0.CR1 WebDriver extension and Drone 1.1.0.CR2 WebDriver extension.
>            Reporter: Katie Miller
>            Assignee: Karel Piwko
>              Labels: Arquillian, Capabilities, Drone, WebDriver
>             Fix For: drone_1.2.0.next
>
>
> According to the release highlights at http://planet.jboss.org/post/arquillian_drone_extension_1_1_0_cr1_released, Drone should now have the capability to configure WebDriver using the Capabilities interface. However, when attempted, a NullPointerException is thrown by the TypedWebDriverConfiguration class, which attempts to run the code {code}new DesiredCapabilities(TypedWebDriverConfiguration.this.capabilityMap){code} on the class variable 'capabilityMap', which does not seem to be initialised anywhere. This occurs both in version 1.1.0.CR1 of the Drone WebDriver extension and version 1.1.0.CR2. As a result, it does not seem possible to configure a WebDriver this way.
> Note that in order to use version 1.1.0.CR1/2 of the WebDriver extension, the artifact 'arquillian-drone-webdriver' must be declared as a Maven dependency. If only 'arquillian-drone-webdriver-depchain' is declared as a dependency, the version of 'arquillian-drone-webdriver' used is one older than 1.1.0.CR1, even if the version given for the depchain is 1.1.0.CR1 or higher.

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