March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-437) Introduce annotation to control lifecycle of selenium session

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-437?page=com.atlassian.jira.plugin.sy... ] Karel Piwko updated ARQ-437: ---------------------------- Fix Version/s: drone_2.0.0.Alpha3 (was: drone_2.0.0.Alpha1) > Introduce annotation to control lifecycle of selenium session > ------------------------------------------------------------- > > Key: ARQ-437 > URL: https://issues.jboss.org/browse/ARQ-437 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Lukáš Fryč > Fix For: drone_2.0.0.Alpha3 > > > Following options are being considered: > BEFORE_SUITE > BEFORE_CLASS > BEFORE_METHOD -- 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)

Karel Piwko created ARQ-1707: -------------------------------- Summary: 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-1706) Add multilanguage to AsciiDocExporter

by Alex Soto (JIRA)

Alex Soto created ARQ-1706: ------------------------------ Summary: Add multilanguage to AsciiDocExporter Key: ARQ-1706 URL: https://issues.jboss.org/browse/ARQ-1706 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto Priority: Minor Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it. -- 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-1705) Update Core to 1.1.3.Final

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1705?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1705. ---------------------------- > Update Core to 1.1.3.Final > -------------------------- > > Key: ARQ-1705 > URL: https://issues.jboss.org/browse/ARQ-1705 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update to lastest Arquillian Core. -- 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-1659) Update Selenium to 2.40.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1659?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1659. ---------------------------- > Update Selenium to 2.40.0 > ------------------------- > > Key: ARQ-1659 > URL: https://issues.jboss.org/browse/ARQ-1659 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update Selenium to support latest browsers. > Note, some of the deprecated items might get dropped (AndroidDriver, iOSDriver). We need a strategy how to handle that. -- 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 commented on ARQGRA-408: ------------------------------------------ [~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] (ARQ-1673) Implement asciidoctor exporter for reporter

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1673?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1673. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done https://github.com/arquillian/arquillian-recorder/commit/988e0bfbd0bec075... > Implement asciidoctor exporter for reporter > ------------------------------------------- > > Key: ARQ-1673 > URL: https://issues.jboss.org/browse/ARQ-1673 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Alex Soto > Fix For: recorder_1.0.0.Alpha2 > > -- 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-1673) Implement asciidoctor exporter for reporter

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1673?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1673: ----------------------------------- Assignee: Alex Soto > Implement asciidoctor exporter for reporter > ------------------------------------------- > > Key: ARQ-1673 > URL: https://issues.jboss.org/browse/ARQ-1673 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Alex Soto > -- 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 Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-408: ----------------------------------- 2) I usually use just a final class with constant immutable members: https://github.com/arquillian/arquillian-graphene/blob/1.0.0.Final/graphe... > 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 commented on ARQGRA-408: ------------------------------------------ 1) +1 2) I do not know how to do it. When it comes to it, you use that UriScheme enumeration in Location annotation. When you want to use anothe scheme, I just do not see a way how to add there your custom one without changing UriScheme enumeration. Maybe UriScheme would implement some base interface so you would implement your own as well or your custom scheme would extends base UriScheme. I am not sure. Wdty? :) > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2014