June 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1140) Warp: upgrade LittleProxy to 0.5

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1140?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1140 started by Lukáš Fryč. > Warp: upgrade LittleProxy to 0.5 > -------------------------------- > > Key: ARQ-1140 > URL: https://issues.jboss.org/browse/ARQ-1140 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Alpha3 > > > LittleProxy 0.5-SNAPSHOT contains improved filters which allows to automatically pair response with request. > There are heavy code changes involved. > https://github.com/lfryc/arquillian-extension-warp/tree/feature/upgrading... -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1140) Warp: upgrade LittleProxy to 0.5

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1140?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned ARQ-1140: ------------------------------- Assignee: Lukáš Fryč > Warp: upgrade LittleProxy to 0.5 > -------------------------------- > > Key: ARQ-1140 > URL: https://issues.jboss.org/browse/ARQ-1140 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Alpha3 > > > LittleProxy 0.5-SNAPSHOT contains improved filters which allows to automatically pair response with request. > There are heavy code changes involved. > https://github.com/lfryc/arquillian-extension-warp/tree/feature/upgrading... -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1144) Update Spock version to 0.7

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1144?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1144: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-testrunner-spock/pull/8 > Update Spock version to 0.7 > --------------------------- > > Key: ARQ-1144 > URL: https://issues.jboss.org/browse/ARQ-1144 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Alpha2 > Reporter: Bartosz Majsak > Assignee: Karel Piwko > Fix For: spock_1.0.0.next > > -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1143) Provide support for Groovy 2.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1143?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1143: ----------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/arquillian/arquillian-testrunner-spock/pull/8 (was: https://github.com/arquillian/arquillian-testrunner-spock/pull/7) New PR > Provide support for Groovy 2.0 > ------------------------------ > > Key: ARQ-1143 > URL: https://issues.jboss.org/browse/ARQ-1143 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Alpha2 > Reporter: Bartosz Majsak > Assignee: Karel Piwko > Fix For: spock_1.0.0.next > > > This might require changing dependency structure, hence Spock has two different versions 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1143) Provide support for Groovy 2.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1143?page=com.atlassian.jira.plugin.s... ] Karel Piwko reassigned ARQ-1143: -------------------------------- Assignee: Karel Piwko (was: Bartosz Majsak) > Provide support for Groovy 2.0 > ------------------------------ > > Key: ARQ-1143 > URL: https://issues.jboss.org/browse/ARQ-1143 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Alpha2 > Reporter: Bartosz Majsak > Assignee: Karel Piwko > Fix For: spock_1.0.0.next > > > This might require changing dependency structure, hence Spock has two different versions 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1144) Update Spock version to 0.7

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1144?page=com.atlassian.jira.plugin.s... ] Karel Piwko reassigned ARQ-1144: -------------------------------- Assignee: Karel Piwko (was: Bartosz Majsak) > Update Spock version to 0.7 > --------------------------- > > Key: ARQ-1144 > URL: https://issues.jboss.org/browse/ARQ-1144 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Alpha2 > Reporter: Bartosz Majsak > Assignee: Karel Piwko > Fix For: spock_1.0.0.next > > -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1409) Reformat Spock extension code to follow jboss-common formatter

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1409: -------------------------------- Summary: Reformat Spock extension code to follow jboss-common formatter Key: ARQ-1409 URL: https://issues.jboss.org/browse/ARQ-1409 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Karel Piwko Reformat source code to use common JBoss formatter style -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-264) Create possibility to "inject" elements from frames

