October 2015 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1992) ServletTestRunner is leaking memmory

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1992?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1992: ------------------------------------ Aa, nice catch. I guess a local reference would do just as well. > ServletTestRunner is leaking memmory > ------------------------------------ > > Key: ARQ-1992 > URL: https://issues.jboss.org/browse/ARQ-1992 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.9.Final > Environment: Using arquillian with servlet protocol > Reporter: Tomaz Cerar > Priority: Critical > > ServletTestRunner saves ThreadLocal reference to ServletContex in its init() method, > and clears it in destroy(). > Problem is that thread that calls init and thread that call destroy() are not guaranteed to be the same thread. > In wildfly/undertow undeploy/server shotdown is executed in different thread than he one that was used to call servlet init first. > reproducer and some evaluation on the bug can be found at https://github.com/wildfly/wildfly/issues/8263 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1992) ServletTestRunner is leaking memmory

by Andreas Weise (JIRA)

[ https://issues.jboss.org/browse/ARQ-1992?page=com.atlassian.jira.plugin.s... ] Andreas Weise commented on ARQ-1992: ------------------------------------ Direct linnk to reproducer is https://github.com/catandgrep/wildfly-undertow-mem-leak > ServletTestRunner is leaking memmory > ------------------------------------ > > Key: ARQ-1992 > URL: https://issues.jboss.org/browse/ARQ-1992 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.9.Final > Environment: Using arquillian with servlet protocol > Reporter: Tomaz Cerar > Priority: Critical > > ServletTestRunner saves ThreadLocal reference to ServletContex in its init() method, > and clears it in destroy(). > Problem is that thread that calls init and thread that call destroy() are not guaranteed to be the same thread. > In wildfly/undertow undeploy/server shotdown is executed in different thread than he one that was used to call servlet init first. > reproducer and some evaluation on the bug can be found at https://github.com/wildfly/wildfly/issues/8263 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-326) Support for full initialization of outer class instance of a page fragment declared as inner class

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-326?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-326: ------------------------------ Fix Version/s: 2.1-Tracking (was: 2.0-Tracking) > Support for full initialization of outer class instance of a page fragment declared as inner class > -------------------------------------------------------------------------------------------------- > > Key: ARQGRA-326 > URL: https://issues.jboss.org/browse/ARQGRA-326 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha4 > Reporter: Juraj Húska > Priority: Minor > Fix For: 2.1-Tracking > > > If a Page Fragment is declared as inner class, then it can not access the fields of its outer class, as their are not inicialized by Graphene Enrichers, thus are {{null}}. > The possible ugly workaround for such initialization can be: > {code} > if (pageFragment.getClass().getEnclosingClass() != null) { > Field field = pageFragment.getClass().getDeclaredField("this$0"); > field.setAccessible(true); > Object outer = field.get(pageFragment); > enrichRecursively(root, outer); > } > {code} > It should be placed in some utility class, so it can be easily unit tested. > There is one drawback of this method and that is, the outer class can not contain injection point for the inner class, otherwise it will cycle. The inner class can be obtained only dynamically via {{Graphene.createPageFragment}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-471) GrapheneContextualHandler: do not wrap AssertionErrors in IllegalStateException

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-471?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-471: ------------------------------ Fix Version/s: 2.1-Tracking > GrapheneContextualHandler: do not wrap AssertionErrors in IllegalStateException > ------------------------------------------------------------------------------- > > Key: ARQGRA-471 > URL: https://issues.jboss.org/browse/ARQGRA-471 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.1.0.Alpha2 > Reporter: Jiří Štefek > Priority: Trivial > Fix For: 2.1-Tracking > > > When you perform an assertion in e.g. a page fragment, which leads to throwing an AssertionError, the error is wrapped in IllegalStateException. This is imho an unwanted behaviour and these errors should be forwarded. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-471) GrapheneContextualHandler: do not wrap AssertionErrors in IllegalStateException

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-471?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-471: ----------------------------------- [~jstefek] do you have any concrete sample? > GrapheneContextualHandler: do not wrap AssertionErrors in IllegalStateException > ------------------------------------------------------------------------------- > > Key: ARQGRA-471 > URL: https://issues.jboss.org/browse/ARQGRA-471 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.1.0.Alpha2 > Reporter: Jiří Štefek > Priority: Trivial > Fix For: 2.1-Tracking > > > When you perform an assertion in e.g. a page fragment, which leads to throwing an AssertionError, the error is wrapped in IllegalStateException. This is imho an unwanted behaviour and these errors should be forwarded. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-472) TestCases are copy-pasted

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-472?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-472: ------------------------------ Fix Version/s: 2.1-Tracking > TestCases are copy-pasted > ------------------------- > > Key: ARQGRA-472 > URL: https://issues.jboss.org/browse/ARQGRA-472 > Project: Arquillian Graphene > Issue Type: Bug > Components: unit-test > Affects Versions: 2.1-Tracking > Reporter: Vitalii Grygoryuk > Fix For: 2.1-Tracking > > > TestHandlingOfStaleElements.testDeletion() and TestHandlingOfStaleElements.testReplacement() are both testing deletion, so there is no test case for node replacement logic: > {code} > @Test > public void testDeletion() { > rootElement.isDisplayed(); > executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement); > try { > rootElement.isDisplayed(); > fail("rootElement should not be found"); > } catch (NoSuchElementException e) { > } > } > @Test > public void testReplacement() { > rootElement.isDisplayed(); > executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement); > try { > rootElement.isDisplayed(); > fail("rootElement should not be found"); > } catch (NoSuchElementException e) { > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-474) Remove arquillian-graphene depchain as no one uses it

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-474?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-474: ------------------------------ Status: Open (was: Pull Request Sent) This is confusing, the issue says there is a PR sent but I can't see any. We still need to remove it. > Remove arquillian-graphene depchain as no one uses it > ----------------------------------------------------- > > Key: ARQGRA-474 > URL: https://issues.jboss.org/browse/ARQGRA-474 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Fix For: 2.1-Tracking > > > Docs and tutorials mention graphene-webdriver depchain: > https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > http://arquillian.org/guides/functional_testing_using_graphene/ > The depchains are not used by EAP BOMs too: > https://issues.jboss.org/browse/JDF-840 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-474) Remove arquillian-graphene depchain as no one uses it

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-474?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-474: ------------------------------ Summary: Remove arquillian-graphene depchain as no one uses it (was: Remove arquillian-graphene as no one uses it) > Remove arquillian-graphene depchain as no one uses it > ----------------------------------------------------- > > Key: ARQGRA-474 > URL: https://issues.jboss.org/browse/ARQGRA-474 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Fix For: 2.1-Tracking > > > Docs and tutorials mention graphene-webdriver depchain: > https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options > http://arquillian.org/guides/functional_testing_using_graphene/ > The depchains are not used by EAP BOMs too: > https://issues.jboss.org/browse/JDF-840 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-476) Extend root element from GrapheneElement

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-476?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-476: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Extend root element from GrapheneElement > ----------------------------------------- > > Key: ARQGRA-476 > URL: https://issues.jboss.org/browse/ARQGRA-476 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Michael Kotten > Assignee: Michael Kotten > Priority: Minor > Fix For: 2.1-Tracking > > > Currently the root element in page fragments must extend WebElement. I would like to extend this, so it can also extend GrapheneElement. I'm preparing a pull request for this currently. Would be nice if this enhancement would make it to the next release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-475) Support inheritance for page fragments delegating to WebElement

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-475?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-475: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Support inheritance for page fragments delegating to WebElement > --------------------------------------------------------------- > > Key: ARQGRA-475 > URL: https://issues.jboss.org/browse/ARQGRA-475 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Michael Kotten > Assignee: Michael Kotten > Priority: Minor > > When implementing page fragments that extend WebElement as described in https://docs.jboss.org/author/display/ARQGRA2/Delegate+to+WebElement it is not possible to use superclasses for this construct. > This is because the method {{isAboutToDelegateToWebElement}} in {{PageFragmentEnricher}} just searches the current class, but not the superclasses. > I'm preparing a minor change for this currently. Hope to send the pull request soon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2015