March 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1362) Unable to inject (jms) ContainerFactory (via any of various methods)

by Marco Rietveld (JIRA)

Marco Rietveld created ARQ-1362: ----------------------------------- Summary: Unable to inject (jms) ContainerFactory (via any of various methods) Key: ARQ-1362 URL: https://issues.jboss.org/browse/ARQ-1362 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBoss AS Containers Affects Versions: 1.0.3.Final Reporter: Marco Rietveld I've tried the following tests: - https://community.jboss.org/thread/198882 - https://github.com/arquillian/arquillian-showcase/blob/master/jms And neither approach (injecting the InitialContext or using @Resource to inject ConnectionFactory seems to work. I'm using jBoss AS 7.1.1.Final to test this. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1325) Warp: replace piggy-backing on request/response with direct test->filter communication

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1325?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1325 started by Lukáš Fryč. > Warp: replace piggy-backing on request/response with direct test->filter communication > -------------------------------------------------------------------------------------- > > Key: ARQ-1325 > URL: https://issues.jboss.org/browse/ARQ-1325 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We can do similar processing as we did with CommandService here: > https://github.com/arquillian/arquillian-extension-warp/blob/aa0745237f5d... > The CommandService communicates with the WarpFilter asynchronously and its requests are not processed directly, they delegates to the request-serving routine. > ---- > This way, Warp could: > 0. request is issued against proxy > 1. catch the request on the proxy > 2. register the RequestPayload (with Inspection) in the registry via the WarpFilter (under generated request-specific UUID) > 3. proxy passes request to WarpFilter with a request header which contains UUID > 4. WarpFilter associates Inspection from the registry with given request > 5. Warp proceeds with a request inspection > 6. response is commited and sent back to the proxy (with given UUID as response header) > 7. proxy catches the response and obtains ResponsePayload (with Inspection result) from the WarpFilter (using UUID) > 8. proxy processes the ResponsePayload and passes the request to the client > 9. the client processes response > This would avoid a need for piggy-backing on request/response, so it will also eliminate need for response-wrapping (NonWritingResponse). -- 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

11 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č resolved ARQ-1361. ----------------------------- Resolution: Done > 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.Alpha3 > > > See the [Forum Reference]. > The message could state: > {code} > The warped request timed out when waiting for a response for the request [GET /login.jsf]. > The 2 other request/-s were noticed by Warp for the given activity: [GET /authenticated.jsf] and [GET /header.png]. > There were no requests done for observer: [request().uri().contains("/rest")]. > If Warp enriched a 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1291) Warp: single request execution does enrich only first request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1291?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1291. ----------------------------- Resolution: Done > Warp: single request execution does enrich only first request > ------------------------------------------------------------- > > Key: ARQ-1291 > URL: https://issues.jboss.org/browse/ARQ-1291 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When single-request execution API is used > {code} > Warp.initiate(Activity) > .inspect(Inspection); > {code} > then the default filter is applied which says that only first request can be enriched, > and thus when user-provided filter selects second or further request, nothing will be enriched. > In fact it should work in the way that first user-selected request is enriched. -- 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

11 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: ---------------------------- Sprint: Warp Alpha3 > 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.Alpha3 > > > See the [Forum Reference]. > The message could state: > {code} > The warped request timed out when waiting for a response for the request [GET /login.jsf]. > The 2 other request/-s were noticed by Warp for the given activity: [GET /authenticated.jsf] and [GET /header.png]. > There were no requests done for observer: [request().uri().contains("/rest")]. > If Warp enriched a 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-279) Support for method Graphene.element(WebElement, By) and its condition isPresent

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-279?page=com.atlassian.jira.plugin... ] Jan Papousek resolved ARQGRA-279. --------------------------------- Resolution: Out of Date Closing since there is an already working API for this scenario. > Support for method Graphene.element(WebElement, By) and its condition isPresent > ------------------------------------------------------------------------------- > > Key: ARQGRA-279 > URL: https://issues.jboss.org/browse/ARQGRA-279 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api > Reporter: Sona Jamborova > > Please, can you add support for method Graphene.element(WebElement, By) for searching element (located by By) in parent element. > Motivation: > A panel which display content of current directory. Operations with this panel are open a file, open a child directory, go back. The content of this panel depends on file system and we use different file system for our test. I need create general framework for our tests. I think about: > {code} > public class Designer { > ... > @FindBy(jquery = "div.tabbable:contains('Project Explorer')") > private ProjectExplorer projExpl; > ... > } > {code} > {code} > public class ProjectExplorer { > ... > @Root > private WebElement root; > > @FindBy(css = "table>tr:first-child() div"); > private WebElement path; > ... > > public void openFile(String path) { > String[] parts = path.split("/"); > for (String part: parts) { > By by = jquerySelector(format("a.gwt-Anchor:contains('%s')", part)); > waitAjax().until(element(root, by).isPresent()); > root.findElement(by).click(); //this should be reduce to waitAjax().until(element(root, by).isPresent()).click(); (this is not point of this issue) > } > } > public String getPath () { > return path.getText(); > } > } > {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

11 years, 9 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-269?page=com.atlassian.jira.plugin... ] Jan Papousek resolved ARQGRA-269. --------------------------------- Resolution: Out of Date I've added functional tests (https://github.com/arquillian/arquillian-graphene/commit/b42708ce1d9562fe...). The issue should be already resolved by ARQGRA-273. > 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: Jan Papousek > 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

11 years, 9 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-269?page=com.atlassian.jira.plugin... ] Work on ARQGRA-269 started by Jan Papousek. > 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: Jan Papousek > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-287) Deprecate Graphene.element and attribute methods

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-287?page=com.atlassian.jira.plugin... ] Jan Papousek resolved ARQGRA-287. --------------------------------- Resolution: Done > Deprecate Graphene.element and attribute methods > ------------------------------------------------ > > Key: ARQGRA-287 > URL: https://issues.jboss.org/browse/ARQGRA-287 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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

11 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]. The message could state: {code} The warped request timed out when waiting for a response for the request [GET /login.jsf]. The 2 other request/-s were noticed by Warp for the given activity: [GET /authenticated.jsf] and [GET /header.png]. There were no requests done for observer: [request().uri().contains("/rest")]. If Warp enriched a 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 a response for the request [GET /login.jsf]. The 2 other request/-s were noticed by Warp for the given activity: [GET /authenticated.jsf] and [GET /header.png]. If Warp enriched a 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.Alpha3 > > > See the [Forum Reference]. > The message could state: > {code} > The warped request timed out when waiting for a response for the request [GET /login.jsf]. > The 2 other request/-s were noticed by Warp for the given activity: [GET /authenticated.jsf] and [GET /header.png]. > There were no requests done for observer: [request().uri().contains("/rest")]. > If Warp enriched a 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

11 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2013