7:26 p.m.
Katie Miller created ARQ-1075:
---------------------------------
Summary: 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.CR2, drone_1.1.0.CR1
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
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
7:28 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
Katie Miller updated ARQ-1075:
------------------------------
Steps to Reproduce:
- Declare the following dependencies, where Drone version is 1.1.0.CR1/2:
{code}
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-drone-webdriver</artifactId>
<version>${drone.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-drone-webdriver-depchain</artifactId>
<version>${drone.version}</version>
<type>pom</type>
<scope>test</scope>
</dependency>
{code}
- Create an arquillian.xml like this:
{code}
<arquillian xmlns="http://jboss.org/schema/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://jboss.org/schema/arquillian
http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
<extension qualifier="webdriver">
<property name="browserCapabilities">firefox</property>
<property
name="capabilityWebdriverFirefoxBin">/usr/bin/firefox</property>
</extension>
</arquillian>
{code}
- Create an Arquillian test using a WebDriver and run it
- See an Exception like this:
{code}
java.lang.NullPointerException
at
org.openqa.selenium.remote.DesiredCapabilities.<init>(DesiredCapabilities.java:51)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration$5.invoke(TypedWebDriverConfiguration.java:268)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration$5.invoke(TypedWebDriverConfiguration.java:259)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration$CallInterceptor.intercept(TypedWebDriverConfiguration.java:65)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration.getCapabilities(TypedWebDriverConfiguration.java:274)
at
org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:79)
at
org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:42)
at
org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129)
at
org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:43)
at
org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71)
etc.
{code}
was:
- Declare the following dependencies, where Drone version is 1.1.0.CR1/2:
{code}
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-drone-webdriver</artifactId>
<version>${drone.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-drone-webdriver-depchain</artifactId>
<version>${drone.version}</version>
<type>pom</type>
<scope>test</scope>
</dependency>
{code}
- Create an arquillian.xml like this:
{code}
<arquillian xmlns="http://jboss.org/schema/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://jboss.org/schema/arquillian
http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
<extension qualifier="webdriver">
<property name="browserCapabilities">firefox</property>
<property
name="capabilityWebdriverFirefoxBin">/usr/bin/firefox</property>
</extension>
</arquillian>
{code}
- Create an Arquillian test using a WebDriver and run it
- See an Exception like this:
{code}
java.lang.NullPointerException
at
org.openqa.selenium.remote.DesiredCapabilities.<init>(DesiredCapabilities.java:51)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration$5.invoke(TypedWebDriverConfiguration.java:268)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration$5.invoke(TypedWebDriverConfiguration.java:259)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration$CallInterceptor.intercept(TypedWebDriverConfiguration.java:65)
at
org.jboss.arquillian.drone.webdriver.configuration.TypedWebDriverConfiguration.getCapabilities(TypedWebDriverConfiguration.java:274)
at
org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:79)
at
org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:42)
at
org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129)
at
org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:43)
at
org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71)
etc.
{code}
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
7:28 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
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
7:38 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
Katie Miller updated ARQ-1075:
------------------------------
Environment: Running on Fedora, using OpenJDK7 and JBoss AS 7 as a container. Using
Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2. (was: 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.)
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
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
7:47 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
--
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
3:31 a.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
Karel Piwko commented on ARQ-1075:
----------------------------------
Katie,
do you have Drone BOM in <dependencyManagement> section?
{code:xml}
<!-- We use development version of Arquillian Drone -->
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-drone-bom</artifactId>
<version>${drone.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
{code}
This should fix the version related problem.
You're hitting NPE while using a generic WebDriver, right, e.g.?
{code}
@Drone WebDriver driver;
{code}
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
--
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
4:22 a.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
Karel Piwko commented on ARQ-1075:
----------------------------------
capabilityMap is initialized in ConfigurationMapper.class. I guess that
org.jboss.arquillian.extension:arquillian-drone-configuration artifact is still the
1.0.0.Final. This should be fixed by including the Drone BOM in
<depedencyManagement> as well.
Please let me know if that works for you.
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
--
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
4:50 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
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.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
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.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
--
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
4:52 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
Katie Miller commented on ARQ-1075:
-----------------------------------
Aha, yes, I did not realise the arquillian-drone-bom dependency needed to be declared
under <dependencyManagement> with import scope. It does work when declared that way.
Thank you.
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
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.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
--
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
4:54 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
Katie Miller edited comment on ARQ-1075 at 8/19/12 5:52 PM:
------------------------------------------------------------
Aha, yes, I did not realise the arquillian-drone-bom dependency needed to be declared
under <dependencyManagement> with import scope. It does work when declared that way.
I had it declared in the regular <dependencies> section with test scope. Thank you
for your help.
was (Author: codemiller):
Aha, yes, I did not realise the arquillian-drone-bom dependency needed to be declared
under <dependencyManagement> with import scope. It does work when declared that way.
Thank you.
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
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.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
--
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
4:56 p.m.
[
https://issues.jboss.org/browse/ARQ-1075?page=com.atlassian.jira.plugin.s...
]
Katie Miller resolved ARQ-1075.
-------------------------------
Fix Version/s: (was: drone_1.2.0.next)
Resolution: Done
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.
Using Arquillian 1.0.2.Final with Drone 1.1.0.CR1/2.
Reporter: Katie Miller
Assignee: Karel Piwko
Labels: Arquillian, Capabilities, Drone, WebDriver
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.
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. Going through the same steps described in
'Steps to Reproduce' with only the depchain dependency declared results in the
capability configuration not being recognised at all and the tests running with
HtmlUnitDriver.
--
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
4320
days inactive
4322
days old
arquillian-issues@lists.jboss.org
10 comments
2 participants
participants (2)
-
Karel Piwko (JIRA) -
Katie Miller (JIRA)