April 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-293) introduce JavaScript interface to fire JS events

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-293?page=com.atlassian.jira.plugin... ] Jan Papousek updated ARQGRA-293: -------------------------------- Priority: Minor (was: Major) > introduce JavaScript interface to fire JS events > ------------------------------------------------ > > Key: ARQGRA-293 > URL: https://issues.jboss.org/browse/ARQGRA-293 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Assignee: Jan Papousek > Priority: Minor > Fix For: 2.0.0.Alpha5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > It would be nice to be able to fire events on elements manually (sometimes it's necessary). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-293) introduce JavaScript interface to fire JS events

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-293?page=com.atlassian.jira.plugin... ] Jan Papousek commented on ARQGRA-293: ------------------------------------- See https://github.com/richfaces/qa/blob/master/metamer/ftest/src/test/java/o.... Yes, I admit these tests can be rewritten to emulate user's interaction, but components contain a lot of these "on" attributes. > introduce JavaScript interface to fire JS events > ------------------------------------------------ > > Key: ARQGRA-293 > URL: https://issues.jboss.org/browse/ARQGRA-293 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > It would be nice to be able to fire events on elements manually (sometimes it's necessary). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-280) Refactor handling of staleness to improve performance

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ] Jan Papousek updated ARQGRA-280: -------------------------------- Fix Version/s: 2.0.0.Beta1 (was: 2.0.0.Alpha5) > Refactor handling of staleness to improve performance > ----------------------------------------------------- > > 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.Beta1 > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-280) Refactor handling of staleness to improve performance

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ] Work on ARQGRA-280 stopped by Jan Papousek. > Refactor handling of staleness to improve performance > ----------------------------------------------------- > > 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.Beta1 > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-280) Refactor handling of staleness to improve performance

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ] Jan Papousek commented on ARQGRA-280: ------------------------------------- To solve the performance issue, I suggest to refactor GrapheneProxy.FutureTarget interface: {code} public interface FutureTarget { Object getTarget(); } {code} to {code} public interface FutureTarget { Object getTarget(boolean cacheAllowed); } {code} > Refactor handling of staleness to improve performance > ----------------------------------------------------- > > 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.Alpha5 > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-296) Provide a way for checking whether an element is present

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-296?page=com.atlassian.jira.plugin... ] Jan Papousek commented on ARQGRA-296: ------------------------------------- The second possibility is to introduce the "isElementPresent(WebElement element)" method. > Provide a way for checking whether an element is present > -------------------------------------------------------- > > Key: ARQGRA-296 > URL: https://issues.jboss.org/browse/ARQGRA-296 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Assignee: Jan Papousek > Priority: Minor > Fix For: 2.0.0.Alpha5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-296) Provide a way for checking whether an element is present

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-296?page=com.atlassian.jira.plugin... ] Jan Papousek commented on ARQGRA-296: ------------------------------------- The current Graphene utility class contains the following deprecated method: {code} public static ElementConditionFactory element(WebElement element) { return new WebElementConditionFactory(element); } {code} I'd like to replace this method by one which returns object for advanced interaction with the given web element: {code} public static EnhancedElement element(WebElement element) { ... } {code} where: {code} public interface EnhancedElement { boolean isPresent(); void fire(Event event); } {code} > Provide a way for checking whether an element is present > -------------------------------------------------------- > > Key: ARQGRA-296 > URL: https://issues.jboss.org/browse/ARQGRA-296 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Assignee: Jan Papousek > Priority: Minor > Fix For: 2.0.0.Alpha5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-267) Upgrade HTMLUnit to newer version (from 2.11)

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-267?page=com.atlassian.jira.plugin... ] Jan Papousek resolved ARQGRA-267. --------------------------------- Resolution: Out of Date Lukas: Yes, you're right the latest HTMLUnit driver contains HTMLUnit in version 2.12. > Upgrade HTMLUnit to newer version (from 2.11) > --------------------------------------------- > > Key: ARQGRA-267 > URL: https://issues.jboss.org/browse/ARQGRA-267 > Project: Arquillian Graphene > Issue Type: Task > Affects Versions: 2.0.0.Alpha3 > Reporter: Jan Papousek > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1382) Prepare Glassfish 1.0.0.CR4

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1382?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1382. ------------------------------ Resolution: Done pushed to nexus > Prepare Glassfish 1.0.0.CR4 > --------------------------- > > Key: ARQ-1382 > URL: https://issues.jboss.org/browse/ARQ-1382 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: glassfish_1.0.0.CR4 > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1293) Add Support for GlassFish 4.x series

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1293?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1293. ------------------------------ > Add Support for GlassFish 4.x series > ------------------------------------ > > Key: ARQ-1293 > URL: https://issues.jboss.org/browse/ARQ-1293 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR3 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: glassfish_1.0.0.CR4 > > -- 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

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2013