[JBoss JIRA] (ARQGRA-226) graphene-webdriver-ftest cleanup for reference usage
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-226?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-226:
------------------------------
Assignee: Lukáš Fryč
> graphene-webdriver-ftest cleanup for reference usage
> ----------------------------------------------------
>
> Key: ARQGRA-226
> URL: https://issues.jboss.org/browse/ARQGRA-226
> Project: Arquillian Graphene
> Issue Type: Enhancement
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Trivial
> Fix For: 2.0.0.Beta1
>
>
> {{graphene-webdriver-ftest}} should be used as reference usage for Graphene, thus we need to:
> * remove dependency on {{arquillian-test-impl-base}}
> * remove dependencies which are commented out
> * add comments
> ** on depchain - it brings all the dependencies
> ** on arquillian-junit-standalone - explain what dependencies might be used instead {{arquillian-{testng,junit}-{standalone,container}}}
--
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-264) Create possibility to "inject" elements from frames
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-264?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-264:
------------------------------
Fix Version/s: 2.0.0.Alpha4
(was: 2.0.0.Beta1)
> 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
> Fix For: 2.0.0.Alpha4
>
>
> 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-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:
------------------------------
Assignee: Jan Papousek
Fix Version/s: 2.0.0.Alpha4
(was: 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
> 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
13 years
[JBoss JIRA] (ARQGRA-264) Create possibility to "inject" elements from frames
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-264?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-264:
------------------------------
Assignee: Juraj Húska
> 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
>
>
> 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