January 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1261) Warp: setup container-compatibility integration builds

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1261: ------------------------------- Summary: Warp: setup container-compatibility integration builds Key: ARQ-1261 URL: https://issues.jboss.org/browse/ARQ-1261 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Warp Reporter: Lukáš Fryč Fix For: warp_1.0.0.tracking We should test compatibility with following containers; * TomEE * Glassfish * WebSphere? * WebLogic? * CloudBees? -- 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] (ARQ-1260) print contextpath and option to sleep after starting the @Deployment

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1260?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1260: ----------------------------- Affects Version/s: 1.0.3.Final Component/s: Base Implementation > print contextpath and option to sleep after starting the @Deployment > -------------------------------------------------------------------- > > Key: ARQ-1260 > URL: https://issues.jboss.org/browse/ARQ-1260 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Reporter: Mark Struberg > Assignee: Lukáš Fryč > > 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

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1260?page=com.atlassian.jira.plugin.s... ] Karel Piwko moved ARQGRA-213 to ARQ-1260: ----------------------------------------- Project: Arquillian (was: Arquillian Graphene) Key: ARQ-1260 (was: ARQGRA-213) Security: Public Fix Version/s: (was: 2.0-Tracking) > print contextpath and option to sleep after starting the @Deployment > -------------------------------------------------------------------- > > Key: ARQ-1260 > URL: https://issues.jboss.org/browse/ARQ-1260 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Struberg > Assignee: Lukáš Fryč > > 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-233) Graphene does not guard against StaleElementException

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-233?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-233: ----------------------------------- There is fix which protects injected ({{@FindBy}}) elements against {{StaleElementReferenceException}}: https://github.com/arquillian/arquillian-graphene/commit/61826d6bae70ed3c... However we should protect also elements found manually: {{SearchContext#findElement/-s()}} This can be done by interceptor's propagation to inferred SearchContexts (driver -> element - > element). This request is tracked here: ARQGRA-252 > Graphene does not guard against StaleElementException > ----------------------------------------------------- > > Key: ARQGRA-233 > URL: https://issues.jboss.org/browse/ARQGRA-233 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > There are situations when changes in DOM causes our WebElements to be staled. > We need to write extensive functional test suite which will count with different type of DOM changes: > * replacements > * deletions > * addiotions > * updates -- 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-252) Protect manually found WebElements from StaleElementReferenceException

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-252?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-252: ------------------------------ Description: In scope of ARQGRA-233, we have protected injected elements ({{@FindBy}}). However we should protect also elements found manually: {{SearchContext#findElement/-s()}} This can be done by interceptor's propagation to inferred SearchContexts (driver -> element - > element). This issue depends on interceptor propagation in ARQGRA-79. was: In scope of ARQGRA-233, we have protected injected elements ({{@FindBy}}). However we should protect also elements found manually: {{SearchContext#findElement/-s()}} This can be done by interceptor's propagation to inferred SearchContexts (driver -> element - > element). > Protect manually found WebElements from StaleElementReferenceException > ---------------------------------------------------------------------- > > Key: ARQGRA-252 > URL: https://issues.jboss.org/browse/ARQGRA-252 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Lukáš Fryč > Fix For: 2.0-Tracking > > > In scope of ARQGRA-233, we have protected injected elements ({{@FindBy}}). > However we should protect also elements found manually: {{SearchContext#findElement/-s()}} > This can be done by interceptor's propagation to inferred SearchContexts (driver -> element - > element). > This issue depends on interceptor propagation in ARQGRA-79. -- 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-233) Graphene does not guard against StaleElementException

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-233?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-233. ------------------------------- Resolution: Done > Graphene does not guard against StaleElementException > ----------------------------------------------------- > > Key: ARQGRA-233 > URL: https://issues.jboss.org/browse/ARQGRA-233 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > There are situations when changes in DOM causes our WebElements to be staled. > We need to write extensive functional test suite which will count with different type of DOM changes: > * replacements > * deletions > * addiotions > * updates -- 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-252) Protect manually found WebElements from StaleElementReferenceException

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-252: --------------------------------- Summary: Protect manually found WebElements from StaleElementReferenceException Key: ARQGRA-252 URL: https://issues.jboss.org/browse/ARQGRA-252 Project: Arquillian Graphene Issue Type: Enhancement Reporter: Lukáš Fryč Fix For: 2.0-Tracking In scope of ARQGRA-233, we have protected injected elements ({{@FindBy}}). However we should protect also elements found manually: {{SearchContext#findElement/-s()}} This can be done by interceptor's propagation to inferred SearchContexts (driver -> element - > element). -- 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-233) Graphene does not guard against StaleElementException

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-233?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-233: --------------------------------- Assignee: Lukáš Fryč (was: Jan Papousek) > Graphene does not guard against StaleElementException > ----------------------------------------------------- > > Key: ARQGRA-233 > URL: https://issues.jboss.org/browse/ARQGRA-233 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > There are situations when changes in DOM causes our WebElements to be staled. > We need to write extensive functional test suite which will count with different type of DOM changes: > * replacements > * deletions > * addiotions > * updates -- 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-79) Migrate command interceptors to Selenium 2

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-79?page=com.atlassian.jira.plugin.... ] Lukáš Fryč commented on ARQGRA-79: ---------------------------------- Note that interceptors should be propagated from parent to children - e.g. from WebDriver to all WebElements. This can be done optionally - e.g. interceptors implementing Progatable interface will be propagated automatically. > Migrate command interceptors to Selenium 2 > ------------------------------------------ > > Key: ARQGRA-79 > URL: https://issues.jboss.org/browse/ARQGRA-79 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api, core > Reporter: Lukáš Fryč > Priority: Optional > Fix For: 2.0.0.Beta1 > > > There is listener capability in Selenium 2, it could by used in place of interceptors from Ajocado 1. -- 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-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: ------------------------------------ We plan to add browser information to INFO into Drone. However, writing deployment url is something container related (Drone does not have to use deployment at all) and thus be a part of Arquillian container implementation. > 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-Tracking > > > 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2013