September 2013 - arquillian-issues

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

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1509: -------------------------------- Summary: 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) 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

12 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 updated ARQ-1509: ----------------------------- Affects Version/s: droidium_1.0.0.Alpha1 > 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) > 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

12 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 updated ARQ-1509: ----------------------------- Component/s: Extension - Droidium > 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1508) WindowResizer does not fail-safe on Android

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1508: -------------------------------- Summary: WindowResizer does not fail-safe on Android Key: ARQ-1508 URL: https://issues.jboss.org/browse/ARQ-1508 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.0.CR1 Reporter: Karel Piwko WindowResizer does fails when running on Android with {code} org.openqa.selenium.WebDriverException: Window handling not supported on Android {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1507) Make usage of Arquillian Droidium stack easier

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1507: -------------------------------- Summary: Make usage of Arquillian Droidium stack easier Key: ARQ-1507 URL: https://issues.jboss.org/browse/ARQ-1507 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha1 Reporter: Karel Piwko Currently, Droidium consists of 3 thinks: 1/ Container 2/ Native extension 3/ Web extension User can arbitrary combine these extensions. For that reason, it would be great if container, which is always used, will emit some huge warning in case that it discovers Drone is injected and browser==android and web extension is missing on class path. Similarly, container should be able to figure out that native extension is missing but it will likely be needed - as it has access to @Instrumented deployments. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1506) Rename Droidium Container artifactId

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1506: -------------------------------- Summary: Rename Droidium Container artifactId Key: ARQ-1506 URL: https://issues.jboss.org/browse/ARQ-1506 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha1 Reporter: Karel Piwko Current *org.arquillian.container:arquillian-droidium-container-depchain:pom* does not follow naming for other containers. It would be great to remove -depchain and make this non pom but jar artifact. Note that depchain does not make much sense here anyway. You either want the container or don't wont the container. Depchains are used to simplify usage of tools that are often extended and consists of many components. For the same matter, it might be reasonable to just rename *-impl artifact for the container to be the new depchain replacement, that is arquillian-droidium-container. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1505) Wrong handling of Android Debug Bridge initialization

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1505: -------------------------------- Summary: Wrong handling of Android Debug Bridge initialization Key: ARQ-1505 URL: https://issues.jboss.org/browse/ARQ-1505 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha1 Reporter: Karel Piwko When ADB is started, but the port is already occupied by a different tooling, it logs an E/ddms message, however it continues with the execution. This is indeed faulty behaviour. The port should be configurable, if the port is occupied - it should fail with Unable to start container or unable to connect to the running container exception - similar to behavior you experience with other remote / managed containers. {code} org.arquillian.droidium.container.impl.AndroidBridgeImpl connect INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true 10:01:23 E/ddms: Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by something else, choose a new port number in the preferences. Sep 27, 2013 10:01:23 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge INFO: Android Debug Bridge was initialized in 350ms. {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-834) Executing Android packaged tests in Arquillian

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-834?page=com.atlassian.jira.plugin.sy... ] Karel Piwko updated ARQ-834: ---------------------------- Fix Version/s: (was: android_1.0.0.next) > Executing Android packaged tests in Arquillian > ---------------------------------------------- > > Key: ARQ-834 > URL: https://issues.jboss.org/browse/ARQ-834 > Project: Arquillian > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: android_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Aleksey Shilin > > Once the packaging problem is figured out, the next step consists of bringing user a way how to configure what should be tested in Arquillian test. > More information about Android is here http://developer.android.com/guide/topics/testing/testing_android.html, focus on "Running Tests" section. > Possible proposal > {code} > @RunWith(Arquillian.class) > public class AndroidTest { > > @Test > public void androidActivity(@AndroidActivity HelloAndroid helloAndroid) { > mView = (TextView) mActivity.findViewById(com.example.helloandroid.R.id.textview); > resourceString = mActivity.getString(com.example.helloandroid.R.string.hello); > assertEquals(resourceString,(String)mView.getText()); > } > } > {code} > You can obviously inject into fields, make this a class scoped, not method scoped etc. Feel free to experiment and figure out what is the most convenient for users. > Also note that your infrastructure should support Robotium in future. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-831) Allow Arquillian to execute Android Integration tests

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-831?page=com.atlassian.jira.plugin.sy... ] Karel Piwko updated ARQ-831: ---------------------------- Fix Version/s: (was: android_1.0.0.next) > Allow Arquillian to execute Android Integration tests > ----------------------------------------------------- > > Key: ARQ-831 > URL: https://issues.jboss.org/browse/ARQ-831 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: android_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Aleksey Shilin > > InstrumentationTestRunner is a foundation for running integration tests on Android. > !http://developer.android.com/images/testing/test_framework.png! > The task is about decoupling InstrumentationTestRunner from Android SDK and integrate it into Arquillian. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-833) Packaging test application for Android devices

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-833?page=com.atlassian.jira.plugin.sy... ] Karel Piwko updated ARQ-833: ---------------------------- Fix Version/s: (was: android_1.0.0.next) > Packaging test application for Android devices > ---------------------------------------------- > > Key: ARQ-833 > URL: https://issues.jboss.org/browse/ARQ-833 > Project: Arquillian > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: android_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Aleksey Shilin > > Figure out what is needed for test application packaging w.r.t. > http://developer.android.com/guide/topics/testing/testing_android.html > You would probably have to check out basic directory structure for Android based tests, InstrumentationTestCaseRunner and how this is used in a sample Android Test project together. I can recommend you to start with a plain Android Test project generated from an IDE and investigate what happens inside during execution. > The key is to abstract needed steps and bring them to Arquillian (or even to ShrinkWrap if needed). -- 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

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2013