[arquillian-issues] [JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone

[Stefan Miklosovic (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925393#comment-12925393 ] 

Stefan Miklosovic commented on ARQ-1509:
----------------------------------------

https://github.com/arquillian/arquillian-droidium/commit/8d3db439aa9e6738a6b071af67fbc6635a8b7a2e

related test

https://github.com/arquillian/arquillian-droidium/commit/60efc6092dd47ea3fa92dd4337d659a98fbbf811

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