November 2013 - arquillian-issues

[JBoss JIRA] (ARQ-1567) Explain validation errors in more depth

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1567: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha3 > Explain validation errors in more depth > --------------------------------------- > > Key: ARQ-1567 > URL: https://issues.jboss.org/browse/ARQ-1567 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > In many cases, it is not sufficient to provide a user just with stack trace when something goes wrong, for example, from this one: > {code} > java.lang.IllegalStateException: Directory to check against readability is null object or empty string. > at org.arquillian.droidium.container.configuration.Validate.notNullOrEmpty(Validate.java:98) > at org.arquillian.droidium.container.configuration.Validate.isReadableDirectory(Validate.java:147) > at org.arquillian.droidium.container.configuration.AndroidSDK.<init>(AndroidSDK.java:189) > at org.arquillian.droidium.container.AndroidDeployableContainer.setup(AndroidDeployableContainer.java:153) > {code} > It basically says that user does not have specified JAVA_HOME but he can not know that without looking into sources which is *totally* not desired. > Review all crucial configuration properties and its setters / getters and be sure that when it fails user knows whats going on. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1578) @ArquillianResource is not injected for WebSocket Client Endpoint

by Arun Gupta (JIRA)

Arun Gupta created ARQ-1578: ------------------------------- Summary: @ArquillianResource is not injected for WebSocket Client Endpoint Key: ARQ-1578 URL: https://issues.jboss.org/browse/ARQ-1578 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Arun Gupta Priority: Minor @ArquillianResource URI uri; throws the following exception: Caused by: java.lang.RuntimeException: Provider for type class java.net.URI returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URIResourceProvider@f9dd284 at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:115) at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:57) ... 90 more for a WebSocket client endpoint. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1537) Support for Safari browser

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1537?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1537: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/4b7f7fd63.... Thanks! > Support for Safari browser > -------------------------- > > Key: ARQ-1537 > URL: https://issues.jboss.org/browse/ARQ-1537 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.CR1 > Environment: Mac OS X > Reporter: Sona Jamborova > Assignee: Jiri Locker > Fix For: drone_1.3.next > > > I found out that SafariDriver is a part of selenium server from version 2.30 (our version is 2.33). I try to use "safari" for property "browserCapabilities" in arquillian.xml, but I get an exception: > java.lang.IllegalStateException: Unable to initialize WebDriver instance. Please specify a valid browserCapabilities instead of safari. Available options are: firefox, android, htmlUnit, chrome, opera, phantonsjs, iphone, internetExplorer. > Can you add support for Safari? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1534: ---------------------------------------- https://code.google.com/p/android/issues/detail?id=62645 > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1534: ---------------------------------------- [~kpiwko] {quote} That should be avoided. AndroidDebugBridge should be run in a separate process instead. {quote} The problem is that it is just a method to call and that method in is AndroidDebugBridge ddmlib Droidium depends on so there is not really any process to execute. >From Droidium point of view we call this: {code} AndroidDebugBridge.initIfNeeded(false); {code} and this method propagates internally to method in ddmlib which gets environment property via System.getenv("ANDROID_ADB_SERVER_PORT") so that port is set. As I said, it seems there is no (sane) way how to change environment property once JVM started. You are right about the possiblity to be able to use environment properties in arquillian.xml via ${env.SOME_ENV_PROPERTY} but how would you change some in runtime? > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reopened ARQ-1534: ------------------------------------ > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1577) Do not start Android container when there is not android browser in webdriver extension specified

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1577?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1577: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha3 > Do not start Android container when there is not android browser in webdriver extension specified > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1577 > URL: https://issues.jboss.org/browse/ARQ-1577 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > This is related to ARQ-1509 but it is Droidium specific. > When I do have both Android and JBoss adapter classes on class path and when I want to test on regular desktop browser only (meaning browser property in webdriver extension configuration is not set to "android"), there is no need to start Android container so it should not be started. > The solution is to listen to [DroidiumExtensionConfigured|https://github.com/arquillian/arquillian-droi...] event. It is fired when some Droidium extension is fired. Extensions are configured before containers are started so that is the right time to remove container def from ContainerRegistry so that Android container will not be started afterwards. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1577) Do not start Android container when there is not android browser in webdriver extension specified

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1577?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1577. ------------------------------------ Resolution: Done > Do not start Android container when there is not android browser in webdriver extension specified > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1577 > URL: https://issues.jboss.org/browse/ARQ-1577 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > This is related to ARQ-1509 but it is Droidium specific. > When I do have both Android and JBoss adapter classes on class path and when I want to test on regular desktop browser only (meaning browser property in webdriver extension configuration is not set to "android"), there is no need to start Android container so it should not be started. > The solution is to listen to [DroidiumExtensionConfigured|https://github.com/arquillian/arquillian-droi...] event. It is fired when some Droidium extension is fired. Extensions are configured before containers are started so that is the right time to remove container def from ContainerRegistry so that Android container will not be started afterwards. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1577) Do not start Android container when there is not android browser in webdriver extension specified

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1577?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1577: ---------------------------------------- Implemented in https://github.com/arquillian/arquillian-droidium/commit/b349ffdc45fdc4ce... Example how it is done: https://github.com/arquillian/arquillian-droidium/commit/074e45d73e7dcba9... > Do not start Android container when there is not android browser in webdriver extension specified > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1577 > URL: https://issues.jboss.org/browse/ARQ-1577 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > This is related to ARQ-1509 but it is Droidium specific. > When I do have both Android and JBoss adapter classes on class path and when I want to test on regular desktop browser only (meaning browser property in webdriver extension configuration is not set to "android"), there is no need to start Android container so it should not be started. > The solution is to listen to [DroidiumExtensionConfigured|https://github.com/arquillian/arquillian-droi...] event. It is fired when some Droidium extension is fired. Extensions are configured before containers are started so that is the right time to remove container def from ContainerRegistry so that Android container will not be started afterwards. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1577) Do not start Android container when there is not android browser in webdriver extension specified

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1577?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1577: -------------------------------------- Assignee: Stefan Miklosovic > Do not start Android container when there is not android browser in webdriver extension specified > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1577 > URL: https://issues.jboss.org/browse/ARQ-1577 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > This is related to ARQ-1509 but it is Droidium specific. > When I do have both Android and JBoss adapter classes on class path and when I want to test on regular desktop browser only (meaning browser property in webdriver extension configuration is not set to "android"), there is no need to start Android container so it should not be started. > The solution is to listen to [DroidiumExtensionConfigured|https://github.com/arquillian/arquillian-droi...] event. It is fired when some Droidium extension is fired. Extensions are configured before containers are started so that is the right time to remove container def from ContainerRegistry so that Android container will not be started afterwards. -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2013