November 2013 - arquillian-issues

[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1582: ---------------------------------- This makes almost impossible to use Droidium in multitenant enviroments - e.g. Jenkins, as metadata are shared across all jobs.. > Honor ANDROID_SDK_HOME, deprecate generatedAvdPath > -------------------------------------------------- > > Key: ARQ-1582 > URL: https://issues.jboss.org/browse/ARQ-1582 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Critical > > ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME. > However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs. > Droidium should be able to: > * pass androidSdkHome in arquillian.xml with default = user.home > * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd > Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1582: ----------------------------- Priority: Critical (was: Major) > Honor ANDROID_SDK_HOME, deprecate generatedAvdPath > -------------------------------------------------- > > Key: ARQ-1582 > URL: https://issues.jboss.org/browse/ARQ-1582 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Critical > > ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME. > However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs. > Droidium should be able to: > * pass androidSdkHome in arquillian.xml with default = user.home > * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd > Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1582: ---------------------------------- ANDROID_SDK_HOME, specified in arquillian.xml needs to be propagated to ProcessExecutor, so swapned process are aware of it. > Honor ANDROID_SDK_HOME, deprecate generatedAvdPath > -------------------------------------------------- > > Key: ARQ-1582 > URL: https://issues.jboss.org/browse/ARQ-1582 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME. > However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs. > Droidium should be able to: > * pass androidSdkHome in arquillian.xml with default = user.home > * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd > Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1585) Droidium does not figure out AVD is broken

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1585: -------------------------------- Summary: Droidium does not figure out AVD is broken Key: ARQ-1585 URL: https://issues.jboss.org/browse/ARQ-1585 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha2 Reporter: Karel Piwko Priority: Blocker Current AVD name parsing is broken, it won't figure out that AVD is actually broken - for instance metadata point to AVD images that are no longer on filesystem. Even in such situations Drodium starts emulator, which is deemed to fail and Droidium waits up to all timeout to fail the test. Ideally, Droidium should handle such situation and figure out that metadata of broken device should be deleted if user requested that AVD by name. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1585) Droidium does not figure out AVD is broken

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1585?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1585: ---------------------------------- Hint: *android list avd -c* might be better format for parsing available device names. > Droidium does not figure out AVD is broken > ------------------------------------------ > > Key: ARQ-1585 > URL: https://issues.jboss.org/browse/ARQ-1585 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Priority: Blocker > > Current AVD name parsing is broken, it won't figure out that AVD is actually broken - for instance metadata point to AVD images that are no longer on filesystem. Even in such situations Drodium starts emulator, which is deemed to fail and Droidium waits up to all timeout to fail the test. > Ideally, Droidium should handle such situation and figure out that metadata of broken device should be deleted if user requested that AVD by name. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1581: ---------------------------------- This would need to fix DDMLIB or provide alternative way how Droidium works with Android SDK. > Droidium does not work with remote emulators > -------------------------------------------- > > Key: ARQ-1581 > URL: https://issues.jboss.org/browse/ARQ-1581 > 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 > > *When*: > I use Android Jenkins Plugin to start the device > *Then*: > It starts the emulator using remote syntax, that is including --port port1,port2 > *Expect*: > Drodium will connect to already running emulator. > *Actual problem*: > AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from adb devices. This results into Droidium trying to start emulator with the same name, however this emulator is already started so event marking correct startup is never send and test fails. > Output: > {code} > export ANDROID_ADB_SERVER_PORT=52892 > [tester@fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test ./tools/android-sdk/platform-tools/adb devices > List of devices attached > localhost:46689 device > {code} > However, emulators are expected to be in format of emulator-XYZ. > Drodium should be able to modify the behavior to handle this correctly. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1584) Remove duplication from Droidium modules

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1584: -------------------------------- Summary: Remove duplication from Droidium modules Key: ARQ-1584 URL: https://issues.jboss.org/browse/ARQ-1584 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha2 Reporter: Karel Piwko Currently, a lot of modules are not necessary and could be removed altogether to make structure simpler For instance, build per each native, container, web might be moved into a single build module, some depchain could be removed - depchain make more sense if there is a sense in including only a part of extension, which is not valid for native, web - it's all-or-nothing. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1581: ----------------------------- Priority: Major (was: Critical) > Droidium does not work with remote emulators > -------------------------------------------- > > Key: ARQ-1581 > URL: https://issues.jboss.org/browse/ARQ-1581 > 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 > > *When*: > I use Android Jenkins Plugin to start the device > *Then*: > It starts the emulator using remote syntax, that is including --port port1,port2 > *Expect*: > Drodium will connect to already running emulator. > *Actual problem*: > AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from adb devices. This results into Droidium trying to start emulator with the same name, however this emulator is already started so event marking correct startup is never send and test fails. > Output: > {code} > export ANDROID_ADB_SERVER_PORT=52892 > [tester@fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test ./tools/android-sdk/platform-tools/adb devices > List of devices attached > localhost:46689 device > {code} > However, emulators are expected to be in format of emulator-XYZ. > Drodium should be able to modify the behavior to handle this correctly. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1583: ----------------------------- Description: *When*: I let Droidium start emulator. *Given*: Emulator command fails, for instance when DISPLAY is not set. *Then*: Droidium waits up to emulator start time, then fails. *Expected*: Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. was: *When*: I let Droidium start emulator. *Given*: DISPLAY is not set. *Then*: Droidium waits up to emulator start time, then fails. *Expected*: Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Priority: Critical > > *When*: > I let Droidium start emulator. > *Given*: > Emulator command fails, for instance when DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1583: ----------------------------- Priority: Critical (was: Major) > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Priority: Critical > > *When*: > I let Droidium start emulator. > *Given*: > DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2013