December 2012 - arquillian-issues

[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 commented on ARQGRA-199: ------------------------------------ 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

[JBoss JIRA] (ARQGRA-213) print contextpath and option to sleep after starting the @Deployment

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-213: ----------------------------------- Exactly, you can dump information about last deployment to filesystem. +1 to contextPath and browser information written to INFO log > print contextpath and option to sleep after starting the @Deployment > -------------------------------------------------------------------- > > Key: ARQGRA-213 > URL: https://issues.jboss.org/browse/ARQGRA-213 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Mark Struberg > Assignee: Lukáš Fryč > Fix For: 2.0.0.Alpha3 > > > Most graphene unit test have a @Deployment section and something similar to the following: > {code} > @ArquillianResource > private URL contextPath; > {code} > When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information. > Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server. -- 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-213) print contextpath and option to sleep after starting the @Deployment

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ] Karel Piwko commented on ARQGRA-213: ------------------------------------ Speaking about contextPath, there is a plan to echo what browser is actually used. We can maybe define a richer set of object to be echoed in Arquillian Drone. > print contextpath and option to sleep after starting the @Deployment > -------------------------------------------------------------------- > > Key: ARQGRA-213 > URL: https://issues.jboss.org/browse/ARQGRA-213 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Mark Struberg > Assignee: Lukáš Fryč > Fix For: 2.0.0.Alpha3 > > > Most graphene unit test have a @Deployment section and something similar to the following: > {code} > @ArquillianResource > private URL contextPath; > {code} > When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information. > Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server. -- 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-213) print contextpath and option to sleep after starting the @Deployment

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ] Karel Piwko commented on ARQGRA-213: ------------------------------------ [~lfryc] how you want to figure out what is the last deployment? Should you mark it somehow on the filesystem? > print contextpath and option to sleep after starting the @Deployment > -------------------------------------------------------------------- > > Key: ARQGRA-213 > URL: https://issues.jboss.org/browse/ARQGRA-213 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Mark Struberg > Assignee: Lukáš Fryč > Fix For: 2.0.0.Alpha3 > > > Most graphene unit test have a @Deployment section and something similar to the following: > {code} > @ArquillianResource > private URL contextPath; > {code} > When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information. > Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server. -- 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-213) print contextpath and option to sleep after starting the @Deployment

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-213: ----------------------------------- +1 (y) > print contextpath and option to sleep after starting the @Deployment > -------------------------------------------------------------------- > > Key: ARQGRA-213 > URL: https://issues.jboss.org/browse/ARQGRA-213 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Mark Struberg > Assignee: Lukáš Fryč > Fix For: 2.0.0.Alpha3 > > > Most graphene unit test have a @Deployment section and something similar to the following: > {code} > @ArquillianResource > private URL contextPath; > {code} > When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information. > Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server. -- 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-213) print contextpath and option to sleep after starting the @Deployment

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin... ] Mark Struberg commented on ARQGRA-213: -------------------------------------- well, but logging out the contextPath would be nice nonetheless, wdyt? > print contextpath and option to sleep after starting the @Deployment > -------------------------------------------------------------------- > > Key: ARQGRA-213 > URL: https://issues.jboss.org/browse/ARQGRA-213 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Mark Struberg > Assignee: Lukáš Fryč > Fix For: 2.0.0.Alpha3 > > > Most graphene unit test have a @Deployment section and something similar to the following: > {code} > @ArquillianResource > private URL contextPath; > {code} > When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information. > Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server. -- 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-238) Catch client-side errors

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-238?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-238: ------------------------------ Description: Graphene should allow to inspect errors on client-side. E.g. console.log output. > Catch client-side errors > ------------------------ > > Key: ARQGRA-238 > URL: https://issues.jboss.org/browse/ARQGRA-238 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha2 > Reporter: Lukáš Fryč > > Graphene should allow to inspect errors on client-side. > E.g. console.log output. -- 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-238) Catch client-side errors

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-238: --------------------------------- Summary: Catch client-side errors Key: ARQGRA-238 URL: https://issues.jboss.org/browse/ARQGRA-238 Project: Arquillian Graphene Issue Type: Feature Request Affects Versions: 2.0.0.Alpha2 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, 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: ------------------------------ Description: When cache is enabled then one cannot change e.g. JavaScript resource and see changes immediately. > 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č > > 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

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1236?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1236: ---------------------------- Original Estimate: 1 hour, 30 minutes (was: 3 hours) Remaining Estimate: 1 hour, 30 minutes (was: 3 hours) > Warp: filter favicon requests by default > ---------------------------------------- > > 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č > Priority: Minor > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2012