February 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1655) NPE in WebDriverFactory.createInstance()

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created ARQ-1655: --------------------------------------- Summary: NPE in WebDriverFactory.createInstance() Key: ARQ-1655 URL: https://issues.jboss.org/browse/ARQ-1655 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: 1.1.3.Final Reporter: Juergen Zimmermann When I try to run my tests for Firefox (also Chrome and HtmlUnit) I'm getting the attached stacktrace. I also attach the output of "mvn dependency:tree" and arquillian.xml. My appserver is WildFly 8.0.0.Final. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1638) ChromeDriver binary capability is not propagated

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1638?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1638. ------------------------------ Assignee: Karel Piwko Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/b3e700862... > ChromeDriver binary capability is not propagated > ------------------------------------------------ > > Key: ARQ-1638 > URL: https://issues.jboss.org/browse/ARQ-1638 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.4.Final > > > Due to double deprecation checks, something a capability might get lost. > For instance: > * configuration contains *chromeBinary* field > * capability is named *chrome.binary* > Hence, when this is set, double deprecation message is emitted but capability is actually never put to map but field is set instead. Factory does not rely on deprecated field, expecting that legacy configurator did the work and value is effectively lost. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1638) ChromeDriver binary capability is not propagated

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1638?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1638: ----------------------------- Description: Due to double deprecation checks, something a capability might get lost. For instance: * configuration contains *chromeBinary* field * capability is named *chrome.binary* Hence, when this is set, double deprecation message is emitted but capability is actually never put to map but field is set instead. Factory does not rely on deprecated field, expecting that legacy configurator did the work and value is effectively lost. was: Latest ChromeDriver requires capabilities to be set in ChromeOptions object. Hence passing stuff like 'binary' from arquillian.properties does not work. > ChromeDriver binary capability is not propagated > ------------------------------------------------ > > Key: ARQ-1638 > URL: https://issues.jboss.org/browse/ARQ-1638 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Fix For: drone_1.2.4.Final > > > Due to double deprecation checks, something a capability might get lost. > For instance: > * configuration contains *chromeBinary* field > * capability is named *chrome.binary* > Hence, when this is set, double deprecation message is emitted but capability is actually never put to map but field is set instead. Factory does not rely on deprecated field, expecting that legacy configurator did the work and value is effectively lost. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1638) ChromeDriver binary capability is not propagated

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1638?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1638: ----------------------------- Summary: ChromeDriver binary capability is not propagated (was: Chrome driver options are not wrapped into ChromeOptions object) > ChromeDriver binary capability is not propagated > ------------------------------------------------ > > Key: ARQ-1638 > URL: https://issues.jboss.org/browse/ARQ-1638 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Priority: Critical > Fix For: drone_1.2.4.Final > > > Latest ChromeDriver requires capabilities to be set in ChromeOptions object. > Hence passing stuff like 'binary' from arquillian.properties does not work. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1638) ChromeDriver binary capability is not propagated

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1638?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1638: ----------------------------- Priority: Major (was: Critical) > ChromeDriver binary capability is not propagated > ------------------------------------------------ > > Key: ARQ-1638 > URL: https://issues.jboss.org/browse/ARQ-1638 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Fix For: drone_1.2.4.Final > > > Latest ChromeDriver requires capabilities to be set in ChromeOptions object. > Hence passing stuff like 'binary' from arquillian.properties does not work. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1653?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1653: ---------------------------------- Pushed upstream for Drone in https://github.com/arquillian/arquillian-extension-drone/commit/38c31b9c2... > Drone use concurrent.ExecutorService without Context inheritance on Threads > ---------------------------------------------------------------------------- > > Key: ARQ-1653 > URL: https://issues.jboss.org/browse/ARQ-1653 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > > Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. > Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. > https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1653?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1653: ----------------------------- Fix Version/s: drone_1.2.4.Final > Drone use concurrent.ExecutorService without Context inheritance on Threads > ---------------------------------------------------------------------------- > > Key: ARQ-1653 > URL: https://issues.jboss.org/browse/ARQ-1653 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: drone_1.2.4.Final > > > Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. > Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. > https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1654: ---------------------------------- This might get incorporated into Spacelift. Spacelift already has an executor service and provides a submit(*) method: https://github.com/arquillian/arquillian-spacelift/blob/master/spacelift-... Or the other way around, some parts of Spacelift might become the core. > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.0.0.Beta1 > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit\(\*\) methods should probably be enough. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-420) Port unified screenshooter implementation for Graphene into Graphene project itself

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-420?page=com.atlassian.jira.plugin... ] Stefan Miklosovic commented on ARQGRA-420: ------------------------------------------ Well, the idea is just to ship it with Graphene in some way or have it in some kind of bom so it would not been technically on classpath unless you explicity use that dependency in your target pom. I would go for placing it to impl/screenshooter and make it as standalone dependency. However I am not sure what about versioning then. > Port unified screenshooter implementation for Graphene into Graphene project itself > ----------------------------------------------------------------------------------- > > Key: ARQGRA-420 > URL: https://issues.jboss.org/browse/ARQGRA-420 > Project: Arquillian Graphene > Issue Type: Task > Components: api, build, core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > Port screenshooter implementation from unified screenshooter repository, [here|https://github.com/smiklosovic/arquillian-unified-recorder/tree/mast...], > into Graphene project repository. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-420) Port unified screenshooter implementation for Graphene into Graphene project itself

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-420?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-420: ----------------------------------- Does it makes sense to place it into {{impl}} under {{org.jboss.arquillian.graphene.integration}} package? It would need to make sure that extension won't try to register itself unless appropriate API artifacts are on classpath. > Port unified screenshooter implementation for Graphene into Graphene project itself > ----------------------------------------------------------------------------------- > > Key: ARQGRA-420 > URL: https://issues.jboss.org/browse/ARQGRA-420 > Project: Arquillian Graphene > Issue Type: Task > Components: api, build, core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > Port screenshooter implementation from unified screenshooter repository, [here|https://github.com/smiklosovic/arquillian-unified-recorder/tree/mast...], > into Graphene project repository. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2014