[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 edited comment on ARQ-1509 at 10/26/13 8:45 PM:
------------------------------------------------------------------
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 …
[View More]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.
was (Author: smikloso):
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 is not found, I stopped that container from being started. But the fact is that a user could even after this somehow interact with 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
[View Less]
11 years, 2 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:
----------------------------------------
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 is not found, I stopped …
[View More]that container from being started. But the fact is that a user could even after this somehow interact with 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
[View Less]
11 years, 2 months
[JBoss JIRA] (ARQ-1533) Uninstall packages from device before test when they are already installed
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1533?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1533.
------------------------------------
Fix Version/s: droidium_1.0.0.Alpha3
Resolution: Done
https://github.com/arquillian/arquillian-droidium/commit/bc93c4a953149546...
> Uninstall packages from device before test when they are already installed
> --------------------------------------------------------------------------
>
> …
[View More] Key: ARQ-1533
> URL: https://issues.jboss.org/browse/ARQ-1533
> Project: Arquillian
> Issue Type: Feature Request
> 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
>
>
> Given: Android device prior to test.
> When: I run test with packages to be installed which are already in Android device.
> I expect: old packages will be uninstalled and packages from current test run will be installed
> This situation can happen if something really horrible happens and whole test fails in the middle so packages are not uninstalled (Selendroid server and ordinary apks as well). When I run tests for the second time, I want that packages will be removed and installed once again to get them fresh.
> Example: We could use different rebuilt Selendroid server which has the same package name but it is rebuilt for another application.
--
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
[View Less]
11 years, 2 months
[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 edited comment on ARQ-1534 at 10/26/13 7:49 PM:
------------------------------------------------------------------
The port where Android debug bridge server component communicates when trying to connect to adb clients on emulator can be set by property ANDROID_ADB_SERVER_PORT.
This property has to be environment one. You can set environment property e.g. by exporting it in your shell by …
[View More]export command or you can setup your pom.xml as specified in the comment to this issue. Every emulator in that test run will talk to that server instance so it should not collide with the clients of Eclipse's DDMS.
was (Author: smikloso):
The port where Android debug bridge server component communicates when trying to connect to adb clients on emulator can be set by environment property ANDROID_ADB_SERVER_PORT.
This property has to be environment one. You can set environment property e.g. by exporting it in your shell by export command or you can setup your pom.xml as specified in the comment to this issue. Every emulator in that test run will talk to that server instance so it should not collide with the clients of Eclipse's DDMS.
> 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
[View Less]
11 years, 2 months