by Aliaksei Lahachou (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-264?page=com.atlassian.jira.plugin... ] Aliaksei Lahachou commented on ARQGRA-264: ------------------------------------------ I didn't mean nested iframes. What I meant is that currently, some of my tests have calls to {{browser.switchTo().frame(...)}}. I wonder, if these tests will break now. May be I just have to try and see if it works. > Create possibility to "inject" elements from frames > --------------------------------------------------- > > Key: ARQGRA-264 > URL: https://issues.jboss.org/browse/ARQGRA-264 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha3 > Reporter: Aliaksei Lahachou > Assignee: Juraj Húska > Fix For: 2.0.0.Alpha5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > I don't like how WebDriver works with frames. I have to constantly switch between frames, I cannot simply "inject" element from a specific frame. I would love to have something like the following: > {code:java} > @FindBy(id = "menuBar") > @InFrame(id = "header") > private MenuBarFragment menuBar; > {code} > In this case Graphene should switch to frame "header" before any operation on menuBar and switch back to previous frame after (today, I have to do it manually). It seems to me that it is not too complex to do it with Arquillian/Graphene - you only need one more interceptor. > Elements not annotated with @InFrame should work on current frame just as today. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-264) Create possibility to "inject" elements from frames

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-264?page=com.atlassian.jira.plugin... ] Juraj Húska edited comment on ARQGRA-264 at 6/18/13 4:50 AM: ------------------------------------------------------------- You are right Aliaksei, it would not work for all cases. It is not supporting nested structure of iframes, only one level of iframes. The nested functionality if needed can be IMHO implemented as I described [here|https://github.com/arquillian/arquillian-graphene/pull/81#discussion...]. Is there a real life scenario where this multiple iframe levels are needed ? Otherwise, well documented feature would be sufficient IMHO. The {{@InFrame}} annotation can not be used to switch to the default iframe. IMHO the legacy tests should be rewritten to use this annotation. Another option is to implement such {{@InFrame}} which would be capable doing so. What do you think Lukas ? was (Author: jhuska): You are right Aliaksei, it would not work for all cases. It is not supporting nested structure of iframes, only one level of iframes. The nested functionality if needed can be IMHO implemented as I described [here|https://github.com/arquillian/arquillian-graphene/pull/81#discussion...]. Is there a real life scenario where this multiple iframe levels are needed ? The {{@InFrame}} annotation can not be used to switch to the default iframe. IMHO the legacy tests should be rewritten to use this annotation. Another option is to implement such {@InFrame}} which would be capable doing so. What do you think Lukas ? > Create possibility to "inject" elements from frames > --------------------------------------------------- > > Key: ARQGRA-264 > URL: https://issues.jboss.org/browse/ARQGRA-264 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha3 > Reporter: Aliaksei Lahachou > Assignee: Juraj Húska > Fix For: 2.0.0.Alpha5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > I don't like how WebDriver works with frames. I have to constantly switch between frames, I cannot simply "inject" element from a specific frame. I would love to have something like the following: > {code:java} > @FindBy(id = "menuBar") > @InFrame(id = "header") > private MenuBarFragment menuBar; > {code} > In this case Graphene should switch to frame "header" before any operation on menuBar and switch back to previous frame after (today, I have to do it manually). It seems to me that it is not too complex to do it with Arquillian/Graphene - you only need one more interceptor. > Elements not annotated with @InFrame should work on current frame just as today. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-264) Create possibility to "inject" elements from frames

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-264?page=com.atlassian.jira.plugin... ] Juraj Húska commented on ARQGRA-264: ------------------------------------ You are right Aliaksei, it would not work for all cases. It is not supporting nested structure of iframes, only one level of iframes. The nested functionality if needed can be IMHO implemented as I described [here|https://github.com/arquillian/arquillian-graphene/pull/81#discussion...]. Is there a real life scenario where this multiple iframe levels are needed ? The {{@InFrame}} annotation can not be used to switch to the default iframe. IMHO the legacy tests should be rewritten to use this annotation. Another option is to implement such {@InFrame}} which would be capable doing so. What do you think Lukas ? > Create possibility to "inject" elements from frames > --------------------------------------------------- > > Key: ARQGRA-264 > URL: https://issues.jboss.org/browse/ARQGRA-264 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha3 > Reporter: Aliaksei Lahachou > Assignee: Juraj Húska > Fix For: 2.0.0.Alpha5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > I don't like how WebDriver works with frames. I have to constantly switch between frames, I cannot simply "inject" element from a specific frame. I would love to have something like the following: > {code:java} > @FindBy(id = "menuBar") > @InFrame(id = "header") > private MenuBarFragment menuBar; > {code} > In this case Graphene should switch to frame "header" before any operation on menuBar and switch back to previous frame after (today, I have to do it manually). It seems to me that it is not too complex to do it with Arquillian/Graphene - you only need one more interceptor. > Elements not annotated with @InFrame should work on current frame just as today. -- 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

11 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2013