March 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1361) Warp: bring more clarity to ServerResponseTimeoutException failures

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1361?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1361: ---------------------------- Description: See the [Forum Reference]. The message could state: {code} The warped request timed out when waiting for response for request [GET /login.jsf]. If it is wrong request, use observe(...) method to select appropriate request which should be enriched instead. Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. {code} was: See the [Forum Reference]. The message could state: {code} The warped request timed out when waiting for response for request [GET /login.jsf]. If it is wrong request, use observe(...) method to select appropriate request which should be enriched instead. Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. {code} > Warp: bring more clarity to ServerResponseTimeoutException failures > ------------------------------------------------------------------- > > Key: ARQ-1361 > URL: https://issues.jboss.org/browse/ARQ-1361 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Beta1 > > > See the [Forum Reference]. > The message could state: > {code} > The warped request timed out when waiting for response for request [GET /login.jsf]. > If it is wrong request, use observe(...) method to select appropriate request which should be enriched instead. > Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1361) Warp: bring more clarity to ServerResponseTimeoutException failures

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1361?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1361: ---------------------------- Description: See the [Forum Reference] > Warp: bring more clarity to ServerResponseTimeoutException failures > ------------------------------------------------------------------- > > Key: ARQ-1361 > URL: https://issues.jboss.org/browse/ARQ-1361 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Beta1 > > > See the [Forum Reference] -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1361) Warp: bring more clarity to ServerResponseTimeoutException failures

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1361: ------------------------------- Summary: Warp: bring more clarity to ServerResponseTimeoutException failures Key: ARQ-1361 URL: https://issues.jboss.org/browse/ARQ-1361 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha2 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: warp_1.0.0.Beta1 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-269) Argument is of an illegal type, when attempting to switchTo an iframe

