March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-408: ----------------------------------- Yeah, right, one of other approaches could be using marking interface for an enumeration of classes: http://deltaspike.apache.org/jsf.html#view > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-na... -- 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin... ] Stefan Miklosovic updated ARQGRA-408: ------------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/103 (was: https://github.com/arquillian/arquillian-graphene/pull/102) > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-na... -- 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin... ] Stefan Miklosovic updated ARQGRA-408: ------------------------------------- Comment: was deleted (was: [~lfryc] when you meant it like this {code} @Location(scheme = UriScheme.HTTP) {code} where UriScheme is {code} public class UriScheme { public static final UriScheme HTTP = new UriScheme("http"); private final String scheme; private UriScheme(String scheme) { this.scheme = scheme; } } {code} you can not have that class as a parameter for an annotation just because of Java. I try to approach that with enumerations again.) > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-na... -- 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin... ] Stefan Miklosovic updated ARQGRA-408: ------------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/102 (was: https://github.com/arquillian/arquillian-graphene/pull/101) > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi... > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-na... -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1708) Remove legacy configuration

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1708?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1708. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/ddf2ea596... > Remove legacy configuration > --------------------------- > > Key: ARQ-1708 > URL: https://issues.jboss.org/browse/ARQ-1708 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Remove system property based configuration provided by Drone, as this is now available in Arquillian Core. > Remove configuration fields mapped as deprecated, that are now mapped to capabilities. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1708) Remove legacy configuration

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1708?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1708: ----------------------------- Affects Version/s: (was: drone_1.3.0.Final) > Remove legacy configuration > --------------------------- > > Key: ARQ-1708 > URL: https://issues.jboss.org/browse/ARQ-1708 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Remove system property based configuration provided by Drone, as this is now available in Arquillian Core. > Remove configuration fields mapped as deprecated, that are now mapped to capabilities. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1707) Provide better timeout exception message

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1707?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1707. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/e070731df... > Provide better timeout exception message > ---------------------------------------- > > Key: ARQ-1707 > URL: https://issues.jboss.org/browse/ARQ-1707 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > In case that Callable instantiation times out, Drone should emit a better message. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1688) Drop Selenium 1.0 support

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1688?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1688. ------------------------------ Assignee: Karel Piwko Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/56701bdce... > Drop Selenium 1.0 support > ------------------------- > > Key: ARQ-1688 > URL: https://issues.jboss.org/browse/ARQ-1688 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Drop Selenium 1.0 altogether from Drone. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1700) Provide Deployment scope support for Drone

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1700?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1700. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/48d3c38d1... > Provide Deployment scope support for Drone > ------------------------------------------ > > Key: ARQ-1700 > URL: https://issues.jboss.org/browse/ARQ-1700 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Tadeas Kriz > Fix For: drone_2.0.0.Alpha1 > > > For Droidium and iOSium containers, there should be a support for @Deployment based scopes. > This is a foundation for Drone 2.0.0. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1708) Remove legacy configuration

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1708: -------------------------------- Summary: Remove legacy configuration Key: ARQ-1708 URL: https://issues.jboss.org/browse/ARQ-1708 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.3.0.Final Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_2.0.0.Alpha1 Remove system property based configuration provided by Drone, as this is now available in Arquillian Core. Remove configuration fields mapped as deprecated, that are now mapped to capabilities. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2014