March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-428) Upgrade Arq Core to 1.1.3 and Drone to 1.3.0

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-428?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-428: ------------------------------ Fix Version/s: 2.0.2 > Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 > -------------------------------------------- > > Key: ARQGRA-428 > URL: https://issues.jboss.org/browse/ARQGRA-428 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Lukáš Fryč > Fix For: 2.0.2 > > -- 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-428) Upgrade Arq Core to 1.1.3 and Drone to 1.3.0

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-428: --------------------------------- Summary: Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 Key: ARQGRA-428 URL: https://issues.jboss.org/browse/ARQGRA-428 Project: Arquillian Graphene Issue Type: Component Upgrade Reporter: Lukáš Fryč -- 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-425) Allow @Location with relative URL when there is no deployment

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-425: ----------------------------------- This is duplicate of ARQGRA-374. > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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: ----------------------------------- Sounds good. 1) Wouldn't Droidium users appreciate that they won't need to configure scheme on each location? I.e. they should be able to configure scheme globally: {code} <extension name="graphene">  <property name="scheme">org.jboss.arquillian.graphene.location.Scheme.HTTPS</property> </extension> {code} 2) Shouldn't we make Scheme an extensible concept? As you said, having extensible set of schemes {HTTP,HTTPS,FILE,RESOURCE} that could e.g. Droidium extend with Scheme.DROIDIUM. There should be SPI for registration new schemes. Wdyt? > 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-427) Support for AngularJS locators and interaction synchronization

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-427: ------------------------------ Summary: Support for AngularJS locators and interaction synchronization (was: Support for AngularJS locators and interaction syncing) > Support for AngularJS locators and interaction synchronization > -------------------------------------------------------------- > > Key: ARQGRA-427 > URL: https://issues.jboss.org/browse/ARQGRA-427 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > -- 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-409) Support for Ember.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-409: ----------------------------------- Created: ARQGRA-427 > Support for Ember.js > -------------------- > > Key: ARQGRA-409 > URL: https://issues.jboss.org/browse/ARQGRA-409 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Final > Reporter: Karel Piwko > > Ember.js dynamically updates view based on various action. This makes usage of locators and guards pretty complicated. > It would be great it Graphene could provide: > * A way how to stability ids for elements in DOM generated as a part of view > * Guards that are able to guard DOM update without any request. > [~smikloso] can provide more details, additional discussions at: > http://stackoverflow.com/questions/12933422/ember-best-practices-with-sel... > http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-base... > I believe that such tools might be handy for angular.js testing as well. -- 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-427) Support for AngularJS locators and callbacks

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-427: --------------------------------- Summary: Support for AngularJS locators and callbacks Key: ARQGRA-427 URL: https://issues.jboss.org/browse/ARQGRA-427 Project: Arquillian Graphene Issue Type: Bug Reporter: Lukáš Fryč -- 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-427) Support for AngularJS locators and interaction syncing

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-427: ------------------------------ Summary: Support for AngularJS locators and interaction syncing (was: Support for AngularJS locators and callbacks) > Support for AngularJS locators and interaction syncing > ------------------------------------------------------ > > Key: ARQGRA-427 > URL: https://issues.jboss.org/browse/ARQGRA-427 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > -- 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-427) Support for AngularJS locators and interaction synchronization

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-427: ----------------------------------- Selectors: {code} @FindByNg(model = "username") WebElement usernameInput; @FindByNg(action = "search()") WebElement searchButton; {code} --- Syncing interaction: https://github.com/ALRubinger/continuous-enterprise-development/blob/mast... > Support for AngularJS locators and interaction synchronization > -------------------------------------------------------------- > > Key: ARQGRA-427 > URL: https://issues.jboss.org/browse/ARQGRA-427 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > -- 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-409) Support for Ember.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-409: ----------------------------------- +1 we can do that for both of frameworks, I just don't know Ember.js internals. Angular wraps all XHR objects and timeouts in order to be able run its model/view synchronization process. Ember doesn't have to allow similar mechanism at all. So let's go ahead and research whether there is a way. :-) ---- On side note, for AngularJS, it is very handy to have special selectors based on ng- attributes such as ng-click, ng-model, etc, such as: {code} @FindByNg(model = "username") WebElement usernameInput; @FindByNg(action = "search()") WebElement searchButton; {code} Is there anything similar for Ember? ---- I would love to have extensions for Graphene and certain frameworks in place. so you could just add artifact on classpath and you will be all setup: {code} graphene-ember graphene-angular {code} > Support for Ember.js > -------------------- > > Key: ARQGRA-409 > URL: https://issues.jboss.org/browse/ARQGRA-409 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Final > Reporter: Karel Piwko > > Ember.js dynamically updates view based on various action. This makes usage of locators and guards pretty complicated. > It would be great it Graphene could provide: > * A way how to stability ids for elements in DOM generated as a part of view > * Guards that are able to guard DOM update without any request. > [~smikloso] can provide more details, additional discussions at: > http://stackoverflow.com/questions/12933422/ember-best-practices-with-sel... > http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-base... > I believe that such tools might be handy for angular.js testing as well. -- 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