December 2013 - arquillian-issues

[JBoss JIRA] (ARQ-1568) Droidium fails if emulator is about to start and there is not API level 10 and apiLevel is not in config

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1568?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1568. ---------------------------------- > Droidium fails if emulator is about to start and there is not API level 10 and apiLevel is not in config > -------------------------------------------------------------------------------------------------------- > > Key: ARQ-1568 > URL: https://issues.jboss.org/browse/ARQ-1568 > Project: Arquillian > Issue Type: Enhancement > 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: > 1. Already existing emulator with API level != 10 available > 2. Emulator is not started prior to tests > 3. API level 10 is not installed locally on developers machine > 4. apiLevel configuration option is not set in arquillian.xml > When: > I want to start emulator with the environment above > Then: > Droidium does not fail. > The reason why it fails is that in case AVD of such name in avdName property does not exist, Droidium tries to create AVD dynamically and it is deleted after tests. Default API level is 10 so when apiLevel is not specified, it attempts to create emulator with that API level, but it might not be present on the system - so it fails. > The workaround could be to filter all available API level and choose the lowest one as the default one and not API level 10 which is set statically. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1571) Remove API 10 from default platform

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1571?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1571: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha3 > Remove API 10 from default platform > ----------------------------------- > > Key: ARQ-1571 > URL: https://issues.jboss.org/browse/ARQ-1571 > 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 > Fix For: droidium_1.0.0.Alpha3 > > > Related to fix ARQ-1568, it is no longer necessary to check for API 10 presence. Default behavior could simply be to find out newest (highest) API level if no level is specified to create the AVD. -- 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, 6 months

1
0
0 / 0

[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 closed ARQ-1533. ---------------------------------- > Uninstall packages from device before test when they are already installed > -------------------------------------------------------------------------- > > 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1547) Improve the parsing of activities from AndroidManifest.xml of AUT

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1547?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1547. ---------------------------------- > Improve the parsing of activities from AndroidManifest.xml of AUT > ----------------------------------------------------------------- > > Key: ARQ-1547 > URL: https://issues.jboss.org/browse/ARQ-1547 > 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 > > > Current parsing of activities from AndroidManifest.xml during activity scanning is not sufficient. There are cases when parser gets lost like package contains "activity" string but parser relies on the appearance of that string somewhere else which ends up with IndexOutOfBoundException. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1571) Remove API 10 from default platform

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1571?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1571. ---------------------------------- > Remove API 10 from default platform > ----------------------------------- > > Key: ARQ-1571 > URL: https://issues.jboss.org/browse/ARQ-1571 > 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 > Fix For: droidium_1.0.0.Alpha3 > > > Related to fix ARQ-1568, it is no longer necessary to check for API 10 presence. Default behavior could simply be to find out newest (highest) API level if no level is specified to create the AVD. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1567) Explain validation errors in more depth

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1567. ---------------------------------- > Explain validation errors in more depth > --------------------------------------- > > Key: ARQ-1567 > URL: https://issues.jboss.org/browse/ARQ-1567 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > In many cases, it is not sufficient to provide a user just with stack trace when something goes wrong, for example, from this one: > {code} > java.lang.IllegalStateException: Directory to check against readability is null object or empty string. > at org.arquillian.droidium.container.configuration.Validate.notNullOrEmpty(Validate.java:98) > at org.arquillian.droidium.container.configuration.Validate.isReadableDirectory(Validate.java:147) > at org.arquillian.droidium.container.configuration.AndroidSDK.<init>(AndroidSDK.java:189) > at org.arquillian.droidium.container.AndroidDeployableContainer.setup(AndroidDeployableContainer.java:153) > {code} > It basically says that user does not have specified JAVA_HOME but he can not know that without looking into sources which is *totally* not desired. > Review all crucial configuration properties and its setters / getters and be sure that when it fails user knows whats going on. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1577) Do not start Android container when there is not android browser in webdriver extension specified

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1577?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1577. ---------------------------------- > Do not start Android container when there is not android browser in webdriver extension specified > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1577 > URL: https://issues.jboss.org/browse/ARQ-1577 > Project: Arquillian > Issue Type: Enhancement > 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 > > > This is related to ARQ-1509 but it is Droidium specific. > When I do have both Android and JBoss adapter classes on class path and when I want to test on regular desktop browser only (meaning browser property in webdriver extension configuration is not set to "android"), there is no need to start Android container so it should not be started. > The solution is to listen to [DroidiumExtensionConfigured|https://github.com/arquillian/arquillian-droi...] event. It is fired when some Droidium extension is fired. Extensions are configured before containers are started so that is the right time to remove container def from ContainerRegistry so that Android container will not be started afterwards. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1580) Provide better AVD logging information

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1580?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1580. ---------------------------------- > Provide better AVD logging information > -------------------------------------- > > Key: ARQ-1580 > URL: https://issues.jboss.org/browse/ARQ-1580 > 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 > Fix For: droidium_1.0.0.Alpha3 > > > In case there is an AVD match, provide a debug output for it, such as > {code} > Name: random-avd > Path: /home/kpiwko/.android/avd/random-avd.avd > Target: Android 4.2.2 (API level 17) > ABI: x86 > Skin: 480x800 > {code} > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1587) Droidium has to fail when there is already started emulator on the same ports

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1587: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha3 (was: 1.0.0.Alpha3) > Droidium has to fail when there is already started emulator on the same ports > ----------------------------------------------------------------------------- > > Key: ARQ-1587 > URL: https://issues.jboss.org/browse/ARQ-1587 > 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 > Fix For: droidium_1.0.0.Alpha3 > > > Given: > Already started emulator on some console and adb port. > When: > I specify in arquillian.xml that I want to start emulator on such port which matches the one which is used by already started emulator. > Then: > Droidium fails to start it and provides a reason why. > Use case: > I have already started emulator and I want to start another one and with explicitly specified ports from configuration. These ports are already used by the first emulator. Droidium has to fail. There has to be some free port checking utility. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1587) Droidium has to fail when there is already started emulator on the same ports

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1587. ---------------------------------- > Droidium has to fail when there is already started emulator on the same ports > ----------------------------------------------------------------------------- > > Key: ARQ-1587 > URL: https://issues.jboss.org/browse/ARQ-1587 > 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 > Fix For: droidium_1.0.0.Alpha3 > > > Given: > Already started emulator on some console and adb port. > When: > I specify in arquillian.xml that I want to start emulator on such port which matches the one which is used by already started emulator. > Then: > Droidium fails to start it and provides a reason why. > Use case: > I have already started emulator and I want to start another one and with explicitly specified ports from configuration. These ports are already used by the first emulator. Droidium has to fail. There has to be some free port checking utility. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2013