by Sona Jamborova (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-269?page=com.atlassian.jira.plugin... ] Sona Jamborova commented on ARQGRA-269: --------------------------------------- Does some workaround exist for this issue? > Argument is of an illegal type, when attempting to switchTo an iframe > --------------------------------------------------------------------- > > Key: ARQGRA-269 > URL: https://issues.jboss.org/browse/ARQGRA-269 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.Alpha3 > Environment: Windows 7 > JDK 1.7U10 64-bit > Drone 1.2.0Alpha > Graphen 2.0.0.Alpha3 > Reporter: Simon Knott > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Alpha4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I am getting the following exception thrown when attempting to switchTo() an iframe: > {code}java.lang.IllegalArgumentException: Argument is of an illegal type: $Proxy26 > at org.openqa.selenium.remote.internal.WebElementToJsonConverter.apply(WebElementToJsonConverter.java:78) > at org.openqa.selenium.remote.RemoteWebDriver$RemoteTargetLocator.frame(RemoteWebDriver.java:797) > 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:601) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:209) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler$1.invoke(GrapheneProxyHandler.java:140) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invoke(GrapheneProxyHandler.java:170) > at $Proxy27.frame(Unknown Source){code} > The test code which is causing the exception looks like: > {code}WebElement iframe = driver.findElement(By.tagName("iframe")); > TargetLocator targetLocator = driver.switchTo(); > targetLocator.frame(iframe);{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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-659) Testclass is missing in test.ear when bundling EnterpriseArchive with Arquillian.

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-659?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak updated ARQ-659: ------------------------------- Assignee: Bartosz Majsak > Testclass is missing in test.ear when bundling EnterpriseArchive with Arquillian. > ---------------------------------------------------------------------------------- > > Key: ARQ-659 > URL: https://issues.jboss.org/browse/ARQ-659 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Integration Test Suite > Affects Versions: 1.0.0.CR2 > Environment: Windows 64bit, Netbeans 7.07, Glassfish 3.1.1, Maven 3.03, testng 6.3, arquillian resolver 1.1.0-alpha-1 > Reporter: Hanspeter Gisler > Assignee: Bartosz Majsak > Labels: Arquillian, EAR, EnterpriseArchive > > if shrink wrapping in the following way: > {code} > @Deployment > public static EnterpriseArchive createTestArchive() { > JavaArchive jar = ShrinkWrap.create(JavaArchive.class,"test.jar").addClasses( > SomeClass1.class, > SomeClass2.class) > .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); > > File file = new File("src/test/resources/arquillian-application.xml"); > > EnterpriseArchive ear = ShrinkWrap.create(EnterpriseArchive.class, "test.ear") > .addAsLibraries(DependencyResolvers.use(MavenDependencyResolver.class) > .artifact("org.demo.test:util:1.0-SNAPSHOT").resolveAs(GenericArchive.class)) > .setApplicationXML(file) > .addAsLibraries(jar) > return ear; > } > {code} > then the actual test class (the one extending Arquillian.class) is nowhere to be found in {code}test.ear{code}. > This means a "no class def found" exception is beeing thrown by the container upon test execution after deployment. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-700) Properties in arquillian.xml should handle new lines (by trimming them)

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-700?page=com.atlassian.jira.plugin.sy... ] Bartosz Majsak updated ARQ-700: ------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-core/pull/47/files > Properties in arquillian.xml should handle new lines (by trimming them) > ------------------------------------------------------------------------ > > Key: ARQ-700 > URL: https://issues.jboss.org/browse/ARQ-700 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Configuration > Affects Versions: 1.0.0.CR6 > Reporter: Hardy Ferentschik > Labels: starter > > When trying to add _javaVmArguments_ to _arquillian.xml_ in order to debug the container new lines in the property will cause the container start to fail. > For example, the following works: > {code} > <arquillian xmlns="http://jboss.org/schema/arquillian" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > <engine> > <property name="deploymentExportPath">target/</property> > </engine> > <container qualifier="jboss" default="true"> > <protocol type="jmx-as7"> > <property name="executionType">REMOTE</property> > </protocol> > <configuration> > <property name="jbossHome">target/jboss-as-7.1.0.Beta1</property> > <property name="javaVmArguments">-Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=y -Xmx512m -XX:MaxPermSize=128m</property> > </configuration> > </container> > </arquillian> > {code} > whereas this fails: > {code} > <arquillian xmlns="http://jboss.org/schema/arquillian" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > <engine> > <property name="deploymentExportPath">target/</property> > </engine> > <container qualifier="jboss" default="true"> > <protocol type="jmx-as7"> > <property name="executionType">REMOTE</property> > </protocol> > <configuration> > <property name="jbossHome">target/jboss-as-7.1.0.Beta1</property> > <property name="javaVmArguments"> > -Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=y -Xmx512m -XX:MaxPermSize=128m > </property> > </configuration> > </container> > </arquillian> > {code} > given that often people use auto-formatting for xml the parser should take care of this and trim the configuration value. Also the resulting exception for the case where the value is on a new line is very confusing: > {noformat} > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:180) > at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:78) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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:134) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:71) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:199) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:62) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [30] s > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:176) > ... 65 more > {noformat} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-170) Merge all static contexts to one (GrapheneContext)

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-170?page=com.atlassian.jira.plugin... ] Work on ARQGRA-170 stopped by Jan Papousek. > Merge all static contexts to one (GrapheneContext) > -------------------------------------------------- > > Key: ARQGRA-170 > URL: https://issues.jboss.org/browse/ARQGRA-170 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Merge the following static contexts to one: > - GrapheneContext > - GrapheneConfigurationContext > - GraphenePageExtensionsContext -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-170) Merge all static contexts to one (GrapheneContext)

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-170?page=com.atlassian.jira.plugin... ] Work on ARQGRA-170 started by Jan Papousek. > Merge all static contexts to one (GrapheneContext) > -------------------------------------------------- > > Key: ARQGRA-170 > URL: https://issues.jboss.org/browse/ARQGRA-170 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Merge the following static contexts to one: > - GrapheneContext > - GrapheneConfigurationContext > - GraphenePageExtensionsContext -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-283) Create blog entry about Graphene vs WebDriver

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-283?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-283: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Create blog entry about Graphene vs WebDriver > --------------------------------------------- > > Key: ARQGRA-283 > URL: https://issues.jboss.org/browse/ARQGRA-283 > Project: Arquillian Graphene > Issue Type: Task > Components: doc > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Create blog entry about core differences between WebDriver and Graphene. It should summarize all Graphene features to promote it. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-283) Create blog entry about Graphene vs WebDriver

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-283?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-283: ------------------------------- Description: Create blog entry about core differences between WebDriver and Graphene. It should summarize all Graphene features to promote them. (was: Create blog entry about core differences between WebDriver and Graphene. It should summarize all Graphene features to promote it.) > Create blog entry about Graphene vs WebDriver > --------------------------------------------- > > Key: ARQGRA-283 > URL: https://issues.jboss.org/browse/ARQGRA-283 > Project: Arquillian Graphene > Issue Type: Task > Components: doc > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.0.0.Alpha4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Create blog entry about core differences between WebDriver and Graphene. It should summarize all Graphene features to promote them. -- 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, 9 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 March 2013