December 2012 - arquillian-issues

[JBoss JIRA] (ARQ-1244) Warp: shortcuts for defining WebDriver activities

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1244?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1244: ---------------------------- Component/s: Extension - Warp > Warp: shortcuts for defining WebDriver activities > ------------------------------------------------- > > Key: ARQ-1244 > URL: https://issues.jboss.org/browse/ARQ-1244 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > > {code:java} > @FindBy > WebElement loginButton; > Warp > .initiate(drive(loginButton).click()) > .inspect(new Inspect() { > ... > }); > {code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-237) Allow setting Chrome browser profile to disable cache

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-237?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-237: ----------------------------------- As workaround, one may use {{F12 > Settings (tool icon) > Disable cache}} > Allow setting Chrome browser profile to disable cache > ----------------------------------------------------- > > Key: ARQGRA-237 > URL: https://issues.jboss.org/browse/ARQGRA-237 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Attachments: disable-cache.png > > > When cache is enabled then one cannot change e.g. JavaScript resource and see changes immediately. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-237) Allow setting Chrome browser profile to disable cache

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-237?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-237: ------------------------------ Attachment: disable-cache.png > Allow setting Chrome browser profile to disable cache > ----------------------------------------------------- > > Key: ARQGRA-237 > URL: https://issues.jboss.org/browse/ARQGRA-237 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Attachments: disable-cache.png > > > When cache is enabled then one cannot change e.g. JavaScript resource and see changes immediately. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1236) Warp: filter favicon requests by default and use only first request for single executor

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1236?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1236: ---------------------------- Summary: Warp: filter favicon requests by default and use only first request for single executor (was: Warp: filter favicon requests by default) Assignee: Lukáš Fryč Priority: Critical (was: Minor) > Warp: filter favicon requests by default and use only first request for single executor > --------------------------------------------------------------------------------------- > > Key: ARQ-1236 > URL: https://issues.jboss.org/browse/ARQ-1236 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > Real browsers usually issue request for {{favicon.ico}} right after initial request for given domain. > This makes necessary to use filtering for each request with real browser. > Let's introduce default filter feature which will filter {{favicon.ico}} out. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1236) Warp: filter favicon requests by default and use only first request for single executor

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1236?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1236 started by Lukáš Fryč. > Warp: filter favicon requests by default and use only first request for single executor > --------------------------------------------------------------------------------------- > > Key: ARQ-1236 > URL: https://issues.jboss.org/browse/ARQ-1236 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > Real browsers usually issue request for {{favicon.ico}} right after initial request for given domain. > This makes necessary to use filtering for each request with real browser. > Let's introduce default filter feature which will filter {{favicon.ico}} out. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1233) Warp: rename API according to results of survey

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1233?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1233. ----------------------------- Resolution: Done > Warp: rename API according to results of survey > ----------------------------------------------- > > Key: ARQ-1233 > URL: https://issues.jboss.org/browse/ARQ-1233 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: warp_1.0.0.Alpha2 > > Attachments: warp-api-method-naming-survey-responses.pdf > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > There were discussion about Warp API method naming: > As a result, interesting options were selected and survey for choosing most natural and popular ones was opened: > https://docs.google.com/spreadsheet/viewform?formkey=dFlZeGI3ZklOUVlDX2M2... > As a response, we got 8 answers with following results: > {code} > most favorite: > option #1: Warp .initiate(Activity) .observe(What) .inspect(Inspection); > followed by: > option #5: Warp .execute(ClientAction) .filter(Filter) .inspect(ServerInspection); > {code} > The complete overview of responses is attached in PDF. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1233) Warp: rename API according to results of survey

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1233?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1233: --------------------------------- Changes pushed to {{master}}: https://github.com/arquillian/arquillian-extension-warp/commit/4bf887fc3a... > Warp: rename API according to results of survey > ----------------------------------------------- > > Key: ARQ-1233 > URL: https://issues.jboss.org/browse/ARQ-1233 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: warp_1.0.0.Alpha2 > > Attachments: warp-api-method-naming-survey-responses.pdf > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > There were discussion about Warp API method naming: > As a result, interesting options were selected and survey for choosing most natural and popular ones was opened: > https://docs.google.com/spreadsheet/viewform?formkey=dFlZeGI3ZklOUVlDX2M2... > As a response, we got 8 answers with following results: > {code} > most favorite: > option #1: Warp .initiate(Activity) .observe(What) .inspect(Inspection); > followed by: > option #5: Warp .execute(ClientAction) .filter(Filter) .inspect(ServerInspection); > {code} > The complete overview of responses is attached in PDF. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1233) Warp: rename API according to results of survey

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1233?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1233: --------------------------------- There is migration script which helps to migrate to new API: https://gist.github.com/4275537 > Warp: rename API according to results of survey > ----------------------------------------------- > > Key: ARQ-1233 > URL: https://issues.jboss.org/browse/ARQ-1233 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: warp_1.0.0.Alpha2 > > Attachments: warp-api-method-naming-survey-responses.pdf > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > There were discussion about Warp API method naming: > As a result, interesting options were selected and survey for choosing most natural and popular ones was opened: > https://docs.google.com/spreadsheet/viewform?formkey=dFlZeGI3ZklOUVlDX2M2... > As a response, we got 8 answers with following results: > {code} > most favorite: > option #1: Warp .initiate(Activity) .observe(What) .inspect(Inspection); > followed by: > option #5: Warp .execute(ClientAction) .filter(Filter) .inspect(ServerInspection); > {code} > The complete overview of responses is attached in PDF. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1233) Warp: rename API according to results of survey

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1233?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1233: ---------------------------- Original Estimate: 3 hours (was: 1 hour) Remaining Estimate: 3 hours (was: 1 hour) > Warp: rename API according to results of survey > ----------------------------------------------- > > Key: ARQ-1233 > URL: https://issues.jboss.org/browse/ARQ-1233 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: warp_1.0.0.Alpha2 > > Attachments: warp-api-method-naming-survey-responses.pdf > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > There were discussion about Warp API method naming: > As a result, interesting options were selected and survey for choosing most natural and popular ones was opened: > https://docs.google.com/spreadsheet/viewform?formkey=dFlZeGI3ZklOUVlDX2M2... > As a response, we got 8 answers with following results: > {code} > most favorite: > option #1: Warp .initiate(Activity) .observe(What) .inspect(Inspection); > followed by: > option #5: Warp .execute(ClientAction) .filter(Filter) .inspect(ServerInspection); > {code} > The complete overview of responses is attached in PDF. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-199) Provide a way to create Page Fragments dynamically

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-199?page=com.atlassian.jira.plugin... ] Juraj Húska edited comment on ARQGRA-199 at 12/12/12 10:33 AM: --------------------------------------------------------------- As we discussed offline, we decided to support for now: {code} @FindBy TabPanel panel; public void test() { Tab tab1 = panel.switchTo(1); UserDetials usrDet = tab1.getContent(UserDetails.class); } {code} There was an proposition for the future: {code} @FindBy TabPanel panel; @Content(item = 1) UserDetails details; public void test() { panel.switchTo(details); } {code} Which unfortunately does not solve the problem with the state when there are more {{@FindBy}} fields on the page, and it is not clear with which {{panel}} or {{@FindBy}} the {{@Content}} is associated. Then I had this suggestion which start to be however a little ugly: {code} @FindBy @DynamicPanel(1) TabPanel panel1; @FindBy @DynamicPanel(2) TabPanel panel2 @Content(item = 1) @DynamicPanel(1) UserDetails details; @Content @DynamicPanel(2) WebElement text; public void test() { panel.switchTo(details); } {code} was (Author: jhuska): As we discussed offline, we decided to support for now: {code} @FindBy TabPanel panel; public void test() { Tab tab1 = panel.switchTo(1); UserDetials usrDet = tab1.getContent(UserDetails.class); } {code} There was an proposition for the future: {code} @FindBy TabPanel panel; @Content(item = 1) UserDetails details; public void test() { panel.switchTo(details); } {code} Which unfortunately does not solve the problem with the state when there are more {{@FindBy}} fields on the page, and it is not clear with which {{panel}} or {{@FindBy}} the content is associated. Then I had this suggestion which start to be however a little bit messy: {code} @FindBy @DynamicPanel(1) TabPanel panel1; @FindBy @DynamicPanel(2) TabPanel panel2 @Content(item = 1) @DynamicPanel(1) UserDetails details; @Content @DynamicPanel(2) WebElement text; public void test() { panel.switchTo(details); } {code} > Provide a way to create Page Fragments dynamically > -------------------------------------------------- > > Key: ARQGRA-199 > URL: https://issues.jboss.org/browse/ARQGRA-199 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api, unit-test > Affects Versions: 2.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.0.0.Alpha3 > > > The only way now to declare and initialize Page Fragment is to annotate the implementation class of that Page Fragment by {{@FindBy}} (or use static factory method). > It will nice and vital addition to have way how to declare and create Page Fragments dynamically. > It will be for example useful in the use case described in the [comment|https://issues.jboss.org/browse/ARQGRA-199?focusedCommentId=12731...] below. -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2012