December 2013 - arquillian-issues

[JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1590. ---------------------------- Resolution: Done > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > 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 > > > Bump jboss-parent from version 11 to version 12. -- 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 Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.s... ] Karel Piwko reopened ARQ-1587: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > 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 > Assignee: 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-1590) Update JBoss parent to the latest one

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.s... ] Karel Piwko reopened ARQ-1590: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > 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 > > > Bump jboss-parent from version 11 to version 12. -- 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 Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1587. ---------------------------- Resolution: Done > 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 > Assignee: 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-1567) Explain validation errors in more depth

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1567. ---------------------------- Assignee: Stefan Miklosovic Resolution: Done > 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 > Assignee: 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-1567) Explain validation errors in more depth

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.s... ] Karel Piwko reopened ARQ-1567: ------------------------------ Reopened to change asignee > 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-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1509. ---------------------------- Resolution: Done > 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 > Assignee: Stefan Miklosovic > Priority: Critical > Fix For: droidium_1.0.0.Alpha3 > > > 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

10 years, 6 months

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.s... ] Karel Piwko reopened ARQ-1509: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > 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 > Assignee: Stefan Miklosovic > Priority: Critical > Fix For: droidium_1.0.0.Alpha3 > > > 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

10 years, 6 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 closed ARQ-1585. ---------------------------- Resolution: Done > 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 > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha3 > > > 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, 6 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 reopened ARQ-1585: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > 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 > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha3 > > > 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, 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