[JBoss JIRA] (ARQ-1537) Support for Safari browser
by Jiri Locker (JIRA)
[ https://issues.jboss.org/browse/ARQ-1537?page=com.atlassian.jira.plugin.s... ]
Jiri Locker resolved ARQ-1537.
------------------------------
Resolution: Done
Pull request: https://github.com/arquillian/arquillian-extension-drone/pull/30
> 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, 10 months
[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:
-----------------------------------
Description:
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.
was:
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 [https://github.com/arquillian/arquillian-droidium/blob/master/droidium-co...] - extensions are configured before containers are started so that is time to remove container def from ContainerRegistry so that one will not be started afterwards.
> 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
>
> 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, 10 months
[JBoss JIRA] (ARQ-1577) Do not start Android container when there is not android browser in webdriver extension specified
by Stefan Miklosovic (JIRA)
Stefan Miklosovic created ARQ-1577:
--------------------------------------
Summary: 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
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 [https://github.com/arquillian/arquillian-droidium/blob/master/droidium-co...] - extensions are configured before containers are started so that is time to remove container def from ContainerRegistry so that one 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, 10 months
[JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1509.
------------------------------------
Resolution: Done
> Arquillian Droidium Multiple Container does not work correctly when used standalone
> -----------------------------------------------------------------------------------
>
> Key: ARQ-1509
> URL: https://issues.jboss.org/browse/ARQ-1509
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Priority: Critical
> Fix For: droidium_1.0.0.Alpha3
>
>
> Supposing you want to use web based testing with Droidium.
> In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers.
> However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate <group> in order to do that.
> Otherwise, MultipleContainer Extension will let Arquillian create container def for each <container> in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration.
> This will obvisously fail, for instance with
> {code}
> org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist
> at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139)
> {code}
> So, if you put only multicontainer extension jar into <dependencies>, behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser.
> This represents a serious usability issues, hence marked as Critical.
--
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, 10 months
[JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1509:
----------------------------------------
https://github.com/arquillian/arquillian-droidium/commit/8d3db439aa9e6738...
related test
https://github.com/arquillian/arquillian-droidium/commit/60efc6092dd47ea3...
There are two containers in arquillian.xml but only that one which has adapter class on classpath is registered into container registry by MultipleContainerRegistryCreator. There is simple guesser made which maps container defs to container adapters in the background.
The next step is to not start Android container when its adapter class is on classpath but there is not android browser in webdriver extension properties found.
This is related to arquillian-droidium-container artifact hence I create new JIRA and mark this as closed.
> Arquillian Droidium Multiple Container does not work correctly when used standalone
> -----------------------------------------------------------------------------------
>
> Key: ARQ-1509
> URL: https://issues.jboss.org/browse/ARQ-1509
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Priority: Critical
>
> Supposing you want to use web based testing with Droidium.
> In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers.
> However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate <group> in order to do that.
> Otherwise, MultipleContainer Extension will let Arquillian create container def for each <container> in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration.
> This will obvisously fail, for instance with
> {code}
> org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist
> at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139)
> {code}
> So, if you put only multicontainer extension jar into <dependencies>, behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser.
> This represents a serious usability issues, hence marked as Critical.
--
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, 10 months
[JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1509:
-----------------------------------
Fix Version/s: droidium_1.0.0.Alpha3
> Arquillian Droidium Multiple Container does not work correctly when used standalone
> -----------------------------------------------------------------------------------
>
> Key: ARQ-1509
> URL: https://issues.jboss.org/browse/ARQ-1509
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Priority: Critical
> Fix For: droidium_1.0.0.Alpha3
>
>
> Supposing you want to use web based testing with Droidium.
> In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers.
> However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate <group> in order to do that.
> Otherwise, MultipleContainer Extension will let Arquillian create container def for each <container> in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration.
> This will obvisously fail, for instance with
> {code}
> org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist
> at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139)
> {code}
> So, if you put only multicontainer extension jar into <dependencies>, behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser.
> This represents a serious usability issues, hence marked as Critical.
--
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, 10 months
[JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1509:
----------------------------------------
[~kpiwko]
The solution to this one is to modify default [ContainerRegistryCreator|https://github.com/arquillian/arquillian-core/bl...] which is already done for multicontainers purposes in [MultipleContainerRegistryCreator|https://github.com/arquillian/arquillian...] however when we want to control which containers get registered and which not from underlying ArquillianDescriptor, there is a need to be able to recognize if some container def is backed by actual container adapter class.
Lets say you have a group of Droidium and JBoss but you do not have Droidium container on classpath. To prevent your behaviour, I need to recognize that some container def relates to Android container in order to not add it to registry. And here, we can just guess ... It is _simple_ to use it for Android purpose, i just filter if container qualifier is something like "android" and when not, i can check the presence of other Android related properties and act accordingly, but in general I humbly guess it is quite unsolvable.
> Arquillian Droidium Multiple Container does not work correctly when used standalone
> -----------------------------------------------------------------------------------
>
> Key: ARQ-1509
> URL: https://issues.jboss.org/browse/ARQ-1509
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Priority: Critical
>
> Supposing you want to use web based testing with Droidium.
> In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers.
> However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate <group> in order to do that.
> Otherwise, MultipleContainer Extension will let Arquillian create container def for each <container> in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration.
> This will obvisously fail, for instance with
> {code}
> org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist
> at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139)
> {code}
> So, if you put only multicontainer extension jar into <dependencies>, behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser.
> This represents a serious usability issues, hence marked as Critical.
--
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, 10 months
[JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1509:
-----------------------------------
Comment: was deleted
(was: "If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser" - that is right however I do not know how that should be implemented. Is it even possible to start the container on purpose when both of them are configured in arq.xml? When you do not want that container in the ContainerRegistry, you have to decide that android container is not going to be added there (so it will not be started) which in turn means there has to be some logic behind which scans arquillian.xml and scans webdriver extensions to test them of the presence of android browser configuration property.
I do not say it is wrong idea but I do not like the fact that container implementation depends / knows something "outside" like extensions ... it should be totally isolated from anything else.
Since DroidiumNativeConfiguration and DroidiumWebConfiguration are treated before Android container startup, I could do that logic in extensions and I would remove Android container from already filled container registry so when StartContainer gets treated, there will be only JBoss container to start since there is no android browser for drone extension which in turn means android container should not be started.)
> Arquillian Droidium Multiple Container does not work correctly when used standalone
> -----------------------------------------------------------------------------------
>
> Key: ARQ-1509
> URL: https://issues.jboss.org/browse/ARQ-1509
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Priority: Critical
>
> Supposing you want to use web based testing with Droidium.
> In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers.
> However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate <group> in order to do that.
> Otherwise, MultipleContainer Extension will let Arquillian create container def for each <container> in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration.
> This will obvisously fail, for instance with
> {code}
> org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist
> at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139)
> {code}
> So, if you put only multicontainer extension jar into <dependencies>, behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser.
> This represents a serious usability issues, hence marked as Critical.
--
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, 10 months
[JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1509:
-----------------------------------
Comment: was deleted
(was: In addition to the last paragraph, when I do as said there, it means that I do not allow a user the very specific scenario when he uses just firefox browser and (e.g.) JBoss AS instance and he wants to do any other Android related operations since I just scanned Arquillian descriptor and when android browser was not found, I stopped that container from being started. But the fact is that a user could even after this somehow interact with the device - and he can not.
If this is not any big deal, I'll do as it was said previously.)
> Arquillian Droidium Multiple Container does not work correctly when used standalone
> -----------------------------------------------------------------------------------
>
> Key: ARQ-1509
> URL: https://issues.jboss.org/browse/ARQ-1509
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha1
> Reporter: Karel Piwko
> Priority: Critical
>
> Supposing you want to use web based testing with Droidium.
> In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers.
> However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate <group> in order to do that.
> Otherwise, MultipleContainer Extension will let Arquillian create container def for each <container> in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration.
> This will obvisously fail, for instance with
> {code}
> org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist
> at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139)
> {code}
> So, if you put only multicontainer extension jar into <dependencies>, behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser.
> This represents a serious usability issues, hence marked as Critical.
--
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, 10 months
[JBoss JIRA] (ARQ-1537) Support for Safari browser
by Jiri Locker (JIRA)
[ https://issues.jboss.org/browse/ARQ-1537?page=com.atlassian.jira.plugin.s... ]
Work on ARQ-1537 started by Jiri Locker.
> 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, 10 months