[JBoss JIRA] (ARQGRA-264) Create possibility to "inject" elements from frames
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-264?page=com.atlassian.jira.plugin... ]
Juraj Húska updated ARQGRA-264:
-------------------------------
Original Estimate: 6 hours
Remaining Estimate: 6 hours
> Create possibility to "inject" elements from frames
> ---------------------------------------------------
>
> Key: ARQGRA-264
> URL: https://issues.jboss.org/browse/ARQGRA-264
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Alpha3
> Reporter: Aliaksei Lahachou
> Assignee: Juraj Húska
> Fix For: 2.0.0.Alpha4
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> I don't like how WebDriver works with frames. I have to constantly switch between frames, I cannot simply "inject" element from a specific frame. I would love to have something like the following:
> {code:java}
> @FindBy(id = "menuBar")
> @InFrame(id = "header")
> private MenuBarFragment menuBar;
> {code}
> In this case Graphene should switch to frame "header" before any operation on menuBar and switch back to previous frame after (today, I have to do it manually). It seems to me that it is not too complex to do it with Arquillian/Graphene - you only need one more interceptor.
> Elements not annotated with @InFrame should work on current frame just as today.
--
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-72) Support parallel browser sessions API for Selenium 2
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-72?page=com.atlassian.jira.plugin.... ]
Jan Papousek updated ARQGRA-72:
-------------------------------
Original Estimate: 2 days
Remaining Estimate: 2 days
> 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
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> 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
13 years
[JBoss JIRA] (ARQGRA-280) refactor handling of staleness
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ]
Jan Papousek updated ARQGRA-280:
--------------------------------
Original Estimate: 4 hours (was: 6 hours)
Remaining Estimate: 4 hours (was: 6 hours)
> 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
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> 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
13 years