September 2014 - arquillian-issues

[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č resolved ARQGRA-425. ------------------------------- Assignee: Lukáš Fryč (was: Stefan Miklosovic) Fix Version/s: (was: 2.1-Tracking) Resolution: Duplicate Issue > 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: Lukáš Fryč > > 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 was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

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 > > 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 was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-374) Allow to setup custom Location URL via arquillian.xml configuration with CustomizableURLResourceProvider

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-374?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-374: ------------------------------ Summary: Allow to setup custom Location URL via arquillian.xml configuration with CustomizableURLResourceProvider (was: Allow to setup custom Location URL via arquillian.xml configuration with CustmizableURLResourceProvider) > Allow to setup custom Location URL via arquillian.xml configuration with CustomizableURLResourceProvider > -------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-374 > URL: https://issues.jboss.org/browse/ARQGRA-374 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > {code:xml} > <arquillian> > <extension name="graphene"> > <property name="url">http://localhost:8080/app/</property> > </extension> > </arquillian> > {code} > The provider will obtain URL from {{URLResourceProvider}} and use it if no other URL is provided. > Configuring this provider should also block deploying application, since its unnecessary. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-374) Allow to setup custom Location URL via arquillian.xml configuration with CustmizableURLResourceProvider

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-374?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-374: ----------------------------------- Hey [~smikloso] have you made any progress here? > Allow to setup custom Location URL via arquillian.xml configuration with CustmizableURLResourceProvider > ------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-374 > URL: https://issues.jboss.org/browse/ARQGRA-374 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > {code:xml} > <arquillian> > <extension name="graphene"> > <property name="url">http://localhost:8080/app/</property> > </extension> > </arquillian> > {code} > The provider will obtain URL from {{URLResourceProvider}} and use it if no other URL is provided. > Configuring this provider should also block deploying application, since its unnecessary. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-374) Allow to setup custom Location URL via arquillian.xml configuration with CustmizableURLResourceProvider

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-374?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-374: ------------------------------ Summary: Allow to setup custom Location URL via arquillian.xml configuration with CustmizableURLResourceProvider (was: Allow to setup custom URL via arquillian.xml configuration with CustmizableURLResourceProvider) > Allow to setup custom Location URL via arquillian.xml configuration with CustmizableURLResourceProvider > ------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-374 > URL: https://issues.jboss.org/browse/ARQGRA-374 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > {code:xml} > <arquillian> > <extension name="graphene"> > <property name="url">http://localhost:8080/app/</property> > </extension> > </arquillian> > {code} > The provider will obtain URL from {{URLResourceProvider}} and use it if no other URL is provided. > Configuring this provider should also block deploying application, since its unnecessary. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-409) Support for Ember.js

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin... ] Stefan Miklosovic commented on ARQGRA-409: ------------------------------------------ [~lfryc] +1 or resolving this > 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 was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-409) Support for Ember.js

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin... ] Stefan Miklosovic edited comment on ARQGRA-409 at 9/22/14 8:14 AM: ------------------------------------------------------------------- [~lfryc] +1 on resolving this was (Author: smikloso): [~lfryc] +1 or resolving this > 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 was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-426) Provide API for dynamic @Location

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-426?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-426: ------------------------------ Fix Version/s: 2.1-Tracking > Provide API for dynamic @Location > --------------------------------- > > Key: ARQGRA-426 > URL: https://issues.jboss.org/browse/ARQGRA-426 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Fix For: 2.1-Tracking > > > There are use cases when the same page object has different URLs. One of such use cases is described in [this|https://community.jboss.org/message/861996#861996] post. > To enhance re-usability, we should IMHO provide an API for dynamic @Location resolutions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-459) Allow to load Page Extensions from within WAR deployment

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-459?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-459: ------------------------------ Fix Version/s: 2.1-Tracking > Allow to load Page Extensions from within WAR deployment > -------------------------------------------------------- > > Key: ARQGRA-459 > URL: https://issues.jboss.org/browse/ARQGRA-459 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Final > Reporter: Lukáš Fryč > Fix For: 2.1-Tracking > > > Allows for debuggability -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-380) Debugging in Eclipse throw InvocationException when inspecting fields enriched by Graphene

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-380?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-380: ------------------------------ Fix Version/s: 2.1-Tracking > Debugging in Eclipse throw InvocationException when inspecting fields enriched by Graphene > ------------------------------------------------------------------------------------------ > > Key: ARQGRA-380 > URL: https://issues.jboss.org/browse/ARQGRA-380 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.Beta2 > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.1-Tracking > > > During debugging in Eclipse, when inspecting the values of the fields which are enriched by Graphene, an {{InvocationException}} is thrown. > We should investigate why it is so, and improve it if it is feasible. It can enhance the usability. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2014