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

Stefan Miklosovic (JIRA) jira-events at lists.jboss.org
Wed Nov 20 08:51:05 EST 2013


     [ 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: 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


More information about the arquillian-issues mailing list