July 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-454?page=com.atlassian.jira.plugin... ] Juergen Zimmermann commented on ARQGRA-454: ------------------------------------------- [~jhuska] Hello Juraj, I'm booked out this week. I'll try to provide a testcase till the end of next week. > NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final > -------------------------------------------------------------- > > Key: ARQGRA-454 > URL: https://issues.jboss.org/browse/ARQGRA-454 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Juergen Zimmermann > > I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. > The stacktrace: > {code} > org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: > Error while initializing: class de.shop.util.IndexPage > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) > at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) > at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) > at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) > at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) > ... 34 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1813) REST TestSuite has execution order issues

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/ARQ-1813?page=com.atlassian.jira.plugin.s... ] Bernard Labno resolved ARQ-1813. -------------------------------- Resolution: Done Resolved in 52a5a6b3d34ab599090f15f4f5a3ddd82066aaf1 > REST TestSuite has execution order issues > ----------------------------------------- > > Key: ARQ-1813 > URL: https://issues.jboss.org/browse/ARQ-1813 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - REST > Reporter: Aslak Knutsen > Assignee: Bernard Labno > Fix For: rest_1.0.0.next > > > Depending on the @Test method execution order the REST test suite randomly fail. > This seems to effect all ftests and local tests, RestClientTestCase. > If the ban* @Test methods are executed first, everything is ok. The banX methods will call findAllCustomers on CustomerResourceImpl and if it's the first call create Customer with id (nextId()) 1 and 2 which the Test Case is trying to lookup. > If on the other hand some of the following @Test methods run first, createCustomerBareResource, manualClassModifier, nextId() is invoked and when banX methods are called later and the 'customer list' is created, the expected Customers now have id 3-4. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1813) REST TestSuite has execution order issues

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1813?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1813: ------------------------------------ Created temp fix to allow Alpha3 release to go through; https://github.com/arquillian/arquillian-extension-rest/commit/c9146cc4a8... > REST TestSuite has execution order issues > ----------------------------------------- > > Key: ARQ-1813 > URL: https://issues.jboss.org/browse/ARQ-1813 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - REST > Reporter: Aslak Knutsen > Assignee: Bernard Labno > Fix For: rest_1.0.0.next > > > Depending on the @Test method execution order the REST test suite randomly fail. > This seems to effect all ftests and local tests, RestClientTestCase. > If the ban* @Test methods are executed first, everything is ok. The banX methods will call findAllCustomers on CustomerResourceImpl and if it's the first call create Customer with id (nextId()) 1 and 2 which the Test Case is trying to lookup. > If on the other hand some of the following @Test methods run first, createCustomerBareResource, manualClassModifier, nextId() is invoked and when banX methods are called later and the 'customer list' is created, the expected Customers now have id 3-4. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1813) REST TestSuite has execution order issues

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1813?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1813: ------------------------------- Fix Version/s: rest_1.0.0.next (was: rest_1.0.0.Alpha3) > REST TestSuite has execution order issues > ----------------------------------------- > > Key: ARQ-1813 > URL: https://issues.jboss.org/browse/ARQ-1813 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - REST > Reporter: Aslak Knutsen > Assignee: Bernard Labno > Fix For: rest_1.0.0.next > > > Depending on the @Test method execution order the REST test suite randomly fail. > This seems to effect all ftests and local tests, RestClientTestCase. > If the ban* @Test methods are executed first, everything is ok. The banX methods will call findAllCustomers on CustomerResourceImpl and if it's the first call create Customer with id (nextId()) 1 and 2 which the Test Case is trying to lookup. > If on the other hand some of the following @Test methods run first, createCustomerBareResource, manualClassModifier, nextId() is invoked and when banX methods are called later and the 'customer list' is created, the expected Customers now have id 3-4. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1813) REST TestSuite has execution order issues

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1813: ---------------------------------- Summary: REST TestSuite has execution order issues Key: ARQ-1813 URL: https://issues.jboss.org/browse/ARQ-1813 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - REST Reporter: Aslak Knutsen Assignee: Bernard Labno Fix For: rest_1.0.0.Alpha3 Depending on the @Test method execution order the REST test suite randomly fail. This seems to effect all ftests and local tests, RestClientTestCase. If the ban* @Test methods are executed first, everything is ok. The banX methods will call findAllCustomers on CustomerResourceImpl and if it's the first call create Customer with id (nextId()) 1 and 2 which the Test Case is trying to lookup. If on the other hand some of the following @Test methods run first, createCustomerBareResource, manualClassModifier, nextId() is invoked and when banX methods are called later and the 'customer list' is created, the expected Customers now have id 3-4. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1812) Add Jersey Client support

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1812?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1812: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-rest/pull/17/ > Add Jersey Client support > ------------------------- > > Key: ARQ-1812 > URL: https://issues.jboss.org/browse/ARQ-1812 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - REST > Affects Versions: rest_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Bernard Labno > Fix For: rest_1.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1812) Add Jersey Client support

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1812?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1812: ------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done > Add Jersey Client support > ------------------------- > > Key: ARQ-1812 > URL: https://issues.jboss.org/browse/ARQ-1812 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - REST > Affects Versions: rest_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Bernard Labno > Fix For: rest_1.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1812) Add Jersey Client support

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1812?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1812: ------------------------------- Assignee: Bernard Labno > Add Jersey Client support > ------------------------- > > Key: ARQ-1812 > URL: https://issues.jboss.org/browse/ARQ-1812 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - REST > Affects Versions: rest_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Bernard Labno > Fix For: rest_1.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1812) Add Jersey Client support

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1812: ---------------------------------- Summary: Add Jersey Client support Key: ARQ-1812 URL: https://issues.jboss.org/browse/ARQ-1812 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - REST Affects Versions: rest_1.0.0.Alpha2 Reporter: Aslak Knutsen Fix For: rest_1.0.0.Alpha3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-449) Graphene can not switch between contexts

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-449?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-449: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Graphene can not switch between contexts > ---------------------------------------- > > Key: ARQGRA-449 > URL: https://issues.jboss.org/browse/ARQGRA-449 > Project: Arquillian Graphene > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 2.0.3.Final > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: 2.0.4.Final > > > This code: > {code} > @Test > public void nativeViewTest() > { > driver.switchTo().window("NATIVE_APP"); > } > {code} > That window() parameter is Selendroid-related and it has nothing to do with Graphene. Graphene is just not able to handle that. > It produces this exception: > {code} > java.lang.IllegalArgumentException: methods with same signature getContext() but incompatible return types: [class java.lang.String, class org.jboss.arquillian.graphene.context.GrapheneContext] > at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:686) > at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:437) > at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:323) > at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:636) > at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.createProxy(GrapheneProxy.java:166) > at org.jboss.arquillian.graphene.proxy.GrapheneProxy.getProxyForTargetWithInterfaces(GrapheneProxy.java:92) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:165) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy27.window(Unknown Source) > at org.arquillian.droidium.showcase.hybrid.test01.SelendroidHybridTestAppTestCase.nativeViewTest(SelendroidHybridTestAppTestCase.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2014