November 2013 - arquillian-issues

[JBoss JIRA] (ARQGRA-414) Update ftest to pass with Safari

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-414?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-414: ----------------------------------- Thanks Jiri, I will merge it asap. > Update ftest to pass with Safari > -------------------------------- > > Key: ARQGRA-414 > URL: https://issues.jboss.org/browse/ARQGRA-414 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: ftest > Affects Versions: 2.0.0.Final > Reporter: Jiri Locker > > Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with {{mvn clean test -Dbrowser=safari}} in ftest module. > The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. -- 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] (ARQGRA-415) Cloudbees matrix job fails with NPE

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-415: --------------------------------- Summary: Cloudbees matrix job fails with NPE Key: ARQGRA-415 URL: https://issues.jboss.org/browse/ARQGRA-415 Project: Arquillian Graphene Issue Type: Task Reporter: Lukáš Fryč https://arquillian.ci.cloudbees.com/job/arquillian-graphene-webdriver-fte... {code} Error Message Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.jboss.arquillian.graphene.ftest.condition.ConditionsTestCase.createTestArchive() Stacktrace java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.jboss.arquillian.graphene.ftest.condition.ConditionsTestCase.createTestArchive() at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:177) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:99) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:62) at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:173) ... 54 more Caused by: java.lang.NullPointerException at org.jboss.arquillian.graphene.ftest.Resource$ResourceBuilder.all(Resource.java:81) at org.jboss.arquillian.graphene.ftest.Resources.all(Resources.java:65) at org.jboss.arquillian.graphene.ftest.condition.ConditionsTestCase.createTestArchive(ConditionsTestCase.java:79) ... 59 more {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, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-414) Update ftest to pass with Safari

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-414?page=com.atlassian.jira.plugin... ] Jiri Locker updated ARQGRA-414: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/92 This should fix 5 tests. > Update ftest to pass with Safari > -------------------------------- > > Key: ARQGRA-414 > URL: https://issues.jboss.org/browse/ARQGRA-414 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: ftest > Affects Versions: 2.0.0.Final > Reporter: Jiri Locker > > Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with {{mvn clean test -Dbrowser=safari}} in ftest module. > The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. -- 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] (ARQGRA-414) Update ftest to pass with Safari

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-414?page=com.atlassian.jira.plugin... ] Jiri Locker updated ARQGRA-414: ------------------------------- Description: Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with {{mvn clean test -Dbrowser=safari}} in ftest module. The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. was:Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with mvn clean test -Dbrowser=safari in ftest module. The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. > Update ftest to pass with Safari > -------------------------------- > > Key: ARQGRA-414 > URL: https://issues.jboss.org/browse/ARQGRA-414 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: ftest > Affects Versions: 2.0.0.Final > Reporter: Jiri Locker > > Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with {{mvn clean test -Dbrowser=safari}} in ftest module. > The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. -- 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] (ARQGRA-414) Update ftest to pass with Safari

by Jiri Locker (JIRA)

Jiri Locker created ARQGRA-414: ---------------------------------- Summary: Update ftest to pass with Safari Key: ARQGRA-414 URL: https://issues.jboss.org/browse/ARQGRA-414 Project: Arquillian Graphene Issue Type: Enhancement Components: ftest Affects Versions: 2.0.0.Final Reporter: Jiri Locker Support for SafariDriver was recently added to Drone. It is possible to run ftest agaist Safari (on Mac) with mvn clean test -Dbrowser=safari in ftest module. The initial result was 16 failures out of 274 tests. The failing tests should be fixed before stating Safari support by Graphene. -- 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-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 reassigned ARQ-1580: -------------------------------------- Assignee: Stefan Miklosovic > 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 > > 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, 5 months

1
0
0 / 0

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

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1581: -------------------------------------- Assignee: Stefan Miklosovic > 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 > Priority: Critical > > *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-1581) Droidium does not work with remote emulators

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1581: -------------------------------- Summary: 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 Priority: Critical *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-1580) Provide better AVD logging information

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1580: -------------------------------- Summary: 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 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1579) Prepare JRebel 1.0.0.Alpha1

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1579?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1579. ------------------------------ Resolution: Done pushed to nexus > Prepare JRebel 1.0.0.Alpha1 > --------------------------- > > Key: ARQ-1579 > URL: https://issues.jboss.org/browse/ARQ-1579 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - JRebel > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jrebel_1.0.0.Alpha1 > > -- 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