[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č reassigned ARQGRA-72:
--------------------------------
Assignee: Jan Papousek
> 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, 9 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:
-----------------------------
Fix Version/s: 2.0.0.Alpha4
(was: 2.0.0.Beta1)
> 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č
> 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, 9 months
[JBoss JIRA] (ARQGRA-284) Rename guardXhr to guardAjax
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQGRA-284:
---------------------------------
Summary: Rename guardXhr to guardAjax
Key: ARQGRA-284
URL: https://issues.jboss.org/browse/ARQGRA-284
Project: Arquillian Graphene
Issue Type: Task
Reporter: Lukáš Fryč
Fix For: 2.0.0.Alpha4
The guardXhr should be renamed because the XHR term is not part of general web application developer/tester knowledge.
Deprecate guardXhr.
--
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
[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:
------------------------------
Fix Version/s: 2.0.0.Beta1
> 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
> Fix For: 2.0.0.Beta1
>
>
> 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, 9 months