[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:
----------------------------
Fix Version/s: warp_1.0.0.Alpha3
(was: warp_1.0.0.Beta1)
> 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].
> 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
13 years
[JBoss JIRA] (ARQGRA-269) Argument is of an illegal type, when attempting to switchTo an iframe
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-269?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-269:
-----------------------------------
The {{AbstractWebElementEnricher}} took care about the injected element proxies implementing WrapsElement:
http://grepcode.com/file/repository.jboss.org$nexus$content$repositories$...
Jan, is the issue based in fact the WebElement is found using {{findElement}} instead of injecting by TestEnricher?
We should make sure all proxied elements implements the required interfaces & registers required invocation handlers.
> 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
13 years
[JBoss JIRA] (ARQGRA-269) Argument is of an illegal type, when attempting to switchTo an iframe
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-269?page=com.atlassian.jira.plugin... ]
Lukáš Fryč reassigned ARQGRA-269:
---------------------------------
Assignee: Jan Papousek (was: Lukáš Fryč)
> 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
13 years
[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... ]
Work on ARQ-1291 started by Lukáš Fryč.
> 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
13 years
[JBoss JIRA] (ARQ-1286) Support Warp on Java EE 5 (Servlets 2.5) compliant containers
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1286?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč reassigned ARQ-1286:
-------------------------------
Assignee: Lukáš Fryč
> Support Warp on Java EE 5 (Servlets 2.5) compliant containers
> -------------------------------------------------------------
>
> Key: ARQ-1286
> URL: https://issues.jboss.org/browse/ARQ-1286
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Warp is currently focused on Java EE 6 and higher, since it uses {{@WebFilter}} annotation to intercept incoming requests.
> We may decide to support Servlets 2.5 containers as well in case there is enough interest (please vote if you are interested).
--
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
13 years
[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č reassigned ARQ-1291:
-------------------------------
Assignee: Lukáš Fryč
> 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
13 years
[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... ]
Lukáš Fryč reassigned ARQ-1325:
-------------------------------
Assignee: 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
13 years
[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... ]
Lukáš Fryč updated ARQ-1325:
----------------------------
Sprint: Critical Issues, Warp Alpha3 (was: Critical Issues)
> 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č
> 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
13 years