[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:all-tabpanel ]

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