[JBoss JIRA] (ARQ-1350) Drone: allow reuse of session even though all capabilities are not serializable
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1350?page=com.atlassian.jira.plugin.s... ]
Karel Piwko closed ARQ-1350.
----------------------------
> Drone: allow reuse of session even though all capabilities are not serializable
> -------------------------------------------------------------------------------
>
> Key: ARQ-1350
> URL: https://issues.jboss.org/browse/ARQ-1350
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Labels: graphene-sprint
> Fix For: drone_1.2.0.Alpha2
>
>
> Remote drivers might store non-serializable instances in Capabilities map.
> Drone fails to reuse such browsers since it is not able to store and serialize their capabilities in ReusedSession object.
> One example of such a driver is PhantomJSDriver which stores object under key 'proxy': com.google.common.collect.Maps$TransformedEntriesMap.
> ---
> In order to maximize ability of session reusal, Drone may avoid reusing driver's capabilities at own, but try serialization of each capabilities entry separately and store them in new instance of DesiredCapabilities.
> This allows to reuse PhantomJS sessions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (ARQ-1314) Better exception message when creating a new instance fails
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1314?page=com.atlassian.jira.plugin.s... ]
Karel Piwko closed ARQ-1314.
----------------------------
> Better exception message when creating a new instance fails
> -----------------------------------------------------------
>
> Key: ARQ-1314
> URL: https://issues.jboss.org/browse/ARQ-1314
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.2.0.Alpha1
> Reporter: Jiri Locker
> Assignee: Jiri Locker
> Fix For: drone_1.2.0.Alpha2
>
>
> org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance() catches a number of exceptions and rethrows them with better description hinting at what might be wrong with arquillian configuration. In the case of catching InvocationTargetException, more important is its cause, whose message describes the problem. However this piece of code:
> {code:java}
> } catch (InvocationTargetException e) {
> throw new RuntimeException(
> "Unable to instantiate Drone via " + getConstructorName(...),
> e.getCause());
> }
> {code}
> will provide stack trace of the cause, but its message is not included, producing an exception looking like:
> {noformat}java.lang.RuntimeException: Unable to instantiate Drone via org.openqa.selenium.firefox.FirefoxDriver(Capabilities)
> {noformat}
> The exception handling code should be improved so that the message of InovcationTargetException's cause is included in the wrapping RuntimeException message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months