[JBoss JIRA] (ARQGRA-280) refactor handling of staleness
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-280:
------------------------------
Sprint: Sprint for Alpha4
> refactor handling of staleness
> ------------------------------
>
> Key: ARQGRA-280
> URL: https://issues.jboss.org/browse/ARQGRA-280
> Project: Arquillian Graphene
> Issue Type: Task
> Affects Versions: 2.0.0.Alpha3
> Reporter: Jan Papousek
> Assignee: Jan Papousek
> Fix For: 2.0.0.Alpha4
>
>
> The current situation of handling staleness is it works purely accidentally in some cases and it prevents any caching of web elements.
> Imagine the following code:
> {code}
> Action action = new Actions(driver).moveToElement(element).build();
> ... // some action causing staleness
> action.perform();
> {code}
> The previous code doesn't throw StaleElementReferenceException only in the case when the action causing staleness finishes before the requested action starts performing and when there is no caching of web elements. Currently Graphene can't force the action to perform again when StaleElementReferenceException is thrown.
> In the case of caching the scenerio would be:
> # element is loaded and put to the cache
> # ... some actions ...
> # action causing staleness is performed
> # the requested action starts performing
> -- cached element is used => StaleElementReferenceException
--
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, 10 months
[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č updated ARQGRA-269:
------------------------------
Sprint: Sprint for Alpha4
> 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
>
>
> 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, 10 months
[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-274:
------------------------------
Sprint: Sprint for Alpha4
> The request guard does timeout for delayed requests
> ---------------------------------------------------
>
> Key: ARQGRA-274
> URL: https://issues.jboss.org/browse/ARQGRA-274
> Project: Arquillian Graphene
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha3
> Reporter: Bernard Labno
> Assignee: Lukáš Fryč
> Fix For: 2.0.0.Alpha4
>
>
> In RichFaces, there is request queue which can delay a processing of an user action which avoids overwhelming communication channel.
> This is simply the case where request guard should:
> * wait specified timeout (by default type "Ajax" timeout) for user action to start AJAX request (xhr.open)
> * then wait another timeout (by default type "Ajax" timeout) for AJAX action to complete the request (xhr.readyState == 4)
--
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, 10 months
[JBoss JIRA] (ARQGRA-72) Support parallel browser sessions API for Selenium 2
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-72?page=com.atlassian.jira.plugin.... ]
Lukáš Fryč updated ARQGRA-72:
-----------------------------
Sprint: Sprint for Alpha4
> Support parallel browser sessions API for Selenium 2
> ----------------------------------------------------
>
> Key: ARQGRA-72
> URL: https://issues.jboss.org/browse/ARQGRA-72
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: core
> Reporter: Lukáš Fryč
> Assignee: Jan Papousek
> Priority: Critical
> Fix For: 2.0.0.Alpha4
>
>
> In Selenium 1, it was possible to open multiple windows using browser.openWindow(url, windowId); and browser.selectWindow(windowId);
> In Selenium 2, this can be done by creating multiple WebDriver instances.
> There is no way to simply do this in Graphene 2. You can create 2 fields with @Drone, which will open 2 browsers with 2 WebDrivers, but all @FindBy and @Page will resolve against the first one.
--
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, 10 months